RE: [Flow] Serious problem with cocoon.getComponent(id)
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:[EMAIL PROTECTED]
Sent: Monday, June 30, 2003 12:57 PM
To: [EMAIL PROTECTED]
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: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED]
> Sent: Monday, June 30, 2003 9:11 PM
> To: [EMAIL PROTECTED]
> Subject: cvs commit:
> cocoon-2.1/src/scratchpad/src/org/apache/cocoon/components/flo
> w/javascript/fom FOM_Cocoon.java
>
>
> reinhard2003/06/30 12:11:10
>
> Modified:
> src/scratchpad/src/org/apache/cocoon/components/flow/javascript/fom
> FOM_Cocoon.java
> +public Object jsFunction_getComponent( String id ) {
> +Object o = null;
> +try {
> + o = this.componentManager.lookup( id );
> + } catch (ComponentException e) {
> + o = null;
> + }
> +return o;
> +}
RE: [Flow] Serious problem with cocoon.getComponent(id)
> From: Christopher Oliver [mailto:[EMAIL PROTECTED]
>
>
> You need to describe how to recreate the problem in more
> detail
ok, here some more details:
As you can see I implemented cocoon.getComponent(id). If I call
this method from the flow and do a lot of refreshes at once
(pushing the F5 key at IE) this error occurs.
If I include a debug statement writing the ComponentManager to
System.out I sometimes get null and not the manager.
IIRC last week a problem with the petstore examples and the
database connections was reported altough the "old" implementation
exposed the ComponentManager itself.
If you need more information please let me know!
Reinhard
> 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:[EMAIL PROTECTED]
> Sent: Monday, June 30, 2003 12:57 PM
> To: [EMAIL PROTECTED]
> 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: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED]
> > Sent: Monday, June 30, 2003 9:11 PM
> > To: [EMAIL PROTECTED]
> > Subject: cvs commit:
> > cocoon-2.1/src/scratchpad/src/org/apache/cocoon/components/flo
> > w/javascript/fom FOM_Cocoon.java
> >
> >
> > reinhard2003/06/30 12:11:10
> >
> > Modified:
> > src/scratchpad/src/org/apache/cocoon/components/flow/javascript/fom
> > FOM_Cocoon.java
>
>
>
> > +public Object jsFunction_getComponent( String id ) {
> > +Object o = null;
> > +try {
> > + o = this.componentManager.lookup( id );
> > + } catch (ComponentException e) {
> > + o = null;
> > + }
> > +return o;
> > +}
>
Re: [Flow] Serious problem with cocoon.getComponent(id)
I can't reproduce this. Are you sure you don't have an old version of rhino
in your classpath? I fixed a problem with setting up dynamic scopes
recently.
Regards,
Chris
Reinhard Pötz wrote:
From: Christopher Oliver [mailto:[EMAIL PROTECTED]
You need to describe how to recreate the problem in more
detail
ok, here some more details:
As you can see I implemented cocoon.getComponent(id). If I call
this method from the flow and do a lot of refreshes at once
(pushing the F5 key at IE) this error occurs.
If I include a debug statement writing the ComponentManager to
System.out I sometimes get null and not the manager.
IIRC last week a problem with the petstore examples and the
database connections was reported altough the "old" implementation
exposed the ComponentManager itself.
If you need more information please let me know!
Reinhard
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:[EMAIL PROTECTED]
Sent: Monday, June 30, 2003 12:57 PM
To: [EMAIL PROTECTED]
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: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED]
Sent: Monday, June 30, 2003 9:11 PM
To: [EMAIL PROTECTED]
Subject: cvs commit:
cocoon-2.1/src/scratchpad/src/org/apache/cocoon/components/flo
w/javascript/fom FOM_Cocoon.java
reinhard2003/06/30 12:11:10
Modified:
src/scratchpad/src/org/apache/cocoon/components/flow/javascript/fom
FOM_Cocoon.java
+public Object jsFunction_getComponent( String id ) {
+Object o = null;
+try {
+ o = this.componentManager.lookup( id );
+ } catch (ComponentException e) {
+ o = null;
+ }
+return o;
+}
Re: [Flow] Serious problem with cocoon.getComponent(id)
> I can't reproduce this. Are you sure you don't have an old version of rhino > in your classpath? I fixed a problem with setting up dynamic scopes > recently. were your changes before 2.1M2 ? I had the same problems, see http://marc.theaimsgroup.com/?l=xml-cocoon-dev&m=105540495810202&w=2 for details. After applying the suggested change, the problems never occured again. For me, the new Database.js doesn't really change something, but nevertheless - the null componentmanager problem never raised again. Maybe the suggested change in database.js gives you a idea where to look for ? Frank
