The jar manifest spec doesn't preclude a reference to the current directory. It is our deployer logic that is looping when it sees the '.'. We need to be validating that references are not causing duplicate deployments.
xxxxxxxxxxxxxxxxxxxxxxxx Scott Stark Chief Technology Officer JBoss Group, LLC xxxxxxxxxxxxxxxxxxxxxxxx ----- Original Message ----- From: "David Jencks" <[EMAIL PROTECTED]> To: <[EMAIL PROTECTED]> Sent: Wednesday, May 29, 2002 7:37 AM Subject: Re: [JBoss-user] Re: jpos1.4.0.jar causes infinite recursion in Main Deployer under RC2 and RC3 > The crucial clue is perhaps this log line: > 11:58:24,774 INFO [MainDeployer] Starting deployment of package: > file:/C:/bin/jboss-3.0.0RC2TB/lib/ > > which indicates that jboss is now trying to deploy the lib directory as a > package. This will result in an infinite loop when it gets back to the > jpos jar. Indeed it is "correctly" interpreting . as "the current (parent) > directory". Offhand I can't think of any situation where this behavior is > reasonable. > > Can you check the spec on the manifest classpath to see if it specifies or > prohibits or doesn't talk about this behavior? If it prohibits or doesn't > mention this please file a bug report on sourceforge. > > Thanks > david jencks > > > On 2002.05.29 07:30:12 -0400 Jonathan.O'[EMAIL PROTECTED] wrote: > > Whew, > > I found the problem and the solution is easy! But, JBoss should watch for > > > > this. > > > > The manifest file had the following line: > > Class-path: jmxri.jar xalan_2_0_0.jar xerces_1_2_3.jar . > > > > That last little "." is the cause of all the problems. I presume what > > happens is that when JBoss doesn't find xalan_2_0_0.jar and > > xerces_1_2_3.jar it starts searching the current directory. It then finds > > > > it hasn't loaded jpos1.4.0.jar, and we're off again on the merry go > > round. > > > > The temporary solution is easy: just remove the scurillous little dot, > > and > > repackage the jar. > > > > However, I think this should be a low priority bug to be fixed in the > > deployer. What say you all? > > Ciao, > > Jonathan O'Connor > > Ph: +353 1 872 3305 > > Mob: +353 86 824 9736 > > Fax: +353 1 873 3612 > > > > <br><font size=2 face="sans-serif">Whew,</font> > > <br><font size=2 face="sans-serif">I found the problem and the solution > > is easy! But, JBoss should watch for this.</font> > > <br> > > <br><font size=2 face="sans-serif">The manifest file had the following > > line:</font> > > <br><font size=2 face="Courier New">Class-path: jmxri.jar xalan_2_0_0.jar > > xerces_1_2_3.jar .</font> > > <br> > > <br><font size=2 face="sans-serif">That last little "." is the > > cause of all the problems. I presume what happens is that when JBoss > > doesn't find xalan_2_0_0.jar and xerces_1_2_3.jar it starts searching the > > current directory. It then finds it hasn't loaded jpos1.4.0.jar, and > > we're off again on the merry go round.</font> > > <br> > > <br><font size=2 face="sans-serif">The temporary solution is easy: just > > remove the scurillous little dot, and repackage the jar.</font> > > <br> > > <br><font size=2 face="sans-serif">However, I think this should be a low > > priority bug to be fixed in the deployer. What say you all?<br> > > Ciao,<br> > > Jonathan O'Connor<br> > > Ph: +353 1 872 3305<br> > > Mob: +353 86 824 9736<br> > > Fax: +353 1 873 3612</font> > > _______________________________________________________________ > > Don't miss the 2002 Sprint PCS Application Developer's Conference > August 25-28 in Las Vegas -- http://devcon.sprintpcs.com/adp/index.cfm > > _______________________________________________ > JBoss-user mailing list > [EMAIL PROTECTED] > https://lists.sourceforge.net/lists/listinfo/jboss-user > _______________________________________________________________ Don't miss the 2002 Sprint PCS Application Developer's Conference August 25-28 in Las Vegas -- http://devcon.sprintpcs.com/adp/index.cfm _______________________________________________ JBoss-user mailing list [EMAIL PROTECTED] https://lists.sourceforge.net/lists/listinfo/jboss-user
