RE: [PATCH] proposed for peid

> -Original Message- > From: Glenn Golden [mailto:[EMAIL PROTECTED]] > Sent: Tuesday, March 26, 2002 12:56 PM > To: 'Jetspeed Developers List' > Subject: RE: [PATCH] proposed for peid > > > I think I figured out what the $jlink. call should be to add > the peid parts to the URL, inst

RE: [PATCH] proposed for peid

I think I figured out what the $jlink. call should be to add the peid parts to the URL, instead of setPortlet() or forPortlet()... If we use the model of addQueryData() and addPathInfo(), why not: addPortalElement(peid) addPortalElement can decide to do it as a query or a path, and what "js_pei

[PATCH] for redirect

Ok, I've sent a patch to Turbine. The solution I selected was to have the Action class just do a: RunData.setRedirectURI() When it wants to call for a redirect. Make sure not to set any headers or body in the response directly before (or after) this. If the Action class does this, and turbine

Re: Turbine - Jetspeed interaction problems

Oops. Embarassing. I didn't reply to the whole list on purpose. Cynthia Harris wrote: > Hi Craig, > > I'm not replying to the whole list because I'm kinda new around here and I don't > know the ropes. > > The form handling technique that I use would help you out. > > In J2EE, I think the stan

Re: Turbine - Jetspeed interaction problems

Hi Craig, I'm not replying to the whole list because I'm kinda new around here and I don't know the ropes. The form handling technique that I use would help you out. In J2EE, I think the standard form handling technique is to put the form on some page, and make the action of the form point back

RE: Turbine - Jetspeed interaction problems

I'm in agreement with Glenn that redirect's are necessary here or at least the behavior we get when we redirect. I've found no other good solution within the limits of HTTP to make the browser do the right thing. I originally asked for redirects in Jetspeed a few months back because of the error

RE: Turbine - Jetspeed interaction problems

Yes, it means all this extra traffic. But is the cost worth the benefit? The goal is to get the browser to have a good URL, one that could be "reloaded" or "back"ed without fuss and bother. If we are customizing, or doing other things that use a different url, and want to switch back to the por

Re: Maven and Jetspeed :-)

Hi, --- Jason van Zyl <[EMAIL PROTECTED]> wrote: > > http://jakarta.apache.org/turbine/maven/ > Excuse my ignorance, but what is it? I had a quick look - it has some tools for projects, like generating code metrics and producing fancy javadocs. Is it just the latest way of generating the site

cvs commit: jakarta-jetspeed/src/java/org/apache/jetspeed/services/registry NormalizedPortletEntry.java

taylor 02/03/26 01:06:54 Modified:src/java/org/apache/jetspeed/om/registry PortletEntry.java PortletInfoEntry.java RegistryEntry.java src/java/org/apache/jetspeed/om/registry/base BasePortletEntry.java BasePortletInfoEntry.

cvs commit: jakarta-jetspeed/src/java/org/apache/jetspeed/services/registry TestMarshallRegistry.java

taylor 02/03/26 01:03:19 Added: src/java/org/apache/jetspeed/services/registry TestMarshallRegistry.java Log: - test case for registry Revision ChangesPath 1.1 jakarta-jetspeed/src/java/org/apache/jetspeed/services/registry/Te

cvs commit: jakarta-jetspeed/webapp/WEB-INF/psml/test testcase-2.xreg url-testcase.xreg

taylor 02/03/26 01:02:04 Modified:webapp/WEB-INF/conf registry.xml Added: webapp/WEB-INF/psml/test testcase-2.xreg url-testcase.xreg Log: - first phase on registry refactoring and added features. - test cases for registry marshalling Revision ChangesPath 1.7

cvs commit: jakarta-jetspeed/build build.xml

taylor 02/03/26 01:00:18 Modified:buildbuild.xml Log: - added unit test for registry marshalling Revision ChangesPath 1.130 +1 -1 jakarta-jetspeed/build/build.xml Index: build.xml ===