cocoon-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Christopher Oliver" <coli...@SeeBeyond.com>
Subject RE: [Flow] Serious problem with cocoon.getComponent(id)
Date Mon, 30 Jun 2003 20:18:06 GMT
You need to describe how to recreate the problem in more detail for me to help you. The component
manager will only become null when the FOM_Cocoon object is invalidated. Your scripts should
not be executing in this state. If they are that that indicates a bug and we need to find
it.


Regards,

Chris

-----Original Message-----
From: Reinhard Pötz [mailto:reinhard_poetz@gmx.net] 
Sent: Monday, June 30, 2003 12:57 PM
To: cocoon-dev@xml.apache.org
Subject: [Flow] Serious problem with cocoon.getComponent(id)
Importance: High

I think we have I serious problem with the lookup of components
within flow scripts.
Under load the component manager can become null!!!

Could somebody with more knowledge about this part of Cocoon have
a look at it?

TIA!

Cheers,
Reinhard

> -----Original Message-----
> From: reinhard@apache.org [mailto:reinhard@apache.org] 
> Sent: Monday, June 30, 2003 9:11 PM
> To: cocoon-2.1-cvs@apache.org
> Subject: cvs commit: 
> cocoon-2.1/src/scratchpad/src/org/apache/cocoon/components/flo
> w/javascript/fom FOM_Cocoon.java
> 
> 
> reinhard    2003/06/30 12:11:10
> 
>   Modified:    
> src/scratchpad/src/org/apache/cocoon/components/flow/javascript/fom
>                         FOM_Cocoon.java

<snip/>

>   +    public Object jsFunction_getComponent( String id ) { 
>   +        Object o = null;
>   +        try {
>   +		  o = this.componentManager.lookup( id );
>   +		} catch (ComponentException e) {
>   +          o = null; 
>   +		}
>   +        return o;
>   +    }


Mime
View raw message