Enhydra/XMLC 3.0.1 works with Orion

2000-05-04 Thread Montebove Luciano
Applying some patches to the xerces version (1.0.3) included in orion is possible to use the Enhydra/XMLC 3.0.1 compiler. For people who don't know it, XMLC is an elegant solution (better than JSP on my opinion) to separate HTML/XML from java code. If you are interested I can send you details on

how do you shut down the server?

2000-05-04 Thread Benjamin Geer
The documentation doesn't appear to say how to shut down the server. Following the 'Usage' statement that was printed when I typed 'java -jar shutdown.jar', I tried this: java -jar shutdown.jar ormi://localhost admin pentacom restart And got this: Error:

Problem with orion.jar and servlet.jar

2000-05-04 Thread Steven W. Rock
Hi All, I keep all my J2EE java .jar files under jdk1.2.2/jre/lib/ext/, including the newest servlet sdk 2.2. I just downloaded it twice from java.sun.com. However, whenever I have the servlet.jar in this directory, the Orion server won't start. It gives me the error: Servlet API version 2.2 or

Stateful Session timeout, JSPs

2000-05-04 Thread Thomas Munro
Hello I have a design question. I have a (1) JSP session which stores a reference to (2) a stateful session EJB. If either times out, I want the user to be bounced to a page where they have to log in (again). The problem is that the JSP session and the session EJB time out under different

RE: Stateful Session timeout, JSPs

2000-05-04 Thread Conrad Chan
I bet you don't really want to have a dummy ping method to burden your server load. If the current implementation will throw java.rmi.NoSuchObjectException when session beans timeout, you could define in your war archive configuration to redirect to a particular page automatically if this

RE: Stateful Session timeout, JSPs

2000-05-04 Thread Kevin Duffey
Very interesting. I never did consider this. I think there are different approaches as to the best way to accomplish this. Because the network can get bottlenecked, I understand its best to use STATELESS ejb session beans. That is, they simply do logic, but do not store any session information.