Hello, 

I' have the matcher for the scripts, but the link to the js is missing in the 
source of the generated html.

Regards

Mike


---------- Original Message ----------------------------------
From: "Ard Schrijvers" <[EMAIL PROTECTED]>
Reply-To: [email protected]
Date:  Fri, 24 Nov 2006 12:24:00 +0100

>Look in the source code of the html. Do you see the script elements there for 
>mattkruse libs? 
><script src="/someURL" type="text/javascript">
>
>Try the /someURL directly in the browser url, perhaps you forget the matchers 
>in cocoon for getting the .js files?
>
>Regards Ard
>
>
>> Hello, 
>> 
>> I'm making a new webapp with cocoon 2.1.9. I've copied the 
>> stylesheets and the mattkruse-lib directy into my file 
>> strukture, because later, I'll have to make some modifications.
>> The stylesheets in a stylesheets folder and the js in a 
>> scripts folder. Sure I had to modify some pathes in the files.
>> 
>> Now, when I open a page with a callendar field, I see the 
>> Icon to open the js-callendar, but if I click, it doesn't open.
>> The reason is, that imports for the scripts aren't generated 
>> into my page source. This should happen with the 
>> forms-advanced-field-styling.xsl transformation.
>> 
>> First I thought that perhabs some path to the file isn't set 
>> correcty and cocoon doesen't find it, but if I rename the 
>> file, I receive the error that it could not be found.
>> 
>> The pipeline I use is: 
>> 
>>                 <map:match pattern="*.form">
>>                     <map:aggregate element="document">
>>                         <map:part src="cocoon:/info/{1}"/>
>>                         <map:part src="cocoon:/header/{1}"/>
>>                         <map:part src="cocoon:/menu/{1}"/>
>>                         <map:part src="cocoon:/form/{1}"/>
>>                     </map:aggregate>
>> 
>>                     <map:transform type="xalan" 
>> src="stylesheets/layout.xsl"/>
>>                     <map:transform type="forms"/>
>>                     <map:transform type="jx"/>
>>                     <map:transform type="i18n">
>>                         <map:parameter name="locale" 
>> value="{../locale}"/>
>>                     </map:transform>
>>                     <map:transform type="xalan" 
>> src="stylesheets/forms-styling.xsl"/>
>>                     <map:serialize type="html"/>
>>                 </map:match>
>> 
>>                 <map:match pattern="info/*">
>>                     <map:generate type="serverpages" 
>> src="pages/info/info.xsp">
>>                         <map:parameter name="context" value="{1}"/>
>>                     </map:generate>
>>                     <map:serialize type="xml"/>
>>                 </map:match>
>> 
>>                 <map:match pattern="header/*">
>>                     <map:generate type="serverpages" 
>> src="pages/menus/hmenu.xsp">
>>                         <map:parameter name="context" value="{1}"/>
>>                     </map:generate>
>>                     <map:serialize type="xml"/>
>>                 </map:match>
>> 
>>                 <map:match pattern="menu/*">
>>                     <map:generate type="serverpages" 
>> src="pages/menus/vmenu.xsp">
>>                         <map:parameter name="context" value="{1}"/>
>>                     </map:generate>
>>                     <map:serialize type="xml"/>
>>                 </map:match>
>> 
>>                 <map:match pattern="formcontent/**">
>>                     <map:generate type="file" src="pages/{1}.xml"/>
>>                     <map:serialize type="xml"/>
>>                 </map:match>
>> 
>>                 <map:match pattern="form/*">
>>                     <map:generate src="pages/{1}.xml"/>
>>                     <map:serialize type="xml"/>
>>                 </map:match>
>> 
>> I've used the same principle with an older project (2.1.6) 
>> and didn't have this problem.
>> 
>> Do you have any idea?
>> 
>> Thanks
>> 
>> Mike 
>> 
>> 
>> ____________________________________________
>> QuickLine WebMail - http://www.QuickLine.com
>> 
>> ---------------------------------------------------------------------
>> To unsubscribe, e-mail: [EMAIL PROTECTED]
>> For additional commands, e-mail: [EMAIL PROTECTED]
>> 
>> 
>
>---------------------------------------------------------------------
>To unsubscribe, e-mail: [EMAIL PROTECTED]
>For additional commands, e-mail: [EMAIL PROTECTED]
>
>
 


____________________________________________
QuickLine WebMail - http://www.QuickLine.com

---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]

Reply via email to