Hi,
this is what we found during some inital analasys of the Estore (JPS):
1. errorpage.jsp does not import java.io (but implicitly uses it).
2. The web.xml for the web-app has an ejb-ref by the name of ejb/inventory
which lists inventory as a session while it in fact is an entity.
3. Internal errors are not logged (swallowed by errorpage and not logged
from there either). Severe bug for paranoid admins (disables the containers
logging, ie alerting the admin by mail etc).
4. Internal errors sometimes lead to a simple "the user id is already taken"
without any hint regarding the real error.
5. JSP Tags are used to store state outside of their own scope - This is a
programmer error since tags are usually reused once they're out of scope
(after doEndTag()) so the state will get corrupted.

Cannot dig deeper at the moment I'm afraid as it'd involve rewriting too
much of the Estore itself (which is not a top priority right now, we hope
the JPS team fixes these issues by themselves).

/Magnus Stenman, the Orion team


----- Original Message -----
From: "Neville Burnell" <[EMAIL PROTECTED]>
To: "Orion-Interest" <[EMAIL PROTECTED]>
Cc: "Orion-Interest" <[EMAIL PROTECTED]>
Sent: Wednesday, May 03, 2000 1:44 AM
Subject: RE: Orion 1.0 RC 1 released


> Hi Karl,
>
> Great Stuff.
>
> Now that Orion is RC1 and the JavaPetStore is FCS, could you publish
> instructions on how to deploy the JPS estore.ear on Orion pls?
>
> We have an app developed with the J2EE RI that is based on the JPS and I
> want to use Orion as our deployment server of choice, but my attempts to
> get the JPS deployed have Orion failed.
>
> Kind Regards
>
> Neville Burnell
> Business Manager Software
>
> > -----Original Message-----
> > From: Karl Avedal [mailto:[EMAIL PROTECTED]]
> > Sent: Tuesday, 2 May 2000 10:11 PM
> > To: Orion-Interest
> > Subject: Orion 1.0 RC 1 released
> >
> >
> > We are proud to announce the availablibilty of the first Orion 1.0
> > Release Candidate. As usual it contains many bug fixes and also many
> > enhancements. A few productivity related improvements worth mentioning
> > are:
> >
> > Auto-compilation of web-components. Now all web-code will be
> > automatically compiled if development mode is set to true.
> > (http://www.orionserver.com/docs/orion-web.xml.html) shows
> > the location
> > of the development attribute).
> >
> > For example, this means that you can make a servlet,
> > MyServlet.java, put
> > it in the right dir, and the server will automatically pick it up and
> > compile it. This goes for tag extension libraries, etc. as well.
> >
> > Auto-generation of common custom finders (for CMP beans). If you have
> > finders called findAll() or findByX() (where X can be anything), the
> > finders will be automatically generated for finding all enties
> > (findAll()) or find the entities matching a specific field-value
> > (findByX()).
> >
> > As some of you might have noticed, Orion now also provide
> > full JSP line
> > information in stack traces and compilation errors. You are not only
> > given the line number for the generted class, but for the actual JSP
> > file.
> >
> > The Orion team
> >
> >


Reply via email to