[JBoss-user] [JBossWS] - Re: JBossWS - new webservice stack information required

Hi, We were actually looking to use the current JBoss Axis stack for our webservices. But I read from the JBoss WIKI recently that, JBoss is not going to support/further develop JBoss Axis stack once it's own stack is released. So we are now quite concerned/confused about what webservice stack

[JBoss-user] [JBossWS] - JBossWS - new webservice stack information required

Hi, I would like to know where I can download new JBossWS (jboss proprietary webservice stack) and is it available as a stand alone version; If not which jboss version (will) contain it ? Is it already GA or when it is expected to be released. Thanks in advance Ram View the original post :

[JBoss-user] [JBossWS] - Re: Configure JBoss (serialization) to return only non-null

Hi Thomas, Can you please suggest me a workaround for this ( to eliminate null values) in jboss 4.0.3? Thanks in advance. -Ram View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=3917163#3917163 Reply to the post : http://www.jboss.com/index.html?module=bb&op

[JBoss-user] [JBossWS] - Re: Problem using inheritance in Webservice value types

Hi, I am really stuck with this issue. Any pointers on this will be higly appreciated. Thanks -Ram View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=3916435#3916435 Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=3916435

[JBoss-user] [JBossWS] - Problem using inheritance in Webservice value types

Hi, We are using JBoss 4.0.3 for our webservice implementation. We want to expose a generic interface which can take a valuetype or any of its subtypes as parameters. My Service Interface looks like this public interface PolicyWS extends java.rmi.Remote { | public Policy createPolicy(Pol

[JBoss-user] [JBossWS] - Configure JBoss (serialization) to return only non-null valu

Hi, We are using jboss 4.0.3 for our webservice implementation. We are using Java to WSDL development approach for webservices. (We define our service interface with java beans as our input and output parameters and use wscompile tool to generate wsdl from it.) I would like to know if it is

[JBoss-user] [JBossWS] - Re: xsd:any: content of _any not present in SOAP message ret

Hi, Thanks for the response. Actually when i run wscompile against xsd:any element it correctly creates SOAPElement or SOAPElement[] depending on the maxOccurs value. I think the problem is not with this.According to what I found, JBoss JAX-RPC internally tries to deserialize any xsd:elemen

[JBoss-user] [JBossWS] - Re: xsd:any: content of _any not present in SOAP message ret

Hi Thomas, I face the same issue with JBoss 4.0.3 too. Is the fix for this not available in JBoss 4.0.3 ? Is there any work around for this in JBoss 4.0.3. Another issue which I came across is (request to) xsd:any works only if it is mapped to SOAPElement[] array even if we want to use a sin

[JBoss-user] [JBossWS] - JBoss xsd:any mapping

Hi, We are using xsd:any for our webservice to expose a generic interface that will be able to receive different formats of XML. When i used wscompile to generate the server side interfaces (etc..) it maps this xsd:any to a single SOAPElement.(we use maxOccurs=1). But now when i try to invoke

[JBoss-user] [Persistence,JBoss/CMP, Hibernate, Database] - Re: problem with cmp byte data type mapping in jboss 4.0.3+I

We are really in urgent need of help to solve this issue. Any help on this would be greatly appreciated. View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=3904056#3904056 Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=3904

[JBoss-user] [Persistence,JBoss/CMP, Hibernate, Database] - problem with byte data type in jboss 4.0.3+Ingres 3.0.1

We are using jboss 4.0.3 with Ingres 3.0.1 as our datasource . We are using CMP 2.0 as our persistence layer. When we try to update any field of byte datatype we get the following exception trace.It seems to be some problem with byte type-mapping in standardjbosscmp-jdbc.xml configuration fil