flow of code

[Anuraag Sarangi <as...@cs.indiana.edu>]

Hi,

I am newbie to WSRP.  I need a little help understanding what is going on
in the code once we start up the SwingConsumer.  What is the flow of code
after that?!  Which files should I "follow" so that I can understand the
interactions going on between the SwingConsumer and the wsrp-webapps (the
one in Tomcat) producer?! Is there any documentation about this
somewhere?!  This will allow me to experiment with creating and modifying
portlets.

Thanks very much for your support,
Regards,
Anuraag

--------------------------------

Anuraag Sarangi
PhD Student
Computer Science
Indiana University - Bloomington

--------------------------------

"The mind is not a vessel to be
filled, but a fire to be kindled."
		     --- Plutarch

--------------------------------

On Thu, 22 Apr 2004, Julie MacNaught wrote:

> Jason,
>
> You probably know this already, but you are more than welcome to change
> the code and send us a patch.  We can always use more folks involved.
>
> Also, you can submit a bug into JIRA.
>
> Thanks!
>
> Jason Novotny wrote:
>
> >
> > Thanks Rus,
> >
> >    Sadly I just took a quick glance and it's not exactly JSR
> > compliant-- there are some pluto imports at the top:
> >
> > import org.apache.pluto.core.CoreUtils;
> > import org.apache.pluto.om.window.PortletWindow;
> >
> >    If someone could just remove these to use the core portlet objects
> > than it may just work I suppose....
> >
> >    Thanks, Jason
> >
> > Russell Heywood wrote:
> >
> >> A simpler place to start might be to look at ProxyPortlet, which is
> >> located in the portlets/ subdirectory of the WSRP distribution.
> >> ProxyPortlet is a JSR-168 portlet which can consume remote WSRP
> >> portlets.  You'll need to hack it up a little to get it to work, but
> >> it's probably much closer to what you need than trying to start with
> >> the Swing consumer.
> >>
> >> Good luck,
> >> - rus
> >>
> >> -----Original Message-----
> >> From: Jason Novotny [mailto:novotny@aei.mpg.de]
> >> Sent: Wednesday, April 21, 2004 3:12 AM
> >> To: wsrp4j-user@ws.apache.org
> >> Subject: Re: using wsrp in portlet based portal
> >>
> >>
> >>
> >> Hi Julie,
> >>
> >>     Thanks very much for your clarifications. I suppose with GridSphere
> >> we would like to be a consumer so I imagine I would have to look at the
> >> sample consumer code you have (the Swing client) to see how thats done.
> >> Not knowing too much about the technical details, I assume I would
> >> create a special portlet on our side that uses the sample consumer code
> >> to act as a proxy for the remote portlets-- does this sound right?
> >>     I'm also interested in what is the minimum work needed to show
> >> integration. For instance is there a demo WSRP deployment somewhere
> >> providing services I can invoke to get portlet markup, etc to display as
> >> a sample for our project? Who else is using WSRP4J now anyway?
> >>
> >>     Thanks, Jason
> >>
> >> Julie MacNaught wrote:
> >>
> >> > WSRP4J is architected so that "provider" is pluggable.  WSRP4J comes
> >> > with an implementation of the provider interface that works with
> >> > Pluto, but you can write your own. "Provider" is interface between the
> >> > WSRP4J engine (the actual web service responding to SOAP requests),
> >> > and the portlet container (i.e. provider).
> >> >
> >> > In your architecture WRT GridSphere, are you trying to implement a
> >> > Consumer or a Producer?   The WSRP4J Apache project is really all
> >> > about providing an open source Producer.  We do provided a piece of
> >> > code called the Swing Consumer, but this is primarily used to test the
> >> > Producer and portlets.  You are certainly welcome to use the code in
> >> > the Consumer, but it is not fully compliant with the spec, nor is it a
> >> > very nice Portal.
> >> >
> >> > Here's a little background you might need.  Maybe you know this
> >> already:
> >> >
> >> > There are 2 major components in the WSRP spec.  One is the Consumer
> >> > and the other is the Producer.  The role of the Consumer is the
> >> > Portal.  It is the part of the system that communicates with actual
> >> > end users,  and aggregates content from remote WSRP Producers and
> >> > locally hosted portlets.   A WSRP Producer exposes portlets via a
> >> > webservice interface.   WSRP is agnostic as to how those portlets are
> >> > implemented.  A simplified way to look at it is that the WSRP Producer
> >> > is a server of portlet markup, and the WSRP Consumer is a client.
> >> > Hope this helps.
> >> >
> >> > Jason Novotny wrote:
> >> >
> >> >>
> >> >> Hi,
> >> >>
> >> >>    I'd like to know what it would take to use wsrp4j in our own
> >> >> portlet based portal, GridSphere, available at www.gridsphere.org. We
> >> >> our now JSR 168 compliant and have implemented our own implementation
> >> >> of the spec. I would rather not have to implement wsrp spec as well
> >> >> and would like to use wsrp4j. In the source code, I see lots of files
> >> >> pertaining to Pluto, and I wonder what I have to do to support our
> >> >> portal-- is this supported/documented anywhere, or is it pretty much
> >> >> glued to Pluto?
> >> >>
> >> >>    Thanks, Jason
> >> >>
> >> >>
> >> >
> >>
> >
> >
>
> --
> Julie MacNaught
> IBM Research
> jmacna@apache.org
> jmacna@us.ibm.com
>
>