[ http://jira.jboss.com/jira/browse/JBPORTAL-1667?page=all ] Mehmet Salgar updated JBPORTAL-1667: ------------------------------------ Description: I have problem for connecting a Weblogic Portal 10 as a remote Producer. I am receiving a message 'ERROR [CallImpl] Call invocation failed with SOAPFaultException javax.xml.rpc.soap.SOAPFaultException: The given registrationHandle [null] is invalid.; nested exception is: java.lang.NumberFormatException: null' I have a simple Portal application for Weblogic Portal 10 which is inluding only a JSF portlet. When I try to connect from WSRP Admin portlet to the WSDL URL and refresh I am getting this exception. Funny part about it, I deployed the same portal application to the WLP 9.2 then I was able to access it with JBoss Portal without problem. Because of the some difficulties we are getting at WLP 9.2 I like to see the same portal at WLP 10, but we are getting this exception. I look to the WSDL off the WLP it looks like somethings are changed from 9.2 to 10, so I am guessing that is the reason for the problem. The reason that I report this as a bug, I think JBoss has to change something to stay compatible and draw attention to the problem. Btw, WLP 10 can connect to is own portlet as Remote Portlet over WSRP. So I think the implementation from Weblogic side is correct, at least for themselves. I would try to attach the Portal Project, while it is really simple and can function as reproducer and WLP 10 is freely downloadable for development purposes. was: I have problem for connecting a Weblogic Portal 10 as a remote Producer. I am receiving a message 'ERROR [CallImpl] Call invocation failed with SOAPFaultException javax.xml.rpc.soap.SOAPFaultException: The given registrationHandle [null] is invalid.; nested exception is: java.lang.NumberFormatException: null' I have a simple Portal application for Weblogic Portal 10 which is inluding only a JSF portlet. When I try to connect from WSRP Admin portlet to the WSDL URL I am getting this exception. Funny part about it, I deployed the same portal application to the WLP 9.2 then I was able to access it with JBoss Portal without problem. Because of the some difficulties we are getting at WLP 9.2 I like to see the same portal at WLP 10, but we are getting this exception. I look to the WSDL off the WLP it looks like somethings are changed from 9.2 to 10, so I am guessing that is the reason for the problem. The reason that I report this as a bug, I think JBoss has to change something to stay compatible and draw attention to the problem. Btw, WLP 10 can connect to is own portlet as Remote Portlet over WSRP. So I think the implementation from Weblogic side is correct, at least for themselves. I would try to attach the Portal Project, while it is really simple and can function as reproducer and WLP 10 is freely downloadable for development purposes. -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: http://jira.jboss.com/jira/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira

[ http://jira.jboss.com/jira/browse/JBPORTAL-1667?page=comments#action_1237... ] Chris Laprun commented on JBPORTAL-1667: ---------------------------------------- "The reason that I report this as a bug, I think JBoss has to change something to stay compatible and draw attention to the problem. Btw, WLP 10 can connect to is own portlet as Remote Portlet over WSRP. So I think the implementation from Weblogic side is correct, at least for themselves." Why do you assume that it's JBoss Portal's fault? I could make modifications to both our consumer and producer in such a way that it would not be conform to the specification and yet work perfectly well with each other but break with every other products out there... The fact that WLP works with itself is not conclusive evidence that its implementation is correct. That said I will look into the problem. Could you please attach the ServiceDescription sent by WLP 10? -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: http://jira.jboss.com/jira/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira

[ http://jira.jboss.com/jira/browse/JBPORTAL-1667?page=all ] Mehmet Salgar updated JBPORTAL-1667: ------------------------------------ Attachment: jboss_portal_wlp_10_refresh_soap.txt -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: http://jira.jboss.com/jira/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira

[ http://jira.jboss.com/jira/browse/JBPORTAL-1667?page=all ] Mehmet Salgar updated JBPORTAL-1667: ------------------------------------ Attachment: jboss_portal_wlp10_wsdl_binding_tcp_mon.txt -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: http://jira.jboss.com/jira/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira

[ http://jira.jboss.com/jira/browse/JBPORTAL-1667?page=all ] Mehmet Salgar updated JBPORTAL-1667: ------------------------------------ Attachment: jboss_portal_wlp92_wsdl_tcp_mon.txt -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: http://jira.jboss.com/jira/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira

[ http://jira.jboss.com/jira/browse/JBPORTAL-1667?page=all ] Mehmet Salgar updated JBPORTAL-1667: ------------------------------------ Attachment: jboss_portal_wlp10_wsdl_tcp_mon.txt -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: http://jira.jboss.com/jira/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira

[ http://jira.jboss.com/jira/browse/JBPORTAL-1667?page=comments#action_1237... ] Mehmet Salgar commented on JBPORTAL-1667: ----------------------------------------- I had made little bit more research hier is a working request from WLP to register itself as WLP Producer. I am copying here part of the request.... Complete request I would add as attachement in file WLP_self_registration.txt for WLP10. <env:Body> <v1:getServiceDescription xmlns:v1="urn:oasis:names:tc:wsrp:v1:types"> <v1:registrationContext xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance" xsi:nil="true"/> </v1:getServiceDescription> </env:Body> and here is the JBoss request <env:Body> <ns1:getServiceDescription xmlns:ns1="urn:oasis:names:tc:wsrp:v1:types" xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance"> <ns1:registrationContext xsi:nil="1"/> <ns1:desiredLocales>en-US</ns1:desiredLocales> <ns1:desiredLocales>en</ns1:desiredLocales> </ns1:getServiceDescription> </env:Body> Only differences I can see the expression of the namespace 'xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance"' in registrationContext command and '<ns1:registrationContext xsi:nil="1"/>'. And off course there is a difference of "true" to "1" could these can be the reason of the problem????? -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: http://jira.jboss.com/jira/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira

[ http://jira.jboss.com/jira/browse/JBPORTAL-1667?page=comments#action_1237... ] Chris Laprun commented on JBPORTAL-1667: ---------------------------------------- Thanks a lot for all the hard work. Today was a holiday here in the US, I will look at everything in greater detail tomorrow. From what I see, I think the problem might indeed come from nil="1" as the problem reported by WLP is that the registrationHandle is null which seems to indicate that WLP considers that the registrationContext we give is NOT null. According to http://www.w3.org/TR/2004/REC-xmlschema-2-20041028/datatypes.html#boolean, 1 is a valid value for xsi:nil (which is of simple datatype boolean). At this point, it seems to point to a BEA problem, especially since our consumer was working with WLP 9.2. I will try to confirm that this is the case. -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: http://jira.jboss.com/jira/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira

[ http://jira.jboss.com/jira/browse/JBPORTAL-1667?page=comments#action_1237... ] Chris Laprun commented on JBPORTAL-1667: ---------------------------------------- "That means I would have no influence to change this from '1' to 'true'.... " Indeed and neither do I. :/ "I think, when WLP receives a number it automatically thinks this is RegistrationContext and try to convert to a handle :(" I don't think that's what is going on. The problem is probably more in the unmarshalling side of WLP which seems to fail to understand xsi:nil="1" == xsi:nil="true" which in turns causes it to not realize that the RegistrationContext we give it is null and therefore tries to look for the mandatory registrationHandle and when it doesn't find it (because it doesn't exist) throws the exception. You mentioned you have a Weblogic service account, try to see with them what they think. -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: http://jira.jboss.com/jira/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira