The stuff in javascript/ is there for reference purposes, so we assume some
editing.

That being said, most of these paths should probably be changed to be
relative to the /ifr servlet rather than making any explicit assumptions
about host names and whatnot. At a minimum, we want to avoid hard coding any
host names.

localhost:8080 is where the server runs by default when using the jetty
target. This will of course be different if you're not using jetty, and you
should use whatever is appropriate for your server environment.

~Kevin

On Jan 23, 2008 11:11 AM, Adam Mathias Bittlingmayer <
[EMAIL PROTECTED]> wrote:

> <Pardon me if this question or its answer has already been seen here.>
>
> The docs and several hardcoded partial urls sort of assume that one is
> serving the contents of javascript/ at http://yourhost:yourport/gadgets
>
> For example:
>
> javascript/README:
>    C) Hit the sample container at
>    http://yourserver:yourport/gadgets/samplecontainer/samplecontainer.html
>
> javascript/samplecontainer/samplecontainer.html:
> var specUrl = '
>
> http://localhost:8080/gadgets/samplecontainer/examples/SocialHelloWorld.xml
> ';
>
> javascript/samplecontainer/examples/SocialHelloWorld.xml
> background-image: url(/gadgets/samplecontainer/examples/bubble.gif);
>
> This also implies that it should be served from the same port as the java/
> (the rendering servlet).  Since someone is obviously doing it this way,
> there's no sense making my life hard by changing everything to work with a
>
> different setup especially as changes continue to flow in, so I would like
> to emulate that setup, but it's not immediately obvious to me how (or if
> there is some very simple way to do this).
>
> Thanks and regards,
>
> Adam
>

Reply via email to