xsi:type usually indicates rpc/encoding, which is probably what the php soap library is doing. Basically with encoding you pass all of the type information at runtime, instead of negotiating it in advance with schema. So in most literal requests you will never see the xsi:type attribute because it is redundant, and it increases the size of the message. An example of a literal message that would use xsi:type is one that involves inheritence (a message takes a base type, and the sender passes a derived type).
getCarrier is behaving correctly by not including the type information in the request. So basically you need to use a php soap library that supports rpc/literal or doc/literal. I believe that php 5 includes such an implementation. -Jason View the original post : http://www.jboss.org/index.html?module=bb&op=viewtopic&p=3884109#3884109 Reply to the post : http://www.jboss.org/index.html?module=bb&op=posting&mode=reply&p=3884109 ------------------------------------------------------- This SF.Net email is sponsored by the 'Do More With Dual!' webinar happening July 14 at 8am PDT/11am EDT. We invite you to explore the latest in dual core and dual graphics technology at this free one hour event hosted by HP, AMD, and NVIDIA. To register visit http://www.hp.com/go/dualwebinar _______________________________________________ JBoss-user mailing list [email protected] https://lists.sourceforge.net/lists/listinfo/jboss-user
