Mailing-List: contact dev-help@cocoon.apache.org; run by ezmlm
Precedence: bulk
Reply-To: dev@cocoon.apache.org
Received-SPF: pass (hermes.apache.org: local policy)
Message-ID: <428EFC38.1030909@nada.kth.se>
Date: Sat, 21 May 2005 11:15:36 +0200
From: Daniel Fagerstrom <danielf@nada.kth.se>
User-Agent: Mozilla Thunderbird 1.0 (Windows/20041206)
MIME-Version: 1.0
To: dev@cocoon.apache.org
Subject: Re: JXTemplate initialization in non-flowscript scenarios
References: <428DBE4D.2060004@apache.org> <428DD451.2060006@nada.kth.se>
 <428DD850.6080402@apache.org> <428DDE4F.70502@nada.kth.se>
 <428E19D8.3020802@apache.org>
In-Reply-To: <428E19D8.3020802@apache.org>
Content-Type: text/plain; charset=ISO-8859-1; format=flowed
Content-Transfer-Encoding: 7bit

Reinhard Poetz wrote:
> Daniel Fagerstrom wrote:
> 
>> Ok, but I still need to know the content of the value attribute to the 
>> jx:set that creates the problem to be able to help. From the 
>> stacktrace it seem like something goes wrong when JXPath uses 
>> reflection on the value.
> 
> 
> The debugger showed that it's this line:
>       <jx:set var="cformsHelper" 
> value="#{org.apache.cocoon.forms.generation.JXMacrosHelper.createHelper($cocoon/consumer,$cocoon/request)}"/> 
> 
> 
> Unfortunatly my knowledge in jxtemplate isn't sufficient to see the 
> difference between the two cases (with/witout <map:flow/>).

You are only supposed to have direct access to java.*, IIUC, packages 
from FOM for other packages you must have a "Package." prefix, i.e. 
value="#{Package.org.apache.cocoon.forms.generation.JXMacrosHelper.createHelper($cocoon/consumer,$cocoon/request)}

This is the behaviour that is implemented in 
o.a.c.environment.TemplateObjectModelHelper.addJavaPackages.

In 
org.apache.cocoon.components.flow.javascript.fom.FOM_JavaScriptInterpreter.setupPackages 
the packages javax.*, org.* and com.* where also setup so that you have 
direct access to them in rev 26848. The log says: "Also added 
experimental fix to provide direct access to javax, org, and com 
packages". Don't know if there was any discussions or decisions about this.

Anyway, we have had the functionality for 16 months, so we should 
probably continue to support it.

/Daniel