ofbiz development and deployment strategy !

Previous Topic Next Topic
 
classic Classic list List threaded Threaded
7 messages Options
Reply | Threaded
Open this post in threaded view
|

ofbiz development and deployment strategy !

prashant punekar
Hi All,

Here is the requirement :

Using ofbiz, we want to develop different applications, services which caters to independent requirements. They can be deployed independently as well as on single ofbiz instance. Need some guidance on the development methodology for this setup.

Basically we do not want to change the ofbiz core src code but just utilize the built in services, entities etc. This will allow us to upgrade to latest ofbiz version at any given time.

Here are some thoughts on the deployment strategy:

Proposed Solution 1 :

-          Create separate web app in specialpurpose folder.
ofbiz/specialpurpose/app1
ofbiz/specialpurpose/app2
ofbiz/specialpurpose/app3

With this we will have:

-          One source code to handle. Version controlling will be easy.

-          During deployment we can tell ofbiz which applications(order, party etc) to be deployed for each specialpurpose app (minisite, user_mgmt etc.)

Proposed Solution 2:

-          Create a separate project, independent of ofbiz and use ofbiz jars(base src code) to develop the new application/project.


With this we will have:

-          Different customized source codes using ofbiz base src code.

-          Deployment will need each application being deployed with the original ofbiz base src code.

Please comment .. Any ideas/thoughts are welcome.

Thanks In Advance !

Regards,
Prashant

________________________________
http://www.mindtree.com/email/disclaimer.html
Reply | Threaded
Open this post in threaded view
|

Re: ofbiz development and deployment strategy !

BJ Freeman
I have switched to use the ./ant create-component in 10.4 and trunk
you can make one that is named the same as one of the  component and
override it or
you can create your own component and add your functionality.
the second will show up as a tab.


=========================
BJ Freeman
http://bjfreeman.elance.com
Strategic Power Office with Supplier Automation  <http://www.businessesnetwork.com/automation/viewforum.php?f=52>
Specialtymarket.com  <http://www.specialtymarket.com/>

Systems Integrator-- Glad to Assist

Chat  Y! messenger: bjfr33man
Linkedin
<http://www.linkedin.com/profile?viewProfile=&key=1237480&locale=en_US&trk=tab_pro>


Prashant Punekar sent the following on 6/21/2010 6:19 PM:

> Hi All,
>
> Here is the requirement :
>
> Using ofbiz, we want to develop different applications, services which caters to independent requirements. They can be deployed independently as well as on single ofbiz instance. Need some guidance on the development methodology for this setup.
>
> Basically we do not want to change the ofbiz core src code but just utilize the built in services, entities etc. This will allow us to upgrade to latest ofbiz version at any given time.
>
> Here are some thoughts on the deployment strategy:
>
> Proposed Solution 1 :
>
> -          Create separate web app in specialpurpose folder.
> ofbiz/specialpurpose/app1
> ofbiz/specialpurpose/app2
> ofbiz/specialpurpose/app3
>
> With this we will have:
>
> -          One source code to handle. Version controlling will be easy.
>
> -          During deployment we can tell ofbiz which applications(order, party etc) to be deployed for each specialpurpose app (minisite, user_mgmt etc.)
>
> Proposed Solution 2:
>
> -          Create a separate project, independent of ofbiz and use ofbiz jars(base src code) to develop the new application/project.
>
>
> With this we will have:
>
> -          Different customized source codes using ofbiz base src code.
>
> -          Deployment will need each application being deployed with the original ofbiz base src code.
>
> Please comment .. Any ideas/thoughts are welcome.
>
> Thanks In Advance !
>
> Regards,
> Prashant
>
> ________________________________
> http://www.mindtree.com/email/disclaimer.html
>

Reply | Threaded
Open this post in threaded view
|

Re: ofbiz development and deployment strategy !

Bilgin Ibryam-2
In reply to this post by prashant punekar
The common practice of using Ofbiz is "solution 1"

Bilgin


On Tue, Jun 22, 2010 at 2:19 AM, Prashant Punekar <
[hidden email]> wrote:

> Hi All,
>
> Here is the requirement :
>
> Using ofbiz, we want to develop different applications, services which
> caters to independent requirements. They can be deployed independently as
> well as on single ofbiz instance. Need some guidance on the development
> methodology for this setup.
>
> Basically we do not want to change the ofbiz core src code but just utilize
> the built in services, entities etc. This will allow us to upgrade to latest
> ofbiz version at any given time.
>
> Here are some thoughts on the deployment strategy:
>
> Proposed Solution 1 :
>
> -          Create separate web app in specialpurpose folder.
> ofbiz/specialpurpose/app1
> ofbiz/specialpurpose/app2
> ofbiz/specialpurpose/app3
>
> With this we will have:
>
> -          One source code to handle. Version controlling will be easy.
>
> -          During deployment we can tell ofbiz which applications(order,
> party etc) to be deployed for each specialpurpose app (minisite, user_mgmt
> etc.)
>
> Proposed Solution 2:
>
> -          Create a separate project, independent of ofbiz and use ofbiz
> jars(base src code) to develop the new application/project.
>
>
> With this we will have:
>
> -          Different customized source codes using ofbiz base src code.
>
> -          Deployment will need each application being deployed with the
> original ofbiz base src code.
>
> Please comment .. Any ideas/thoughts are welcome.
>
> Thanks In Advance !
>
> Regards,
> Prashant
>
> ________________________________
> http://www.mindtree.com/email/disclaimer.html
>
Reply | Threaded
Open this post in threaded view
|

Re: ofbiz development and deployment strategy !

jonatan soto
Check
https://cwiki.apache.org/confluence/display/OFBIZ/SVN+Tips+-+svn_load_dirs+Vendor+Branchit
might be of interest too.

I've had to take the same decision recently and I found this way the more
practical and easy. You can merge from vendor branch to custom branch easily
using svn tools.



On Tue, Jun 22, 2010 at 10:28 AM, Bilgin Ibryam <[hidden email]> wrote:

> The common practice of using Ofbiz is "solution 1"
>
> Bilgin
>
>
> On Tue, Jun 22, 2010 at 2:19 AM, Prashant Punekar <
> [hidden email]> wrote:
>
> > Hi All,
> >
> > Here is the requirement :
> >
> > Using ofbiz, we want to develop different applications, services which
> > caters to independent requirements. They can be deployed independently as
> > well as on single ofbiz instance. Need some guidance on the development
> > methodology for this setup.
> >
> > Basically we do not want to change the ofbiz core src code but just
> utilize
> > the built in services, entities etc. This will allow us to upgrade to
> latest
> > ofbiz version at any given time.
> >
> > Here are some thoughts on the deployment strategy:
> >
> > Proposed Solution 1 :
> >
> > -          Create separate web app in specialpurpose folder.
> > ofbiz/specialpurpose/app1
> > ofbiz/specialpurpose/app2
> > ofbiz/specialpurpose/app3
> >
> > With this we will have:
> >
> > -          One source code to handle. Version controlling will be easy.
> >
> > -          During deployment we can tell ofbiz which applications(order,
> > party etc) to be deployed for each specialpurpose app (minisite,
> user_mgmt
> > etc.)
> >
> > Proposed Solution 2:
> >
> > -          Create a separate project, independent of ofbiz and use ofbiz
> > jars(base src code) to develop the new application/project.
> >
> >
> > With this we will have:
> >
> > -          Different customized source codes using ofbiz base src code.
> >
> > -          Deployment will need each application being deployed with the
> > original ofbiz base src code.
> >
> > Please comment .. Any ideas/thoughts are welcome.
> >
> > Thanks In Advance !
> >
> > Regards,
> > Prashant
> >
> > ________________________________
> > http://www.mindtree.com/email/disclaimer.html
> >
>



--
-----

Jonatan Soto
Reply | Threaded
Open this post in threaded view
|

Re: ofbiz development and deployment strategy !

jonatan soto
In fact, my suggestion is probably an enhancement of option 2...

On Tue, Jun 22, 2010 at 10:43 AM, Jonatan Soto <[hidden email]>wrote:

> Check
> https://cwiki.apache.org/confluence/display/OFBIZ/SVN+Tips+-+svn_load_dirs+Vendor+Branchit might be of interest too.
>
> I've had to take the same decision recently and I found this way the more
> practical and easy. You can merge from vendor branch to custom branch easily
> using svn tools.
>
>
>
>
> On Tue, Jun 22, 2010 at 10:28 AM, Bilgin Ibryam <[hidden email]> wrote:
>
>> The common practice of using Ofbiz is "solution 1"
>>
>> Bilgin
>>
>>
>> On Tue, Jun 22, 2010 at 2:19 AM, Prashant Punekar <
>> [hidden email]> wrote:
>>
>> > Hi All,
>> >
>> > Here is the requirement :
>> >
>> > Using ofbiz, we want to develop different applications, services which
>> > caters to independent requirements. They can be deployed independently
>> as
>> > well as on single ofbiz instance. Need some guidance on the development
>> > methodology for this setup.
>> >
>> > Basically we do not want to change the ofbiz core src code but just
>> utilize
>> > the built in services, entities etc. This will allow us to upgrade to
>> latest
>> > ofbiz version at any given time.
>> >
>> > Here are some thoughts on the deployment strategy:
>> >
>> > Proposed Solution 1 :
>> >
>> > -          Create separate web app in specialpurpose folder.
>> > ofbiz/specialpurpose/app1
>> > ofbiz/specialpurpose/app2
>> > ofbiz/specialpurpose/app3
>> >
>> > With this we will have:
>> >
>> > -          One source code to handle. Version controlling will be easy.
>> >
>> > -          During deployment we can tell ofbiz which applications(order,
>> > party etc) to be deployed for each specialpurpose app (minisite,
>> user_mgmt
>> > etc.)
>> >
>> > Proposed Solution 2:
>> >
>> > -          Create a separate project, independent of ofbiz and use ofbiz
>> > jars(base src code) to develop the new application/project.
>> >
>> >
>> > With this we will have:
>> >
>> > -          Different customized source codes using ofbiz base src code.
>> >
>> > -          Deployment will need each application being deployed with the
>> > original ofbiz base src code.
>> >
>> > Please comment .. Any ideas/thoughts are welcome.
>> >
>> > Thanks In Advance !
>> >
>> > Regards,
>> > Prashant
>> >
>> > ________________________________
>> > http://www.mindtree.com/email/disclaimer.html
>> >
>>
>
>
>
> --
> -----
>
> Jonatan Soto
>



--
-----

Jonatan Soto
Reply | Threaded
Open this post in threaded view
|

Re: ofbiz development and deployment strategy !

MICHAEL BUTLER
You mightwant to use https://cwiki.apache.org/confluence/display/OFBIZ/SVN+Tips+-+MS+Vendor+Branch

The URL below does not work

MikeyB





________________________________
From: Jonatan Soto <[hidden email]>
To: [hidden email]
Sent: Tuesday, 22 June, 2010 10:45:16
Subject: Re: ofbiz development and deployment strategy !

In fact, my suggestion is probably an enhancement of option 2...

On Tue, Jun 22, 2010 at 10:43 AM, Jonatan Soto <[hidden email]>wrote:

> Check
> https://cwiki.apache.org/confluence/display/OFBIZ/SVN+Tips+-+svn_load_dirs+Vendor+Branchit might be of interest too.
>
> I've had to take the same decision recently and I found this way the more
> practical and easy. You can merge from vendor branch to custom branch easily
> using svn tools.
>
>
>
>
> On Tue, Jun 22, 2010 at 10:28 AM, Bilgin Ibryam <[hidden email]> wrote:
>
>> The common practice of using Ofbiz is "solution 1"
>>
>> Bilgin
>>
>>
>> On Tue, Jun 22, 2010 at 2:19 AM, Prashant Punekar <
>> [hidden email]> wrote:
>>
>> > Hi All,
>> >
>> > Here is the requirement :
>> >
>> > Using ofbiz, we want to develop different applications, services which
>> > caters to independent requirements. They can be deployed independently
>> as
>> > well as on single ofbiz instance. Need some guidance on the development
>> > methodology for this setup.
>> >
>> > Basically we do not want to change the ofbiz core src code but just
>> utilize
>> > the built in services, entities etc. This will allow us to upgrade to
>> latest
>> > ofbiz version at any given time.
>> >
>> > Here are some thoughts on the deployment strategy:
>> >
>> > Proposed Solution 1 :
>> >
>> > -          Create separate web app in specialpurpose folder.
>> > ofbiz/specialpurpose/app1
>> > ofbiz/specialpurpose/app2
>> > ofbiz/specialpurpose/app3
>> >
>> > With this we will have:
>> >
>> > -          One source code to handle. Version controlling will be easy.
>> >
>> > -          During deployment we can tell ofbiz which applications(order,
>> > party etc) to be deployed for each specialpurpose app (minisite,
>> user_mgmt
>> > etc.)
>> >
>> > Proposed Solution 2:
>> >
>> > -          Create a separate project, independent of ofbiz and use ofbiz
>> > jars(base src code) to develop the new application/project.
>> >
>> >
>> > With this we will have:
>> >
>> > -          Different customized source codes using ofbiz base src code.
>> >
>> > -          Deployment will need each application being deployed with the
>> > original ofbiz base src code.
>> >
>> > Please comment .. Any ideas/thoughts are welcome.
>> >
>> > Thanks In Advance !
>> >
>> > Regards,
>> > Prashant
>> >
>> > ________________________________
>> > http://www.mindtree.com/email/disclaimer.html
>> >
>>
>
>
>
> --
> -----
>
> Jonatan Soto
>



--
-----

Jonatan Soto



Reply | Threaded
Open this post in threaded view
|

Re: ofbiz development and deployment strategy !

BJ Freeman
might check if the complete URL got put in browser or if there is a
firewall problem.
it works for me.

MICHAEL BUTLER sent the following on 6/22/2010 2:07 AM:


=========================
BJ Freeman
http://bjfreeman.elance.com
Strategic Power Office with Supplier Automation  <http://www.businessesnetwork.com/automation/viewforum.php?f=52>
Specialtymarket.com  <http://www.specialtymarket.com/>

Systems Integrator-- Glad to Assist

Chat  Y! messenger: bjfr33man
Linkedin
<http://www.linkedin.com/profile?viewProfile=&key=1237480&locale=en_US&trk=tab_pro>

> You mightwant to use https://cwiki.apache.org/confluence/display/OFBIZ/SVN+Tips+-+MS+Vendor+Branch
>
> The URL below does not work
>
> MikeyB
>
>
>
>
>
> ________________________________
> From: Jonatan Soto<[hidden email]>
> To: [hidden email]
> Sent: Tuesday, 22 June, 2010 10:45:16
> Subject: Re: ofbiz development and deployment strategy !
>
> In fact, my suggestion is probably an enhancement of option 2...
>
> On Tue, Jun 22, 2010 at 10:43 AM, Jonatan Soto<[hidden email]>wrote:
>
>> Check
>> https://cwiki.apache.org/confluence/display/OFBIZ/SVN+Tips+-+svn_load_dirs+Vendor+Branchit might be of interest too.
>>
>> I've had to take the same decision recently and I found this way the more
>> practical and easy. You can merge from vendor branch to custom branch easily
>> using svn tools.
>>
>>
>>
>>
>> On Tue, Jun 22, 2010 at 10:28 AM, Bilgin Ibryam<[hidden email]>  wrote:
>>
>>> The common practice of using Ofbiz is "solution 1"
>>>
>>> Bilgin
>>>
>>>
>>> On Tue, Jun 22, 2010 at 2:19 AM, Prashant Punekar<
>>> [hidden email]>  wrote:
>>>
>>>> Hi All,
>>>>
>>>> Here is the requirement :
>>>>
>>>> Using ofbiz, we want to develop different applications, services which
>>>> caters to independent requirements. They can be deployed independently
>>> as
>>>> well as on single ofbiz instance. Need some guidance on the development
>>>> methodology for this setup.
>>>>
>>>> Basically we do not want to change the ofbiz core src code but just
>>> utilize
>>>> the built in services, entities etc. This will allow us to upgrade to
>>> latest
>>>> ofbiz version at any given time.
>>>>
>>>> Here are some thoughts on the deployment strategy:
>>>>
>>>> Proposed Solution 1 :
>>>>
>>>> -          Create separate web app in specialpurpose folder.
>>>> ofbiz/specialpurpose/app1
>>>> ofbiz/specialpurpose/app2
>>>> ofbiz/specialpurpose/app3
>>>>
>>>> With this we will have:
>>>>
>>>> -          One source code to handle. Version controlling will be easy.
>>>>
>>>> -          During deployment we can tell ofbiz which applications(order,
>>>> party etc) to be deployed for each specialpurpose app (minisite,
>>> user_mgmt
>>>> etc.)
>>>>
>>>> Proposed Solution 2:
>>>>
>>>> -          Create a separate project, independent of ofbiz and use ofbiz
>>>> jars(base src code) to develop the new application/project.
>>>>
>>>>
>>>> With this we will have:
>>>>
>>>> -          Different customized source codes using ofbiz base src code.
>>>>
>>>> -          Deployment will need each application being deployed with the
>>>> original ofbiz base src code.
>>>>
>>>> Please comment .. Any ideas/thoughts are welcome.
>>>>
>>>> Thanks In Advance !
>>>>
>>>> Regards,
>>>> Prashant
>>>>
>>>> ________________________________
>>>> http://www.mindtree.com/email/disclaimer.html
>>>>
>>>
>>
>>
>>
>> --
>> -----
>>
>> Jonatan Soto
>>
>
>
>