Yeah it seems both solutions are pretty much equivalent in the end. Thanks guys, this is good stuff for me to get going on. I guess still being new to this I will start with copying and deleting.
Andrew Sykes wrote: > Kurt, Chris, > > Just to clarify, I was not suggesting you maintain an entire copy of > ecommerce. My suggestion was to delete everything you didn't need and > simply reference from the original ecommerce. > > More advanced users generally approach this the other way around, i.e. > build an application and see what they can use from the codebase as they > go, but if this is your first time, you might find it easier to start by > making a copy and deleting things you aren't going to change. At least > that way you start with a working application, which for a newbie is > normally fairly important as you don't want to begin with a whole lot of > exotic unfamiliar errors! > > Andrew > > > On Thu, 2006-10-05 at 05:54 -0700, Chris Howe wrote: > >> Instead of copying the ecommerce app, you may prefer >> this approach >> http://ofbizwiki.go-integral.com/Wiki.jsp?page=FAQ21 >> >> The advantage of this approach is that it's likely you >> only need to maintain the pieces that you modify. >> With the approach that Andrew suggested, if you copy >> all of the ecommerce files and change them to >> newecommerce then you must maintain all of >> newecommerce and will not benefit from any advancement >> in the ofbiz community's ecommerce without starting >> over in your application. >> >> --- Kurt T Stam <[EMAIL PROTECTED]> wrote: >> >> >>> Andrew this is exactly what I need, and your >>> comments exactly addresses >>> other concerns I had while I was doing what I was >>> doing. Thanks so much! >>> >>> --Kurt >>> >>> Andrew Sykes wrote: >>> >>>> Kurt, >>>> >>>> I'd warn against modifying the ofbiz-component.xml >>>> >>> inside ecommerce. >>> >>>> This is both unnecessary and means you're mixing >>>> >>> your code and OFBiz >>> >>>> code which will lead to difficulties if you need >>>> >>> to do an upgrade. >>> >>>> There is a directory specifically for bespoke >>>> >>> applications called "hot- >>> >>>> deploy". You can use the ecommerce application as >>>> >>> a starting point for >>> >>>> your new app. Simply copy the ecommerce app into >>>> >>> hot-deploy change the >>> >>>> mount point, application name etc and you will >>>> >>> have a second >>> >>>> application. >>>> >>>> You'll notice that the controller.xml for this new >>>> >>> app refers to >>> >>>> artifacts in the original ecommerce app, for >>>> >>> example... >>> >>>> <view-map name="ViewRequest" type="screen" >>>> >>>> >> page="component://ecommerce/widget/RequestScreens.xml#ViewRequest"/> >> >>>> Note "component://ecommerce". You can therefore >>>> >>> remove everything from >>> >>>> the new ecommerce directories that are simply >>>> >>> duplicates of the original >>> >>>> ecommerce code. This means that you now will only >>>> >>> have copies of >>> >>>> original ecommerce code where you have had to make >>>> >>> specific changes, >>> >>>> let's say the new app was called "newecommerce", >>>> >>> you would reference >>> >>>> like this... >>>> "component://newecommerce/....." >>>> >>>> Once you have your app setup, you can decide >>>> >>> whether you need to simply >>> >>>> mount each app to a different place >>>> e.g. /newecommerce1 /newecommerce2 /newecommerce3 >>>> >>> etc, which would be >>> >>>> fine if you were using OFBiz in conjunction with >>>> >>> Apache, or if it's >>> >>>> standalone, you might want to use the virtualhost >>>> >>> stuff. >>> >>>> I hope that helps clarify. >>>> >>>> >>>
