Ellecer Valencia wrote:
Thanks for the suggestion Dennis. I have also used it to generate
client code via CXF (which defaults to JAXB), and didn't fail on
generation of code as well.
JAXB may be stripping off the whitespace. That's what I initially
assumed should be done, but from looking at
It turns out JAXB is actually treating the whitespace as part of the
name, just like ADB (and JiBX, at present). The funny part is JAXB
actually reports an error if the name contains any invalid
non-whitespace characters.
I'll point out this problem on the JAXB list.
- Dennis
Dennis
Hi,
What's wrong with this schema fragment?
element name=authorizePurchaseResponse
complexType
sequence
element name=purchaseId type=string
maxOccurs=1
minOccurs=1/element
Hi Ellecer,
I'd say this is an error in your schema definition and should be
reported as such by the schema processing. Schema says the value of the
name attribute should be of type NCName, which only allows name
characters in the value.
Have you tried this schema with any other schema
Thanks for the suggestion Dennis. I have also used it to generate
client code via CXF (which defaults to JAXB), and didn't fail on
generation of code as well. Haven't looked at xmlbeans or jibx yet.
I also got errors about unexpected subelement when calling the web
service, but it was for
Yes I'm using Axis2 (1.4).
I noticed the same thing. Did you try to deploy the service and called it
using a test client?
Thanks for your help. Does anybody have a suggestion why two similar classes
are being generated?
Regards,
Harm!
On Fri, Aug 15, 2008 at 5:06 PM, Detelin Yordanov [EMAIL
Hi all,
I'm trying to generate a SOAP service server from an existing WSDL file.
I have generated all necessary class using the following command:
wsdl2java.sh -t -o server/title_edition/ -uri wsdl/Webs_TitelEdition.wsdl -p
nl.kabisa.sanoma.webservices.server -d adb -s -wv 1.2 -ss -sd -ssi
I
Hi,
Are you using Axis2 1.4 ?
I tried your wsdl on Axis2 1.4 using following command:
wsdl2java -t -o server/title_edition/ -uri wsdl/Webs_TitelEdition.wsdl -p
nl.kabisa.sanoma.webservices.server -d adb
And the generated code contains two repeating classes:
1. There is Edition_type0 and
use tcpmon[1] to look at the request and response. then check whether your
response
match with the WSDL file.
thanks,
Amila.
[1]http://ws.apache.org/commons/tcpmon/
2008/3/28 Ken Ferguson [EMAIL PROTECTED]:
That error is usually caused by you returning XML that doesn't match the
schema.
Hello;
Error is like that...
- An error occured while creating stub!
[*java*] org.apache.axis2.AxisFault: *
org.apache.axis2.databinding.ADBException*: Unexpected subelement timeCode
[*java*] at org.apache.axis2.AxisFault.makeFault(*AxisFault.java:417*)
[*java*] at
That error is usually caused by you returning XML that doesn't match the
schema. With me it's almost always caused by a missing XML element where
one is required.
HTH
Ken
On 28/03/2008, Umut DOĞAN [EMAIL PROTECTED] wrote:
Hello;
Error is like that...
- An error occured while creating
Hi Neil,
Can you post your wsdl and/or service archive please?
regards
Charitha
Nelli Vanan wrote:
Hi there,
I am trying out with a simple web service client program. I generated
the code using wsdl2java.(axis2, 1.1.1). Now, when I tried to connect
to the service I am getting an error
Hi there,
I am trying out with a simple web service client program. I generated
the code using wsdl2java.(axis2, 1.1.1). Now, when I tried to connect
to the service I am getting an error saying that Unexpected Subelement
; Java runtime exception. I used the wsdl from the server. I am not
sure
HI all,
I've found a solution. When one uses useOriginalWsdl the package to namespace
mappings are read from the services.xml file (see ServiceBuilder.java method
processTypeMappings). The problem is when classes are out of the target
namespace. All we have to do is to write the mappings in
Hi Mike,
The InputData and OutputData are simple JavaBean classes as:
package dev.axis2.ws.data;
public class InputData {
private String data;
public String getData() {
return data;
}
public void setData(String data) {
this.data = data;
}
}
Recently I've
Hola Jose,
I usually have those problems when using rampart but only with classes that
extend from others.
Regards,
Jorge Fernández
Jose Luis Alba [EMAIL PROTECTED] escribió: Hi Mike,
The InputData and OutputData are simple JavaBean classes as:
package dev.axis2.ws.data;
public class
Hi Jose ,
Please have a look at Axis2 1.3 RC1 release , I think we have fixed the
issue there.
http://people.apache.org/~deepal/axis2/1.3-RC1/
Thanks
Deepal
Hi,
- I'm using Axis2 1.2
I've create a POJO test web service that resides in package
dev.axis2.ws.service and uses in/out bean data
Hi,
- I'm using Axis2 1.2
I've create a POJO test web service that resides in package
dev.axis2.ws.service and uses in/out bean data from package dev.axis2.ws.data.
The interface is:
package dev.axis2.ws.service;
import dev.axis2.ws.data.InputData;
import dev.axis2.ws.data.OutputData;
Jose,
Does your OutputData class extend a java collection object or similar data
type? If so, then this is why you are getting such an error. You should return
a single element; even if you have an array or so to return, wrap that in a
property of another class and return that other type
types at all in the WSDL file along with the
restrictions??
Thanks
From: Vibhor_Sharma [mailto:[EMAIL PROTECTED]
Sent: Wednesday, March 21, 2007 6:05 PM
To: axis-user@ws.apache.org
Subject: Problem while using Rampart (Unexpected subelement error)
Hi
I had to modify AddressBookADBClient because setParam0 is not available
in the generated service stub.
//addEntry.setParam0(entry);
addEntry.setEntry(entry);
//findEntry.setParam0(Abby Cadabby);
findEntry.setName(Abby Cadabby);
When executed, it received java.lang.RuntimeException: Unexpected
, if additional
fields get added to the data which were not in the wsdl when the java files were
generated with Axis2, then the code blows up with the java.lang.RuntimeException:
Unexpected subelement error. Obviously, I can regenerate the java code using a
new wsdl. But, as long as those additional
added to the data which were not in the wsdl when the java files were generated with Axis2, then the code blows up with the java.lang.RuntimeException
: Unexpected subelement error. Obviously, I can regenerate the java code using a new wsdl. But, as long as those additional fields are not needed in my
, if additional fields get added to the data which were not in
the wsdl when the java files were generated with Axis2, then the code blows
up with the java.lang.RuntimeException: Unexpected subelement error.
Obviously, I can regenerate the java code using a new wsdl. But, as long as
those additional
in the generated code about this
field. The generated code throws the error when the parser comes to
cdCustType.
-Original Message-
From: Davanum Srinivas [mailto:[EMAIL PROTECTED]
Sent: Thursday, November 09, 2006 10:48 AM
To: axis-user@ws.apache.org
Subject: Re: Axis2 unexpected subelement error
Moore
: Re: Axis2 unexpected subelement error
Moore,
It depends on the schema. *IF* your schema (in your wsdl) says, they are
needed only then we throw an exception. We also throw an exception if
the schema specifies a certain order and the runtime soap message does
not have the same order.
-- dims
a solution.
Essentially, if additional fields get added to the data which were not
in the wsdl when the java files were generated with Axis2, then the
code blows up with the java.lang.RuntimeException: Unexpected
subelement error.
Obviously, I can regenerate the java code using a new
=required/
/xs:complexType
Data returned looks good:
Report Name=name Value=value /
The Problem: Examining the stub generated code, it looks like the stub
checks and gets the attributes but then looks for Name and Value
elements, too. Since they are not there the stub throws a Unexpected
subelement
28 matches
Mail list logo
