[Moving the thread to Jetspeed Dev]
> >My problem is that is seems impossible to do both of:
> > a) Have a Portal implemented on top of a standard Servlet
> Container
> > b) Run multiple Portlet Applications, preferrably in a
> standard Portlet
> >Container, preferrably -the same- container
Hi Endre,
Well I'm happy to see I'm not the only one with this concern. I was
beginning to think that nobody had this problem except me :)
At 11:54 AM 7/29/2003 +0200, you wrote:
My problem is that is seems impossible to do both of:
a) Have a Portal implemented on top of a standard Servlet Con
On Wed, 23 Jul 2003, Serge Huber wrote:
| At 09:05 AM 7/23/2003 -0700, you wrote:
|
| >Tomcat and Resin have a cross-context invoker feature.
| >See http://jakarta.apache.org/tomcat/tomcat-4.1-doc/config/context.html
|
| Yes I am aware of those, but it still doesn't solve the problem of
| dispatch
On Friday, July 25, 2003, at 01:59 AM, Serge Huber wrote:
At 05:25 PM 7/24/2003 -0400, you wrote:
> As for a Jetspeed portal dispatching to a Weblogic container, that
is
> something that I don't think is covered by the spec.
> The spec covers the contract between the portlet and the containe
age-
> From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED]
> Sent: Thursday, July 24, 2003 5:26 PM
> To: [EMAIL PROTECTED]
> Subject: RE: Re[2]: JSR-168 Comments
>
>
> > As for a Jetspeed portal dispatching to a Weblogic container, that is
> > something that I don't thin
At 05:25 PM 7/24/2003 -0400, you wrote:
> As for a Jetspeed portal dispatching to a Weblogic container, that is
> something that I don't think is covered by the spec.
> The spec covers the contract between the portlet and the container.
> You may want to look into the WSRP for that kind of inter
> As for a Jetspeed portal dispatching to a Weblogic container, that is
> something that I don't think is covered by the spec.
> The spec covers the contract between the portlet and the container.
> You may want to look into the WSRP for that kind of interoperability.
Oracle claims to be using W
On Thursday, July 24, 2003, at 08:31 AM, Serge Huber wrote:
At 08:16 AM 7/24/2003 -0700, you wrote:
Im sorry, but I don't follow your logic.
The proxy servlet is a part of the portlet container implementation.
You can still take your exact same Portlet Application and drop it in
any other comp
At 08:16 AM 7/24/2003 -0700, you wrote:
Im sorry, but I don't follow your logic.
The proxy servlet is a part of the portlet container implementation.
You can still take your exact same Portlet Application and drop it in any
other compliant container.
From the portlet's point of view, it shouldn'
On Thursday, July 24, 2003, at 06:54 AM, Serge Huber wrote:
Hi David,
At 10:05 AM 7/23/2003 -0700, you wrote:
Yes I am aware of those, but it still doesn't solve the problem of
dispatching to a Portlet API portlet. The entry point for one of
those portlets is a class that complies to a certai
Hi David,
At 10:05 AM 7/23/2003 -0700, you wrote:
Yes I am aware of those, but it still doesn't solve the problem of
dispatching to a Portlet API portlet. The entry point for one of those
portlets is a class that complies to a certain interface. For a Servlet
in a different web application we
On Wednesday, July 23, 2003, at 09:30 AM, Serge Huber wrote:
At 09:05 AM 7/23/2003 -0700, you wrote:
Tomcat and Resin have a cross-context invoker feature.
See
http://jakarta.apache.org/tomcat/tomcat-4.1-doc/config/context.html
Yes I am aware of those, but it still doesn't solve the problem of
At 09:05 AM 7/23/2003 -0700, you wrote:
Tomcat and Resin have a cross-context invoker feature.
See http://jakarta.apache.org/tomcat/tomcat-4.1-doc/config/context.html
Yes I am aware of those, but it still doesn't solve the problem of
dispatching to a Portlet API portlet. The entry point for one o
On Wednesday, July 23, 2003, at 06:00 AM, Serge Huber wrote:
What's interesting about that document is page 14 "What The Portlet
Specification Does Not Address", notably : Portlet Aggregators,
Pre-built Portlets and Administration and Portlet Deployment.
One of the issues I see for Jetspeed 2,
What's interesting about that document is page 14 "What The Portlet
Specification Does Not Address", notably : Portlet Aggregators, Pre-built
Portlets and Administration and Portlet Deployment.
One of the issues I see for Jetspeed 2, using the new Portlet API, is how
to port Jetspeed to other a
http://developers.sun.com/prodtech/portalserver/reference/techart/jsr168/pb_whitepaper.pdf
Jetspeed 2.0 is JSP taglib for Portlet?? what do you think
Regards,
Frans Thamura <[EMAIL PROTECTED]>
Intercitra Innovation Center
+62 855 7888 699
We help you manage and control.
--
Tertarik de
16 matches
Mail list logo
