Implement clases conforming to the EJBUserManager API and overide the permission
checking methods with logic that does that kind of checking ... then deploy like so:
http://www.orionsupport.com/articles/ejbusermanager.html
Justin
-Original Message-
From: Pletka, John [mailto:[EMAIL
Implementing a Message-Driven Bean in Orion.
(Tested with orion 1.5.4)
1.) == The MDB code - LogBean
package mycode.ejb.mdb;
import javax.ejb.*;
import javax.jms.*;
public class LogBean implements MessageDrivenBean, MessageListener {
protected MessageDrivenContext
/applications/beantest/ejb homes: JMS Error: Invalid
acknowledgeMode
Orion/1.5.4 initialized
Our message broker is SonicMQ. Has anyone got any suggestions as to what can be
causing this.
Regards
Justin Wood
message from archive--
Magnus has said that documentation
Title: RE: Nimda Virus
er no
... you meet on IRC get the other guys IP and then you ...
Justin
-Original Message-From: Nusairat, Joseph F.
[mailto:[EMAIL PROTECTED]]Sent: 18 October 2001
04:02To: Orion-InterestSubject: RE: Nimda
Virus
Wow
i didnt believe rudeness
If this is code hiding issue consider using a taglib.
-Original Message-
From: Lachezar Dobrev [mailto:[EMAIL PROTECTED]]
Sent: 15 October 2001 09:35
To: Orion-Interest
Subject: Re: JSP Compilation Questions and More.
Hello.
is this a speed issue?
NO!
if so, use jikes. it's
It sounds like some of you may be forgetting to create an initial account in
the database ...
You can't have a user in principals.xml and expect orion to know where to
fetch the authentication information.
I have an EJB user manager and to make things easy for my self. I protected
a minimal
You can change this by selecting green threads instead of native threads
when you run your jvm. Check this out
http://java.sun.com/products/jdk/1.1/packs/native-threads/README
and then do a search on linux and green threads to get something more
specific to Linux.
Justin
-Original
If you have to rely on how many columns a query returns it is very likely
that your database is not properly normalised so look there first.
It could be that ODBC does not support the number of columns metadata but I
am not sure. Your problems should be solved with your move to mySQL; I
