Bugs item #608720, was opened at 2002-09-13 13:14 You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=376685&aid=608720&group_id=22866
Category: JBossServer Group: v3.0 Rabbit Hole Status: Open Resolution: None Priority: 5 Submitted By: Anthony Ikeda (akikeda) Assigned to: Dain Sundstrom (dsundstrom) Summary: J2EE EJB Compat with J2EE SDK Server Initial Comment: When running the build template supplied with the JBoss examples pack, the generated Home and remote interfaces have some compatibility problems when deploying the same ejb.jar on the Sun J2EE SDK server (problem with valid RMI-IIOP types). See the TestCase.txt contained in the jar file for more details. NOTE: This jar is only an archive of non-java files not a java executable. Anthony ---------------------------------------------------------------------- >Comment By: Anthony Ikeda (akikeda) Date: 2002-09-18 09:39 Message: Logged In: YES user_id=610611 I had a similar problem with the entityPK.j file in version xdoclet 1.1.2. The datatypes it was using for the hashcode were primitives. Cheers, Anthony ---------------------------------------------------------------------- Comment By: Anthony Ikeda (akikeda) Date: 2002-09-18 09:34 Message: Logged In: YES user_id=610611 EJBDoclet is adding new variables (COMP_NAME and JNDI_NAME) to the home interface which J2EE SDK doesn't seem to like. Apparently they are not valid RMI-IIOP types? If I remove these fields after the ejb doclet generation and recreate the jar it works fine. To remove them from the actual ejbdoclet process, the: xdoclet.modules.ejb.home.resources.home.xdt file needs to be edited to prevent these variables to be added (unless there is an ejbdoclet attribute to prevent it?). Or is it a sun bug instead? Cheers, Anthony ---------------------------------------------------------------------- Comment By: Dain Sundstrom (dsundstrom) Date: 2002-09-18 07:25 Message: Logged In: YES user_id=251431 The Sun J2EE SDK server is not a test kit. They may have gotten the spec wrong. Then again we maybe we got it wrong. Anyway, what exactally is the SDK complaining about? Have you tried hacking the code by hand to see what you need to change to fix this? ---------------------------------------------------------------------- You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=376685&aid=608720&group_id=22866 ------------------------------------------------------- This SF.NET email is sponsored by: AMD - Your access to the experts on Hammer Technology! Open Source & Linux Developers, register now for the AMD Developer Symposium. Code: EX8664 http://www.developwithamd.com/developerlab _______________________________________________ Jboss-development mailing list [EMAIL PROTECTED] https://lists.sourceforge.net/lists/listinfo/jboss-development