JBossDeveloper

The last error I posted came from my Weblogic side. The equivilant error from the JBoss server side is:
$ 13:24:09,988 ERROR [SOAPFaultExceptionHelper] SOAP request exception
javax.xml.rpc.JAXRPCException: org.jboss.ws.binding.BindingException: javax.xml.bind.JAXBException: Failed to parse source: Requested element {urn:bea:wsrp:ext:v1:types}LookAndFeelDescriptor is not allowed in this position in the sequence.
at org.jboss.ws.soap.SOAPContentElement.getObjectValue(SOAPContentElement.java:307)
at org.jboss.ws.binding.EndpointInvocation.transformPayloadValue(EndpointInvocation.java:233)
at org.jboss.ws.binding.EndpointInvocation.getRequestParamValue(EndpointInvocation.java:103)
at org.jboss.ws.binding.EndpointInvocation.getRequestPayload(EndpointInvocation.java:117)
at org.jboss.ws.server.ServiceEndpointInvokerJSE.invokeServiceEndpoint(ServiceEndpointInvokerJSE.java:94)
at org.jboss.ws.server.ServiceEndpointInvoker.invoke(ServiceEndpointInvoker.java:118)
at org.jboss.ws.server.ServiceEndpoint.handleRequest(ServiceEndpoint.java:234)
at org.jboss.ws.server.ServiceEndpointServlet.doPost(ServiceEndpointServlet.java:120)

I think this is the fault send back from the producer to the consumer.

It does indeed look like an extension problem.

Thanks for the quick responses. Does this mean I need to wait for the next release that implements the "special handler"?

you can get the fix from the CVS once we have fixed it and compile it from there.

or wait 'til the next one.

I had removed the extension stripping handler in the last revision because I thought that we only needed it on the consumer side. This has been fixed in CVS. Thanks for the report.

Looks like I will have to wait for the next release. Can't seem to build the JBoss/jboss-portal/ source from cvs as of June 8th.

Which JBoss/jboss-portal/ branch should I use?

cvs co jboss-portal-2.4

Grabbed the update (webservices.xml) from cvs and still get the same exception after a full redeploy.

wsrp_services.wsdl in the wsdl directory should also have been updated.

I'll keep an eye out for that update in CVS.

It has been modified at the same time... So you should have gotten it with the last update. The problem you're experiencing might not be related...

I don't see any mods to the WSDL file within the same time frame on the MAIN branch.

Are you looking at fisheye? If yes, it's not very reliable...
The change is shown there though it doesn't appear at the top level changelog for some reason:
http://fisheye.jboss.com/viewrep/JBoss/jboss-portal/wsrp/src/resources/portal-wsrp-war/WEB-INF/wsdl/wsrp_services.wsdl