Haruki, what exactly would you want in the generated code?
In most of the examples I've come across for the
ServiceLocator pattern, it's just a utility class that does
generic JNDI lookups for different types of references
(MailSessions, DataSources, EJB home interfaces,
MessageQueues), looked up in the context of the EJB that's
using it based on a name the EJB passes to it; nothing
that's specific to a particular EJB(s) that uses it.
Perhaps you could upload a sample of what you're wanting it
to produce?
If you would like to refer to this comment somewhere else in this project, copy and paste the following link:
Logged In: YES
user_id=247081
Haruki, what exactly would you want in the generated code?
In most of the examples I've come across for the
ServiceLocator pattern, it's just a utility class that does
generic JNDI lookups for different types of references
(MailSessions, DataSources, EJB home interfaces,
MessageQueues), looked up in the context of the EJB that's
using it based on a name the EJB passes to it; nothing
that's specific to a particular EJB(s) that uses it.
Perhaps you could upload a sample of what you're wanting it
to produce?
Logged In: YES
user_id=247081
Last chance to tell us just what you'd want it to generate,
before SF automatically deletes the issue...