|
From: B. <jer...@xt...> - 2002-01-29 18:01:10
|
Hi, I have been experiencing problems with ObjectNames containing spaces. The way the XSTL stylesheets are built is a problem because the URL produced are not valid. I have found (and implemented) a "trick" in order to solve that: we can add a method in common.xsl (I called it urlencode) that encodes properly the URL and do a window.location to this newly created url. We replace all href values with urlencode(the old href value) and we're done. Is anyone ok for such a fix? If so I will start updating all the stylesheet and commit. Jerome. |
|
From: Carlos Q. <car...@we...> - 2002-01-29 18:12:34
|
On Tuesday 29 January 2002 20:00, J=E9r=F4me BERNARD wrote: Hi > Hi, > > I have been experiencing problems with ObjectNames containing spaces. > The way the XSTL stylesheets are built is a problem because the URL > produced are not valid. Checking the specs now I discovered that this is indeed legal, never=20 thougt about before. > > I have found (and implemented) a "trick" in order to solve that: we can > add a method in common.xsl (I called it urlencode) that encodes properl= y > the URL and do a window.location to this newly created url. Where exactly do you want to put that? For instance to jump from the serv= er=20 view to the mbean view? It will be perhaps necessary in many places > > We replace all href values with urlencode(the old href value) and we're > done. Is this XSL? Or are you using some extension? > > Is anyone ok for such a fix? > > If so I will start updating all the stylesheet and commit. I think is ok, but could you send me a copy beforehand > > > Jerome. > > > _______________________________________________ > Openjmx-devel mailing list > Ope...@li... > https://lists.sourceforge.net/lists/listinfo/openjmx-devel |
|
From: <jer...@xt...> - 2002-01-29 18:49:43
|
----- Original Message ----- From: "Carlos Quiroz" <car...@we...> To: <ope...@li...> Sent: Tuesday, January 29, 2002 7:09 PM Subject: Re: [Openjmx-devel] Proposed bug fix in the XSLT stylesheets [...] > > I have found (and implemented) a "trick" in order to solve that: we can > > add a method in common.xsl (I called it urlencode) that encodes properly > > the URL and do a window.location to this newly created url. > Where exactly do you want to put that? For instance to jump from the server > view to the mbean view? It will be perhaps necessary in many places Yes, this is where my first problem is but I guess that this must happen somewhere else too. > > We replace all href values with urlencode(the old href value) and we're > > done. > Is this XSL? Or are you using some extension? Nope JavaScript :-) > > Is anyone ok for such a fix? > > > > If so I will start updating all the stylesheet and commit. > I think is ok, but could you send me a copy beforehand I will send you tomorrow the updated common.xsl stylesheet and an update serverbydomain.xsl. Jerome. |
|
From: <jer...@xt...> - 2002-01-29 18:40:33
|
I forgot to precise that the method is implemented in JavaScript (so running on client-side). Jerome. ----- Original Message ----- From: "Jérôme BERNARD" <jer...@xt...> To: <ope...@li...> Sent: Tuesday, January 29, 2002 7:00 PM Subject: [Openjmx-devel] Proposed bug fix in the XSLT stylesheets > Hi, > > I have been experiencing problems with ObjectNames containing spaces. > The way the XSTL stylesheets are built is a problem because the URL > produced are not valid. > > I have found (and implemented) a "trick" in order to solve that: we can > add a method in common.xsl (I called it urlencode) that encodes properly > the URL and do a window.location to this newly created url. > > We replace all href values with urlencode(the old href value) and we're > done. > > Is anyone ok for such a fix? > > If so I will start updating all the stylesheet and commit. > > > Jerome. > > > _______________________________________________ > Openjmx-devel mailing list > Ope...@li... > https://lists.sourceforge.net/lists/listinfo/openjmx-devel > |
|
From: Carlos Q. <car...@we...> - 2002-01-29 18:47:53
|
On Tuesday 29 January 2002 20:40, J=E9r=F4me BERNARD wrote: > I forgot to precise that the method is implemented in JavaScript (so > running on client-side). I'm not a very big fan of JavaScript, specially when I think of usage wit= h=20 non supporting browser. This happens to me when I can only ssh to a serve= r=20 and I can only use Lynx. I'd prefer some other solution > > Jerome. > > ----- Original Message ----- > From: "J=E9r=F4me BERNARD" <jer...@xt...> > To: <ope...@li...> > Sent: Tuesday, January 29, 2002 7:00 PM > Subject: [Openjmx-devel] Proposed bug fix in the XSLT stylesheets > > > Hi, > > > > I have been experiencing problems with ObjectNames containing spaces. > > The way the XSTL stylesheets are built is a problem because the URL > > produced are not valid. > > > > I have found (and implemented) a "trick" in order to solve that: we c= an > > add a method in common.xsl (I called it urlencode) that encodes prope= rly > > the URL and do a window.location to this newly created url. > > > > We replace all href values with urlencode(the old href value) and we'= re > > done. > > > > Is anyone ok for such a fix? > > > > If so I will start updating all the stylesheet and commit. > > > > > > Jerome. > > > > > > _______________________________________________ > > Openjmx-devel mailing list > > Ope...@li... > > https://lists.sourceforge.net/lists/listinfo/openjmx-devel > > _______________________________________________ > Openjmx-devel mailing list > Ope...@li... > https://lists.sourceforge.net/lists/listinfo/openjmx-devel |
|
From: <jer...@xt...> - 2002-01-29 18:53:01
|
Another one would be to use some XSL:PI (processing instructions) but I guess we would be "linked" to the XSL transformer which is problably not even better. Any other suggestion? Jerome. ----- Original Message ----- From: "Carlos Quiroz" <car...@we...> To: <ope...@li...> Sent: Tuesday, January 29, 2002 7:44 PM Subject: Re: [Openjmx-devel] Proposed bug fix in the XSLT stylesheets > On Tuesday 29 January 2002 20:40, Jérôme BERNARD wrote: > > I forgot to precise that the method is implemented in JavaScript (so > > running on client-side). > I'm not a very big fan of JavaScript, specially when I think of usage with > non supporting browser. This happens to me when I can only ssh to a server > and I can only use Lynx. > > I'd prefer some other solution > > > > > Jerome. > > > > ----- Original Message ----- > > From: "Jérôme BERNARD" <jer...@xt...> > > To: <ope...@li...> > > Sent: Tuesday, January 29, 2002 7:00 PM > > Subject: [Openjmx-devel] Proposed bug fix in the XSLT stylesheets > > > > > Hi, > > > > > > I have been experiencing problems with ObjectNames containing spaces. > > > The way the XSTL stylesheets are built is a problem because the URL > > > produced are not valid. > > > > > > I have found (and implemented) a "trick" in order to solve that: we can > > > add a method in common.xsl (I called it urlencode) that encodes properly > > > the URL and do a window.location to this newly created url. > > > > > > We replace all href values with urlencode(the old href value) and we're > > > done. > > > > > > Is anyone ok for such a fix? > > > > > > If so I will start updating all the stylesheet and commit. > > > > > > > > > Jerome. > > > > > > > > > _______________________________________________ > > > Openjmx-devel mailing list > > > Ope...@li... > > > https://lists.sourceforge.net/lists/listinfo/openjmx-devel > > > > _______________________________________________ > > Openjmx-devel mailing list > > Ope...@li... > > https://lists.sourceforge.net/lists/listinfo/openjmx-devel > > _______________________________________________ > Openjmx-devel mailing list > Ope...@li... > https://lists.sourceforge.net/lists/listinfo/openjmx-devel > |
|
From: Carlos Q. <car...@we...> - 2002-01-29 19:00:44
|
On Tuesday 29 January 2002 20:52, J=E9r=F4me BERNARD wrote: > Another one would be to use some XSL:PI (processing instructions) but I > guess we would be "linked" to the XSL transformer which is problably no= t > even better. > Any other suggestion? We could use a xalan extension. That will tie us to xalan but we are alre= ady=20 tied since both saxon and JDK 1.4 keep throwing exception, and I was thin= king=20 to use them anyway for handling custom data types. I'll investigate this and if nothing else works you can commit the JavaSc= ript=20 solution > > Jerome. > > > ----- Original Message ----- > From: "Carlos Quiroz" <car...@we...> > To: <ope...@li...> > Sent: Tuesday, January 29, 2002 7:44 PM > Subject: Re: [Openjmx-devel] Proposed bug fix in the XSLT stylesheets > > > On Tuesday 29 January 2002 20:40, J=E9r=F4me BERNARD wrote: > > > I forgot to precise that the method is implemented in JavaScript (s= o > > > running on client-side). > > > > I'm not a very big fan of JavaScript, specially when I think of usage > > with non supporting browser. This happens to me when I can only ssh t= o a > > server and I can only use Lynx. > > > > I'd prefer some other solution > > > > > Jerome. > > > > > > ----- Original Message ----- > > > From: "J=E9r=F4me BERNARD" <jer...@xt...> > > > To: <ope...@li...> > > > Sent: Tuesday, January 29, 2002 7:00 PM > > > Subject: [Openjmx-devel] Proposed bug fix in the XSLT stylesheets > > > > > > > Hi, > > > > > > > > I have been experiencing problems with ObjectNames containing spa= ces. > > > > The way the XSTL stylesheets are built is a problem because the U= RL > > > > produced are not valid. > > > > > > > > I have found (and implemented) a "trick" in order to solve that: = we > > can > > > > > add a method in common.xsl (I called it urlencode) that encodes > > properly > > > > > the URL and do a window.location to this newly created url. > > > > > > > > We replace all href values with urlencode(the old href value) and > > we're > > > > > done. > > > > > > > > Is anyone ok for such a fix? > > > > > > > > If so I will start updating all the stylesheet and commit. > > > > > > > > > > > > Jerome. > > > > > > > > > > > > _______________________________________________ > > > > Openjmx-devel mailing list > > > > Ope...@li... > > > > https://lists.sourceforge.net/lists/listinfo/openjmx-devel > > > > > > _______________________________________________ > > > Openjmx-devel mailing list > > > Ope...@li... > > > https://lists.sourceforge.net/lists/listinfo/openjmx-devel > > > > _______________________________________________ > > Openjmx-devel mailing list > > Ope...@li... > > https://lists.sourceforge.net/lists/listinfo/openjmx-devel > > _______________________________________________ > Openjmx-devel mailing list > Ope...@li... > https://lists.sourceforge.net/lists/listinfo/openjmx-devel |
|
From: Carlos Q. <car...@we...> - 2002-01-29 19:26:26
|
On Tuesday 29 January 2002 20:00, J=E9r=F4me BERNARD wrote: > Hi, > > I have been experiencing problems with ObjectNames containing spaces. > The way the XSTL stylesheets are built is a problem because the URL > produced are not valid. How does this happen exactly? The XSLT requires that if output is set to = html=20 href elements are escaped and that's what happens in my testing here. I'm= =20 having a MBean called 'Http Adaptor:name=3DHttp Adaptor' and the link wor= ks ok. What XSLT processor are you using? > > I have found (and implemented) a "trick" in order to solve that: we can > add a method in common.xsl (I called it urlencode) that encodes properl= y > the URL and do a window.location to this newly created url. > > We replace all href values with urlencode(the old href value) and we're > done. > > Is anyone ok for such a fix? > > If so I will start updating all the stylesheet and commit. > > > Jerome. > > > _______________________________________________ > Openjmx-devel mailing list > Ope...@li... > https://lists.sourceforge.net/lists/listinfo/openjmx-devel |
|
From: Carlos Q. <car...@we...> - 2002-01-29 20:39:47
|
On Tuesday 29 January 2002 20:00, J=E9r=F4me BERNARD wrote: > Hi, > > I have been experiencing problems with ObjectNames containing spaces. > The way the XSTL stylesheets are built is a problem because the URL > produced are not valid. > > I have found (and implemented) a "trick" in order to solve that: we can > add a method in common.xsl (I called it urlencode) that encodes properl= y > the URL and do a window.location to this newly created url. Hi I added one template which uses a xalan extension. It basically passes= the=20 URL via URLEncode.encode(). This is better than using XSLT default output= =20 becuse it warantees that some characters will be right encoded in particu= lar=20 '&' It is working with Konqueror and Mozilla (Linux) but it should be tested = with=20 IE and Netscape in M$ Windows which I don't use The big problem is that we are now stuck with xalan. Opinions? If this is= ok=20 I can commit it ASAP > > We replace all href values with urlencode(the old href value) and we're > done. > > Is anyone ok for such a fix? > > If so I will start updating all the stylesheet and commit. > > > Jerome. > > > _______________________________________________ > Openjmx-devel mailing list > Ope...@li... > https://lists.sourceforge.net/lists/listinfo/openjmx-devel |
|
From: Carlos Q. <car...@we...> - 2002-01-30 08:05:33
|
On Tuesday 29 January 2002 20:00, J=E9r=F4me BERNARD wrote: > Hi, Hi I commited my solution. Please take a look and give me your comments Regards > > I have been experiencing problems with ObjectNames containing spaces. > The way the XSTL stylesheets are built is a problem because the URL > produced are not valid. > > I have found (and implemented) a "trick" in order to solve that: we can > add a method in common.xsl (I called it urlencode) that encodes properl= y > the URL and do a window.location to this newly created url. > > We replace all href values with urlencode(the old href value) and we're > done. > > Is anyone ok for such a fix? > > If so I will start updating all the stylesheet and commit. > > > Jerome. > > > _______________________________________________ > Openjmx-devel mailing list > Ope...@li... > https://lists.sourceforge.net/lists/listinfo/openjmx-devel |
|
From: B. <jer...@xt...> - 2002-01-30 08:42:57
|
That's fine for me. Thanks. Jerome. Carlos Quiroz wrote: >On Tuesday 29 January 2002 20:00, J=E9r=F4me BERNARD wrote: > >>Hi, >> > >Hi I commited my solution. Please take a look and give me your comments >Regards > >>I have been experiencing problems with ObjectNames containing spaces. >>The way the XSTL stylesheets are built is a problem because the URL >>produced are not valid. >> >>I have found (and implemented) a "trick" in order to solve that: we can= >>add a method in common.xsl (I called it urlencode) that encodes properl= y >>the URL and do a window.location to this newly created url. >> >>We replace all href values with urlencode(the old href value) and we're= >>done. >> >>Is anyone ok for such a fix? >> >>If so I will start updating all the stylesheet and commit. >> >> >>Jerome. >> |