|I think that the best that we can do is to make a best effort approach
|to determine a file classpath that we can pass to the JspServlet.
|We should also provide good override mechanisms to allow a deployer (or ear
|developer) to explicitly set the classpath passed to the JspServlet
but in the
unday, November 25, 2001 5:23 PM
|To: marc fleury
|Cc: Anatoly Akkerman; Dain Sundstrom; Julian Gosnell;
|[EMAIL PROTECTED]
|Subject: Re: [JBoss-dev] EAR classpath access
|
|
|
|I can't see how we can get java compilers to use our classloaders
|without actually modifying the javac compilers.
I can't see how we can get java compilers to use our classloaders
without actually modifying the javac compilers. Ant does not
do this - it passed a classpath that you have specified in the
build.xml
The fundamental problem is that JSPs are not well designed when it comes
to deployment, as you
|Yeap, jikes is not java -- it is C++. Also, it may very well be so that
|even Sun's compiler can't do this. In Tomcat they configure a command line
|for sun.tools.javac which has a special -classpath switch. Don't know if
|the jvm uses it or javac itself reads the entries in the classpath and
|lo
> >
> > Sounds like a great idea, you need to call the
> > getResourceAsStream on it,
> >
> > why don't you look into it?
> >
> > marcf
>
> This won't work for an out-of-process compiler such as jikes.
Yeap, jikes is not java -- it is C++. Also, it may very well be so that
even Sun's compil
> |Tomcat has a similar problem, though, it seems it is even worse. The
> |invocation of javac to compile the jsps sets up the path to
> the WAR and
> |standard java classes and does not use the classloader, so
> you would have
> |to do something that David Jencks proposes, namely, get the
> UR
|Tomcat has a similar problem, though, it seems it is even worse. The
|invocation of javac to compile the jsps sets up the path to the WAR and
|standard java classes and does not use the classloader, so you would have
|to do something that David Jencks proposes, namely, get the URLs from the
|clas
OK ok
look class visibility is something we can solve easily with the cl
integration, so
either
1- pass teh ear ref from the deployer on down,
2- wait for the integration.
david, if you read this "integration" is a big word that says "in the first
iteration let just set the system SL to be
Tomcat has a similar problem, though, it seems it is even worse. The
invocation of javac to compile the jsps sets up the path to the WAR and
standard java classes and does not use the classloader, so you would have
to do something that David Jencks proposes, namely, get the URLs from the
classloa
I'm not sure how this works currently. I'm working on a revision in which
everything in a package gets put into a URLClassLoader after unpacking. If
you got this classloader could you call getURLs() on it and turn the URLs
into Files? (they will all be local copies). I haven't gotten to the j2e
10 matches
Mail list logo
