I agree this is the way to go. Certain parts of certain application components 
should have been in the framework from the beginning, but certainly not all of 
them. Splitting out those specific parts and putting them in framework 
components as needed is the way to go.

-David


On Dec 15, 2010, at 11:04 AM, Scott Gray wrote:

> I really think you'd need to split the content component into two, simply 
> moving it to the framework would probably introduce a whole other set of 
> dependencies to deal with.
> 
> Regards
> Scott
> 
> HotWax Media
> http://www.hotwaxmedia.com
> 
> On 16/12/2010, at 7:40 AM, Adrian Crum wrote:
> 
>> To clarify, I'm trying to get the components in the framework folder to run 
>> by themselves - without the components found in the applications folder. 
>> Some of the framework components have UIs.
>> 
>> I understand everyone has a different opinion on what constitutes a 
>> framework, so I don't want to rehash that discussion. I just want to disable 
>> the components in the applications folder and still have OFBiz run.
>> 
>> -Adrian
>> 
>> On 12/15/2010 10:13 AM, BJ Freeman wrote:
>>> first question is should there be any UI activity at the framework level.
>>> Should not it just be the support to allow a UI system to put installed.
>>> when I mean UI I am talking about any interaction to the user.
>>> 
>>> =========================
>>> BJ Freeman
>>> 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
>>> 
>>> 
>>> Adrian Crum sent the following on 12/15/2010 9:52 AM:
>>>> I'm working on a project that requires only the OFBiz framework. I'm
>>>> trying to get a framework-only installation to run.
>>>> 
>>>> There are a lot of dependencies on the party and content components.
>>>> Removing dependencies on the party component should be fairly easy. The
>>>> online help system uses the content component, so that is an issue.
>>>> Should we move the content component to the framework?
>>>> 
>>>> -Adrian
>>>> 
>>> 
>>> 
> 

Reply via email to