You are viewing a plain text version of this content. The canonical link for it is here.
Posted to wsrp4j-dev@portals.apache.org by ri...@peoplesoft.com on 2004/10/20 01:38:49 UTC

Getting SAXException: No deserializer for boolean in WSRP4J producer

When a user of a IBM WebSphere Portal requests markup from a WSRP4J
producer a fault occurs. It appears that the "secureClientCommunication"
isn't using the xml ns according to the wsrp 1.0 spec.

Is this a correct analysis?
 Has anyone seen this problem before?
 If this is allowable, how can it be worked around?

Here is the complete message exchange:


==============
Listen Port: 8080
Target Host: localhost
Target Port: 80
==== Request ====
POST /pspc/wsrp4j/WSRPBaseService HTTP/1.0
Content-Type: text/xml; charset=utf-8
Accept: application/soap+xml, application/dime, multipart/related, text/*
User-Agent: IBM WebServices/1.0
Host: localhost:8080
Cache-Control: no-cache
Pragma: no-cache
SOAPAction: "urn:oasis:names:tc:wsrp:v1:getMarkup"
Content-Length: 1450
Cookie:
JSESSIONID=B1QC7Hjv7PsGpy4FXK0yCmyvqG0zvHy2SThk1wJNnmT7L3Wp7rv6!-62586972

<?xml version="1.0" encoding="UTF-8"?>
<soapenv:Envelope
 xmlns:soapenv="http://schemas.xmlsoap.org/soap/envelope/"
 xmlns:soapenc="http://schemas.xmlsoap.org/soap/encoding/"
 xmlns:xsd="http://www.w3.org/2001/XMLSchema"
 xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance">
<soapenv:Body>
 <getMarkup xmlns="urn:oasis:names:tc:wsrp:v1:types">
  <registrationContext xsi:nil="true"/>
  <portletContext>
    <portletHandle>testsuite.TestPortlet1</portletHandle>
  </portletContext>
  <runtimeContext>
    <userAuthentication>wsrp:none</userAuthentication>
    <portletInstanceKey>7_0_FM</portletInstanceKey>
    <namespacePrefix>wsrp_rewrite_</namespacePrefix>
  </runtimeContext>
  <userContext>
    <userContextKey>wpsadmin</userContextKey>
    <profile/>
  </userContext>
  <markupParams>
    <secureClientCommunication
xsi:type="soapenc:boolean">0</secureClientCommunication>
    <locales>en</locales>
    <mimeTypes>text/html</mimeTypes>
    <mode>wsrp:view</mode>
    <windowState>wsrp:normal</windowState>
    <clientData>
      <userAgent>Mozilla/4.0 (compatible; MSIE 6.0; Windows NT 5.0; .NET
CLR 1.1.4322)</userAgent>
    </clientData>
    <markupCharacterSets>UTF-8</markupCharacterSets>
    <validNewModes>wsrp:edit</validNewModes>
    <validNewModes>wsrp:view</validNewModes>
    <validNewModes>wsrp:help</validNewModes>
    <validNewWindowStates>wsrp:normal</validNewWindowStates>
    <validNewWindowStates>wsrp:maximized</validNewWindowStates>
    <validNewWindowStates>wsrp:minimized</validNewWindowStates>
  </markupParams>
 </getMarkup>
</soapenv:Body>
</soapenv:Envelope>

==== Response ====
HTTP/1.1 500 Internal Server Error
Date: Tue, 19 Oct 2004 22:08:02 GMT
Server: WebLogic Server 8.1 SP3 Tue Jun 29 23:11:19 PDT 2004 404973
Content-Type: text/xml; charset=utf-8
Connection: Close

<?xml version="1.0" encoding="utf-8"?>
<soapenv:Envelope xmlns:soapenv="http://schemas.xmlsoap.org/soap/envelope/"
xmlns:xsd="http://www.w3.org/2001/XMLSchema"
xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance">
 <soapenv:Body>
  <soapenv:Fault>
   <faultcode>soapenv:Server.userException</faultcode>
   <faultstring>org.xml.sax.SAXException: No deserializer for
{http://schemas.xmlsoap.org/soap/encoding/}boolean</faultstring>
   <detail/>
  </soapenv:Fault>
 </soapenv:Body>
</soapenv:Envelope>
==============

Re: Getting SAXException: No deserializer for boolean in WSRP4J producer

Posted by Julie MacNaught <jm...@apache.org>.
I'm not sure why WPS is using this namepace in the middle of the 
markupParams type.  The WSDL defines the structure for markupParams and 
the secureClientCommunication element has type xsd:boolean.

I've sent a note to a couple of guys in WPS.  Hopefully we can figure 
this out.

Alternatively, you could try to install a deserializer on the Axis side 
as a workaround.  The file server.wsdd contains registration information 
about serializers and deserializers.  You could write one and add it to 
the file.

Which version of WPS are you using?

ricky_frost@peoplesoft.com wrote:

> When a user of a IBM WebSphere Portal requests markup from a WSRP4J
> producer a fault occurs. It appears that the "secureClientCommunication"
> isn't using the xml ns according to the wsrp 1.0 spec.
> 
> Is this a correct analysis?
>  Has anyone seen this problem before?
>  If this is allowable, how can it be worked around?
> 
> Here is the complete message exchange:
> 
> 
> ==============
> Listen Port: 8080
> Target Host: localhost
> Target Port: 80
> ==== Request ====
> POST /pspc/wsrp4j/WSRPBaseService HTTP/1.0
> Content-Type: text/xml; charset=utf-8
> Accept: application/soap+xml, application/dime, multipart/related, text/*
> User-Agent: IBM WebServices/1.0
> Host: localhost:8080
> Cache-Control: no-cache
> Pragma: no-cache
> SOAPAction: "urn:oasis:names:tc:wsrp:v1:getMarkup"
> Content-Length: 1450
> Cookie:
> JSESSIONID=B1QC7Hjv7PsGpy4FXK0yCmyvqG0zvHy2SThk1wJNnmT7L3Wp7rv6!-62586972
> 
> <?xml version="1.0" encoding="UTF-8"?>
> <soapenv:Envelope
>  xmlns:soapenv="http://schemas.xmlsoap.org/soap/envelope/"
>  xmlns:soapenc="http://schemas.xmlsoap.org/soap/encoding/"
>  xmlns:xsd="http://www.w3.org/2001/XMLSchema"
>  xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance">
> <soapenv:Body>
>  <getMarkup xmlns="urn:oasis:names:tc:wsrp:v1:types">
>   <registrationContext xsi:nil="true"/>
>   <portletContext>
>     <portletHandle>testsuite.TestPortlet1</portletHandle>
>   </portletContext>
>   <runtimeContext>
>     <userAuthentication>wsrp:none</userAuthentication>
>     <portletInstanceKey>7_0_FM</portletInstanceKey>
>     <namespacePrefix>wsrp_rewrite_</namespacePrefix>
>   </runtimeContext>
>   <userContext>
>     <userContextKey>wpsadmin</userContextKey>
>     <profile/>
>   </userContext>
>   <markupParams>
>     <secureClientCommunication
> xsi:type="soapenc:boolean">0</secureClientCommunication>
>     <locales>en</locales>
>     <mimeTypes>text/html</mimeTypes>
>     <mode>wsrp:view</mode>
>     <windowState>wsrp:normal</windowState>
>     <clientData>
>       <userAgent>Mozilla/4.0 (compatible; MSIE 6.0; Windows NT 5.0; .NET
> CLR 1.1.4322)</userAgent>
>     </clientData>
>     <markupCharacterSets>UTF-8</markupCharacterSets>
>     <validNewModes>wsrp:edit</validNewModes>
>     <validNewModes>wsrp:view</validNewModes>
>     <validNewModes>wsrp:help</validNewModes>
>     <validNewWindowStates>wsrp:normal</validNewWindowStates>
>     <validNewWindowStates>wsrp:maximized</validNewWindowStates>
>     <validNewWindowStates>wsrp:minimized</validNewWindowStates>
>   </markupParams>
>  </getMarkup>
> </soapenv:Body>
> </soapenv:Envelope>
> 
> ==== Response ====
> HTTP/1.1 500 Internal Server Error
> Date: Tue, 19 Oct 2004 22:08:02 GMT
> Server: WebLogic Server 8.1 SP3 Tue Jun 29 23:11:19 PDT 2004 404973
> Content-Type: text/xml; charset=utf-8
> Connection: Close
> 
> <?xml version="1.0" encoding="utf-8"?>
> <soapenv:Envelope xmlns:soapenv="http://schemas.xmlsoap.org/soap/envelope/"
> xmlns:xsd="http://www.w3.org/2001/XMLSchema"
> xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance">
>  <soapenv:Body>
>   <soapenv:Fault>
>    <faultcode>soapenv:Server.userException</faultcode>
>    <faultstring>org.xml.sax.SAXException: No deserializer for
> {http://schemas.xmlsoap.org/soap/encoding/}boolean</faultstring>
>    <detail/>
>   </soapenv:Fault>
>  </soapenv:Body>
> </soapenv:Envelope>
> ==============
> 
> 
>