[Middlegen-user] Problem with generated localJNDIName

Discussion:

M.-Leander Reimer

2003-01-20 15:31:05 UTC

Hi Aslak,

a problem once again. Sorry! I recently migrated one of our projects to the
latest Middlegen version and a lot has changed (especially in the template)
from the "super old" version I was using up to now. :)

Here is the problem: The code uses the HomeFactory pattern to perform a
lookup using the full qualified class name of the localhome interfaces. I do
specify the jndiPrefix (the value is:
com.techdivision.mtool.ejbcontainer.domain) in the cmp20 task, but the
generated JNDI name now is

com.techdivision.mtool.ejbcontainer.domain/UserLocalHome

instead of

com.techdivision.mtool.ejbcontainer.domain.UserLocalHome

Can't we just include the last separator in the jndiPrefix instead of hard
coding it into the getLocalJNDIName() method?? What do you think?

Thanks!

Leander

-------
M.-Leander Reimer
MSc Computer Science
Dipl.-Inf. (FH)

Techdivision
Kunstmühlstr. 17
83022 Rosenheim

Fon: +49 (0)8031 356 38 32
Fax: +49 (0)8031 356 38 48
Email: ***@techdivision.com
Internet: www.techdivision.com

Aslak Hellesøy

2003-01-20 15:51:07 UTC

Permalink

-----Original Message-----
M.-Leander Reimer
Sent: 20. januar 2003 18:30
Subject: [Middlegen-user] Problem with generated localJNDIName
Hi Aslak,
a problem once again. Sorry! I recently migrated one of our

Don't worry be happy ;-)

projects to the
latest Middlegen version and a lot has changed (especially in the

Latest release (2.0.b1) or CVS HEAD? Sounds like CVS HEAD, but I'm not sure.

template)
from the "super old" version I was using up to now. :)
Here is the problem: The code uses the HomeFactory pattern to perform a
lookup using the full qualified class name of the localhome
interfaces. I do
com.techdivision.mtool.ejbcontainer.domain) in the cmp20 task, but the
generated JNDI name now is
com.techdivision.mtool.ejbcontainer.domain/UserLocalHome
instead of
com.techdivision.mtool.ejbcontainer.domain.UserLocalHome

Why is that a problem? Couldn't you do
jndiprefix="com/techdivision/mtool/ejbcontainer/domain" and get
com/techdivision/mtool/ejbcontainer/domain/UserLocalHome ?

I recently changed from . to / in CVS: http://tinyurl.com/4nuh
Why is explained here: http://tinyurl.com/4num

So Orion chokes on .
Does your container choke on /

If so, we must add another switch, so Middlegen can choose between . and /

What does the EJB spec say about . and /?

Can't we just include the last separator in the jndiPrefix instead of hard
coding it into the getLocalJNDIName() method?? What do you think?

Hmm, that could be done, but it could also break BWC. But maybe it isn't so
bad. Let's hear what others think.

Thanks!
Leander
-------
M.-Leander Reimer
MSc Computer Science
Dipl.-Inf. (FH)
Techdivision
Kunstmühlstr. 17
83022 Rosenheim
Fon: +49 (0)8031 356 38 32
Fax: +49 (0)8031 356 38 48
Internet: www.techdivision.com
-------------------------------------------------------
This SF.NET email is sponsored by: FREE SSL Guide from Thawte
are you planning your Web Server Security? Click here to get a FREE
Thawte SSL guide and find the answers to all your SSL security issues.
http://ads.sourceforge.net/cgi-bin/redirect.pl?thaw0026en
_______________________________________________
middlegen-user mailing list
https://lists.sourceforge.net/lists/listinfo/middlegen-user

M.-Leander Reimer

2003-01-21 08:19:03 UTC

Permalink

No worries anymore, happy again!

I am using CVS head (3 days old or so) at the moment.

I changed my code of the EJBHomeFactory to replace the "." of the class
names with "/", so the lookups work again. Problem solved.

I am using JBoss, and it accepts both, the "." and "/" as separator. The
difference is, that if you use "." JBoss will make one mega long JNDI name.
When you use the "/", you will get a hierarchical JNDI namespace (which I
actually like a lot better now than using ".") :)

I had a look at the EJB spec and I didn't find anything about "recommended"
JNDI names.

But still, if someone decides not to use "." nor "/" to make up his JNDI
names, let's say + (OK a bit far fetched perhaps) he would end up with a
name containing the "/" between the prefix and the bean name, which might
not be "conform" to the desired naming scheme.

Cheers anyway.

Leander

-----Ursprüngliche Nachricht-----
Von: Aslak Hellesøy [mailto:***@netcom.no]
Gesendet: Montag, 20. Januar 2003 18:51
An: M.-Leander Reimer; middlegen-***@lists.sourceforge.net
Betreff: RE: [Middlegen-user] Problem with generated localJNDIName

Don't worry be happy ;-)

projects to the
latest Middlegen version and a lot has changed (especially in the

Latest release (2.0.b1) or CVS HEAD? Sounds like CVS HEAD, but I'm not sure.

Can't we just include the last separator in the jndiPrefix instead of hard
coding it into the getLocalJNDIName() method?? What do you think?

Hmm, that could be done, but it could also break BWC. But maybe it isn't so
bad. Let's hear what others think.