Thanks for clearing that up Marcus, My lack of knowledge is showing!!! Oisin
-----Original Message----- From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED]] On Behalf Of Marcus Brito Sent: 29 January 2003 17:45 To: [EMAIL PROTECTED] Subject: Re: [Xdoclet-user] Re: Different util classes being created depending on Bean Type Oisin Kim wrote: > Hi All, > I've found a simple solution (of sorts) to my problem, simply put > > @ejb.util > generate="physical" > > In the bean tags, which should make the util object use the > generated.LocalHome.JNDI_NAME always instead of the > generated.LocalHome.COMP_NAME > > This will allow you to test beans from the web tier as the util always > uses the JNDI lookup. You can also override this as a global option instead of indicating it in every bean. Just use <utilobject kind="physical"/> in your build file. > Not as efficent as the solution which uses JNDI_NAME as a backup in > event of COMP_NAME (JNDI ENC) failure but it works! I don't think the util object should do any failure recover. If a name lookup fails, there *is* something wrong, and it shouldn't try to guess why it has failed. And guess what, some servers, like Borland BES, doesn't even bind local beans in the global JNDI scope. That's java:comp name or nothing (or at least I haven't found another way so far). -- MB ------------------------------------------------------- This SF.NET email is sponsored by: SourceForge Enterprise Edition + IBM + LinuxWorld = Something 2 See! http://www.vasoftware.com _______________________________________________ xdoclet-user mailing list [EMAIL PROTECTED] https://lists.sourceforge.net/lists/listinfo/xdoclet-user ------------------------------------------------------- This SF.NET email is sponsored by: SourceForge Enterprise Edition + IBM + LinuxWorld = Something 2 See! http://www.vasoftware.com _______________________________________________ xdoclet-user mailing list [EMAIL PROTECTED] https://lists.sourceforge.net/lists/listinfo/xdoclet-user
