struts-user mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Chris Miller" <k...@vardus.co.uk>
Subject Re: BEA Claims about Struts on Weblogic
Date Fri, 22 Sep 2000 14:54:54 GMT
On top of that, I managed to deploy Struts on orion in about 5 minutes, no
problems. Orion is one of the most J2EE compliant app servers I know of, so
BEA claiming that Struts breaks the spec doesn't ring very true with me.
(again, I'm not sure about the bean-cookie.jsp, haven't tried that one yet -
it's hardly a crucial part of the struts framework!).

----- Original Message -----
From: "Robert Quillen" <robert@fastforms.com>
To: <struts-user@jakarta.apache.org>
Sent: Friday, September 22, 2000 3:31 PM
Subject: RE: BEA Claims about Struts on Weblogic


> Sounds like BS to me.
>
> The spec says that the session identifier must be JSESSIONID.
>
> That bit about bean-cookie.jsp may or may not be true.  (I've never read
> it's source so I can't say.)  However, it doesn't have anything to do with
> the real problems people are having with Weblogic running struts.  Most of
> the problems are the <load-on-startup> for the action servlet not working
> and various classloader issues.
>
> Robert Quillen
>
>
> -----Original Message-----
> From: Luke Taylor [mailto:negaton@freesurf.ch]
> Sent: Friday, September 22, 2000 9:40 AM
> To: struts-user@jakarta.apache.org
> Subject: BEA Claims about Struts on Weblogic
>
>
> Hi, I just spotted this in the Weblogic.developer.interest.jsp
> newsgroup. Is this genuine criticism or just another attempt to cover
> up the fact that getting stuff to run in Weblogic is such a nightmare?
>
> > From:
> >         "WebLogic" <sam@bea.com>
> >
> >  Subject:
> >         Re: Running Struts on weblogic
> >
> > You should be able to get past this point with service pack 5.  One of
the
> > problems with struts is that some of
> > the pages take advantage of non-standard behaviour in Tomcat, however.
> For
> > example, in the bean-cookie.jsp
> > test they attempt to set a property on a bean that was never useBeaned.
> > Section 2.13.2, JSP 1.1 spec:
> >
> > The name of a Bean instance defined by a <jsp:useBean> element or some
> other
> > element. The Bean instance must contain the property you want to set.
The
> > defining element (in JSP 1.1 only a <jsp:useBean> element) must appear
> > before the <jsp:setProperty> element in the same file.
> >
> > They also hard-code the Tomcat session identifier into the tests.  If
you
> > want them to work either change the weblogic cookie name to JSESSIONID
or
> > change the references to JSESSIONID to WebLogicSession.
> >
> > Sam
>
>
>
> --
>  Luke Taylor.
>  PGP Key ID: 0x57E9523C
>


Mime
View raw message