PROTECTED] Sent: Thursday, March 04, 2004
11:35 AMTo: '[EMAIL PROTECTED]'Subject: RE: EJB
Authentication
I
use the default BeanDeserializer. I am attaching the Client code and also the
generated code for this bean.
Thanks,
Ramesh.
-Original Message-
Title: EJB Authentication
I
modified my client to use the static apis and it seems to work. Can anyone tell
me what wrong with my dynamic calls?
The
code that worked:
OAMPServiceManagerService sms = new
OAMPServiceManagerServiceLocator();
OAMPServiceManager smgr
Title: EJB Authentication
I use
the default BeanDeserializer. I am attaching the Client code and also the
generated code for this bean.
Thanks,
Ramesh.
-Original Message-From: Hari Lakshmanan
[mailto:[EMAIL PROTECTED]Sent: Thursday, March 04, 2004 11:26
AMTo: [EMAIL
can you post your client code and deserializer code?
-Original Message-
From: Bobba, Ramesh [mailto:[EMAIL PROTECTED]
Sent: Thu 3/4/2004 11:01 AM
To: '[EMAIL PROTECTED]'
Cc:
Subject: RE: EJB Auth
Title: EJB Authentication
Hi,
I got
this working (kinda) in the sense that the server works fine. It executes the
ejb methods and returns a soap message (according to what I see in the logs),
but on the client side I get an AxisFault saying: Dose anyone know why? I have
all the generated
rom: Bobba, Ramesh [mailto:[EMAIL PROTECTED]
Sent: Thu 04/03/2004 16:59
To: '[EMAIL PROTECTED]'
Cc:
Subject: RE: EJB Authentication
Hi Keith,
I am using Weblogic right now (we also plan to support websphere). I am a
Title: EJB Authentication
Hi
Keith,
I am
using Weblogic right now (we also plan to support websphere). I am a bit
confused about what you mean by - replicating EJB security constraints on the
Axis servlet. Are you talking about adding the
somerole
elements?
Thanks,
Ramesh
cally presents the
right username/password settings to the EJB container.
Hope this helps
Keith
-Original Message-
From: Bobba, Ramesh [mailto:[EMAIL PROTECTED]
Sent: Thu 04/03/2004 00:49
To: Axis-User (E-mail)
Cc:
Subject: EJB Authentic
Hi,
I get an java.rmi.AccessException exception because the EJBs that the
WebService implementation class is trying to use are username/password
protected. We were using weblogic and with that, the client was able to
authenticate by making call:
call.setProperty("javax.xml.rpc.security.auth.usern
