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 the parent of the scoped CL and lets put the scoped CL as default" and that should really help (I think). marcf PS: Sorry I am lazy this weekend and didn't do much work on RH so I won't get to integration by monday. It is on my priority list right when I am done with the invocation layer. |-----Original Message----- |From: [EMAIL PROTECTED] |[mailto:[EMAIL PROTECTED]]On Behalf Of |Julian Gosnell |Sent: Sunday, November 25, 2001 10:20 AM |To: [EMAIL PROTECTED] |Cc: [EMAIL PROTECTED] |Subject: [JBoss-dev] EAR classpath access.... | | | |Is this available to the Jetty integration anywhere. | |It is not enough simply to be passed the classloader because I |need to make up a classpath for the java compiler so I can |compile JSPs on the fly. | |Currently Jetty only knows about classes/jars stored in the war |module. If classes/jars are deployed in the ear above, I |have no way of knowing (without navigating the filesystem) what they are. | |I would rather not have to repeat what someone else has already worked out. | |Is there anyway for me to get hold of this information ? | |Who should I talk to about agreeing how I might get hold of it ? | |Thanks, | | |Jules | | | |_________________________________________________________ |Do You Yahoo!? |Get your free @yahoo.com address at http://mail.yahoo.com | | |_______________________________________________ |Jboss-development mailing list |[EMAIL PROTECTED] |https://lists.sourceforge.net/lists/listinfo/jboss-development _______________________________________________ Jboss-development mailing list [EMAIL PROTECTED] https://lists.sourceforge.net/lists/listinfo/jboss-development
