]
Andrew Oliver commented on JBPORTAL-1536:
-----------------------------------------
This does not work under JDK 5 either. I added relevant screenshots of the WSRP screens
misbehavior 1-6. I also added the relevant log (log.txt) and conversation. Note that in
the conversation the "public" is not saved (I did enter it) and nothing you do
seems to help it be part of the request. I don't discount that this could be a WS
problem but it looks more interface related...like it isn't saving
"public"..
Jboss WSRP incompatible with BEA
--------------------------------
Key: JBPORTAL-1536
URL:
http://jira.jboss.com/jira/browse/JBPORTAL-1536
Project: JBoss Portal
Issue Type: Bug
Security Level: Public(Everyone can see)
Components: Portal WSRP
Affects Versions: 2.6 Final
Reporter: Andrew Oliver
Assigned To: Chris Laprun
Fix For: 2.8 Final, 2.6.1 Final
Attachments: 1.png, 2.png, 3.png, 4.png, 5.png, 6.png, conv.dmp, log.txt,
wireshark.png, wsdl.dump, wsrp_create_consumer_failed.png
do the public-bea-wsrp.xml wsrp example from the doco
(
http://docs.jboss.com/jbportal/v2.6/reference-guide/html_single/#wsrp). If you paste the
WSDL in to the WSRP admin console you get: "Problem getting service description for
producer bea Cause: setProperty must be overridden by all subclasses of SOAPMessage".
If you create the descriptor you get: "Caused by:
org.jboss.xb.binding.JBossXBException: Failed to parse source: The processing instruction
target matching "[xX][mM][lL]" is not allowed. @ *unknown*[3,6]
at
org.jboss.xb.binding.parser.sax.SaxJBossXBParser.parse(SaxJBossXBParser.java:156)
at org.jboss.xb.binding.UnmarshallerImpl.unmarshal(UnmarshallerImpl.java:169)
at org.jboss.portal.wsrp.deployment.WSRPDeployer.init(WSRPDeployer.java:108)
... 21 more
Caused by: org.xml.sax.SAXException: The processing instruction target matching
"[xX][mM][lL]" is not allowed. @ *unknown*[3,6]
at
org.jboss.xb.binding.parser.sax.SaxJBossXBParser$MetaDataErrorHandler.fatalError(SaxJBossXBParser.java:332)"
Over the wire (wireshark) the WSDL etc looks okay. Note this works with 2.4.
--
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators: