[jboss-jira] [JBoss JIRA] Commented: (JBPORTAL-1667) Problems for connecting a Weblogic 10 Portal WSRP Producer
[ http://jira.jboss.com/jira/browse/JBPORTAL-1667?page=comments#action_1237... ]
Mehmet Salgar commented on JBPORTAL-1667:
-----------------------------------------
You are probably right that this can be a Weblogic Bug or just compatiblity problem.
If it is a Weblogic bug, we have an support account and I will report this as a bug to
them.
To be able to help you to understand the problem, I placed a tcp monitor between JBoss
Portal 2.6.1 and WLP 10 and additional I monitored the SOAP Message traffic between JBoss
- WLP during the Refresh operation in admin portlet.
In file jboss_portal_wlp10_wsdl_tcp_mon.txt and
jboss_portal_wlp10_wsdl_binding_tcp_mon.txt you can find the service descriptions. Please
mark that with WLP 10 in default producer?wsdl it also contains definitions for wsrp-2.0
(WLP had implemented some feature of it). To be sure that is not causing the problem I
explecitely used the url for version wsrp-1. I would also additionaly include the version
wsrp-2 part of the wsdl.
In the file jboss_portal_wlp_10_refresh_soap.txt, you can see the SOAP traffic between
JBoss and WLP10.
To be sure that JBoss is not acting differently between the JBoss 2.6.1 and WLP9.2MP2, I
also monitored the messages between these versions.
The files jboss_portal_wlp92_wsdl_tcp_mon.txt and
jboss_portal_wlp92MP_wsdl_binding_tcp_mon.txt contains the service descriptions for WLP92
and jboss_portal_wlp_92MP2_refresh_soap.txt SOAP Messages in the refresh process.
As far as I can see JBoss behaves identitically and for some reason WLP is not happy with
the SOAP message:
<?xml version="1.0" encoding="UTF-8"?>
<env:Envelope xmlns:env="http://schemas.xmlsoap.org/soap/envelope/">
<env:Header/>
<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>
</env:Envelope>
which is identical between WLP92 and WLP10.
So I don't know is Weblogic or JBoss has something problematic, but if you tell me
this is Weblogic problem, I would force the issue there.
Regards
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_wlp_10_refresh_soap.txt,
myPortalEAR.ear
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:
http://jira.jboss.com/jira/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira