ant-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From bugzi...@apache.org
Subject DO NOT REPLY [Bug 8456] New: - EjbJar not finding all dependent classes (Exceptions)
Date Wed, 24 Apr 2002 10:02:21 GMT
DO NOT REPLY TO THIS EMAIL, BUT PLEASE POST YOUR BUG 
RELATED COMMENTS THROUGH THE WEB INTERFACE AVAILABLE AT
<http://nagoya.apache.org/bugzilla/show_bug.cgi?id=8456>.
ANY REPLY MADE TO THIS MESSAGE WILL NOT BE COLLECTED AND 
INSERTED IN THE BUG DATABASE.

http://nagoya.apache.org/bugzilla/show_bug.cgi?id=8456

EjbJar not finding all dependent classes (Exceptions)

           Summary: EjbJar not finding all dependent classes (Exceptions)
           Product: Ant
           Version: 1.5 alpha (nightly)
          Platform: Other
        OS/Version: Other
            Status: NEW
          Severity: Normal
          Priority: Other
         Component: Optional Tasks
        AssignedTo: ant-dev@jakarta.apache.org
        ReportedBy: nigel.magnay@parsec.co.uk


The EjbJar task determines which class files to include in the jar
by a combination of looking at the ejb-jar.xml file to determine the home, 
remote and bean classes, then analysing any superclasses that are also needed.

However, it fails in the circumstance that the remote interface throws an 
exception type which is itself derived from another type within the source. 
This could also be because in this instance, the remote interface is also 
derived from another class within the source.

For Example:
Bean remote interface is: com.newton.cir.cir1.elementrules.ElementRulesRegister.

It's definition is:
-------------------------------------------------------------------
package com.newton.cir.cir1.elementrules;
public interface ElementRulesRegister extends ElementRulesRegisterBusiness, 
javax.ejb.EJBObject {
}

The definition of ElementRulesRegisterBusiness is (truncated):
-------------------------------------------------------------------
package com.newton.cir.cir1.elementrules;

import java.rmi.RemoteException;
import java.rmi.Remote;

public interface ElementRulesRegisterBusiness extends Remote
{
	public String someFunction getAvailableAtoms() throws 
RemoteException,ElementRulesRegisterException;
}

The definition of ElementRulesRegisterException is:
-------------------------------------------------------------------
package com.newton.cir.cir1.elementrules;

import com.newton.cir.CirException;

public class ElementRulesRegisterException extends CirException
{ ...
}

And finally, CirException is defined as:
-------------------------------------------------------------------
package com.newton.cir;

import com.newton.util.j2ee.J2EEException;

public class CirException extends J2EEException
{
...
}

All the above classes are compiled and available.
The ejbjar task neglects to include com.newton.cir.CirException in the EJB Jar,
causing the deployments to fail.

--
To unsubscribe, e-mail:   <mailto:ant-dev-unsubscribe@jakarta.apache.org>
For additional commands, e-mail: <mailto:ant-dev-help@jakarta.apache.org>


Mime
View raw message