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 Cassio Nishiguchi <ca...@9starresearch.com> on 2005/04/29 23:37:42 UTC
Modify proxyportlet to display list of available portlets
Hi,
currently the wsrp_portlet_hanlde for the remote portlet is specified in
portlet.xml, right? I need to modify this behavior so that the proxyportlet
will get a list of remote portlets from the getServiceDescription response
and display them to the user. The user should then select the desired
portlet from the list and the proxyportlet will send the associated
wsrp_portlet_handle in the subsequent getMarkup call. Eventually I want to
be able to select the desired producer from a list too, but this will be good
to start with.
Could anyone give me some guidance as to how I could go about doing this?
Would it take a lot of effort or is it pretty straight-forward once you get
to know the proxyportlet code?
Thanks in advance,
Cassio Nishiguchi
Re: Modify proxyportlet to display list of available portlets
Posted by Diego Louzán <di...@metalicana.org>.
No, I mean in the next 1-2 months, so if you are in a hurry you can do it
yourself for now and then contribute your code to the project :-) I'll stay
tuned on updates.
Regards.
Diego.
Cassio Nishiguchi wrote:
> So Diego, how soon do you expect to implement the ability to get
> wsrp_portlet_handle from the getServiceDescription response, instead of
> specifying it in an xml file (which should be portletentityregistry.xml in
> Pluto, to correct my original question)? I only ask because I wanna get it
> working in the next few weeks and if your "near future" means longer than
> that, I could try and do it myself (perhaps with a little help) and then
> contribute the code back to you.
>
> Cassio
>
> On Thu May 5 2005 10:47 am, Diego Louzán wrote:
>
>>That's a behaviour I expect to implement in a near future version. I need
>>too some kind of wizard to add new portlets for my own project. I haven't
>>still thought how to do it, but I imagine that creating a management
>>portlet should be enough. Given endpoints for the 4 wsrp interfaces (maybe
>>only 2, portletDescription, and registration if applicable), this portlet
>>will implement a discovery mechanism and modify accordingly the appropriate
>>xml files.
>>
>>Regards.
>>Diego.
>>
>>Cassio Nishiguchi wrote:
>>
>>>Hi,
>>>currently the wsrp_portlet_hanlde for the remote portlet is specified in
>>>portlet.xml, right? I need to modify this behavior so that the
>>>proxyportlet will get a list of remote portlets from the
>>>getServiceDescription response and display them to the user. The user
>>>should then select the desired portlet from the list and the proxyportlet
>>>will send the associated wsrp_portlet_handle in the subsequent getMarkup
>>>call. Eventually I want to be able to select the desired producer from a
>>>list too, but this will be good to start with.
>>>Could anyone give me some guidance as to how I could go about doing this?
>>>Would it take a lot of effort or is it pretty straight-forward once you
>>>get to know the proxyportlet code?
>>>
>>>Thanks in advance,
>>>Cassio Nishiguchi
Re: Modify proxyportlet to display list of available portlets
Posted by Diego Louzán <dl...@apache.org>.
As I said, I haven't thoroughly thought about it, but it's the way tomcat
works, you have a web application to manage the other web applications it
deploys, so I suppose we could implement the portlet management this way.
Regards.
Diego.
Cassio Nishiguchi wrote:
> Thanks Diego, that is what I was trying to say. I think I may have confused
> people because I was just thinking about adding this functionality to
> proxyportlet itself - as in the first time you access the proxyportlet you
> would get a setup screen where you can choose the remote portlet you want to
> access from a list. This list would be populated with the information
> received from the serviceDescriptionResponse. Once you pick the portlet, the
> corresponding portletHandle would be written to the xml file and every access
> thereafter would work as it does currently.
> However, a separate management portlet may work too.
>
> Cassio
>
> On Fri May 6 2005 10:45 am, Diego Louzán wrote:
>
>>Julie, I think he means a kind of management portlet in the consumer that
>>allows to specify a wsrp producer endpoint url and then visually get the
>>list of portlet_handles (and I suppose the descriptions also) that the
>>producer returns in a getServiceDescription request. That way you could add
>>this portlet_handles to xml configuration files automatically instead of by
>>hand. In the current state of proxyportlet, if you don't know the
>>portlet_handle that you want from a producer, you have to inspect manually
>>the soap sniffer to see what portlet_handle's the producer returns in a
>>getServiceDescription request and then add the desired ones to the xml
>>configuration files.
>>
>>Regards.
>>Diego.
>>
>>Julie MacNaught wrote:
>>
>>>The portlet handle is returned in the serviceDescriptionResponse
>>>already, so I'm not sure what you're looking for.
>>>
>>>Cassio Nishiguchi wrote:
>>>
>>>>So Diego, how soon do you expect to implement the ability to get
>>>>wsrp_portlet_handle from the getServiceDescription response, instead
>>>>of specifying it in an xml file (which should be
>>>>portletentityregistry.xml in Pluto, to correct my original question)?
>>>>I only ask because I wanna get it working in the next few weeks and if
>>>>your "near future" means longer than that, I could try and do it
>>>>myself (perhaps with a little help) and then contribute the code back
>>>>to you.
>>>>
>>>>Cassio
>>>>
>>>>On Thu May 5 2005 10:47 am, Diego Louzán wrote:
>>>>
>>>>>That's a behaviour I expect to implement in a near future version. I
>>>>>need
>>>>>too some kind of wizard to add new portlets for my own project. I
>>>>>haven't
>>>>>still thought how to do it, but I imagine that creating a management
>>>>>portlet should be enough. Given endpoints for the 4 wsrp interfaces
>>>>>(maybe
>>>>>only 2, portletDescription, and registration if applicable), this
>>>>>portlet
>>>>>will implement a discovery mechanism and modify accordingly the
>>>>>appropriate
>>>>>xml files.
>>>>>
>>>>>Regards.
>>>>>Diego.
>>>>>
>>>>>Cassio Nishiguchi wrote:
>>>>>
>>>>>>Hi,
>>>>>>currently the wsrp_portlet_hanlde for the remote portlet is
>>>>>>specified in
>>>>>>portlet.xml, right? I need to modify this behavior so that the
>>>>>>proxyportlet will get a list of remote portlets from the
>>>>>>getServiceDescription response and display them to the user. The user
>>>>>>should then select the desired portlet from the list and the
>>>>>>proxyportlet
>>>>>>will send the associated wsrp_portlet_handle in the subsequent
>>>>>>getMarkup
>>>>>>call. Eventually I want to be able to select the desired producer
>>>>>>from a
>>>>>>list too, but this will be good to start with.
>>>>>>Could anyone give me some guidance as to how I could go about doing
>>>>>>this?
>>>>>>Would it take a lot of effort or is it pretty straight-forward once
>>>>>>you get to know the proxyportlet code?
>>>>>>
>>>>>>Thanks in advance,
>>>>>>Cassio Nishiguchi
Re: Modify proxyportlet to display list of available portlets
Posted by Cassio Nishiguchi <ca...@9starresearch.com>.
Thanks Diego, that is what I was trying to say. I think I may have confused
people because I was just thinking about adding this functionality to
proxyportlet itself - as in the first time you access the proxyportlet you
would get a setup screen where you can choose the remote portlet you want to
access from a list. This list would be populated with the information
received from the serviceDescriptionResponse. Once you pick the portlet, the
corresponding portletHandle would be written to the xml file and every access
thereafter would work as it does currently.
However, a separate management portlet may work too.
Cassio
On Fri May 6 2005 10:45 am, Diego Louzán wrote:
> Julie, I think he means a kind of management portlet in the consumer that
> allows to specify a wsrp producer endpoint url and then visually get the
> list of portlet_handles (and I suppose the descriptions also) that the
> producer returns in a getServiceDescription request. That way you could add
> this portlet_handles to xml configuration files automatically instead of by
> hand. In the current state of proxyportlet, if you don't know the
> portlet_handle that you want from a producer, you have to inspect manually
> the soap sniffer to see what portlet_handle's the producer returns in a
> getServiceDescription request and then add the desired ones to the xml
> configuration files.
>
> Regards.
> Diego.
>
> Julie MacNaught wrote:
> > The portlet handle is returned in the serviceDescriptionResponse
> > already, so I'm not sure what you're looking for.
> >
> > Cassio Nishiguchi wrote:
> >> So Diego, how soon do you expect to implement the ability to get
> >> wsrp_portlet_handle from the getServiceDescription response, instead
> >> of specifying it in an xml file (which should be
> >> portletentityregistry.xml in Pluto, to correct my original question)?
> >> I only ask because I wanna get it working in the next few weeks and if
> >> your "near future" means longer than that, I could try and do it
> >> myself (perhaps with a little help) and then contribute the code back
> >> to you.
> >>
> >> Cassio
> >>
> >> On Thu May 5 2005 10:47 am, Diego Louzán wrote:
> >>> That's a behaviour I expect to implement in a near future version. I
> >>> need
> >>> too some kind of wizard to add new portlets for my own project. I
> >>> haven't
> >>> still thought how to do it, but I imagine that creating a management
> >>> portlet should be enough. Given endpoints for the 4 wsrp interfaces
> >>> (maybe
> >>> only 2, portletDescription, and registration if applicable), this
> >>> portlet
> >>> will implement a discovery mechanism and modify accordingly the
> >>> appropriate
> >>> xml files.
> >>>
> >>> Regards.
> >>> Diego.
> >>>
> >>> Cassio Nishiguchi wrote:
> >>>> Hi,
> >>>> currently the wsrp_portlet_hanlde for the remote portlet is
> >>>> specified in
> >>>> portlet.xml, right? I need to modify this behavior so that the
> >>>> proxyportlet will get a list of remote portlets from the
> >>>> getServiceDescription response and display them to the user. The user
> >>>> should then select the desired portlet from the list and the
> >>>> proxyportlet
> >>>> will send the associated wsrp_portlet_handle in the subsequent
> >>>> getMarkup
> >>>> call. Eventually I want to be able to select the desired producer
> >>>> from a
> >>>> list too, but this will be good to start with.
> >>>> Could anyone give me some guidance as to how I could go about doing
> >>>> this?
> >>>> Would it take a lot of effort or is it pretty straight-forward once
> >>>> you get to know the proxyportlet code?
> >>>>
> >>>> Thanks in advance,
> >>>> Cassio Nishiguchi
Re: Modify proxyportlet to display list of available portlets
Posted by Diego Louzán <dl...@apache.org>.
Julie, I think he means a kind of management portlet in the consumer that
allows to specify a wsrp producer endpoint url and then visually get the list
of portlet_handles (and I suppose the descriptions also) that the producer
returns in a getServiceDescription request. That way you could add this
portlet_handles to xml configuration files automatically instead of by hand. In
the current state of proxyportlet, if you don't know the portlet_handle that
you want from a producer, you have to inspect manually the soap sniffer to see
what portlet_handle's the producer returns in a getServiceDescription request
and then add the desired ones to the xml configuration files.
Regards.
Diego.
Julie MacNaught wrote:
> The portlet handle is returned in the serviceDescriptionResponse
> already, so I'm not sure what you're looking for.
>
> Cassio Nishiguchi wrote:
>
>> So Diego, how soon do you expect to implement the ability to get
>> wsrp_portlet_handle from the getServiceDescription response, instead
>> of specifying it in an xml file (which should be
>> portletentityregistry.xml in Pluto, to correct my original question)?
>> I only ask because I wanna get it working in the next few weeks and if
>> your "near future" means longer than that, I could try and do it
>> myself (perhaps with a little help) and then contribute the code back
>> to you.
>>
>> Cassio
>>
>> On Thu May 5 2005 10:47 am, Diego Louzán wrote:
>>
>>> That's a behaviour I expect to implement in a near future version. I
>>> need
>>> too some kind of wizard to add new portlets for my own project. I
>>> haven't
>>> still thought how to do it, but I imagine that creating a management
>>> portlet should be enough. Given endpoints for the 4 wsrp interfaces
>>> (maybe
>>> only 2, portletDescription, and registration if applicable), this
>>> portlet
>>> will implement a discovery mechanism and modify accordingly the
>>> appropriate
>>> xml files.
>>>
>>> Regards.
>>> Diego.
>>>
>>> Cassio Nishiguchi wrote:
>>>
>>>> Hi,
>>>> currently the wsrp_portlet_hanlde for the remote portlet is
>>>> specified in
>>>> portlet.xml, right? I need to modify this behavior so that the
>>>> proxyportlet will get a list of remote portlets from the
>>>> getServiceDescription response and display them to the user. The user
>>>> should then select the desired portlet from the list and the
>>>> proxyportlet
>>>> will send the associated wsrp_portlet_handle in the subsequent
>>>> getMarkup
>>>> call. Eventually I want to be able to select the desired producer
>>>> from a
>>>> list too, but this will be good to start with.
>>>> Could anyone give me some guidance as to how I could go about doing
>>>> this?
>>>> Would it take a lot of effort or is it pretty straight-forward once you
>>>> get to know the proxyportlet code?
>>>>
>>>> Thanks in advance,
>>>> Cassio Nishiguchi
>>
>>
>>
>>
>
Re: Modify proxyportlet to display list of available portlets
Posted by Julie MacNaught <jm...@apache.org>.
The portlet handle is returned in the serviceDescriptionResponse already, so I'm not sure what you're looking for.
Cassio Nishiguchi wrote:
> So Diego, how soon do you expect to implement the ability to get
> wsrp_portlet_handle from the getServiceDescription response, instead of
> specifying it in an xml file (which should be portletentityregistry.xml in
> Pluto, to correct my original question)? I only ask because I wanna get it
> working in the next few weeks and if your "near future" means longer than
> that, I could try and do it myself (perhaps with a little help) and then
> contribute the code back to you.
>
> Cassio
>
> On Thu May 5 2005 10:47 am, Diego Louzán wrote:
>
>>That's a behaviour I expect to implement in a near future version. I need
>>too some kind of wizard to add new portlets for my own project. I haven't
>>still thought how to do it, but I imagine that creating a management
>>portlet should be enough. Given endpoints for the 4 wsrp interfaces (maybe
>>only 2, portletDescription, and registration if applicable), this portlet
>>will implement a discovery mechanism and modify accordingly the appropriate
>>xml files.
>>
>>Regards.
>>Diego.
>>
>>Cassio Nishiguchi wrote:
>>
>>>Hi,
>>>currently the wsrp_portlet_hanlde for the remote portlet is specified in
>>>portlet.xml, right? I need to modify this behavior so that the
>>>proxyportlet will get a list of remote portlets from the
>>>getServiceDescription response and display them to the user. The user
>>>should then select the desired portlet from the list and the proxyportlet
>>>will send the associated wsrp_portlet_handle in the subsequent getMarkup
>>>call. Eventually I want to be able to select the desired producer from a
>>>list too, but this will be good to start with.
>>>Could anyone give me some guidance as to how I could go about doing this?
>>>Would it take a lot of effort or is it pretty straight-forward once you
>>>get to know the proxyportlet code?
>>>
>>>Thanks in advance,
>>>Cassio Nishiguchi
>
>
>
--
Julie MacNaught
IBM Research
jmacna@apache.org
jmacna@us.ibm.com
DADB E3B5 8CB7 6B9B F4A0 8BF7 E830 1848 16A8 D3AB
Re: Modify proxyportlet to display list of available portlets
Posted by Cassio Nishiguchi <ca...@9starresearch.com>.
So Diego, how soon do you expect to implement the ability to get
wsrp_portlet_handle from the getServiceDescription response, instead of
specifying it in an xml file (which should be portletentityregistry.xml in
Pluto, to correct my original question)? I only ask because I wanna get it
working in the next few weeks and if your "near future" means longer than
that, I could try and do it myself (perhaps with a little help) and then
contribute the code back to you.
Cassio
On Thu May 5 2005 10:47 am, Diego Louzán wrote:
> That's a behaviour I expect to implement in a near future version. I need
> too some kind of wizard to add new portlets for my own project. I haven't
> still thought how to do it, but I imagine that creating a management
> portlet should be enough. Given endpoints for the 4 wsrp interfaces (maybe
> only 2, portletDescription, and registration if applicable), this portlet
> will implement a discovery mechanism and modify accordingly the appropriate
> xml files.
>
> Regards.
> Diego.
>
> Cassio Nishiguchi wrote:
> > Hi,
> > currently the wsrp_portlet_hanlde for the remote portlet is specified in
> > portlet.xml, right? I need to modify this behavior so that the
> > proxyportlet will get a list of remote portlets from the
> > getServiceDescription response and display them to the user. The user
> > should then select the desired portlet from the list and the proxyportlet
> > will send the associated wsrp_portlet_handle in the subsequent getMarkup
> > call. Eventually I want to be able to select the desired producer from a
> > list too, but this will be good to start with.
> > Could anyone give me some guidance as to how I could go about doing this?
> > Would it take a lot of effort or is it pretty straight-forward once you
> > get to know the proxyportlet code?
> >
> > Thanks in advance,
> > Cassio Nishiguchi
Re: Modify proxyportlet to display list of available portlets
Posted by Diego Louzán <di...@metalicana.org>.
That's a behaviour I expect to implement in a near future version. I need too
some kind of wizard to add new portlets for my own project. I haven't still
thought how to do it, but I imagine that creating a management portlet should
be enough. Given endpoints for the 4 wsrp interfaces (maybe only 2,
portletDescription, and registration if applicable), this portlet will
implement a discovery mechanism and modify accordingly the appropriate xml files.
Regards.
Diego.
Cassio Nishiguchi wrote:
> Hi,
> currently the wsrp_portlet_hanlde for the remote portlet is specified in
> portlet.xml, right? I need to modify this behavior so that the proxyportlet
> will get a list of remote portlets from the getServiceDescription response
> and display them to the user. The user should then select the desired
> portlet from the list and the proxyportlet will send the associated
> wsrp_portlet_handle in the subsequent getMarkup call. Eventually I want to
> be able to select the desired producer from a list too, but this will be good
> to start with.
> Could anyone give me some guidance as to how I could go about doing this?
> Would it take a lot of effort or is it pretty straight-forward once you get
> to know the proxyportlet code?
>
> Thanks in advance,
> Cassio Nishiguchi