Stephan Hesmer wrote:
>
> Raphael,
>
> it seems, that there is a bug in the new registry manager in a special case.
> I'm testing Jetspeed on both Websphere and Tomcat. On Tomcat it is working,
> on Websphere not.
>
> I looked for it and discovered that the registries have to be processed /
> intialized as specified in the JR.p:
> services.RegistryManager.registries=PortletRegistry,CapabilityMapRegistry,Me
> diaTypeRegistry
>
> The problem is, that you parse these strings and then put them into the
> hashtable "registries". Later you call the function refreshAll which
> enumerates the elements of the hashtable.
>
> On Tomcat it is still the same order:
> PortletRegistry,CapabilityMapRegistry,MediaTypeRegistry
> BUT
> on Websphere it is not. In my case:
> MediaTypeRegistry,PortletRegistry,CapabilityMapRegistry
>
> The error occurs because MediaTypeRegistry relies on information of
> CapabilityMapRegistry.
>
> My first suggestion was to replace the hashtable with a vector, but perhaps
> you know something better?
> As alternative, we can use "refresh" instead of "refreshAll" in the function
> init (directly after register( name, classname ); )
>
I didn't know the Registry had any dependencies between them. It's bad :(
We should be able to initialize registries in any order. I'll investigate
the registry code to see why there's a dependency.
If the dependency in necessary, the RegistryBroker will need to be extended
to implement an early/late init phase with dependency detection just like
TurbineServices.
--
Rapha�l Luta - [EMAIL PROTECTED]
--
--------------------------------------------------------------
Please read the FAQ! <http://java.apache.org/faq/>
To subscribe: [EMAIL PROTECTED]
To unsubscribe: [EMAIL PROTECTED]
Archives and Other: <http://marc.theaimsgroup.com/?l=jetspeed>
Problems?: [EMAIL PROTECTED]
