jspc

[Kevin Jones <ke...@develop.com>]

Somebody answered my questions about this a couple of days ago, thanks.

Using jspc I can compile 'simple' JSPs but if I have a page with a taglib on
jspc throws its hands up in the air in horror. It says it can't find the
taglib, which is in the same place as the jsp, which is in the directory i'm
running jspc from.

Ideas anyone?

Kevin Jones
DevelopMentor

RE: jspc

[Kevin Jones <ke...@develop.com>]

OK,

I'll run a series of tests and then do a post to the bug list,

Kevin Jones
DevelopMentor

> -----Original Message-----
> From: Danno Ferrin [mailto:shemnon@earthlink.net]
> Sent: 02 March 2000 16:31
> To: general@jakarta.apache.org
> Subject: Re: jspc
>
>
> This is a case that needs to be put in the bug list, please post it and
> most importantly the part of the file including the taglib directive,
> the directory structure, and how the taglib is deployed (jar/uri to
> tld/tld in web.xml).
>
>
> What you may be seeing is how JspC determines the document root, it is
> geared heavily towards webapps.   All uris are resolved against some
> root considering the working dir in some base, this may be where the bug
> is.  If no -uriroot is specified JspC will go up the directory tree
> until it finds a directory that contains a directory named WEB-INF, this
> is so it can load web-app classes and libraries.  If it walks all the
> way to the top without success it will then use the working dir for the
> uriroot.  This also has an impact on absolute naming of the taglib, but
> shouldn't affect relative naming.  However I do not believe that the
> uribase is adjusted appropriately.
>
> --Danno
>
> Kevin Jones wrote:
> >
> > Somebody answered my questions about this a couple of days ago, thanks.
> >
> > Using jspc I can compile 'simple' JSPs but if I have a page
> with a taglib on
> > jspc throws its hands up in the air in horror. It says it can't find the
> > taglib, which is in the same place as the jsp, which is in the
> directory i'm
> > running jspc from.
> >
> > Ideas anyone?
> >
> > Kevin Jones
> > DevelopMentor
> >
> > ---------------------------------------------------------------------
> > To unsubscribe, e-mail: general-unsubscribe@jakarta.apache.org
> > For additional commands, e-mail: general-help@jakarta.apache.org
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: general-unsubscribe@jakarta.apache.org
> For additional commands, e-mail: general-help@jakarta.apache.org

Re: jspc

[Danno Ferrin <sh...@earthlink.net>]

This is a case that needs to be put in the bug list, please post it and
most importantly the part of the file including the taglib directive,
the directory structure, and how the taglib is deployed (jar/uri to
tld/tld in web.xml).  


What you may be seeing is how JspC determines the document root, it is
geared heavily towards webapps.   All uris are resolved against some
root considering the working dir in some base, this may be where the bug
is.  If no -uriroot is specified JspC will go up the directory tree
until it finds a directory that contains a directory named WEB-INF, this
is so it can load web-app classes and libraries.  If it walks all the
way to the top without success it will then use the working dir for the
uriroot.  This also has an impact on absolute naming of the taglib, but
shouldn't affect relative naming.  However I do not believe that the
uribase is adjusted appropriately.

--Danno

Kevin Jones wrote:
> 
> Somebody answered my questions about this a couple of days ago, thanks.
> 
> Using jspc I can compile 'simple' JSPs but if I have a page with a taglib on
> jspc throws its hands up in the air in horror. It says it can't find the
> taglib, which is in the same place as the jsp, which is in the directory i'm
> running jspc from.
> 
> Ideas anyone?
> 
> Kevin Jones
> DevelopMentor
> 
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: general-unsubscribe@jakarta.apache.org
> For additional commands, e-mail: general-help@jakarta.apache.org