On Wed, Sep 16, 2009 at 7:05 AM, paulbrickell
wrote:
> If I create a url with a context relative path (e.g. /x/y/z) and the I use
> this in the url attribute of an import tag, the import tag seems to attempt
> a lookup of a file in the web application.
>
> So given this...
>
>
> ${aURL} Get reso
Hassan,
If I create a url with a context relative path (e.g. /x/y/z) and the I use
this in the url attribute of an import tag, the import tag seems to attempt
a lookup of a file in the web application.
So given this...
${aURL} Get resource at z
The link in href attribute in the browser is a
On Wed, Sep 16, 2009 at 12:43 AM, paulbrickell
wrote:
> Agreed. Just doesn't work.
? Uh, "doesn't work" exactly how?
This
sets `xmlURL` to a very different value compared to your original
What's the exact error?
--
Hassan Schroeder hassan.schroe...@gmail.com
Hassan,
Agreed. Just doesn't work.
Hassan Schroeder-2 wrote:
>
> On Tue, Sep 15, 2009 at 1:48 AM, paulbrickell
> wrote:
>>
>> Does anyone know how to use the import tag to access dynamic content from
>> the
>> current context?
>
>> I found this...
>>
>> > value="${pageContext.request.scheme}
On Tue, Sep 15, 2009 at 1:48 AM, paulbrickell
wrote:
>
> Does anyone know how to use the import tag to access dynamic content from the
> current context?
> I found this...
>
> value="${pageContext.request.scheme}://${pageContext.request.serverName}:${pageContext.request.serverPort}${pageContext.