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=21543>. 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=21543 <ejbjar> should also produce EJB client files Summary: <ejbjar> should also produce EJB client files Product: Ant Version: 1.5.3 Platform: Other OS/Version: Windows XP Status: NEW Severity: Enhancement Priority: Other Component: Optional Tasks AssignedTo: [EMAIL PROTECTED] ReportedBy: [EMAIL PROTECTED] I use the <ejbjar> task to JAR EJBs. It works well. What I also do is <jar> up the remote and home interfaces and related classes (like exception classes and data transfer classes) in a separate JAR for clients of these EJBs. They don't get the "full" EJB JAR because I don't want the clients to get the EJB implementations. Now since the <ejbjar> already parses the EJBs and finds out through bcel (sp?) which classes are needed, I suggest that the <ejbjar> could optionally produce an EJB client JAR with all the files that are needed just by EJB clients. Essentially, this could be the "full EJB JAR" minus the bean implementation classes and the classes that are only needed by the bean implementation. --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
