Hi all,
Just wanted to wrap this up, there's a much easier way to run jetty for my
use-case:
http://wiki.eclipse.org/Jetty/Howto/Using_Jetty_Runner
This is working fine and the cross origin requests work as expected.
Previously I was going with:
http://wiki.eclipse.org/Jetty/Howto/Run_Jetty
Thanks
On Tue, Feb 5, 2013 at 12:36 PM, Mark Wyszomierski <[email protected]> wrote:
> Hi Joakim,
>
> Ok I verified that the classfile in question exists in my war file. The
> war file was produced by eclipse. I unzipped the war file to examine its
> contents. I can see the .classfile in what I think is the correct location:
>
> http://cl.ly/image/3z1B3S1g3f2i
>
> com.my.project.Config.class
>
> Does that look correct? (the .java file is there too, I had chosen "export
> source files" as well),
>
> Thanks
>
>
>
> On Tue, Feb 5, 2013 at 10:22 AM, Joakim Erdfelt <[email protected]>wrote:
>
>> If you have a full deployable webapp (war file or exploded war
>> directory), then the /WEB-INF/classes/ and /WEB-INF/lib/ jar files are used
>> during compilation.
>>
>> Are you sure that the this class exists in one of those two locations?
>>
>> And yes, learn maven, embrace it, you'll love it. :-)
>>
>> --
>> Joakim Erdfelt <[email protected]>
>> webtide.com <http://www.webtide.com/>
>> Developer advice, services and support
>> from the Jetty & CometD experts
>> eclipse.org/jetty - cometd.org
>>
>>
>> On Tue, Feb 5, 2013 at 7:14 AM, Mark Wyszomierski <[email protected]>wrote:
>>
>>> Thanks, Joakim.
>>>
>>> I've updated to v7.6.9.v20130131. It looks like we need to setup
>>> compilation of our jsp pages with more recent versions (this was being done
>>> for us behind the scenes for us in 7.3.x):
>>>
>>> http://wiki.eclipse.org/Jetty/Howto/Configure_JSP
>>>
>>> I'm not using maven (though maybe I should start). I have a jdk
>>> installed, and am ok with the jsp being compiled on demand. When I deploy
>>> my war (built using eclipse ee), and hit a jsp page containing references
>>> to a class that exists within the war, I'll get an error stating that the
>>> class could not be found:
>>>
>>> // test.jsp:
>>> <%@ page language="java">
>>> ...
>>> <%@ page import="com.my.project.Config" %>
>>> ...
>>> <% if (Config.DEBUG) {} %> // <- no good anymore
>>>
>>> // output error
>>> org.apache.jasper.JasperException: PWC6033:
>>> Error in Javac compilation for JSP||PWC6199: Generated servlet
>>> error:|string:///test_jsp.java:6: package com.my.project does not
>>> exist||PWC6197:
>>> An error occurred at line: 16 in the jsp file:
>>> /private/tools/test.jsp|PWC6199:
>>> Generated servlet error:|string:///test_jsp.java:61: cannot find
>>> symbol|symbol : variable Config|location: class
>>> org.apache.jsp.private_.tools.test_jsp||
>>> at
>>> org.apache.jasper.compiler.DefaultErrorHandler.javacError(DefaultErrorHandler.java:126)
>>> at
>>> org.apache.jasper.compiler.ErrorDispatcher.javacError(ErrorDispatcher.java:296)
>>> at org.apache.jasper.compiler.Compiler.generateClass(Compiler.java:372)
>>> at org.apache.jasper.compiler.Compiler.compile(Compiler.java:433)
>>> ...
>>>
>>> How / where do I let jetty know that the jsp file can use the classes
>>> that are part of its own war file during compilation?
>>>
>>> Thank you
>>>
>>>
>>>
>>>
>>> On Mon, Feb 4, 2013 at 4:32 PM, Joakim Erdfelt <[email protected]>wrote:
>>>
>>>> You should upgrade your Jetty version to at least 7.6.6.v20120903
>>>>
>>>> There's been many improvements in CrossOriginFilter up to that point.
>>>>
>>>> --
>>>> Joakim Erdfelt <[email protected]>
>>>> webtide.com <http://www.webtide.com/>
>>>> Developer advice, services and support
>>>> from the Jetty & CometD experts
>>>> eclipse.org/jetty - cometd.org
>>>>
>>>>
>>>> On Mon, Feb 4, 2013 at 2:23 PM, Mark Wyszomierski <[email protected]>wrote:
>>>>
>>>>> Hi,
>>>>>
>>>>> I've set up a cross origin filter as described here:
>>>>>
>>>>> http://wiki.eclipse.org/Jetty/Feature/Cross_Origin_Filter
>>>>>
>>>>> This is working perfectly when hitting my jetty instance from Firefox
>>>>> 17+ on desktop. When I run the same code from an instance of UIWebView on
>>>>> ios6, I'm getting an SOP violation error (I think). I'm not 100% sure,
>>>>> because the error reporting I see on the client is simply an http response
>>>>> code of zero. Before I implemented the cross origin filter, the Firefox
>>>>> instance would behave the same way.
>>>>>
>>>>> Can someone recommend a way to dump the connection values for a
>>>>> servlet, specifically related to cross origin filters, to see what the
>>>>> difference between the two clients might be? I'm using jetty
>>>>> v7.3.0.v20110203.
>>>>>
>>>>> While searching around, I saw this issue:
>>>>>
>>>>> https://bugs.eclipse.org/bugs/show_bug.cgi?id=384847
>>>>>
>>>>> not sure if it's related, because I'm not getting a 500 response - but
>>>>> I wonder if simply updating to the latest version of jetty would help
>>>>> here.
>>>>>
>>>>> Thanks
>>>>>
>>>>> _______________________________________________
>>>>> jetty-users mailing list
>>>>> [email protected]
>>>>> https://dev.eclipse.org/mailman/listinfo/jetty-users
>>>>>
>>>>>
>>>>
>>>> _______________________________________________
>>>> jetty-users mailing list
>>>> [email protected]
>>>> https://dev.eclipse.org/mailman/listinfo/jetty-users
>>>>
>>>>
>>>
>>> _______________________________________________
>>> jetty-users mailing list
>>> [email protected]
>>> https://dev.eclipse.org/mailman/listinfo/jetty-users
>>>
>>>
>>
>> _______________________________________________
>> jetty-users mailing list
>> [email protected]
>> https://dev.eclipse.org/mailman/listinfo/jetty-users
>>
>>
>
_______________________________________________
jetty-users mailing list
[email protected]
https://dev.eclipse.org/mailman/listinfo/jetty-users
