[Jetty-support] To access a file from jetty application root "webapps/"

-------------------------------------------------------------------------
Sponsored by: SourceForge.net Community Choice Awards: VOTE NOW!
Studies have shown that voting for your favorite open source project,
along with a healthy diet, reduces your potential for chronic lameness
and boredom. Vote Now at http://www.sourceforge.net/community/cca08

_______________________________________________
Jetty-support mailing list
Jetty-support <at> lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/jetty-support

[jetty-user] Weird Jsp-compilation problem

Hello Jetty-users!

Have you already experienced this?:

A simple web-app with the following files:

/jsp/test.jsp
/META-INF/manifest.mf
/WEB-INF/web.xml
/WEB-INF/classes/de/Testing.class
/WEB-INF/classes/de/testing/Test.class

In test.jsp, i have an import of class Test:
<% <at>  page import="de.testing.Test"%>

But when the jsp is being compiled by the JDT-Eclipse-Compiler, i get the
exception:
org.apache.jasper.JasperException: PWC6033: Unable to compile class for JSP

PWC6199: Generated servlet error:
The import de.testing cannot be resolved

PWC6197: An error occurred at line: 7 in the jsp file: /jsp/test.jsp
PWC6199: Generated servlet error:
Test cannot be resolved to a type

	at
org.apache.jasper.compiler.DefaultErrorHandler.javacError(DefaultErrorHandle
r.java:107)
	at
org.apache.jasper.compiler.ErrorDispatcher.javacError(ErrorDispatcher.java:2
80)
	at org.apache.jasper.compiler.Compiler.generateClass(Compiler.java:350)
	at org.apache.jasper.compiler.Compiler.compile(Compiler.java:411)
	at
org.apache.jasper.JspCompilationContext.compile(JspCompilationContext.java:5
92)
	at
org.apache.jasper.servlet.JspServletWrapper.service(JspServletWrapper.java:3
44)
	at org.apache.jasper.servlet.JspServlet.serviceJspFile(JspServlet.java:470)
	at org.apache.jasper.servlet.JspServlet.service(JspServlet.java:364)
	at javax.servlet.http.HttpServlet.service(HttpServlet.java:820)
	at org.mortbay.jetty.servlet.ServletHolder.handle(ServletHolder.java:487)
	at org.mortbay.jetty.servlet.ServletHandler.handle(ServletHandler.java:362)
	at
org.mortbay.jetty.security.SecurityHandler.handle(SecurityHandler.java:216)
	at org.mortbay.jetty.servlet.SessionHandler.handle(SessionHandler.java:181)
	at org.mortbay.jetty.handler.ContextHandler.handle(ContextHandler.java:729)
	at org.mortbay.jetty.webapp.WebAppContext.handle(WebAppContext.java:405)
	at
org.mortbay.jetty.handler.ContextHandlerCollection.handle(ContextHandlerColl
ection.java:206)
	at
org.mortbay.jetty.handler.HandlerCollection.handle(HandlerCollection.java:11
4)
	at org.mortbay.jetty.handler.HandlerWrapper.handle(HandlerWrapper.java:152)
	at org.mortbay.jetty.Server.handle(Server.java:324)
	at org.mortbay.jetty.HttpConnection.handleRequest(HttpConnection.java:505)
	at
org.mortbay.jetty.HttpConnection$RequestHandler.headerComplete(HttpConnectio
n.java:829)
	at org.mortbay.jetty.HttpParser.parseNext(HttpParser.java:513)
	at org.mortbay.jetty.HttpParser.parseAvailable(HttpParser.java:211)
	at org.mortbay.jetty.HttpConnection.handle(HttpConnection.java:380)
	at
org.mortbay.io.nio.SelectChannelEndPoint.run(SelectChannelEndPoint.java:395)
	at
org.mortbay.thread.QueuedThreadPool$PoolThread.run(QueuedThreadPool.java:488
)
It stumbles over the class de.Testing with the same name as the package. I
tested the web-app in Tomcat 6.0.16 successfully which is using the
jasper-jdt-component as well (at least i think it does as the library is in
there - but it might be different from the Glassfish-version). So is this a
Jetty-problem? Or am i doing something wrong?

Here is the war-file:
http://www.photonensturm.de/Testing.war
Hope that someone has time to check it.

Cheers,
Michael

---------------------------------------------------------------------
To unsubscribe from this list, please visit:

    http://xircles.codehaus.org/manage_email

Re: [jetty-user] Weird Jsp-compilation problem

Hi Michael,

Can you tell us your jetty version and platform (windows?)

thanks
Jan

Michael Weigmann wrote:
> Hello Jetty-users!
> 
> Have you already experienced this?:
> 
> A simple web-app with the following files:
> 
> /jsp/test.jsp
> /META-INF/manifest.mf
> /WEB-INF/web.xml
> /WEB-INF/classes/de/Testing.class
> /WEB-INF/classes/de/testing/Test.class
> 
> In test.jsp, i have an import of class Test:
> <% <at>  page import="de.testing.Test"%>
> 
> But when the jsp is being compiled by the JDT-Eclipse-Compiler, i get the
> exception:
> org.apache.jasper.JasperException: PWC6033: Unable to compile class for JSP
> 
> PWC6199: Generated servlet error:
> The import de.testing cannot be resolved
> 
> PWC6197: An error occurred at line: 7 in the jsp file: /jsp/test.jsp
> PWC6199: Generated servlet error:
> Test cannot be resolved to a type
> 
> 
> 	at
> org.apache.jasper.compiler.DefaultErrorHandler.javacError(DefaultErrorHandle
> r.java:107)
> 	at
> org.apache.jasper.compiler.ErrorDispatcher.javacError(ErrorDispatcher.java:2
> 80)
> 	at org.apache.jasper.compiler.Compiler.generateClass(Compiler.java:350)
> 	at org.apache.jasper.compiler.Compiler.compile(Compiler.java:411)
> 	at
> org.apache.jasper.JspCompilationContext.compile(JspCompilationContext.java:5
> 92)
> 	at
> org.apache.jasper.servlet.JspServletWrapper.service(JspServletWrapper.java:3
> 44)
> 	at org.apache.jasper.servlet.JspServlet.serviceJspFile(JspServlet.java:470)
> 	at org.apache.jasper.servlet.JspServlet.service(JspServlet.java:364)
> 	at javax.servlet.http.HttpServlet.service(HttpServlet.java:820)
> 	at org.mortbay.jetty.servlet.ServletHolder.handle(ServletHolder.java:487)
> 	at org.mortbay.jetty.servlet.ServletHandler.handle(ServletHandler.java:362)
> 	at
> org.mortbay.jetty.security.SecurityHandler.handle(SecurityHandler.java:216)
> 	at org.mortbay.jetty.servlet.SessionHandler.handle(SessionHandler.java:181)
> 	at org.mortbay.jetty.handler.ContextHandler.handle(ContextHandler.java:729)
> 	at org.mortbay.jetty.webapp.WebAppContext.handle(WebAppContext.java:405)
> 	at
> org.mortbay.jetty.handler.ContextHandlerCollection.handle(ContextHandlerColl
> ection.java:206)
> 	at
> org.mortbay.jetty.handler.HandlerCollection.handle(HandlerCollection.java:11
> 4)
> 	at org.mortbay.jetty.handler.HandlerWrapper.handle(HandlerWrapper.java:152)
> 	at org.mortbay.jetty.Server.handle(Server.java:324)
> 	at org.mortbay.jetty.HttpConnection.handleRequest(HttpConnection.java:505)
> 	at
> org.mortbay.jetty.HttpConnection$RequestHandler.headerComplete(HttpConnectio
> n.java:829)
> 	at org.mortbay.jetty.HttpParser.parseNext(HttpParser.java:513)
> 	at org.mortbay.jetty.HttpParser.parseAvailable(HttpParser.java:211)
> 	at org.mortbay.jetty.HttpConnection.handle(HttpConnection.java:380)
> 	at
> org.mortbay.io.nio.SelectChannelEndPoint.run(SelectChannelEndPoint.java:395)
> 	at
> org.mortbay.thread.QueuedThreadPool$PoolThread.run(QueuedThreadPool.java:488
> )
> It stumbles over the class de.Testing with the same name as the package. I
> tested the web-app in Tomcat 6.0.16 successfully which is using the
> jasper-jdt-component as well (at least i think it does as the library is in
> there - but it might be different from the Glassfish-version). So is this a
> Jetty-problem? Or am i doing something wrong?
> 
> Here is the war-file:
> http://www.photonensturm.de/Testing.war
> Hope that someone has time to check it.
> 
> Cheers,
> Michael
> 
> 
> 
> 
> 
> 
> 
> ---------------------------------------------------------------------
> To unsubscribe from this list, please visit:
> 
>     http://xircles.codehaus.org/manage_email
> 
> 
> 

--

-- 
Jan Bartel, Webtide LLC | janb <at> webtide.com | http://www.webtide.com

---------------------------------------------------------------------
To unsubscribe from this list, please visit:

    http://xircles.codehaus.org/manage_email

Re: [jetty-user] Weird Jsp-compilation problem

Hi Jan,

sorry, it's Jetty 6.1.11 and Win2K...

Thanks,
Michael

"Jan Bartel" <janb <at> webtide.com> schrieb im Newsbeitrag
news:4875DBB7.8060308 <at> webtide.com...
> Hi Michael,
>
> Can you tell us your jetty version and platform (windows?)
>
> thanks
> Jan
>
>
> Michael Weigmann wrote:
> > Hello Jetty-users!
> >
> > Have you already experienced this?:
> >
> > A simple web-app with the following files:
> >
> > /jsp/test.jsp
> > /META-INF/manifest.mf
> > /WEB-INF/web.xml
> > /WEB-INF/classes/de/Testing.class
> > /WEB-INF/classes/de/testing/Test.class
> >
> > In test.jsp, i have an import of class Test:
> > <% <at>  page import="de.testing.Test"%>
> >
> > But when the jsp is being compiled by the JDT-Eclipse-Compiler, i get
the
> > exception:
> > org.apache.jasper.JasperException: PWC6033: Unable to compile class for
JSP
> >
> > PWC6199: Generated servlet error:
> > The import de.testing cannot be resolved
> >
> > PWC6197: An error occurred at line: 7 in the jsp file: /jsp/test.jsp
> > PWC6199: Generated servlet error:
> > Test cannot be resolved to a type
> >
> >
> > at
> >
org.apache.jasper.compiler.DefaultErrorHandler.javacError(DefaultErrorHandle
> > r.java:107)
> > at
> >
org.apache.jasper.compiler.ErrorDispatcher.javacError(ErrorDispatcher.java:2
> > 80)
> > at org.apache.jasper.compiler.Compiler.generateClass(Compiler.java:350)
> > at org.apache.jasper.compiler.Compiler.compile(Compiler.java:411)
> > at
> >
org.apache.jasper.JspCompilationContext.compile(JspCompilationContext.java:5
> > 92)
> > at
> >
org.apache.jasper.servlet.JspServletWrapper.service(JspServletWrapper.java:3
> > 44)
> > at
org.apache.jasper.servlet.JspServlet.serviceJspFile(JspServlet.java:470)
> > at org.apache.jasper.servlet.JspServlet.service(JspServlet.java:364)
> > at javax.servlet.http.HttpServlet.service(HttpServlet.java:820)
> > at
org.mortbay.jetty.servlet.ServletHolder.handle(ServletHolder.java:487)
> > at
org.mortbay.jetty.servlet.ServletHandler.handle(ServletHandler.java:362)
> > at
> >
org.mortbay.jetty.security.SecurityHandler.handle(SecurityHandler.java:216)
> > at
org.mortbay.jetty.servlet.SessionHandler.handle(SessionHandler.java:181)
> > at
org.mortbay.jetty.handler.ContextHandler.handle(ContextHandler.java:729)
> > at org.mortbay.jetty.webapp.WebAppContext.handle(WebAppContext.java:405)
> > at
> >
org.mortbay.jetty.handler.ContextHandlerCollection.handle(ContextHandlerColl
> > ection.java:206)
> > at
> >
org.mortbay.jetty.handler.HandlerCollection.handle(HandlerCollection.java:11
> > 4)
> > at
org.mortbay.jetty.handler.HandlerWrapper.handle(HandlerWrapper.java:152)
> > at org.mortbay.jetty.Server.handle(Server.java:324)
> > at
org.mortbay.jetty.HttpConnection.handleRequest(HttpConnection.java:505)
> > at
> >
org.mortbay.jetty.HttpConnection$RequestHandler.headerComplete(HttpConnectio
> > n.java:829)
> > at org.mortbay.jetty.HttpParser.parseNext(HttpParser.java:513)
> > at org.mortbay.jetty.HttpParser.parseAvailable(HttpParser.java:211)
> > at org.mortbay.jetty.HttpConnection.handle(HttpConnection.java:380)
> > at
> >
org.mortbay.io.nio.SelectChannelEndPoint.run(SelectChannelEndPoint.java:395)
> > at
> >
org.mortbay.thread.QueuedThreadPool$PoolThread.run(QueuedThreadPool.java:488
> > )
> > It stumbles over the class de.Testing with the same name as the package.
I
> > tested the web-app in Tomcat 6.0.16 successfully which is using the
> > jasper-jdt-component as well (at least i think it does as the library is
in
> > there - but it might be different from the Glassfish-version). So is
this a
> > Jetty-problem? Or am i doing something wrong?
> >
> > Here is the war-file:
> > http://www.photonensturm.de/Testing.war
> > Hope that someone has time to check it.
> >
> > Cheers,
> > Michael
> >
> >
> >
> >
> >
> >
> >
> > ---------------------------------------------------------------------
> > To unsubscribe from this list, please visit:
> >
> >     http://xircles.codehaus.org/manage_email
> >
> >
> >
>
>
> --
> Jan Bartel, Webtide LLC | janb <at> webtide.com | http://www.webtide.com
>
> ---------------------------------------------------------------------
> To unsubscribe from this list, please visit:
>
>     http://xircles.codehaus.org/manage_email
>
>
>

---------------------------------------------------------------------
To unsubscribe from this list, please visit:

    http://xircles.codehaus.org/manage_email

Re: [jetty-user] Weird Jsp-compilation problem

Re: [jetty-user] Weird Jsp-compilation problem

Hi David,

this is funny, isn't it? 

I'll try to post an issue for the glassfish-webtier-team...

Cheers to everyone,
Michael

David Yu schrieb:
> Michael,
> 
> It seems like you've found a glassfish jsp bug 
> The reason behind it is you have a class named de.Testing and you have a 
> package named de.testing
> Try renaming the package to testin (without the 'g', can really be 
> anything cept 'testing'), and the errors will go away.
> 
> Cheers
> 
> On Fri, Jul 11, 2008 at 12:03 AM, Michael Weigmann 
> <michael.weigmann <at> hsh-berlin.com 
> <mailto:michael.weigmann <at> hsh-berlin.com>> wrote:
> 
>     Hi Jan,
> 
>     sorry, it's Jetty 6.1.11 and Win2K...
> 
>     Thanks,
>     Michael
> 
> 
>     "Jan Bartel" <janb <at> webtide.com <mailto:janb <at> webtide.com>> schrieb im
>     Newsbeitrag
>     news:4875DBB7.8060308 <at> webtide.com...
>      > Hi Michael,
>      >
>      > Can you tell us your jetty version and platform (windows?)
>      >
>      > thanks
>      > Jan
>      >
>      >
>      > Michael Weigmann wrote:
>      > > Hello Jetty-users!
>      > >
>      > > Have you already experienced this?:
>      > >
>      > > A simple web-app with the following files:
>      > >
>      > > /jsp/test.jsp
>      > > /META-INF/manifest.mf
>      > > /WEB-INF/web.xml
>      > > /WEB-INF/classes/de/Testing.class
>      > > /WEB-INF/classes/de/testing/Test.class
>      > >
>      > > In test.jsp, i have an import of class Test:
>      > > <% <at>  page import="de.testing.Test"%>
>      > >
>      > > But when the jsp is being compiled by the JDT-Eclipse-Compiler,
>     i get
>     the
>      > > exception:
>      > > org.apache.jasper.JasperException: PWC6033: Unable to compile
>     class for
>     JSP
>      > >
>      > > PWC6199: Generated servlet error:
>      > > The import de.testing cannot be resolved
>      > >
>      > > PWC6197: An error occurred at line: 7 in the jsp file:
>     /jsp/test.jsp
>      > > PWC6199: Generated servlet error:
>      > > Test cannot be resolved to a type
>      > >
>      > >
>      > > at
>      > >
>     org.apache.jasper.compiler.DefaultErrorHandler.javacError(DefaultErrorHandle
>      > > r.java:107)
>      > > at
>      > >
>     org.apache.jasper.compiler.ErrorDispatcher.javacError(ErrorDispatcher.java:2
>      > > 80)
>      > > at
>     org.apache.jasper.compiler.Compiler.generateClass(Compiler.java:350)
>      > > at org.apache.jasper.compiler.Compiler.compile(Compiler.java:411)
>      > > at
>      > >
>     org.apache.jasper.JspCompilationContext.compile(JspCompilationContext.java:5
>      > > 92)
>      > > at
>      > >
>     org.apache.jasper.servlet.JspServletWrapper.service(JspServletWrapper.java:3
>      > > 44)
>      > > at
>     org.apache.jasper.servlet.JspServlet.serviceJspFile(JspServlet.java:470)
>      > > at
>     org.apache.jasper.servlet.JspServlet.service(JspServlet.java:364)
>      > > at javax.servlet.http.HttpServlet.service(HttpServlet.java:820)
>      > > at
>     org.mortbay.jetty.servlet.ServletHolder.handle(ServletHolder.java:487)
>      > > at
>     org.mortbay.jetty.servlet.ServletHandler.handle(ServletHandler.java:362)
>      > > at
>      > >
>     org.mortbay.jetty.security.SecurityHandler.handle(SecurityHandler.java:216)
>      > > at
>     org.mortbay.jetty.servlet.SessionHandler.handle(SessionHandler.java:181)
>      > > at
>     org.mortbay.jetty.handler.ContextHandler.handle(ContextHandler.java:729)
>      > > at
>     org.mortbay.jetty.webapp.WebAppContext.handle(WebAppContext.java:405)
>      > > at
>      > >
>     org.mortbay.jetty.handler.ContextHandlerCollection.handle(ContextHandlerColl
>      > > ection.java:206)
>      > > at
>      > >
>     org.mortbay.jetty.handler.HandlerCollection.handle(HandlerCollection.java:11
>      > > 4)
>      > > at
>     org.mortbay.jetty.handler.HandlerWrapper.handle(HandlerWrapper.java:152)
>      > > at org.mortbay.jetty.Server.handle(Server.java:324)
>      > > at
>     org.mortbay.jetty.HttpConnection.handleRequest(HttpConnection.java:505)
>      > > at
>      > >
>     org.mortbay.jetty.HttpConnection$RequestHandler.headerComplete(HttpConnectio
>      > > n.java:829)
>      > > at org.mortbay.jetty.HttpParser.parseNext(HttpParser.java:513)
>      > > at org.mortbay.jetty.HttpParser.parseAvailable(HttpParser.java:211)
>      > > at org.mortbay.jetty.HttpConnection.handle(HttpConnection.java:380)
>      > > at
>      > >
>     org.mortbay.io.nio.SelectChannelEndPoint.run(SelectChannelEndPoint.java:395)
>      > > at
>      > >
>     org.mortbay.thread.QueuedThreadPool$PoolThread.run(QueuedThreadPool.java:488
>      > > )
>      > > It stumbles over the class de.Testing with the same name as the
>     package.
>     I
>      > > tested the web-app in Tomcat 6.0.16 successfully which is using the
>      > > jasper-jdt-component as well (at least i think it does as the
>     library is
>     in
>      > > there - but it might be different from the Glassfish-version).
>     So is
>     this a
>      > > Jetty-problem? Or am i doing something wrong?
>      > >
>      > > Here is the war-file:
>      > > http://www.photonensturm.de/Testing.war
>      > > Hope that someone has time to check it.
>      > >
>      > > Cheers,
>      > > Michael
>      > >
>      > >
>      > >
>      > >
>      > >
>      > >
>      > >
>      > >
>     ---------------------------------------------------------------------
>      > > To unsubscribe from this list, please visit:
>      > >
>      > >     http://xircles.codehaus.org/manage_email
>      > >
>      > >
>      > >
>      >
>      >
>      > --
>      > Jan Bartel, Webtide LLC | janb <at> webtide.com
>     <mailto:janb <at> webtide.com> | http://www.webtide.com
>      >
>      > ---------------------------------------------------------------------
>      > To unsubscribe from this list, please visit:
>      >
>      >     http://xircles.codehaus.org/manage_email
>      >
>      >
>      >
> 
> 
> 
> 
>     ---------------------------------------------------------------------
>     To unsubscribe from this list, please visit:
> 
>        http://xircles.codehaus.org/manage_email
> 
> 
> 

---------------------------------------------------------------------
To unsubscribe from this list, please visit:

    http://xircles.codehaus.org/manage_email

Re: [jetty-user] Weird Jsp-compilation problem

Is this because of the case-insensitivity of windows?

Jan

Michael Weigmann wrote:
> Hi David,
> 
> this is funny, isn't it? 
> 
> I'll try to post an issue for the glassfish-webtier-team...
> 
> Cheers to everyone,
> Michael
> 
> 
> David Yu schrieb:
>> Michael,
>>
>> It seems like you've found a glassfish jsp bug 
>> The reason behind it is you have a class named de.Testing and you have
>> a package named de.testing
>> Try renaming the package to testin (without the 'g', can really be
>> anything cept 'testing'), and the errors will go away.
>>
>> Cheers
>>
>> On Fri, Jul 11, 2008 at 12:03 AM, Michael Weigmann
>> <michael.weigmann <at> hsh-berlin.com
>> <mailto:michael.weigmann <at> hsh-berlin.com>> wrote:
>>
>>     Hi Jan,
>>
>>     sorry, it's Jetty 6.1.11 and Win2K...
>>
>>     Thanks,
>>     Michael
>>
>>
>>     "Jan Bartel" <janb <at> webtide.com <mailto:janb <at> webtide.com>> schrieb im
>>     Newsbeitrag
>>     news:4875DBB7.8060308 <at> webtide.com...
>>      > Hi Michael,
>>      >
>>      > Can you tell us your jetty version and platform (windows?)
>>      >
>>      > thanks
>>      > Jan
>>      >
>>      >
>>      > Michael Weigmann wrote:
>>      > > Hello Jetty-users!
>>      > >
>>      > > Have you already experienced this?:
>>      > >
>>      > > A simple web-app with the following files:
>>      > >
>>      > > /jsp/test.jsp
>>      > > /META-INF/manifest.mf
>>      > > /WEB-INF/web.xml
>>      > > /WEB-INF/classes/de/Testing.class
>>      > > /WEB-INF/classes/de/testing/Test.class
>>      > >
>>      > > In test.jsp, i have an import of class Test:
>>      > > <% <at>  page import="de.testing.Test"%>
>>      > >
>>      > > But when the jsp is being compiled by the JDT-Eclipse-Compiler,
>>     i get
>>     the
>>      > > exception:
>>      > > org.apache.jasper.JasperException: PWC6033: Unable to compile
>>     class for
>>     JSP
>>      > >
>>      > > PWC6199: Generated servlet error:
>>      > > The import de.testing cannot be resolved
>>      > >
>>      > > PWC6197: An error occurred at line: 7 in the jsp file:
>>     /jsp/test.jsp
>>      > > PWC6199: Generated servlet error:
>>      > > Test cannot be resolved to a type
>>      > >
>>      > >
>>      > > at
>>      > >
>>    
>> org.apache.jasper.compiler.DefaultErrorHandler.javacError(DefaultErrorHandle
>>
>>      > > r.java:107)
>>      > > at
>>      > >
>>    
>> org.apache.jasper.compiler.ErrorDispatcher.javacError(ErrorDispatcher.java:2
>>
>>      > > 80)
>>      > > at
>>     org.apache.jasper.compiler.Compiler.generateClass(Compiler.java:350)
>>      > > at
>> org.apache.jasper.compiler.Compiler.compile(Compiler.java:411)
>>      > > at
>>      > >
>>    
>> org.apache.jasper.JspCompilationContext.compile(JspCompilationContext.java:5
>>
>>      > > 92)
>>      > > at
>>      > >
>>    
>> org.apache.jasper.servlet.JspServletWrapper.service(JspServletWrapper.java:3
>>
>>      > > 44)
>>      > > at
>>    
>> org.apache.jasper.servlet.JspServlet.serviceJspFile(JspServlet.java:470)
>>      > > at
>>     org.apache.jasper.servlet.JspServlet.service(JspServlet.java:364)
>>      > > at javax.servlet.http.HttpServlet.service(HttpServlet.java:820)
>>      > > at
>>    
>> org.mortbay.jetty.servlet.ServletHolder.handle(ServletHolder.java:487)
>>      > > at
>>    
>> org.mortbay.jetty.servlet.ServletHandler.handle(ServletHandler.java:362)
>>      > > at
>>      > >
>>    
>> org.mortbay.jetty.security.SecurityHandler.handle(SecurityHandler.java:216)
>>
>>      > > at
>>    
>> org.mortbay.jetty.servlet.SessionHandler.handle(SessionHandler.java:181)
>>      > > at
>>    
>> org.mortbay.jetty.handler.ContextHandler.handle(ContextHandler.java:729)
>>      > > at
>>     org.mortbay.jetty.webapp.WebAppContext.handle(WebAppContext.java:405)
>>      > > at
>>      > >
>>    
>> org.mortbay.jetty.handler.ContextHandlerCollection.handle(ContextHandlerColl
>>
>>      > > ection.java:206)
>>      > > at
>>      > >
>>    
>> org.mortbay.jetty.handler.HandlerCollection.handle(HandlerCollection.java:11
>>
>>      > > 4)
>>      > > at
>>    
>> org.mortbay.jetty.handler.HandlerWrapper.handle(HandlerWrapper.java:152)
>>      > > at org.mortbay.jetty.Server.handle(Server.java:324)
>>      > > at
>>    
>> org.mortbay.jetty.HttpConnection.handleRequest(HttpConnection.java:505)
>>      > > at
>>      > >
>>    
>> org.mortbay.jetty.HttpConnection$RequestHandler.headerComplete(HttpConnectio
>>
>>      > > n.java:829)
>>      > > at org.mortbay.jetty.HttpParser.parseNext(HttpParser.java:513)
>>      > > at
>> org.mortbay.jetty.HttpParser.parseAvailable(HttpParser.java:211)
>>      > > at
>> org.mortbay.jetty.HttpConnection.handle(HttpConnection.java:380)
>>      > > at
>>      > >
>>    
>> org.mortbay.io.nio.SelectChannelEndPoint.run(SelectChannelEndPoint.java:395)
>>
>>      > > at
>>      > >
>>    
>> org.mortbay.thread.QueuedThreadPool$PoolThread.run(QueuedThreadPool.java:488
>>
>>      > > )
>>      > > It stumbles over the class de.Testing with the same name as the
>>     package.
>>     I
>>      > > tested the web-app in Tomcat 6.0.16 successfully which is
>> using the
>>      > > jasper-jdt-component as well (at least i think it does as the
>>     library is
>>     in
>>      > > there - but it might be different from the Glassfish-version).
>>     So is
>>     this a
>>      > > Jetty-problem? Or am i doing something wrong?
>>      > >
>>      > > Here is the war-file:
>>      > > http://www.photonensturm.de/Testing.war
>>      > > Hope that someone has time to check it.
>>      > >
>>      > > Cheers,
>>      > > Michael
>>      > >
>>      > >
>>      > >
>>      > >
>>      > >
>>      > >
>>      > >
>>      > >
>>     ---------------------------------------------------------------------
>>      > > To unsubscribe from this list, please visit:
>>      > >
>>      > >     http://xircles.codehaus.org/manage_email
>>      > >
>>      > >
>>      > >
>>      >
>>      >
>>      > --
>>      > Jan Bartel, Webtide LLC | janb <at> webtide.com
>>     <mailto:janb <at> webtide.com> | http://www.webtide.com
>>      >
>>      >
>> ---------------------------------------------------------------------
>>      > To unsubscribe from this list, please visit:
>>      >
>>      >     http://xircles.codehaus.org/manage_email
>>      >
>>      >
>>      >
>>
>>
>>
>>
>>     ---------------------------------------------------------------------
>>     To unsubscribe from this list, please visit:
>>
>>        http://xircles.codehaus.org/manage_email
>>
>>
>>
> 
> 
> ---------------------------------------------------------------------
> To unsubscribe from this list, please visit:
> 
>    http://xircles.codehaus.org/manage_email
> 
> 
> 

--

-- 
Jan Bartel, Webtide LLC | janb <at> webtide.com | http://www.webtide.com

---------------------------------------------------------------------
To unsubscribe from this list, please visit:

    http://xircles.codehaus.org/manage_email

[jetty-user] Alert: changing dojo / cometd maven IDs and packages

All,

Due to my recent work in adding maven repositories to dojo and cometd,
it has become apparent that some of the existing and recently assigned
names for maven group IDs, artifact IDs and java package names were
not very consistent, had problems with duplicated names and resulted
in poorly named artefacts.

So this is a small advanced warning that I will soon check in (to dojo,
cometd and Jetty) some renames.

The group/artifact IDs that are:

OLD                              NEW
org.dojotoolkit/project          org.dojotoolkit/dojo-project
org.dojotoolkit/dojo             org.dojotoolkit/dojo
org.dojotoolkit.java/project
org.dojotoolkit.java/dojo        org.dojotoolkit/dojo-war

org.cometd/project               org.cometd/cometd-project
org.cometd.java/project          org.cometd.java/cometd-java-project
org.cometd.java/api              org.cometd.java/cometd-api
org.cometd.dojox/examples        org.cometd.dojox/cometd-examples

org.mortbay.jetty/cometd         org.mortbay.jetty/cometd-project
org.mortbay.jetty/cometd-bayeux  org.mortbay.jetty/cometd-jetty
org.mortbay.jetty/cometd-demo    org.mortbay.jetty/cometd-demo
org.mortbay.jetty/bayeux-client  org.mortbay.jetty/cometd-client

The java package name dojox.cometd has been renamed to org.cometd,
so dojox.cometd.Bayeux api is now org.cometd.Bayeux

The resulting jar names are improved by this change, so that the
jars needed to run cometd-jetty are now called:

  cometd-api-1.0-SNAPSHOT.jar  cometd-jetty-6.1-SNAPSHOT.jar

Sorry for the inconvenience of this refactor, but now is the time
to do this, before any artefacts have been published to the central
repository.

I will attempt to update as many consumers of these artefacts as I
have commit permission for.

regards

---------------------------------------------------------------------
To unsubscribe from this list, please visit:

    http://xircles.codehaus.org/manage_email

Re: [jetty-user] Weird Jsp-compilation problem

Hi Jan,

i was able to debug to the point where the eclipse-compiler is 
initialized and started from within jasper (then the source code ran 
out). Nothing was suspicious so far.

At first i thought it might be a classloader problem inside the 
compiler, but that shouldn't be the case as classloaders normally search 
directly for the file (...)/de/testing/Test.class and that won't collide 
with file or directory (...)/de/testing

But don't know what the actual algorithm is at that point. If the webapp 
is functioning under linux then you could be right.

So where is the problem? From within jasper everything seems to be 
correct. So it must be inside the eclipse-compiler and then this must be 
a different version from the one in tomcat.

I'll take care of it and tell you when i've got news...

Cheers,
Michael

Jan Bartel schrieb:
> Is this because of the case-insensitivity of windows?
> 
> Jan
> 
> Michael Weigmann wrote:
>> Hi David,
>>
>> this is funny, isn't it? 
>>
>> I'll try to post an issue for the glassfish-webtier-team...
>>
>> Cheers to everyone,
>> Michael
>>
>>
>> David Yu schrieb:
>>> Michael,
>>>
>>> It seems like you've found a glassfish jsp bug 
>>> The reason behind it is you have a class named de.Testing and you have
>>> a package named de.testing
>>> Try renaming the package to testin (without the 'g', can really be
>>> anything cept 'testing'), and the errors will go away.
>>>
>>> Cheers
>>>
>>> On Fri, Jul 11, 2008 at 12:03 AM, Michael Weigmann
>>> <michael.weigmann <at> hsh-berlin.com
>>> <mailto:michael.weigmann <at> hsh-berlin.com>> wrote:
>>>
>>>     Hi Jan,
>>>
>>>     sorry, it's Jetty 6.1.11 and Win2K...
>>>
>>>     Thanks,
>>>     Michael
>>>
>>>
>>>     "Jan Bartel" <janb <at> webtide.com <mailto:janb <at> webtide.com>> schrieb im
>>>     Newsbeitrag
>>>     news:4875DBB7.8060308 <at> webtide.com...
>>>      > Hi Michael,
>>>      >
>>>      > Can you tell us your jetty version and platform (windows?)
>>>      >
>>>      > thanks
>>>      > Jan
>>>      >
>>>      >
>>>      > Michael Weigmann wrote:
>>>      > > Hello Jetty-users!
>>>      > >
>>>      > > Have you already experienced this?:
>>>      > >
>>>      > > A simple web-app with the following files:
>>>      > >
>>>      > > /jsp/test.jsp
>>>      > > /META-INF/manifest.mf
>>>      > > /WEB-INF/web.xml
>>>      > > /WEB-INF/classes/de/Testing.class
>>>      > > /WEB-INF/classes/de/testing/Test.class
>>>      > >
>>>      > > In test.jsp, i have an import of class Test:
>>>      > > <% <at>  page import="de.testing.Test"%>
>>>      > >
>>>      > > But when the jsp is being compiled by the JDT-Eclipse-Compiler,
>>>     i get
>>>     the
>>>      > > exception:
>>>      > > org.apache.jasper.JasperException: PWC6033: Unable to compile
>>>     class for
>>>     JSP
>>>      > >
>>>      > > PWC6199: Generated servlet error:
>>>      > > The import de.testing cannot be resolved
>>>      > >
>>>      > > PWC6197: An error occurred at line: 7 in the jsp file:
>>>     /jsp/test.jsp
>>>      > > PWC6199: Generated servlet error:
>>>      > > Test cannot be resolved to a type
>>>      > >
>>>      > >
>>>      > > at
>>>      > >
>>>    
>>> org.apache.jasper.compiler.DefaultErrorHandler.javacError(DefaultErrorHandle
>>>
>>>      > > r.java:107)
>>>      > > at
>>>      > >
>>>    
>>> org.apache.jasper.compiler.ErrorDispatcher.javacError(ErrorDispatcher.java:2
>>>
>>>      > > 80)
>>>      > > at
>>>     org.apache.jasper.compiler.Compiler.generateClass(Compiler.java:350)
>>>      > > at
>>> org.apache.jasper.compiler.Compiler.compile(Compiler.java:411)
>>>      > > at
>>>      > >
>>>    
>>> org.apache.jasper.JspCompilationContext.compile(JspCompilationContext.java:5
>>>
>>>      > > 92)
>>>      > > at
>>>      > >
>>>    
>>> org.apache.jasper.servlet.JspServletWrapper.service(JspServletWrapper.java:3
>>>
>>>      > > 44)
>>>      > > at
>>>    
>>> org.apache.jasper.servlet.JspServlet.serviceJspFile(JspServlet.java:470)
>>>      > > at
>>>     org.apache.jasper.servlet.JspServlet.service(JspServlet.java:364)
>>>      > > at javax.servlet.http.HttpServlet.service(HttpServlet.java:820)
>>>      > > at
>>>    
>>> org.mortbay.jetty.servlet.ServletHolder.handle(ServletHolder.java:487)
>>>      > > at
>>>    
>>> org.mortbay.jetty.servlet.ServletHandler.handle(ServletHandler.java:362)
>>>      > > at
>>>      > >
>>>    
>>> org.mortbay.jetty.security.SecurityHandler.handle(SecurityHandler.java:216)
>>>
>>>      > > at
>>>    
>>> org.mortbay.jetty.servlet.SessionHandler.handle(SessionHandler.java:181)
>>>      > > at
>>>    
>>> org.mortbay.jetty.handler.ContextHandler.handle(ContextHandler.java:729)
>>>      > > at
>>>     org.mortbay.jetty.webapp.WebAppContext.handle(WebAppContext.java:405)
>>>      > > at
>>>      > >
>>>    
>>> org.mortbay.jetty.handler.ContextHandlerCollection.handle(ContextHandlerColl
>>>
>>>      > > ection.java:206)
>>>      > > at
>>>      > >
>>>    
>>> org.mortbay.jetty.handler.HandlerCollection.handle(HandlerCollection.java:11
>>>
>>>      > > 4)
>>>      > > at
>>>    
>>> org.mortbay.jetty.handler.HandlerWrapper.handle(HandlerWrapper.java:152)
>>>      > > at org.mortbay.jetty.Server.handle(Server.java:324)
>>>      > > at
>>>    
>>> org.mortbay.jetty.HttpConnection.handleRequest(HttpConnection.java:505)
>>>      > > at
>>>      > >
>>>    
>>> org.mortbay.jetty.HttpConnection$RequestHandler.headerComplete(HttpConnectio
>>>
>>>      > > n.java:829)
>>>      > > at org.mortbay.jetty.HttpParser.parseNext(HttpParser.java:513)
>>>      > > at
>>> org.mortbay.jetty.HttpParser.parseAvailable(HttpParser.java:211)
>>>      > > at
>>> org.mortbay.jetty.HttpConnection.handle(HttpConnection.java:380)
>>>      > > at
>>>      > >
>>>    
>>> org.mortbay.io.nio.SelectChannelEndPoint.run(SelectChannelEndPoint.java:395)
>>>
>>>      > > at
>>>      > >
>>>    
>>> org.mortbay.thread.QueuedThreadPool$PoolThread.run(QueuedThreadPool.java:488
>>>
>>>      > > )
>>>      > > It stumbles over the class de.Testing with the same name as the
>>>     package.
>>>     I
>>>      > > tested the web-app in Tomcat 6.0.16 successfully which is
>>> using the
>>>      > > jasper-jdt-component as well (at least i think it does as the
>>>     library is
>>>     in
>>>      > > there - but it might be different from the Glassfish-version).
>>>     So is
>>>     this a
>>>      > > Jetty-problem? Or am i doing something wrong?
>>>      > >
>>>      > > Here is the war-file:
>>>      > > http://www.photonensturm.de/Testing.war
>>>      > > Hope that someone has time to check it.
>>>      > >
>>>      > > Cheers,
>>>      > > Michael
>>>      > >
>>>      > >
>>>      > >
>>>      > >
>>>      > >
>>>      > >
>>>      > >
>>>      > >
>>>     ---------------------------------------------------------------------
>>>      > > To unsubscribe from this list, please visit:
>>>      > >
>>>      > >     http://xircles.codehaus.org/manage_email
>>>      > >
>>>      > >
>>>      > >
>>>      >
>>>      >
>>>      > --
>>>      > Jan Bartel, Webtide LLC | janb <at> webtide.com
>>>     <mailto:janb <at> webtide.com> | http://www.webtide.com
>>>      >
>>>      >
>>> ---------------------------------------------------------------------
>>>      > To unsubscribe from this list, please visit:
>>>      >
>>>      >     http://xircles.codehaus.org/manage_email
>>>      >
>>>      >
>>>      >
>>>
>>>
>>>
>>>
>>>     ---------------------------------------------------------------------
>>>     To unsubscribe from this list, please visit:
>>>
>>>        http://xircles.codehaus.org/manage_email
>>>
>>>
>>>
>>
>> ---------------------------------------------------------------------
>> To unsubscribe from this list, please visit:
>>
>>    http://xircles.codehaus.org/manage_email
>>
>>
>>
> 
> 

---------------------------------------------------------------------
To unsubscribe from this list, please visit:

    http://xircles.codehaus.org/manage_email

[jetty-user] JSON.parse returns null

Greetings,

I’m having trouble with the following function:

public Object parse(Source source) inside the org.mortbay.util.ajax.JSON
utility class. When parsing the following message:

"/*[{"channel":"/meta/handshake","version":"1.0","supportedConnectionTypes":
["long-polling","callback-polling"],"minimumVersion":"0.9","id":"0","clientI
d":"cda93129eb75fccb","successful":true,"advice":{"reconnect":"retry","inter
val":0,"multiple-clients":false},"authSuccessful":true}]*/"

It returns null. Shouldn't it return an object array? 

Regards,
- Bjarki B

---------------------------------------------------------------------
To unsubscribe from this list, please visit:

    http://xircles.codehaus.org/manage_email