cocoon-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From Reinhard Poetz <>
Subject Service manager can be null in FOM_Cocoon
Date Thu, 21 Oct 2004 08:22:32 GMT

Does anybody have an idea what's going on here? I remember the problem of losing 
the component manager in July/August last year. Could this be the reason why the 
CallContext object was introduced?

Find more infos on this issue at

Any help would be very appreciated!!!


------- Additional Comments From  2004-10-20 18:50 -------
I can reproduce the problem, but it is not caused by this.continuation being
null: this happens with both versions of Rhino. The real problem is clearly
visible from the full stack trace:

Caused by: java.lang.NullPointerException
	at inv114.invoke()
	at org.mozilla.javascript.MemberBox.invoke(

which points to call to

     public ServiceManager getServiceManager() {
         return currentCall.serviceManager;

in src/java/org/apache/cocoon/components/flow/javascript/fom/
with currentCall == null

The reason for currentCall to be null is that somehow
in jsConstructor gets FOM_Cocoon without pushed call. I will try to see reason
for that.

View raw message