Hi Jim, Thanks for your suggestion.
I guess that is similar to my workaround #1 (all Javascript functions in all pages). That works all right, but I'd prefer to have only the Javascript functions I need in that page included. Something like: <script language="javascript" src="functions1.js"/> For page1 And: <script language="javascript" src="functions2.js"/> For page2. (indications on wether to include functions1.js or functions2.js would be included in maverick.xml as a transform) That would be really flexible, but it seems to be impossible to accomplish this with Maverick. Or am I missing something? Cyrille Bonnet Senior Consultant 3months.com Web: www.3months.com Tel: + 64 4 381 2884 Fax: + 64 4 381 2894 Cell: 021 446 048 -----Original Message----- From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED] On Behalf Of jim moore Sent: Thursday, September 02, 2004 9:49 AM To: [EMAIL PROTECTED] Subject: RE: [Mav-user] Multiple conditional ${wrapped}? Why not just put all the javascript functions in a .js file and then just include that in the pages: <script language="javascript" src="functions.js"/> --jim -----Original Message----- From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED] On Behalf Of Cyrille Bonnet Sent: Wednesday, September 01, 2004 10:07 PM To: [EMAIL PROTECTED] Subject: [Mav-user] Multiple conditional ${wrapped}? Hi Maverick users, I have a simple problem. Of course, I'd like a simple solution :-) We use a header JSP across many JSP pages. On some of those JSP pages, we have Javascript functions available (inside the <head> tag), but not on all pages. We use the ${wrapped} and Maverick transformation to replace the <body> content on our pages. But we can't have multiple ${wrapped} in one page, so we can't use Maverick transform to replace the Javascript functions when needed. Ideally, we would have something like that in the header JSP: <head> <c:out value="${wrapped}" escapeXml="false"/> <-- "transform" this to Javascript functions --> </head> <body> <c:out value="${wrapped}" escapeXml="false"/> <-- "transform" that to body content --> </body> At the moment, we have the choice of several (unsatisfying) workarounds: * have all Javascript functions in all pages, * create a custom header for each set of Javascript functions Any pointer would be appreciated. Cyrille. ------------------------------------------------------- This SF.Net email is sponsored by BEA Weblogic Workshop FREE Java Enterprise J2EE developer tools! Get your free copy of BEA WebLogic Workshop 8.1 today. http://ads.osdn.com/?ad_id=5047&alloc_id=10808&op=click [INVALID FOOTER] ------------------------------------------------------- This SF.Net email is sponsored by BEA Weblogic Workshop FREE Java Enterprise J2EE developer tools! Get your free copy of BEA WebLogic Workshop 8.1 today. http://ads.osdn.com/?ad_id=5047&alloc_id=10808&op=click [INVALID FOOTER] ------------------------------------------------------- This SF.Net email is sponsored by BEA Weblogic Workshop FREE Java Enterprise J2EE developer tools! Get your free copy of BEA WebLogic Workshop 8.1 today. http://ads.osdn.com/?ad_id=5047&alloc_id=10808&op=click [INVALID FOOTER]
