What is the correct structure of a JBIFaut?

[LeeCK <le...@yahoo.com>]

Hi,

How does a correct JBIFault looks like? Below is my JBIFault, but
JbiWsdl11WrapperMapper throws "Invalid NMS message format, expected
{http://java.sun.com/xml/ns/jbi/wsdl-11-wrapper}part but found
{http://www.w3.org/2003/05/soap-envelope}Text" exception.

<?xml version="1.0" encoding="UTF-8"?>
<JBIFault xmlns="http://java.sun.com/xml/ns/jbi/wsdl-11-wrapper">
       <soap:Text xmlns:soap="http://www.w3.org/2003/05/soap-envelope"
xml:lang="en">Exception of type
'Microsoft.SharePoint.SoapServer.SoapServerException' was thrown.
       </soap:Text>
</JBIFault>

LOG:
  in: <?xml version="1.0" encoding="UTF-8"?><message
xmlns="http://java.sun.com/xml/ns/jbi/wsdl-11-wrapper"
xmlns:msgns="http://schemas.microsoft.com/sharepoint/soap/directory/"
type="msgns:AddUserToGroupSoapIn" version="1.0"><part><AddUserToGroup
xmlns="http://schemas.microsoft.com/sharepoint/soap/directory/">
                    </AddUserToGroup></part></message>
  fault: <?xml version="1.0" encoding="UTF-8"?><JBIFault
xmlns="http://java.sun.com/xml/ns/jbi/wsdl-11-wrapper"><soap:Text
xmlns:soap="http://www.w3.org/2003/05/soap-envelope" xml:lang="en">Exception
of type 'Microsoft.SharePoint.SoapServer.SoapServerException' was
thrown.</soap:Text></JBIFault>
]
11:47:18,417 | DEBUG | pool-6-thread-2 | MessageExchangeImpl      |
pel.engine.MessageExchangeImpl  213 | GET MEX property
org.apache.ode.jbi.msgmap.Mapper =
org.apache.ode.jbi.msgmap.JbiWsdl11WrapperMapper
11:47:18,417 | ERROR | pool-6-thread-2 | JbiWsdl11WrapperMapper   |
.msgmap.JbiWsdl11WrapperMapper  173 | Invalid NMS message format, expected
{http://java.sun.com/xml/ns/jbi/wsdl-11-wrapper}part but found
{http://www.w3.org/2003/05/soap-envelope}Text
11:47:18,417 | ERROR | pool-6-thread-2 | OdeConsumer              |
g.apache.ode.jbi.OdeConsumer$4  243 | Error translating message.
org.apache.ode.jbi.msgmap.MessageTranslationException: Invalid NMS message
format, expected {http://java.sun.com/xml/ns/jbi/wsdl-11-wrapper}part but
found {http://www.w3.org/2003/05/soap-envelope}Text
	at
org.apache.ode.jbi.msgmap.JbiWsdl11WrapperMapper.toFaultType(JbiWsdl11WrapperMapper.java:174)
	at org.apache.ode.jbi.OdeConsumer$4.call(OdeConsumer.java:221)
	at org.apache.ode.jbi.OdeConsumer$4.call(OdeConsumer.java:204)
	at
org.apache.ode.scheduler.simple.SimpleScheduler.execTransaction(SimpleScheduler.java:174)
	at org.apache.ode.jbi.OdeConsumer.outResponse(OdeConsumer.java:202)
	at
org.apache.ode.jbi.OdeConsumer.onJbiMessageExchange(OdeConsumer.java:160)
	at
org.apache.ode.jbi.JbiMessageExchangeEventRouter.onJbiMessageExchange(JbiMessageExchangeEventRouter.java:44)
	at org.apache.ode.jbi.Receiver$1.run(Receiver.java:179)
	at java.util.concurrent.Executors$RunnableAdapter.call(Executors.java:441)
	at java.util.concurrent.FutureTask$Sync.innerRun(FutureTask.java:303)
	at java.util.concurrent.FutureTask.run(FutureTask.java:138)
	at
java.util.concurrent.ThreadPoolExecutor$Worker.runTask(ThreadPoolExecutor.java:886)
	at
java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:908)
	at java.lang.Thread.run(Thread.java:619)
-- 
View this message in context: http://www.nabble.com/What-is-the-correct-structure-of-a-JBIFaut--tp25530197p25530197.html
Sent from the ServiceMix - User mailing list archive at Nabble.com.