Do you mean that exposing a web app directly as wsrp (without using jsr168 as an intermediate) is not a standard way of using wsrp (in Java world)? First I should use some bridge to convert ordinary web app to jsr168 and another one to convert jsr168 to wsrp. Doesn't it (using jsr168) duplicate complexity of the solution and/or remove some functionality of wsrp?
BTW, thanks for useful info about how to develop non-jsr168 solution. On 12/3/06, Diego Louzán <[EMAIL PROTECTED]> wrote:
-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 Ali Sakebi escribió: > What about non- jsr168 web apps? I there any sample? > > On 12/3/06, Diego Louzán <[EMAIL PROTECTED]> wrote: > Ali Sakebi escribió: >> Does anyone know what does "producer" do and how does it works? Or how >> can I use WSRP4J to expose a web application as WSRP? > > Using Producer you can expose any jsr-168 portlet app as a WSRP service. > The current svn doesn't work for Producer, so you can't use it. For a > working version, you can download an old snapshot from here: > > http://wiki.apache.org/portals/WSRP4J/WorkingSnapshots > > Select "Attachments" on the menu to download the snapshot. > > Regards. > Diego. >> If you're asking about a non-standard solution, I mean, if you have your own service developed (non-jsr-168) and you want to expose it as a WSRP service, then you'll need to implement your own wrappers around wsrp to be able to expose it as wsrp. Using wsrp4j, you can use the classes provided by org.apache.wsrp4j.producer to implement your solution. The classes under org.apache.wsrp4j.producer are the standard interfaces for the producer; the classes under org.apache.wsrp4j.producer.provider are the wrappers around the actual backend service for the producer: that is, if you provide your own implementation of the org.apache.wsrp4j.producer.provider interfaces, you can have your service exposed as wsrp. Regards. Diego. -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.4.2.2 (GNU/Linux) Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org iD8DBQFFcuKEgyzZYflJelERAqxBAJsHJP9UOFZOek2S1gvP9CeTfWfm8wCfYjVQ pRY9UuExJvnX1+MmLHb4IE8= =y9Fo -----END PGP SIGNATURE-----
