[
https://issues.apache.org/jira/browse/SHINDIG-317?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Cassie Doll closed SHINDIG-317.
-------------------------------
Resolution: Invalid
Assignee: Cassie Doll
This bug is no longer applicable.
> stop hardcoding the context path /social/rest in java source files
> ------------------------------------------------------------------
>
> Key: SHINDIG-317
> URL: https://issues.apache.org/jira/browse/SHINDIG-317
> Project: Shindig
> Issue Type: Improvement
> Components: RESTful API (Java)
> Reporter: David Primmer
> Assignee: Cassie Doll
>
> Moved from shindig-267
> Vasu Nori - 15/May/08 09:17 AM Cassie your patch looks good. but I think this
> test could be a major nuisance for shindig developers because of the way
> Jetty is being run. RunJettyServer hardcodes the context path, abdera
> provider name, servlet name etc which are already declared in web.xml. If
> anyone changes these params in web.xml, this test will fail and people will
> find it difficult to debug it. Until we figure out how to run Jetty correctly
> (by reading params from web.xml), I don't think we should check it in..
> David Primmer - 16/May/08 05:00 PM
> I've done some research on manually loading a web.xml with jetty and there
> are methods to do it. I tried to make it work recently but it was a near
> miss. I think this is the way to go if the filesystem stuff can work.
> http://www.mortbay.org/jetty-6/apidocs/org/mortbay/jetty/webapp/WebAppContext.html#setDescriptor(java.lang.String)
> You can create a webapp context and point it at a web.xml file. If I knew
> how to locate the desired file on the file system I think this would solve
> the problem.
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
