On Wed, Mar 14, 2012 at 2:18 PM, John Arthorne
<John_Arthorne@xxxxxxxxxx> wrote:
Sorry, extension point information gets
cached. You can restart with the -clean command line argument to force
discarding cache and reparsing the plugin registry.
Thanks, I can now force the server to fail by having a syntax error in the plugin.xml. ;-)
However, the CORS call still does not work.
I see in the filter source lines like
Log.debug("Cross-origin filter configuration: " +
is there a way to tell Orion to print the log messages?
jjb
John A
03/14/2012 03:52 PM |
|
To
| Orion developer discussions <orion-dev@xxxxxxxxxxx>
|
|
cc
|
|
|
Subject
| Re: [orion-dev] *SPAM* Re: Using
Sites with Orion |
|
On Wed, Mar 14, 2012 at 10:46 AM, John Arthorne <John_Arthorne@xxxxxxxxxx>
wrote:
Not sure exactly what files you need,
but you could access the orion server projects and files using the Orion
plugin registry and the "orion.core.file" service. fileClient.js
provides a convenience API to talk to a file system on another server via
a plugin.
As for configuring the servlet filter, it happens via an Eclipse extension
point on the server. The bundle org.eclipse.orion.server.configurator has
a plugin.xml file that defines all the servlets.
I edited the file eclipse/plugins/org.eclipse.orion.server.configurator_0.4.0v20120117-2012/plugin.xml
but nothing changes. I tried guessing the syntax and I
tried the lines directly from the wiki page. But also if I add a single
angle bracket to create an error, the server comes up with no extra error
message. So I don't think the file is being read.
Any hints?
jjb
The syntax is a bit different from the
web.xml on that wiki page, but here is an example of a filter we register
that includes parameters that shows the pattern:
<filter
alias="/"
class="org.eclipse.orion.server.configurator.servlet.WelcomeFileFilter">
<init-param
name="includes"
value="/">
</init-param>
</filter>
John A
Orion uses Jetty 8 and Jetty 8 supports CORS:
http://wiki.eclipse.org/Jetty/Feature/Cross_Origin_Filter
So in theory I could configure the jetty server to allow localhost as
well as 127.0.0.*,... if I knew how the jetty config worked in Orion.
Anyone know how?
Also in theory I could configure it to allow the login credential for
127.0.0.* to be sent with the request. The documentation on this seems
very limited however.
jjb
On Tue, Mar 13, 2012 at 4:44 PM, John J Barton
<johnjbarton@xxxxxxxxxxxxxxx>
wrote:
> I am serving my web app out of an Orion site, it runs on
> http://127.0.0.2:8080.
But when it comes time to read Orion files, my
> XHR fails because the Orion files are on http://localhost:8080,
and
> that is interpreted as cross-origin.
>
> I guess I can put my app and the app I am debugging on the same Site,
> but that's a real hack.
>
> Other suggestions?
>
> jjb
> _______________________________________________
> orion-dev mailing list
> orion-dev@xxxxxxxxxxx
> https://dev.eclipse.org/mailman/listinfo/orion-dev
_______________________________________________
orion-dev mailing list
orion-dev@xxxxxxxxxxx
https://dev.eclipse.org/mailman/listinfo/orion-dev
_______________________________________________
orion-dev mailing list
orion-dev@xxxxxxxxxxx
https://dev.eclipse.org/mailman/listinfo/orion-dev
_______________________________________________
orion-dev mailing list
orion-dev@xxxxxxxxxxx
https://dev.eclipse.org/mailman/listinfo/orion-dev
_______________________________________________
orion-dev mailing list
orion-dev@xxxxxxxxxxx
https://dev.eclipse.org/mailman/listinfo/orion-dev
