Re: R: NoClassDefFoundError: com/opensymphony/workflow/loader/AbstractWorkflowFactory

On Friday, June 27, 2003, at 12:37 PM, Travelli Stefano wrote:

> 2. The configuration design forces to have the osworkflow jars loaded 
> by the last class-loader in the application server class-loader 
> hierarchy. In fact osworkflow holds the config stuff in static 
> variables. What about reworking this in order to have an 
> WorkflowInstanceFactory that loads and holds the configuration in 
> instance variables? The WorkflowInstanceFactory could produce 
> instances of Workflow objects and should be held by the application or 
> placed somewhere, maybe in a JNDI tree where the app could retrieve > it.
> In this "service oriented" way osworkflow jars could be loaded by some 
> ancient class-loader and each application could define its 
> WorkflowFactory, Store configuration and so on. (This would get a 
> simple solution to my NoClassDefFound problem).
>
I absolutely agree. Static variables in any kind of server API are 
incredibly retarded, and make reuse of an API with different 
configurations pretty much impossible. Unfortunately this is probably a 
significant change, and likely won't be in for the 2.5 release.



-------------------------------------------------------
This SF.Net email sponsored by: Free pre-built ASP.NET sites including
Data Reports, E-commerce, Portals, and Forums are available now.
Download today and enter to win an XBOX or Visual Studio .NET.
http://aspnet.click-url.com/go/psa00100006ave/direct;at.asp_061203_01/01