Re: Websphere Web Services

[Diego Louzán <dl...@apache.org>]

-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1

Pete wrote:
> I forgot to mention, that to get the WSRP4J web
> services to work in Websphere 6, we had to use
> Websphere version 6.0.1 +.  
> http://www-1.ibm.com/support/docview.wss?rs=0&uid=swg24009071
> 
> See this link for the particular reason:
> http://www-1.ibm.com/support/docview.wss?rs=180&uid=swg1PQ98285
> 
> 
> --- Pete <pd...@yahoo.com> wrote:
> 
> 
>>We have made the effort to re-tool WSRP4J to use the
>>Websphere web services stack.  This is helpful when
>>deploying in the websphere environment - for example
>>you can use the built in administration to secure
>>the
>>web services.
>>
>>I hesitate to put much detail up here because I'm
>>not
>>sure that what we did was "generic".  So I'll
>>outline
>>a few things that had to change.  The hope is that
>>real developers would change WSRP4J to handle this. 
>>Maybe something could be added to the "To Do" list
>>to
>>make the web services stack a bit more configurable.
>>
>>IBM Web services types:
>>
>>We found that we could not generate the appropriate
>>supporting Java classes for the IBM websphere web
>>services via the WSRP WSDL.  Some types were not
>>created.  In the end we used some IBM Websphere
>>Portal
>>jars: wp.wsrp.commons.jar (for the
>>oasis.names.tc.wsrp.v1.types package) and we
>>attempted
>>to use the wp.wsrp.consumer-oasis.jar (for the
>>oasis.names.tc.wsrp.v1.bind package) but found that
>>IBM had used a different case in their class names
>>(capitolized WSRP_V1, rather than WSRP_v1).
>>
>>Required code changes:
>>
>>Access to the servlet object must be modified to
>>support Websphere. The following class changes are
>>required:
>>[add]
>>
> 
> org.apache.wsrp4j.producer.util.ServletEndpointContextHolder
> 
>>[modify]
>>org.apache.wsrp4j.producer.util.ServletAccess
>>[modify]
>>
> 
> org.apache.wsrp4j.persistence.xml.driver.ServerPersistentInformationProviderImpl
> 
>>[modify]
>>org.apache.wsrp4j.producer.driver.WSRPEngine
>>
>>The class 'oasis.names.tc.wsrp.v1.types.Fault' must
>>be
>>modified to support WSRP4J. The following classes
>>are
>>dependent on that change:
>>[modify]org.apache.wsrp4j.exception.WSRPXHelper
>>[modify]org.apache.wsrp4j.util.ParameterChecker
>>[modify]org.apache.wsrp4j.util.PropertyListHelper
>>
>>The following classes are dependent on the axis code
>>and need to be modified:
>>[modify]org.apache.wsrp4j.producer.util.Base64
>>[modify]org.apache.wsrp4j.util.PropertyListHelper
>>[delete]delete
>>org.apache.wsrp4j.util.MessageElementHelper
>>
>>The following classes are dependent on the axis
>>interfaces and need to be modified:
>>[modify]The
>>'org.apache.wsrp4j.producer.driver.WSRPEngine' also
>>requires that the 'implements' statement be removed
>>
> 
> [modify]org.apache.wsrp4j.consumer.driver.PortletDriverImpl
> 
> [modify]org.apache.wsrp4j.consumer.driver.ProducerImpl
> 
>>This obviously does not cover all the details.  If
>>there is anyone in the WSRP4J development team that
>>is
>>interested in more, we would certainly do our best
>>to
>>contribute.  
>>
>>Pete
>>
>>
>>
>>		
>>__________________________________ 
>>Yahoo! Mail - PC Magazine Editors' Choice 2005 
>>http://mail.yahoo.com
>>
> 
> 
> 
> 
> 		
> __________________________________ 
> Yahoo! Mail - PC Magazine Editors' Choice 2005 
> http://mail.yahoo.com

This is definitely very interesting for WSRP4J. I'll take a look. Thank
you ^^

Regards.
Diego.
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.4.1 (Cygwin)
Comment: Using GnuPG with Thunderbird - http://enigmail.mozdev.org

iD8DBQFDQnQagyzZYflJelERAh+eAJ99R4fuHRSEwFa0woLz/tdFuuj8CgCeKFAo
K5xQjLFYNd7r0V9/hCQPzJ8=
=LqUl
-----END PGP SIGNATURE-----