]
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.
Problems for connecting a Weblogic 10 Portal WSRP Producer
----------------------------------------------------------
Key: JBPORTAL-1667
URL:
http://jira.jboss.com/jira/browse/JBPORTAL-1667
Project: JBoss Portal
Issue Type: Bug
Security Level: Public(Everyone can see)
Components: Portal WSRP
Affects Versions: 2.6.1 Final, 2.6 Final
Environment: Microsoft Windows 2000
Sun JDK 1.5.06
JBoss Portal 2.6.1 Final
JBoss Portal 2.6 Final
Reporter: Mehmet Salgar
Assigned To: Chris Laprun
Fix For: 2.6.2 Final, 2.8 Final
Attachments: fullstacktrace.txt, jboss_portal_wlp10_wsdl_binding_tcp_mon.txt,
jboss_portal_wlp10_wsdl_tcp_mon.txt, jboss_portal_wlp92_wsdl_tcp_mon.txt,
jboss_portal_wlp92MP_wsdl_binding_tcp_mon.txt, jboss_portal_wlp_10_refresh_soap.txt,
jboss_portal_wlp_92MP2_refresh_soap.txt, myPortalEAR.ear, WLP_self_registration.txt,
wsrp_2_servicedescription.txt
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.
--
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators: