Found the solution:

marshaller.setSuppressXSIType(true);

(I'm using Axis so I had to do the changes in CastorSerializer)

But I'm still interesed in knowing why this behavior is changed
from 0.9.5.3 to 0.9.6

Cheers,
Are T. Tysnes

-----Original Message-----
From: Tysnes Are Thobias 
Sent: 6. juni 2005 09:53
To: user@castor.codehaus.org; dev@castor.codehaus.org
Subject: RE: [castor-user][XML] strange xsi:type declaration in response
in 0.9.6



Sorry for re- and cross-posting, but I need some help.

Why is this "invalid" xsi:type declaration in my response !?
It was not generated in 0.9.5.3 .. :-/

Any suggestions !?

Cheers,
Are T. Tysnes

-----Original Message-----
From: Tysnes Are Thobias 
Sent: 3. juni 2005 13:10
To: user@castor.codehaus.org
Subject: [castor-user][XML] strange xsi:type declaration in response in
0.9.6



Hello!

I'm trying to migrate from 0.9.5.3 to 0.9.6

In some of my responses there is an "invalid!?" xsi:type declaration
which makes the client unable to DeSerialize the response

I'm using Axis 1.2 with Castor as data-binder

Here is the repsonse:

<?xml version="1.0" encoding="UTF-8"?>
<soapenv:Envelope
xmlns:soapenv="http://schemas.xmlsoap.org/soap/envelope/";
xmlns:xsd="http://www.w3.org/2001/XMLSchema";
xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance";>
        <soapenv:Body>
                <AddDomesticCreditorResponse
xmlns="http://www.edb.com/cps/webservices/creditor/transvo";>
                        <ns1:AddCreditorResponseW
xsi:type="AddCreditorResponseW"
xmlns:ns1="http://www.edb.com/cps/webservices/creditor/common/transvo";>
                                <ns1:creditorId>3026186</ns1:creditorId>
        
<ns1:creditorAccountId>3020187</ns1:creditorAccountId>
                        </ns1:AddCreditorResponseW>
                </AddDomesticCreditorResponse>
        </soapenv:Body>
</soapenv:Envelope>

The strange thing is that it is just some of the responses with this
xsi:type declaration. and it is just on WebSphere 5.1.0.4. When I run
the same code in JBoss 3.2.3 the xsi:type declaration is _not_ present.

Any suggestions !?

Cheers,
Are T. Tysnes

-------------------------------------------------
If you wish to unsubscribe from this list, please 
send an empty message to the following address:

[EMAIL PROTECTED]
-------------------------------------------------

-------------------------------------------------
If you wish to unsubscribe from this list, please 
send an empty message to the following address:

[EMAIL PROTECTED]
-------------------------------------------------

-------------------------------------------------
If you wish to unsubscribe from this list, please
send an empty message to the following address:

[EMAIL PROTECTED]
-------------------------------------------------

Reply via email to