You are viewing a plain text version of this content. The canonical link for it is here.
Posted to wsrp4j-user@portals.apache.org by Alexandre-Michael Neubert <al...@edifixio.com> on 2007/06/27 14:21:40 UTC
WSRP4J producer configuration question
Hello List,
I have a problem regarding WSRP4J configuration. Here is my architecture:
* I use WPS on client side to consume my remote portlets
* I user tomcat 5.5.16 instrumented with wsrp4j and Pluto on server
side to expose the portets
Everything works fine:
* WPS declared a handler which can be found in WSRP4J under:
~/apache-tomcat-5.5.16/webapps/wsrp4j-producer/WEB-INF/persistence/registrie
s/org.apache.wsrp4j.commons.producer.driver.RegistrationImpl@5132526.xml .
Here is its code:
<?xml version="1.0" encoding="UTF-8"?>
<Registration>
<RegistrationContext>
<registration-handle>192.168.0.2_1182184988693_1</registration-handle>
</RegistrationContext>
<RegistrationData method-get-supported="false">
<consumer-name>IBM WebSphere Portal</consumer-name>
<consumer-modes>wsrp:help</consumer-modes>
<consumer-modes>wsrp:edit</consumer-modes>
<consumer-modes>urn:javax:portlet:mode:custom:configure</consumer-modes>
<consumer-modes>wsrp:view</consumer-modes>
<consumer-agent>IBM WebSphere Portal 5.1.0.3</consumer-agent>
<consumer-window-states>wsrp:maximized</consumer-window-states>
<consumer-window-states>wsrp:normal</consumer-window-states>
<consumer-window-states>wsrp:minimized</consumer-window-states>
</RegistrationData>
</Registration>
* There is also a file in the same directory
(org.apache.wsrp4j.commons.producer.provider.driver.ConsumerPortletRegistrat
ionImpl@192.168.0.2_1182184988693_1.xml) which registers the exposed
portlets using WPS identifiers. Here is its code:
<?xml version="1.0" encoding="UTF-8"?>
<consumer-portlet-registration-impl
xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance" empty="false"
xsi:type="java:org.apache.wsrp4j.commons.producer.provider.dri
ver.ConsumerPortletRegistrationImpl">
<registration-handle>192.168.0.2_1182184988693_1</registration-handle>
<portlet-handles
xsi:type="java:java.lang.String">myportlet.192.168.0.2_1182781519037_6</port
let-handles>
<portlet-handles
xsi:type="java:java.lang.String">myportlet.192.168.0.2_1182781519042_5</port
let-handles>
<portlet-handles
xsi:type="java:java.lang.String">myportlet.192.168.0.2_1182781519044_1</port
let-handles>
<portlet-handles
xsi:type="java:java.lang.String">myportlet.192.168.0.2_1182781519043_4</port
let-handles>
<portlet-handles
xsi:type="java:java.lang.String">myportlet.192.168.0.2_1182781519036_2</port
let-handles> .
The same tags can be found in
~/apache-tomcat-5.5.16/webapps/wsrp4j-producer/WEB-INF/data/portletentityreg
istery.xml:
<?xml version="1.0" encoding="UTF-8"?>
<portlet-entity-registry>
<application id="myportlet">
<definition-id> myportlet </definition-id>
<portlet id="192.168.0.2_1182496841942_1">
<definition-id>myportlet.FirstPortlet</definition-id>
</portlet>
But, I get strange behaviours, which I suppose, is due to a lack of
configuration:
* Every time I submit a form in the remote portlet in WPS, a tag like
those above is generated in
org.apache.wsrp4j.commons.producer.provider.driver.ConsumerPortletRegistrati
onImpl@192.168.0.2_1182184988693_1.xml and in portletentityregistery.xml
which causes these files to be incredibly big after a while
* My Portlets behave strange after a while. Sometimes when I navigate
in my portlet, a link action or a form submission causes the portlet to
display the portlets view page as if I had never perfumed the navigation
(information of the navigation is lost).
Now, my questions are:
* First, did I understand well the registration process or are other
files than those above involved?
* How come that I get a tag generation at every form submission? Can
it be related to a bad consumer configuration on WPS side? Or is it supposed
to work that way?
* Is my strange portlet behaviour related to my second question? Or
can it be some sort of cache on consumer side?
I know most problems raised here are probably WPS related, but I want to
make sure at first that nothing goes wrong on wsrp4j side at that time.
Thanks a lot for every help,
Regards,
Alexandre
-----------------------
Alexandre Neubert
Edifixio
23, Avenue Doyen Louis Weil
38000 Grenoble
04-76-29-89-27
alexandre-michael.neubert@edifixio.com