Re: [Xdoclet-user] JNDI_NAME & COMP_NAME

[Hani Suleiman]

Hm, so this behaviour will remain now for any upcoming 1.2 releases? That's rather disheartening. This has worked this way (no Local suffix) since xdoclet 1.1, and all the way up to 11 days ago. I have a fairly huge app with many many ejb's, should I now start the effort to change all ejbrefs to use BlahLocal? Will it remain the way it is currently for the rest of the 1.2 releases?

On Thursday, December 19, 2002, at 11:38 AM, <[EMAIL PROTECTED]> wrote:

----- Original Message -----
From: Hani Suleiman <[EMAIL PROTECTED]>
Date: Thursday, December 19, 2002 3:18 pm
Subject: Re: [Xdoclet-user] JNDI_NAME & COMP_NAME

I still think there's a bug here. There is no way to control what
name
is general in the home util class for the ejb. I realise that it's
the
calling component that has to have the right name, but 3 weeks
ago, the

That's correct, and I have logged it as an issue in JIRA:
http://opensource.atlassian.com/projects/xdoclet/secure/ViewIssue.jspa?
key=XDT-202

This probably won't be fixed until next version (2.x) as it requires
some serious tag changes. COMP name should probably be specified on the
@ejb.ejb-ref tag.

About the bug, read on.

generated COMP_NAME was java:comp/env/ejb prepended onto the ejb
name,
now it seems that what gets specified is some kind of default name
(*Local). This isn't the local name I want. I'm fairly sure it's a
bug
as it used to (in beta1, and halfway through to beta2) work one
way,
and now works another.

Here is where it changed:

http://tinyurl.com/3old

Konstantin?

On Thursday, December 19, 2002, at 07:20 AM, Marcus Brito wrote:

Meyer-Willner, Bernhard wrote:

Anyway, regarding COMP_NAME. THis should work, as required by

the

spec, for
JBoss, though it's a no-no. Currently you can't use COMP_NAME

with

JBoss.
JNDI_NAME always works. I believe JBoss is smart enough though

to

figure out
if you're a local client in the same jar and doesn't really use

JNDI

to do
the lookup then.

Oh, why are you saying COMP_NAME doesn't work with JBoss? Of

course it

works, I'm using it on a daily basis.

What you probably aren't aware of is that the COMP_NAME referers

to a

name in the private java:/comp/env namespace. You need to add an
<ejb-ref> for each bean you need to access in this namespace.

XDoclet

can do this for you, see my previous message about this issue.

--
Pz



-------------------------------------------------------
This SF.NET email is sponsored by: Geek Gift Procrastinating?
Get the perfect geek gift now!  Before the Holidays pass you by.
T H I N K G E E K . C O M      http://www.thinkgeek.com/sf/
_______________________________________________
Xdoclet-user mailing list
[EMAIL PROTECTED]
https://lists.sourceforge.net/lists/listinfo/xdoclet-user

-------------------------------------------------------
This SF.NET email is sponsored by: Geek Gift Procrastinating?
Get the perfect geek gift now!  Before the Holidays pass you by.
T H I N K G E E K . C O M      http://www.thinkgeek.com/sf/
_______________________________________________
Xdoclet-user mailing list
[EMAIL PROTECTED]
https://lists.sourceforge.net/lists/listinfo/xdoclet-user

-------------------------------------------------------
This SF.NET email is sponsored by: Geek Gift Procrastinating?
Get the perfect geek gift now!  Before the Holidays pass you by.
T H I N K G E E K . C O M      http://www.thinkgeek.com/sf/
_______________________________________________
Xdoclet-user mailing list
[EMAIL PROTECTED]
https://lists.sourceforge.net/lists/listinfo/xdoclet-user