What about style sheets? Some scripts work w/ style sheets to set things up. I think
that needs to be in the head, otherwise
you have to programmatically set up the styles. I've seen some scripts which wont
work unless things have been set up in head.
Wayne Christian
Sr. Staff Software Engineer
Genesys Telecommunications Labs
2100 Gateway Centre Blvd. Suite 300
Morrisville, NC 27560
? Office: (919) 466-6151
Fax: (919) 466-6157
? EMail: mailto:[EMAIL PROTECTED]
-----Original Message-----
From: Rutledge, Aaron [mailto:[EMAIL PROTECTED]]
Sent: Wednesday, September 18, 2002 3:17 PM
To: Jetspeed Users List
Subject: RE: Jetspeed portlets and Javascript
I have found very few instances where the script elements need to be in the <HEAD> (in
fact, I don't think it is ever required). It seems to be more often just a convention
that people have used because, obviously, the SCRIPT needs to load before the function
call. I've used many JavaScript functions in my portlets with luck just by ripping
the <SCRIPT> element out of the head and rewriting the portlet without the <HEAD>.
You must be careful, however, to ensure that you do not have redundancy in your script
and variable names.
-----Original Message-----
From: Wayne A Christian [mailto:[EMAIL PROTECTED]]
Sent: Wednesday, September 18, 2002 9:43 AM
To: Jetspeed Users List
Subject: RE: Jetspeed portlets and Javascript
I suspect you have to figure out which "default.xxx" file is being used. If you're
doing JSP, then there will be a default.jsp file.
If using velocity, then there will be a default.vm file. These are somewhere in the
"jetspeed\WEB-INF\templates" directory of
your application server (tomcat).
Wayne Christian
Sr. Staff Software Engineer
Genesys Telecommunications Labs
2100 Gateway Centre Blvd. Suite 300
Morrisville, NC 27560
? Office: (919) 466-6151
Fax: (919) 466-6157
? EMail: mailto:[EMAIL PROTECTED]
-----Original Message-----
From: Sandeep G Nijsure [mailto:[EMAIL PROTECTED]]
Sent: Wednesday, September 18, 2002 11:18 AM
To: Jetspeed Users List
Subject: RE: Jetspeed portlets and Javascript
Hi Wayne,
Thanks!! do you know which jsp/vm file generates the HEAD markup?
Thanks,
Sandeep
On Wed, 18 Sep 2002, Wayne A Christian wrote:
> Unfortunately, IBM's portal server doesn't work as well as its
> advertised. The PageListener interface is suppose to allow you to put
> markup in the Head section of a page but it doesn't work. I suspect you
> would have to do the same thing that I'm doing, namely modifying the jsp
> (or velocity template) which contains the HEAD markup tags. While I
> don't like that solution, since the information is not located with the
> portlet, it does work.
>
> Wayne Christian
> Sr. Staff Software Engineer
> Genesys Telecommunications Labs
> 2100 Gateway Centre Blvd. Suite 300
> Morrisville, NC 27560
> ? Office: (919) 466-6151
> Fax: (919) 466-6157
> ? EMail: mailto:[EMAIL PROTECTED]
>
> -----Original Message-----
> From: Sandeep G Nijsure [mailto:[EMAIL PROTECTED]]
> Sent: Tuesday, September 17, 2002 6:48 PM
> To: [EMAIL PROTECTED]
> Subject: Jetspeed portlets and Javascript
>
> Hi all,
>
> If I want to use Javascript in the rendering of a portlet, how do I go
> about? Ideally, portlet is not supposed to output any page level tags,
> like <html> or <head>, since portlet is just a part of an HTML page, and
> not the entire page. But Javascript needs the functions to be declared in
> <head> section. So how to deal with this?
>
> IBM websphere has a PageListener or something that basically allows you to
> add something to the page level tags, when the page is being created. Is
> there a corresponding mechanism in Jetspeed?
>
> Thanks,
> Sandeep
>
>
> --
> To unsubscribe, e-mail: <mailto:[EMAIL PROTECTED]>
> For additional commands, e-mail: <mailto:[EMAIL PROTECTED]>
>
> --
> To unsubscribe, e-mail: <mailto:[EMAIL PROTECTED]>
> For additional commands, e-mail: <mailto:[EMAIL PROTECTED]>
>
>
--
To unsubscribe, e-mail: <mailto:[EMAIL PROTECTED]>
For additional commands, e-mail: <mailto:[EMAIL PROTECTED]>
--
To unsubscribe, e-mail: <mailto:[EMAIL PROTECTED]>
For additional commands, e-mail: <mailto:[EMAIL PROTECTED]>
--
To unsubscribe, e-mail: <mailto:[EMAIL PROTECTED]>
For additional commands, e-mail: <mailto:[EMAIL PROTECTED]>
--
To unsubscribe, e-mail: <mailto:[EMAIL PROTECTED]>
For additional commands, e-mail: <mailto:[EMAIL PROTECTED]>
