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 Diego Louzán <dl...@apache.org> on 2005/08/31 01:58:12 UTC
[ANNOUNCE] WSRP4J Maven migration and module refactor (almost) finished
-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1
Hello everybody!! I'm pleased to announce the availability of the (almost)
finished Maven migration and module refactoring of the WSRP4J repository. I've
been doing lots of checks and it should work fine now.
Currently, SwingConsumer it's not integrated (I'll try to get it working in a
few hours). As Julie suggested, the repository modules are as follows:
sandbox/wsrp4j/ -->
commons/
Common code.
commons-consumer/
Common code to any consumer implementation.
Depends on commons.
commons-producer/
Common code to any producer implementation.
Depends on commons.
persistence-xml/
XML mapping persistence implementation.
Depends on commons, commons-producer and commons-consumer.
consumer/
JSR-168 portlet consumer implementation.
Depends on commons, commons-consumer and persistence-xml.
consumer-swingconsumer/
Java Swing application consumer implementation.
Depends on commons, commons-consumer and persistence-xml.
producer-axis/
Axis-based producer implementation.
Depends on commons, commons-producer and persistence-xml.
testportlet/
JSR-168 test portlet.
etc/
Miscellaneous configuration for all modules.
site/
WSRP4J site documentation.
As I had already created "consumer/" and "producer/" directories when Julie
suggested the module distribution, they'll be named like that instead of
"consumer-proxyportlet/" and "producer-axis/" until we move to SVN (changing a
directory name in CVS is a lot of work, you know lol).
Tomorrow I'll try to get working the plugin system for consumer code, but the
main functionality is finished.
As part of the migration, I have refactored the code to work with
pluto-1.0.1-rc4 (the main trunk works with pluto-1.0.1-rc3). I won't make any
more changes to the main codebase, as this migration is expected to be the new
main codebase.
For building all (from wsrp4j repository):
$ cd sandbox/wsrp4j
$ cp build.properties.sample build.properties
Edit build.properties for your environment (tomcat location).
$ maven deploy-producer # builds all code, deploys producer
or
$ maven all # builds all code, deploys producer, builds site
The producer, as well as the testportlet will be deployed to tomcat dir. For
consuming this services, download pluto-1.0.1-rc4 source, then (from pluto repo):
$ cp build.properties.sample build.properties
Edit build.properties for your environment (tomcat location).
$ maven fullDeployment
Start <wsrp4jdir>/tools/tunnel.sh (I have to fix and include this in the sandbox/).
Start Tomcat, and point your browser to http://localhost:8080/pluto/portal
Click on the "Admin" portlet and then "Browse...". Select
"<wsrp4dir>/sandbox/wsrp4j/consumer/target/wsrp4j-consumer.war". Click on
"Submit". Write a "Title" and a "Description" for it and click on "Submit"
again. On the next page just click "Submit" again. Stop tomcat, now edit the
file <tomcatdir>/webapps/pluto/WEB-INF/data/portletentityregistry.xml
Taking as reference
<tomcatdir>/webapps/wsrp4j-consumer/examples/portletentityregistry.xml.example
you have to add two preferences to the definition of
wsrp4j-consumer.WSRP4JConsumer:
<application id="6">
<definition-id>wsrp4j-consumer</definition-id>
<portlet id="0">
<definition-id>wsrp4j-consumer.WSRP4JConsumer</definition-id>
<preferences>
<pref-name>wsrp_portlet_handle</pref-name>
<pref-value>0.1</pref-value>
<read-only>false</read-only>
</preferences>
<preferences>
<pref-name>wsrp_producer_id</pref-name>
<pref-value>1</pref-value>
<read-only>false</read-only>
</preferences>
</portlet>
</application>
Now restart tomcat and you should automagically be able to consumer your remote
portlets ;-) You'll see the soap traffic through the tunnel.sh.
The only thing I don't know yet how to do is how to integrate the
tools/tunnel.sh, as now we don't want jars included with the repository. I
thought in creating a new tools/ module that calls the tunnel.sh through maven,
using a dependency on Axis. Anyway, suggestions are welcome on a pretty
solution for this.
Testers are welcome too ^_^
Regards.
Diego.
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.2.6 (GNU/Linux)
iD8DBQFDFPKTgyzZYflJelERAu0YAJ0YfDx7xqYutXIh+bqw4SZzrOBL4gCeKo5X
oL/aL3/6wcTLRJNKAGSJyWo=
=pXy5
-----END PGP SIGNATURE-----
Re: [ANNOUNCE] WSRP4J Maven migration and module refactor (almost)
finished
Posted by Julie MacNaught <jm...@apache.org>.
Great job! This is good work.
Let the testing begin.
Diego Louzán wrote:
> -----BEGIN PGP SIGNED MESSAGE-----
> Hash: SHA1
>
> Hello everybody!! I'm pleased to announce the availability of the (almost)
> finished Maven migration and module refactoring of the WSRP4J repository. I've
> been doing lots of checks and it should work fine now.
>
> Currently, SwingConsumer it's not integrated (I'll try to get it working in a
> few hours). As Julie suggested, the repository modules are as follows:
>
> sandbox/wsrp4j/ -->
> commons/
> Common code.
> commons-consumer/
> Common code to any consumer implementation.
> Depends on commons.
> commons-producer/
> Common code to any producer implementation.
> Depends on commons.
> persistence-xml/
> XML mapping persistence implementation.
> Depends on commons, commons-producer and commons-consumer.
> consumer/
> JSR-168 portlet consumer implementation.
> Depends on commons, commons-consumer and persistence-xml.
> consumer-swingconsumer/
> Java Swing application consumer implementation.
> Depends on commons, commons-consumer and persistence-xml.
> producer-axis/
> Axis-based producer implementation.
> Depends on commons, commons-producer and persistence-xml.
> testportlet/
> JSR-168 test portlet.
> etc/
> Miscellaneous configuration for all modules.
> site/
> WSRP4J site documentation.
>
> As I had already created "consumer/" and "producer/" directories when Julie
> suggested the module distribution, they'll be named like that instead of
> "consumer-proxyportlet/" and "producer-axis/" until we move to SVN (changing a
> directory name in CVS is a lot of work, you know lol).
>
> Tomorrow I'll try to get working the plugin system for consumer code, but the
> main functionality is finished.
>
> As part of the migration, I have refactored the code to work with
> pluto-1.0.1-rc4 (the main trunk works with pluto-1.0.1-rc3). I won't make any
> more changes to the main codebase, as this migration is expected to be the new
> main codebase.
>
> For building all (from wsrp4j repository):
>
> $ cd sandbox/wsrp4j
> $ cp build.properties.sample build.properties
>
> Edit build.properties for your environment (tomcat location).
>
> $ maven deploy-producer # builds all code, deploys producer
> or
> $ maven all # builds all code, deploys producer, builds site
>
> The producer, as well as the testportlet will be deployed to tomcat dir. For
> consuming this services, download pluto-1.0.1-rc4 source, then (from pluto repo):
>
> $ cp build.properties.sample build.properties
>
> Edit build.properties for your environment (tomcat location).
>
> $ maven fullDeployment
>
> Start <wsrp4jdir>/tools/tunnel.sh (I have to fix and include this in the sandbox/).
>
> Start Tomcat, and point your browser to http://localhost:8080/pluto/portal
> Click on the "Admin" portlet and then "Browse...". Select
> "<wsrp4dir>/sandbox/wsrp4j/consumer/target/wsrp4j-consumer.war". Click on
> "Submit". Write a "Title" and a "Description" for it and click on "Submit"
> again. On the next page just click "Submit" again. Stop tomcat, now edit the
> file <tomcatdir>/webapps/pluto/WEB-INF/data/portletentityregistry.xml
> Taking as reference
> <tomcatdir>/webapps/wsrp4j-consumer/examples/portletentityregistry.xml.example
> you have to add two preferences to the definition of
> wsrp4j-consumer.WSRP4JConsumer:
>
> <application id="6">
> <definition-id>wsrp4j-consumer</definition-id>
> <portlet id="0">
> <definition-id>wsrp4j-consumer.WSRP4JConsumer</definition-id>
> <preferences>
> <pref-name>wsrp_portlet_handle</pref-name>
> <pref-value>0.1</pref-value>
> <read-only>false</read-only>
> </preferences>
> <preferences>
> <pref-name>wsrp_producer_id</pref-name>
> <pref-value>1</pref-value>
> <read-only>false</read-only>
> </preferences>
> </portlet>
> </application>
>
> Now restart tomcat and you should automagically be able to consumer your remote
> portlets ;-) You'll see the soap traffic through the tunnel.sh.
>
> The only thing I don't know yet how to do is how to integrate the
> tools/tunnel.sh, as now we don't want jars included with the repository. I
> thought in creating a new tools/ module that calls the tunnel.sh through maven,
> using a dependency on Axis. Anyway, suggestions are welcome on a pretty
> solution for this.
>
> Testers are welcome too ^_^
>
> Regards.
> Diego.
> -----BEGIN PGP SIGNATURE-----
> Version: GnuPG v1.2.6 (GNU/Linux)
>
> iD8DBQFDFPKTgyzZYflJelERAu0YAJ0YfDx7xqYutXIh+bqw4SZzrOBL4gCeKo5X
> oL/aL3/6wcTLRJNKAGSJyWo=
> =pXy5
> -----END PGP SIGNATURE-----
>
>
--
Julie MacNaught
IBM Research
jmacna@apache.org
jmacna@us.ibm.com
DADB E3B5 8CB7 6B9B F4A0 8BF7 E830 1848 16A8 D3AB