Santiago Gala wrote:
- we can first aggregate content, and then the container will
lay it out and style it. (This is my view)
This is an interesting thought, but how would the container know
how to "style" content provided by a particular portlet ?
There are simple special cases like
Michael Sallman wrote:
I just did a checkout from cvs and got the following errors trying to do
the build:
ls: ../../jakarta-site2/lib/jdom*.jar: No such file or directory
./build.sh: [: ==: binary operator expected
./build.sh: [: ==: binary operator expected
type: jikes: not found
After the discussions we had during the last few days and
before the upcoming decision, I'd like to provide a new
summary of the current state of the discussion and explain
IBM's position in a separate section at the end, after the
dotted line.
We are all in agreement about our common goal :)
Thomas Schaeck wrote:
Unlike the Servlet API, the Portlet API would additionaly
provide explicit SAX support in the sax package and introduce a
dependency on org.xml.sax, i.e. a separate package. Such a
dependency of an API package to another API package that is not
part of the core Java
Hola Raphael:
+// Include the servlet or JSP.
+
+// Warning: This does not work correctly with Tomcat
3.x
+// because of a Tomcat implmentation bug (the
dispatcher
+// never use the given response)
+
At 20:04 02/16/01, Raphal Luta wrote:
I updated the java docs in the proposals directory so that everybody can
have a look at them. They are more detailed, but I hope that this mail
did also make the idea clear.
I still owe you a proposal that defines which rules document fragments
will have
Sam Ruby wrote:
Thomas Schaeck wrote:
Unlike the Servlet API, the Portlet API would additionaly
provide explicit SAX support in the sax package and introduce a
dependency on org.xml.sax, i.e. a separate package. Such a
dependency of an API package to another API package that is
"Ignacio J. Ortega" wrote:
Hola Raphael:
+// Include the servlet or JSP.
+
+// Warning: This does not work correctly with Tomcat
3.x
+// because of a Tomcat implmentation bug (the
dispatcher
+// never use the given
Hola Raphael :
I committed this, because on Tomcat 3.x the behavior is
exactly the same
as before (and thus the patch does not break or solve anything since
Tomcat 3.x just ignores my custom response). I'll still have to find
This is a continuos requeriment from Tomcat users :(, and a
At 07:36 PM 2/18/2001 +0100, you wrote:
2.Fragments and/or Full Documents
(This affects portlet container performance and ease of
implementation - and thus development costs)
Alternatives:
a) only document fragments concatenatable without post-processing
- high-performance
I have a portlet that needs to display current information and I need to
make the refresh rate low. I have changed the default to 60 from 3600, but
nothing seems to get my content to refresh. Am I going about this in the
correct manner?
--
11 matches
Mail list logo
