Hi,
i'd like to have this featue too.
but it works only for _servlets_,...!!!
NOT for beans which are only used in jsp-pages!!
try to change any bean from the struts-example
(i.e. com/apache/struts/example/...)
klaus
ps: or did i miss some configuration entrys/switches?
On Mit, 12 Jul 2000, Mike Cannon-Brookes wrote:
>Orion does detect changed beans. If you place the source in the classes
>directory, it will also detect changes to the source and automatically
>recompile.
>
>ie alter source ... save... reload page and voila!
>-----Original Message-----
>From: [EMAIL PROTECTED]
>[mailto:[EMAIL PROTECTED]]On Behalf Of Tom Wnuk
>Sent: Wednesday, July 12, 2000 8:36 AM
>To: Orion-Interest
>Subject: RE: Session time out TOOOO early!
>
>
>Are you saying Orion detects changes in JSP used beans?
>
>That's great if it truly does because most jsp/servlet engines out there do
>Not. If the JSP page changes then it will be recompiled but that doesn't
>necessarily mean you'll get the new bean unless Orion has their own
>class-loader. The bean class is already loaded in the JVM, not your
>instance but the class used for creating instances. I don't know of anyone
>who dynamically reloads the beans. In order to pick up the new bean the
>server needs to be restarted.
>
>I hope you're right because this has been a big headache in managing changes
>to JSP used beans.
>
>My $0.2.
>
>Tom
>-----Original Message-----
>From: [EMAIL PROTECTED]
>[mailto:[EMAIL PROTECTED]]On Behalf Of Steven Punte
>Sent: Tuesday, July 11, 2000 1:11 PM
>To: Orion-Interest
>Cc: Orion-Interest
>Subject: Re: Session time out TOOOO early!
>
>
> If a JSP pages uses a session bean, not EJB but just a server side java
>bean,
> and that bean is recompiled, the server will detect this and reload it,
>but
> it will also dump and re-start a users present session. This makes
>sense.
> Otherwise there would be an attempt to use the old session bean object
> in the context of the new compiled session bean.
>
> In summary the session will appear time-out any time a related bean
> being used in session scope is recompiled.
>
>
>STeve Punte
>e-Business Software Architect
>Technologent Inc
>[EMAIL PROTECTED]
>----- Original Message -----
>From: Porfiriev Sergey
>To: Steven Punte
>Sent: Monday, July 10, 2000 7:24 PM
>Subject: Re: Session time out TOOOO early!
>
>
>I have the same problem, mail me if u received solution
>----- Original Message -----
>From: Steven Punte
>To: Orion-Interest
>Sent: Monday, July 10, 2000 3:19 PM
>Subject: HELP: Session time out TOOOO early!
>
>
>Help:
>
> I'm having serious problem with the servlet session timing-out
> way before it should. I'm running Orion on Solaris, and typically
> only see the problem when development is active (i.e. team
> members changing server side java bean files).
>
>
> I have set the session time-out to 6 hours in the web.xml file as show
>below:
>
><web-app>
> <servlet>
> <servlet-name>snoop</servlet-name>
> <display-name>snoop</display-name>
> <servlet-class>SnoopServlet</servlet-class>
> </servlet>
> <session-config>
> <session-timeout>360</session-timeout>
> </session-config>
> <login-config>
> <auth-method>BASIC</auth-method>
> </login-config>
></web-app>
>
> My JSP file is as simple as possible:
>
><%@ page language="java" session="true" %>
><%@ page import="java.util.*" %>
><html>
><head>
><title><%= "Session Bug" %></title>
></head>
><body>
><br><br>
> Session Information:
> <br>Last Accessed <%= new Date( session.getLastAccessedTime()) %>
> <br>Creation Time <%= new Date( session.getCreationTime() ) %>
> <br>ID <%= session.getId() %>
> <br>Max Interval <%= session.getMaxInactiveInterval() %>
></body>
></html>
>
> In the above examples, the creation time typically only hold from 5
>minutes to 15 minutes,
> and will then move forward to the present time forgetting all other
>session information.
>
> Any suggestion greatly appreciated:
>
>
>STeve Punte
>e-Business Software Architect
>Technologent Inc
>[EMAIL PROTECTED]
--
--
Klaus Thiele - Personal & Informatik AG
mailto:[EMAIL PROTECTED]
"There's got to be more to life than compile-and-go."
