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

[EMAIL PROTECTED] escribió:
> Hello Diego,
> 
> Thank you very much for your quick answer. I was not sure
> that my config was ok and now it is clear for me.
> 
> I have another question if you have some time: I am
> currently making a proof of concept about deploying some
> wsrp portlets in IBM WebSphere Portal 5.1.0.3. The target
> for us is to deploy a large amount of remote portlets for
> one of our important customer.
> 
> At this time it is working pretty well. Are you aware of
> some projects that have already made wsrp4j integration with
> this portal?
> 
> Actually I have seen on the mailing list a discussion
> between you and Julie MacNaught where you said that wsrp4j
> is not ready for a production environment
> (http://mail-archives.apache.org/mod_mbox/portals-wsrp4j-user/200502.mbox/[EMAIL
>  PROTECTED]).
> It was in 2005, so what is your feeling 2 years later?
> 
> Do you think that it is realistic to have an application
> with several thousands of users working with wsrp4J? 
> 
> Thank you by advance for your answer.
> 
> Kind Regards,
> 
> Adrien
> 
> 
> --------------------- ALICE SECURITE ENFANTS ---------------------
> Protégez vos enfants des dangers d'Internet en installant Sécurité Enfants, 
> le contrôle parental d'Alice.
> http://www.aliceadsl.fr/securitepc/default_copa.asp
> 
> 

Well, in the past few months some new functionalities have been added
and we have resolved lots of bugs. If you plan to use ProxyPortlet for
deploying portlets in WebShere you have to keep in mind some things:

- - You'll probably have to tweak some source code in WSRP4J to adapt it
to WebSphere. Right now it should deploy without problems, but in
practice I've found that each portal has its own subtleties that you'll
have to resolve.
- - If you want support for Producer URL Writing you'll have to provide a
plugin implementation for linking the WebSphere Portal URL generation
and WSRP4J. You can check the implementation of that plugin for
PlutoPortal to use it as an example.
- - There's a provision on WSRP4J API for secure communication, but it's
not implemented. If you need it for your customers (which wouldn't
surprise me) then you could add that and contribute the code :-)
- - The persistence layer is completely pluggable, you can choose between
the old Castor-based module (the persistent data is written to XML
files) or the new Hibernate-based DB module. Of course, you can also add
your own persistence module if you need it.
- - There's no support at the moment for uploading binary data on
ProxyPortlet portlets. It's not very hard to add (some members have
already suggested ways of doing it) but it's not implemented.

My main point is that ProxyPortlet is the most mature component of
WSRP4J and the main functionality is there, but be prepared for some
source code tweaking. In fact, although ProxyPortlet aims to be a
portal-independent component, the target of WSRP4J as a whole is to
serve as the base for any portal/client that wishes to add WSRP
consumer/producer support.

Regards.
Diego.
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.4.2.2 (GNU/Linux)
Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org

iD8DBQFFw13rgyzZYflJelERAriOAKCHxUiI5uMMR7t1y/S1mJmOeKU2rQCeMNDi
yOK+et+DhEY/xWXlbbtW+T4=
=sGYu
-----END PGP SIGNATURE-----

Reply via email to