Hi!
I have a strange problem which I can't find a solution to. I am running a system with a two message-driven beans and a couple of entity beans. They are all listening to (and able to publish messages to) the same Topic. One of the entity beans contains a Timer with a couple of TimerTasks that
I was setting up SOAP on Orion and have run into a problem. Anytime I try to use any of the SOAP admin pages( List, Deploy, and un-deploy) I get a ClassDefNotFound Exception for HttpServlet on this line:
ServiceManager serviceManager =
Does anyone know why the request.getHeaderNames() returns the
headernames as uppercase in orion?
regards
/Linus
We're coming up on our deployment date, so we're considering our deployment
options (notably, at this point, JBoss and Orion).
The system is running and working under JBoss, and I've been re-porting it
to Orion so that we can do some testing, try and resolve some issues we had
under Orion (for
You
mention that one of the entity beans contains a timer, but you have not
mentioned how are you holding on to that timer. Is it a "Static" reference
in the entity bean or is it a Member of the EJB? Container could
physically remove the EJB from memory at any time, how are you dealing with
I already asked this question in a different thread but didn't get a reply, so let's
try again.
What is a Dirty Connection (when using -Djdbc.debug=true)? What causes it and what
repercussions does it have? Is a Dirty Connection a bad thing, and if so, what can we
do to avoid it (if
Hmm, want us to write it for you?
But seriously, there are commercial apps for J2EE scheduling if that's
the kind of thing you are after, just use google...
Geoff
-Original Message-
From: [EMAIL PROTECTED]
[mailto:[EMAIL PROTECTED]] On Behalf Of Justin
Crosbie
Sent: Saturday, January
Does anyone know if orion can server cgi and what
needs to be done if so.
Thanks
There is an interesting article on DevX regarding timer tasks.
http://www.devx.com/premier/mgznarch/Javapro/2002/02feb02/eb0202/eb0202-2.asp
It looks like it does what you want.
Cheers,
Scott
Scott Farquhar
[EMAIL PROTECTED]
Atlassian :: www.atlassian.com
Supporting YOUR world
Geoff
I don't think that relying on your Entity Beans for front line data
validation is a good design. As a rule of thumb to get the best performance
in applications you want to validate as early as you can to save the trouble
of having to process all the steps for a transaction only to find the data
10 matches
Mail list logo