Hi Martin,
I have been trying to get this working for months but was not successful . I
would like to know if it can be done..Please reply.
Thanks,Raghav.
--- On Fri, 2/12/10, Rahul Rulz wrote:
From: Rahul Rulz
Subject: RE: xsi:type
To: axis-user@ws.apache.org
Date: Friday, February 12
Hi Martin,
Thanks for your reply.. basically I want to include the XSi:type in the
responses made from my server..
This is the response I am getting from my server presently :
http://schemas.xmlsoap.org/soap/envelope/";
xmlns:xsd="http://www.w3.org/2001/XMLSchema";
xmlns:xsi=&qu
enu fourni.
Date: Thu, 11 Feb 2010 16:38:58 -0800
From: ragul...@yahoo.com
Subject: Re: xsi:type
To: axis-user@ws.apache.org
Hi Users,
can anyone help me out please...
Thanks,Raghav.
--- On Thu, 2/11/10, Rahul Rulz wrote:
From: Rahul Rulz
Subject: xsi:type
To: axis-user@ws.apach
Hi Users,
can anyone help me out please...
Thanks,Raghav.
--- On Thu, 2/11/10, Rahul Rulz wrote:
From: Rahul Rulz
Subject: xsi:type
To: axis-user@ws.apache.org
Date: Thursday, February 11, 2010, 11:03 AM
Hi All,
I am looking to include xsi:type in the responses from my server for a
Hi All,
I am looking to include xsi:type in the responses from my server for a ling
time :( .. Have not done it till now..Could anyone pl. help me as to do it..I
have created a service from scratch(not from WSDL generated java code) which
uses message receivers and send the responses. I am
Hi,
Could anyone pl. help me with this query..?also pl. let me know if its not
possible to send xsi:type responses in the services that are created from
the scratch and possible only with the WSDL generated service.? ..?
Thanks all.
Reg,
De Chandy.
On Thu, Dec 10, 2009 at 4:24 PM, Deepika
Hi all,
I am basically looking to include xsi:type for the responses made from my
axis2 1.5.1 server. This server had been created from scratch and not from
any WSDL.
Below are my queries
1. Is there a way to add xsi:type to the server responses from axis2 ?
2. If the client had been
g the former method to appear) but no
sequence element. I placed the latter in to the WSDL, and wsdl2java created
a setExtraElement(OMElement) method for me.
Glen Mazza wrote:
>
> Hello, I'm writing a client of a web service WSDL that uses xsi:type[1],
> which is a method of dynam
Hello, I'm writing a client of a web service WSDL that uses xsi:type[1],
which is a method of dynamically changing the type of element being used.
(I'm using Axis2 with ADB). The WSDL just asks for a RequestQuery, as
def
/www.sosnoski.co.nz
> Seattle, WA +1-425-939-0576 - Wellington, NZ +64-4-298-6117
>
>
>
>
> Dennis Korbar wrote:
>
>> Hello,
>>
>> I'm using axis2 for stub-generation on a webservice.
>> I was wondering if it is possible to turn off the use of xsi:type
Dennis Korbar wrote:
Hello,
I'm using axis2 for stub-generation on a webservice.
I was wondering if it is possible to turn off the use of xsi:type for
the type definition, to be a bit more specific consider the following
example:
Let's say I have a "vehicle" definition
Hello,
I'm using axis2 for stub-generation on a webservice.
I was wondering if it is possible to turn off the use of xsi:type for the
type definition, to be a bit more specific consider the following example:
Let's say I have a "vehicle" definition which is an abstract ty
Hello All
I am having an issue with the way AXIS is creating the XML-SOAP
request that it sends to a 3rd party webservice.
PROBLEM: AXIS is adding xsi:type="xsd:int" to certain elements of the request.
12
The 3rd party webservice rejects the request, stating "Y
Hi,
I have un OMElement element like that:
<a xmlns:ns4="http://ns4/text";
xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance"; xsi:type="ns4:att1">
<b xsi:type="ns4:att2" uri="http://uri"/>
</a>
when i do:
element.getF
Hi,
I have un OMElement element like that:
when i do:
element.getFirstElement()
i got:
the declaration of ns4 don't appear in the result
how can i fix that ?
thanks
--
View this message in context:
http://www.nabble.com/Axiom-%2B-xsi%3Atype-tp19684690p19684690.html
Sent from the Axi
Try naming your derived simpleType:
This will force Axis to generate a type for you, and then you cast the
short to this type.
Anne
On Thu, Jun 12, 2008 at 5:42 PM, Roger P
<[EMAIL PROTECTED]> wrote:
> On Wed, Jun 11, 2008 at 8:48 PM, David Ojeda <[EMA
On Wed, Jun 11, 2008 at 8:48 PM, David Ojeda <[EMAIL PROTECTED]> wrote:
> Hello,
>
> I didn't notice you were using axis 1.2.1. Is axis generating a AntalBarnHemma
> class? How do you set this? Could you send that piece of code?
> I am guessing that BeraknaBostadsbidragRequest has a setAntalBarnHem
Hello,
I didn't notice you were using axis 1.2.1. Is axis generating a AntalBarnHemma
class? How do you set this? Could you send that piece of code?
I am guessing that BeraknaBostadsbidragRequest has a setAntalBarnHemma method
that receives a short, but perhaps there is a method that receives a
Hi,
On 6/11/08, David Ojeda <[EMAIL PROTECTED]> wrote:
> Hello,
>
> I am sorry I am not replying because I can help you. I was just wondering
> where do you set this SEND_TYPE_ATTR?
First I'm using Axis 1.2.1 so I don't know if this applies to your
problem. I'm setting it on my org.apache.axis.cli
p://www.w3.org/2001/XMLSchema";
> xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance";>
>
> xmlns="http://fk.se/ICC/Integrations/I0021/BeraknaBostadsbidrag/xsd";>
>
> 1
>
>
>
>
>
>
> The
XMLSchema-instance";>
http://fk.se/ICC/Integrations/I0021/BeraknaBostadsbidrag/xsd";>
1
The relevant part of the xsd:
So how can I get Axis to use something similar to the accept
Subject: Re: [Axis2] xsi:type support with JAXB databinding?
Hi,
Thanks for the answer. I used JAXB databinding.
Should I switch to ADB?
Pierre
"Amila Suriarachchi" <[EMAIL PROTECTED]>
01/02/2008 06:22 Veuillez répondre à
axis-us
Hi,
Thanks for the answer. I used JAXB databinding.
Should I switch to ADB?
Pierre
"Amila Suriarachchi" <[EMAIL PROTECTED]>
01/02/2008 06:22
Veuillez répondre à
axis-user@ws.apache.org
A
axis-user@ws.apache.org
cc
Objet
Re: [Axis2] xsi:type support with JAXB databinding?
On Jan 30, 2008 8:58 PM, <[EMAIL PROTECTED]> wrote:
>
> Hello axis users,
> I have a web service client (which I can't modify) which sends requests
> using xsi:type attributes:
> http://www.almerys.com/schemas/requeteOPTOAMC/2.6.0";
> xsi:type="LUNE
Hello axis users,
I have a web service client (which I can't modify) which sends requests
using xsi:type attributes:
http://www.almerys.com/schemas/requeteOPTOAMC/2.6.0";
xsi:type="LUNETTETYPE">
[]
After generating sources from the wsdl using jaxb2 databindin
r class to group the namespaces used to single one. I am not
> > sure as to why the xsi:type is not coming same as what it was coming from
> > the axis1 response.
> > Thanks Amila for pointing this out .
> >
>
> As you have done you have to generate the code. if you go thro
> receiver to set xmlOptions.setSaveAggressiveNamespaces() in
> the receiver class to group the namespaces used to single one. I am not sure
> as to why the xsi:type is not coming same as what it was coming from the
> axis1 response.
> Thanks Amila for pointing this out .
>
As you have done you have to gene
Gaurav,
Your WSDL uses document/literal, therefore the only reason why the
message should use the xsi:type attribute is if it is overriding the
type that the schema defines. You haven't supplied the schemas, so
it's impossible to answer your question. Take a look at the schema for
th
single one. I am not sure as to why the xsi:type
is not coming same as what it was coming from the axis1 response.
Thanks Amila for pointing this out .
I have question is if we need to use xml bean serilazion in axis2, what
is the suggested way of going about it as this feature is not part of
axis2
doing migration to axis2 from axis1, we are using xmlnbeans as
data binding. mechanism.I am using axis 2 version 1.3
We are observing difference in the responses
there is no xsi:type coming out for the response
Also the namespaces are coming for each element in axis 2 response ?
; can you please try with a nighly build. Now axis2 directly use the
> xmlbeans serialization.
> >
> > thanks,
> > Amila.
> >
> >
> > On Jan 9, 2008 1:16 PM, Gaurav Lall < [EMAIL PROTECTED]> wrote:
> >
> > >
> > > Hi all ,
> > >
> Hi all ,
> >
> > We are doing migration to axis2 from axis1, we are using xmlnbeans as
> > data binding. mechanism.I am using axis 2 version 1.3
> >
> > We are observing difference in the responses
> >
> >1. there is no xsi:type coming out for the
migration to axis2 from axis1, we are using xmlnbeans
as data binding. mechanism.I am using axis 2 version 1.3
We are observing difference in the responses
1. there is no xsi:type coming out for the response
2. Also the namespaces are coming for each element in axis 2
chanism.I am using axis 2 version 1.3
>
> We are observing difference in the responses
>
>1. there is no xsi:type coming out for the response
>2. Also the namespaces are coming for each element in axis 2
>response ? I would idealy like to use the prefixes to reduce the siz
Hi all ,
We are doing migration to axis2 from axis1, we are using xmlnbeans as
data binding. mechanism.I am using axis 2 version 1.3
We are observing difference in the responses
1. there is no xsi:type coming out for the response
2. Also the namespaces are coming for each element in
Hi. I have following problem. If i have 2 classed: Parent and child, is SOAP
request tag for Child object looks like instead
of just simple . How to fix it? I'm using axis 1.4. Thanks!!
--
View this message in context:
http://www.nabble.com/Axis-xsi%3Atype-problem.-%28How-to-avoid-it-%29-tp1457
pes and specific elements in a
> different namespace. When using XMLBeans
> the xsi:type is suppressed. E.g. when creating a query like this
>
> QueryDocument query = QueryDocument.Factory.newInstance();
> QueryParameter par = query.addNewQuery();
>
> ExplicitItem
Hello,
I created a webservice (from wsdl) using XMLBeans binding. Short before
finishing the project I run into a problem
with the XML binding.
The wsdl describes some abstract complex_types and specific elements in a
different namespace. When using XMLBeans
the xsi:type is suppressed. E.g
webservice. While HTTP request runs perfectly
the JMS does not. I debugged it and found that AXIS2 is generating different
request strings for JMS and HTTP. The "xsi type" is not being generated for
JMS requests. For HTTP the xsi:type is being generated in the request
correctly.
Because of th
trings for JMS and HTTP. The "xsi type"
> is not being generated for JMS requests. For HTTP the xsi:type is
> being generated in the request correctly.
>
> Because of this the other elements isbn, author start getting
> qualified explicitly to the namespace and their
, Balaji <[EMAIL PROTECTED]> wrote:
Can Anyone help on the below question ?
_
From: Iyer, Balaji
Sent: Tuesday, June 12, 2007 11:54 AM
To: 'axis-user@ws.apache.org'
Subject: AXIS2 XSI:TYPE and qualified namespaces Different S
Can Anyone help on the below question ?
> _
> From: Iyer, Balaji
> Sent: Tuesday, June 12, 2007 11:54 AM
> To: 'axis-user@ws.apache.org'
> Subject: AXIS2 XSI:TYPE and qualified namespaces Different SOAP
> r
pe"
is not being generated for JMS requests. For HTTP the xsi:type is being
generated in the request correctly.
Because of this the other elements isbn, author start getting qualified
explicitly to the namespace and their respective types (isbn type and
authortype) and the webservice on the se
Use document/literal wrapped convention.
On 4/23/07, Bakshi, Umesh (SYSTEM MESSAGING)
<[EMAIL PROTECTED]> wrote:
Hi,
I'm using Java client having Apache AXIS API to invoke multi-platform Java,
.NET and WSE2.0 webservices.
The SOAP requests generated are having xsi:type attrib
Hi,
I'm using Java client having Apache AXIS API to invoke multi-platform
Java, .NET and WSE2.0 webservices.
The SOAP requests generated are having xsi:type attribute present except
for String datatype.
My question is how to remove this xsi:type attribute from the request?
The Call o
Hello,
Following up on various polymorphism questions: How do we send the entire
derived type from an axis generated client to the server? Specifically, soap
requests don't seem to contain fields from derived class that are not
present in the base class.
Lets use the familiar example of Shape an
ement has content the soap-body looks like this:
http://schemas.xmlsoap.org/soap/encoding/";
xmlns:ns1="urn:[myUrn]">
As you can see: In the second example the xsi:type is missing. How can I
get Axis sending the xsi:type.
This causes Axis to serialize an xml with no xsi:type attribute, probably,
as you said, because it has no name for the embedded type for it's symbol
tables.
Declaring this as a type, on the top level, and maybe declaring an element
of this type, instead, makes
and then use that element in your message, such as:
-Original Message-
From: glenn bech [mailto:[EMAIL PROTECTED]
Sent: Wednesday, October 05, 2005 7:41 AM
To: axis-user@ws.apache.org
Subject: RE: Missing xsi:type attribute on abstract element
Hi again Clint,
The WSDL files are specified with the wsdlfile property, and they are all
hand made (you can see the wsdl at the bottom of my original post).
... I'm just curious now on why Axis is not including the xsi:type="" on
my abstract element...
-Original Me
ation of wsdl (while being nice) is pretty limited...
also verify that whatever type should be in the xsi:type="" portion is
actually in your server-config.wsdd (if you're not using the
adminclient)
I personally have gone entirely away from allowing axis to generate a
wsdl, instea
Aa you can see, my abstract element "ItemAttributes" have no xsi:type
attribute, and the BeanDeSerializer has no Idea what concreate
implementation of this class to instantiate.
Any Idea if I can "force" the "xsi:type" attribute, or any Idea why this
is not included ?
Im not
Hi All,
I have a web service developed using .NET and I trying to consume it
using AXIS 1.2.1 Final. When I request the service I am getting
"org.xml.sax.SAXParseException:Document root element is missing"
AxisFault from the service. I was suggest that because of lack of
"xsi:
It sounds like a bug. Please file a bug report.
On 7/1/05, Kurt Indermaur <[EMAIL PROTECTED]> wrote:
> I'm an Axis newbie, and I've got axis working fine for very simple services,
> but any time I have an array in the response I get a duplicate attribute
> (xsi:typ
I'm an Axis newbie, and I've got axis working fine for very simple services,
but any time I have an array in the response I get a duplicate attribute
(xsi:type="soapenc:Array") in the response. Perl's SOAP::Lite chokes on the
duplicate attribute. The WSDD and response ar
When using document/literal, with predefined types ("xsd:string"),
there's no reason to pass xsi:type information in the message. (And it
would be non-compliant with WS-I BP if you did.) If you want to force
Axis to supply xsi:type information, then you should define the "key&q
I am using a JBuilder Java client
(Axis 1.2 I believe ) to send a complex object containing a
HashMap to a WebSphere 6.0 web service. The Map in the SOAP body does not
contain the xsi:type attribute for the key and value. When I use a WebSphere
client it does. With the JBuilder client, the
Dear all,
We have a derived type from short in our schema such as:
When sending an instance document (using document/literal) over the wire
with axis (1.2), it is serialized as:
99
However, I this seems to be incorrect, as MyD
I had the same problem: I use castor to serialize my parameters and it
added the xsi:type attribute, so the request was rejected at server side,
complaining that it is not valid.
I first tried to do this in my stub class:
call.setOption(Call.SEND_TYPE_ATTR, Boolean.FALSE);
But it did not work
As I remember, Castor behavior changed so that it now includes xsi:type
on root elements by default. I've seen case before where this causes
problems with .Net. You can turn this off using the
marshaller.setSuppressXSIType(true) call (within the Axis-Castor
serializer code, in this
t
this is a wrapped service
and that the xsi:type coded in the element should not be there
as the WSDL specifies literal.
When I use the Axis Bean (De)serialization this is not present.
Can anyone tell me
1. If this is correct/incorrect behaviour
2. If this will cause any interop issues
3. If the
61 matches
Mail list logo
