So
what,
Look
in your generated web-service.xml. If there is an element
<typeMapping
qname="PPFacade"
type="java:com.fiserv.banklink.iLink.PositivePay.interfaces.CheckDataSoap"
serializer="org.apache.axis.encoding.ser.BeanSerializerFactory"
deserializer="org.apache.axis.encoding.ser.BeanDeserializerFactory"
encodingStyle="http://schemas.xmlsoap.org/soap/encoding/"/>
then you did everything right. If there is no such section then I guess that you most likely to forgot to include that class into the fileset processed by xdoclet.
One thing that you cannot expect from OSS (unless
buying the excellent support of JBoss Group) is that somebody sits beside you on your desktop and holds your hands and
debugs your ant scripts. A minimum understanding of web-services
is still required if you want to
implement those. Thats why I suggest everyone to RTFAxisM,
first.
Once
Jboss4 comes out and J2EE1.4 is a common standard, there will be common patterns
that everybody knows about, but in the meantime I rather concentrate on getting
these specs implemented before making the tools fool-proof. If you want to share
your experiences, you are welcome to contribute some doco and helpful code.
Either you can help to setup the grain, or you will have to choose a commercial
product with a proprietary approach (good luck, then!).
-----Urspr�ngliche Nachricht-----I am still getting "java.io.IOException: No serializer found for class com.fiserv.banklink.iLink.PositivePay.interfaces.CheckDataSoap", even with having created the subclass and adding the @jboss-net tag. What to do?
Von: Nathan Hoover [mailto:[EMAIL PROTECTED]
Gesendet: Donnerstag, 27. M�rz 2003 06:47
An: [EMAIL PROTECTED]
Betreff: [JBoss-user] JBoss.NET can't find serializer
I get the feeling I am "working against the grain", so to speak. This has to be a common pattern, returning data objects from beans. Is there a better way that I am missing?
Thanks
Nathan
At 11:47 PM 3/26/2003, you wrote:
Never mind, this was just idiocy on my part. I had never seen JBoss' not-found error before, and I didn't realize that someone had dropped the table (and consequently my row).
It's still not working, but I'm working through the errors.
N
At 10:57 PM 3/26/2003, you wrote:
So, I created a class like so:
which extends the CheckData class generated by XDoclet.
- package com.fiserv.banklink.iLink.PositivePay.interfaces;
- /**
- * SOAP-capable Data object for Check.
- * @copyright BANKLINK 2003
- * @author Nathan Hoover
- * @jboss-net:xml-schema urn="PPFacade"
- */
- public class CheckDataSoap extends CheckData {}
Now I no longer receive the IOException and instead get the following new and interesting error:
"javax.ejb.TransactionRolledbackLocalException: Failure while creating a generator session bean: No such entity!; CausedByException is:Failure while creating a generator session bean: No such entity!"
Thanks again for your help,
Nathan
At 10:37 AM 3/26/2003, you wrote:
I had envisioned an answer like this, and I thought it through already.
I will just subclass the "CheckData" class generated by XDoclet and drop that line in the top.
Thanks for your help!
N
At 10:18 AM 3/26/2003, you wrote:
Nathan,
for beans/value classes that you like to serialize, you have to add
@jboss-net:xml-schema urn="QNAME"
in order to get them mapped in the web-service.xml
Unfortunately, this will be a problem if the classes are generated by xdoclet. Can you try to add such a line to the header of the
source (entity-bean?) that xdoclet uses to generate the value class? If you manage that it gets copied to the
bean javadoc header and let it processed by jboss-net-xdoclet, then you have reached your goal.
CGJThe 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.
- -----Urspr�ngliche Nachricht-----
- Von: Nathan Hoover [mailto:[EMAIL PROTECTED]]
- Gesendet: Dienstag, 25. M�rz 2003 20:40
- An: [EMAIL PROTECTED]
- Betreff: Re: AW: AW: AW: [JBoss-user] JBoss.NET error
- 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>
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/ ###########################################
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/
