-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 Ali Sakebi escribió: > Thank u for help about deployment of new portlet to producer, I did it > successfully. I will write a complete instruction about steps needed > to deploy new portlet to WSRP4J manually ASAP. > > But I'm still facing a little more problems from proxy portlet and > producer, some have been solved and struggling with rest. I'm writing > about them in jira. > > Also I have found this two additional link to download Pluto-1.0.1. > (The Admin Portlet bundled with them throws me error when trying to > upload war files, it may be my problem not the Admin Portlet?) > http://archive.apache.org/dist/portals/pluto/BINARIES/ > http://archive.apache.org/dist/portals/pluto/SOURCES/ > > Regards > Ali > > On 12/16/06, Diego Louzán <[EMAIL PROTECTED]> wrote: > Ali Sakebi escribió: >> First I must thank Diego for newly updated README. >> And then I have some question: > >> 1. >> I didn't understand from README (maybe because I'm a little or more >> stupid :'( ) how can I use "producer" without installing Pluto and how >> can I deploy a jsr168 portlet to "producer" manually. (The "producer" >> itself is installed and works.) > > Producer uses PlutoPortal as a backend for its portlets, so it's > basically Pluto's deployer work. If you take a look at the original > testportlet web.xml included in svn and the web.xml deployed in tomcat > by PlutoPortal Admin Portlet, you'll see the difference is that Pluto > adds a wrapper <servlet> around testportlet pointing to pluto's > PortletServlet and a <servlet-mapping> to direct requests to that > servlet. For now, you have two options: > > * Call Pluto's deployer the same way you update the deployed portlets > for ProxyPortlet (NOTE: you need pluto-1.0.1 sources for this to work): > $ maven deploy -Ddeploy=$CATALINA_HOME/webapps/<portletappToDeploy> > > * Manually add those mappings in the web.xml, a reference to the webapp > dir into producer/WEB-INF/data/portletcontexts.txt and another one into > producer/WEB-INF/data/portletentityregistry.txt. > > Obviously, the default testportlet deployed by the AdminPortlet > works because both proxyportlet and producer by default use PlutoPortal. > > The next week I'll add a config webapp to producer to easily upload > a portlet war and deploy it, as well as new instructions to the > README.txt on how to configure tomcat to only use producer. > >> 2. >> "- Point your browser to Pluto Portal Admin page: >> http://localhost:8080/pluto/portal/adminportletapp"; > >> It shows only an empty Pluto (1.0.1-rc2 downloaded form >> http://archive.apache.org/dist/portals/pluto/) page for me, probably I >> should do dependent steps manually. Is there any other idea? > > > I don't know if Pluto 1.0.1-rc2 included the Admin Portlets, better try > with 1.0.1 final or with the sources. > > >> 3. A comment on: >> "- Check that producer is working by pointing your browser to: >> http://localhost:8080/wsrp4j-producer/WSRP4JProducer"; > >> Another useful link for test is: > > > http://localhost:8080/wsrp4j-producer/services/WSRPServiceDescriptionService?method=getServiceDescription > > > >> Note that "/WSRP4JProducer" is replaced with "/services" the reason >> lies in producer servlet-mapping (note /services/*): > >> <servlet-mapping> >> <servlet-name>WSRP4JProducer</servlet-name> >> <url-pattern>/WSRP4JProducer</url-pattern> >> </servlet-mapping> > >> <servlet-mapping> >> <servlet-name>WSRP4JProducer</servlet-name> >> <url-pattern>/services/*</url-pattern> >> </servlet-mapping> > > Yeah, those are the HTTP GET mappings provided by Axis to call its > services. The POST mappings are the default. It won't hurt to add that > info to the README.txt. > > Regards. > Diego. >>
Well, as I said I've always worked with Pluto 1.0.1 source, so I don't know anything about the binaries. You'll have to ask the Pluto folks about those problems. Regards. Diego. -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.4.2.2 (GNU/Linux) Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org iD8DBQFFhmA0gyzZYflJelERAq7lAKCUZPyt5Qq3fjR2hhfTzO/lzY4UvgCfXhwz u7/d9EpZbBz1YRmG2APEkVU= =XF6i -----END PGP SIGNATURE-----
