This worked for me (of course) and my problem with the JNDI name went away.

Hopefully this jar will be included as part of the 3.2 release.

I am now having a new problem:

An unhandled exception of type 'System.Web.Services.Protocols.SoapException' occurred in system.web.services.dll

Additional information: java.io.IOException: No serializer found for class com.fiserv.banklink.iLink.PositivePay.interfaces.CheckData in registry [EMAIL PROTECTED]

How do I include/create this serializer in the registry? the class is being generated by XDoclet...


N



At 04:38 PM 3/25/2003 +0100, you wrote:
I guess that the xdoclet module is not automatically part of the distro ....
 
So you need to build it as a part of the jboss.net build
 
cd jboss.net
build
 
it is then generated into output/lib/
 
CGJ
 
-----Ursprüngliche Nachricht-----
Von: Nathan Hoover [mailto:[EMAIL PROTECTED]]
Gesendet: Dienstag, 25. März 2003 16:04
An: [EMAIL PROTECTED]
Betreff: Re: AW: AW: [JBoss-user] JBoss.NET error

I have 3.2RC4, which was released on Sunday. Shouldn't I have the right code?

How can I get just the XDoclet module without rebuilding JBoss in its entirety?

N


At 03:33 PM 3/25/2003 +0100, you wrote:
this bug has been resolved in the 3.2 branch last week. If you get the latest sources, it should not occur anymore.
-----Ursprüngliche Nachricht-----
Von: Nathan Hoover [mailto:[EMAIL PROTECTED]]
Gesendet: Dienstag, 25. März 2003 14:33
An: [EMAIL PROTECTED]
Betreff: Re: AW: [JBoss-user] JBoss.NET error

You're totally right, the bean is not being hit at all, and it's due to the web-service.xml. I had updated the bean to have both remote and local interfaces since the last time it was working. The problem seems to be a bug in the XDoclet code that generates the web-service.xml - this is what's generated:
<parameter name="beanJndiName" value="ejb/iLink/PositivePay/Facadecomp/env/ejb/iLink/PositivePay/Facade"/>
It has concatenated the local and remote JNDI names of my EJB. Can you confirm that this is a bug? If so, how do I go about submitting it?
Nathan


At 09:07 AM 3/25/2003 +0100, you wrote:
It does not look like your session bean is called at all. What is your global JNDI name of your session bean and how does your
web-service.xml look like? Looks like there is a name "Facadecomp" in your web-service.xml referenced?
 
CGJ
 
 
-----Ursprüngliche Nachricht-----
Von: Nathan Hoover [mailto:[EMAIL PROTECTED]]
Gesendet: Montag, 24. März 2003 15:53
An: [EMAIL PROTECTED]
Betreff: [JBoss-user] JBoss.NET error

I'm getting the following error trying to call a session bean method using JBoss.NET. I have 3.2RC4.
An unhandled exception of type 'System.Web.Services.Protocols.SoapException' occurred in system.web.services.dll
Additional information: org.apache.axis.ConfigurationException: Could not find home in JNDI
AxisFault
 faultCode: {http://xml.apache.org/axis/}Server.generalException
 faultString: Could not find home in JNDI
 faultActor: null
 faultDetail:
Could not find home in JNDI
javax.naming.NameNotFoundException: Facadecomp not bound
        at org.jnp.server.NamingServer.getBinding(NamingServer.java:495)
        at org.jnp.server.NamingServer.getBinding(NamingServer.java:503)
        at org.jnp.server.NamingServer.getObject(NamingServer.java:509)
        at org.jnp.server.NamingServer.lookup(NamingServer.java:253)
        at org.jnp.server.NamingServer.lookup(NamingServer.java:256)
        at org.jnp.server.NamingServer.lookup(NamingServer.java:256)
        at org.jnp.server.NamingServer.lookup(NamingServer.java:256)
        at org.jnp.interfaces.NamingContext.lookup(NamingContext.java:492)
        at org.jnp.interfaces.NamingContext.lookup(NamingContext.java:471)
        at javax.naming.InitialContext.lookup(InitialContext.java:345)
        at org.jboss.net.axis.server.EJBProvider.getEJBHome(EJBProvider.java:94)
        at org.jboss.net.axis.server.EJBProvider.getEJBCreateMethod(EJBProvider.java:107)
        at org.jboss.net.axis.server.EJBProvider.getServiceClass(EJBProvider.java:168)
        at org.apache.axis.providers.java.JavaProvider.initServiceDesc(JavaProvider....java:535)
<snip>
The session bean is trying to make a local call to an entity bean. Let me know if I can provide more information or if anyone has any ideas.

N

###########################################

This message has been scanned by F-Secure Anti-Virus for Microsoft Exchange.
For more information, connect to http://www.F-Secure.com/

###########################################

This message has been scanned by F-Secure Anti-Virus for Microsoft Exchange.
For more information, connect to http://www.F-Secure.com/


###########################################

This message has been scanned by F-Secure Anti-Virus for Microsoft Exchange.
For more information, connect to http://www.F-Secure.com/

Reply via email to