Re: [JBoss-user] JBoss-net with complex type (no serializer found)
Its deprecated because you cannot determine the same quality of information via pure reflection currently as you can by generating stubs from a wsdl file. However, this is just an implementation detail that can be overcome using JavaBean BeanInfos for example, or JSR175 metadata in the future. -- Scott Stark Chief Technology Officer JBoss Group, LLC Heinz-Dieter Conradi wrote: As you may observe from my response, i am myself not really sure what i am doing here. however, at least in my case it seems to work ;-) for e.g. i am not sure how to configure a axis, since i am using the (deprecated) AxisInvocationHandler. i do not know why it is deprecated, but it allows me to work with the remote EJBObject's in almost the same way as directly calling EJB. good look, heinz-dieter conradi --- This sf.net email is sponsored by:ThinkGeek Welcome to geek heaven. http://thinkgeek.com/sf ___ JBoss-user mailing list [EMAIL PROTECTED] https://lists.sourceforge.net/lists/listinfo/jboss-user
Re: [JBoss-user] JBoss-net with complex type (no serializer found)
hi stephan,
>
> I am trying to rollout our application to JBoss.NET instead of a separate
> Axis.war
> I am running xdoclet 1.2b2, JBoss 3.2.2RC4 under redhat 9
>
some days ago, i had the same problem. i solved it by looking into the
jboss-net testsuite which is distributed with the sources.
>
> My session bean (the one exposed as web service is):
>
> * @ejb.bean type="Stateless"
> * name="NodeSyncher"
> *
> * @ejb.transaction type="Required"
> *
> * @jboss-net.web-service urn="NodeSynchService"
> */
> public class NodeSyncherBean implements javax.ejb.SessionBean {
>
>
> My LoginResponse is:
>
> *
> * @jboss-net.xml-schema urn="kserver:LoginResponse"
> *
> public class LoginResponse implements java.io.Serializable {
>
>
> My ant task do :
>
> prefix="kserver"
> destdir="${build.wsr.dir}/META-INF"/>
>
the answer is, that you have to configure your client, i.e. your client's
axis configuration and tell it which serializer to use for which class.
the configuration file could look something like this:
http://net.jboss.org/";
xmlns="http://xml.apache.org/axis/wsdd/";
xmlns:jbnet="http://net.jboss.org/server";
xmlns:java="http://xml.apache.org/axis/wsdd/providers/java";
xmlns:kserver= you have to put something here. the exact content
is not important, it's just a namespace definition.
e.g. "http://xml.kiala.com/kserver";
>
http://schemas.xmlsoap.org/soap/encoding/";
>
As you may observe from my response, i am myself not really sure what i am
doing here. however, at least in my case it seems to work ;-)
for e.g. i am not sure how to configure a axis, since i am using the
(deprecated) AxisInvocationHandler. i do not know why it is deprecated,
but it allows me to work with the remote EJBObject's in almost the same
way as directly calling EJB.
good look, heinz-dieter conradi
---
This sf.net email is sponsored by:ThinkGeek
Welcome to geek heaven.
http://thinkgeek.com/sf
___
JBoss-user mailing list
[EMAIL PROTECTED]
https://lists.sourceforge.net/lists/listinfo/jboss-user
[JBoss-user] JBoss-net with complex type (no serializer found)
Hello list,
I am trying to rollout our application to JBoss.NET instead of a separate
Axis.war
I am running xdoclet 1.2b2, JBoss 3.2.2RC4 under redhat 9
I have a SessionBean exposed as web service with two basic method (login,
logout). My problem is that those return/take complex type and it seems the
generated deployment descriptor is not complete enough:
My session bean (the one exposed as web service is):
* @ejb.bean type="Stateless"
* name="NodeSyncher"
* display-name="NodeSyncher Session Bean"
* jndi-name="ejb/kiala/NodeSyncher"
* local-jndi-name="ejb/kiala/NodeSyncherLocal"
* view-type="local"
*
* @ejb.transaction type="Required"
*
* @jboss-net.web-service urn="NodeSynchService"
*
* @author Stephane Nicoll
* @author $Author: snicoll $ (last edit)
* @version$Revision: 1.1.2.1 $
*/
public class NodeSyncherBean implements javax.ejb.SessionBean {
* @ejb.interface-method view-type="local"
*
* @jboss-net.web-method
*
*/
public LoginResponse login(String hardwareID, String kpID) {
return new LoginResponse();
}
My LoginResponse is:
*
* @jboss-net.xml-schema urn="kserver:LoginResponse"
*
public class LoginResponse implements java.io.Serializable {
My ant task do :
I attached the generated file. When I try to call login, access seems ok but
when Axis need to return the LoginResponse object, I got this:
faultString: java.io.IOException: No serializer found for class
com.kiala.kserver.driver.nodesync.LoginResponse in registry
[EMAIL PROTECTED]
faultActor:
faultNode:
faultDetail:
{http://xml.apache.org/axis/}stackTrace: java.io.IOException: No
serializer found for class com.kiala.kserver.driver.nodesync.LoginResponse in
registry [EMAIL PROTECTED]
at
org.apache.axis.encoding.SerializationContextImpl.serializeActual(Serializati
onContextImpl.java:1281)
at
org.apache.axis.encoding.SerializationContextImpl.serialize(SerializationCont
extImpl.java:795)
at
org.apache.axis.encoding.SerializationContextImpl.outputMultiRefs(Serializati
onContextImpl.java:866)
at org.apache.axis.message.SOAPBody.outputImpl(SOAPBody.java:179)
at
org.apache.axis.message.SOAPEnvelope.outputImpl(SOAPEnvelope.java:509)
at
org.apache.axis.message.MessageElement.output(MessageElement.java:783)
at org.apache.axis.SOAPPart.writeTo(SOAPPart.java:270)
Can anybody help?
Regards,
Stephane <>
___
Stéphane Nicoll
Software Engineer
KIALA NV - The last mile company
Avenue Louise/Louisalaan 149/28 (24th floor)
B-1050 Brussels (BELGIUM)
TEL +32 2 535 93 67
GSM +32 477 77 26 96
E-mail [EMAIL PROTECTED]
___
http://xml.apache.org/axis/wsdd/";
targetNamespace="http://www.jboss.org/net";
xmlns:kserver="http://www.jboss.org/net";
xmlns:java="http://xml.apache.org/axis/wsdd/providers/java";>
~
