PLEASE REMOVE ME FROM THE LIST. PLEASE!!!
- NILES
- Original Message -
From: Tim Pouyer [EMAIL PROTECTED]
To: Orion-Interest [EMAIL PROTECTED]
Sent: Wednesday, November 21, 2001 12:24 PM
Subject: Re: Calling entity bean from a session bean in Orion 1.5.3
Take out the ejb-link
Hi,
I have an application client that uses EJB that I like to
distribute through Java Web Start. The client works fine
with both the ApplicationClientInitialContextFactory and
the RMIInitialContextFactory JNDI factories when launched
from the command line, however when launched from the Java
Web
Unless I am not understanding your question correctly, you _do_ want what I sent below
Greg's
reply which gets a reference to the transaction manager.
Look below for
TransactionManager manager.
--- patrick patrick [EMAIL PROTECTED] wrote:
hi ray,
Thanks for your prompt reply..
Hello Brian,
are you setting the exclusive-write-access to false for that bean?
There is a known bug (bug #532 in bugzilla) about findByPrimaryKey not
throwing an ObjectNotFoundException when it should if
exclusive-write-access is set to false. It's reported from 1.4.5 and
it hasn't be fixed.
A _very_ late answer I know, but it is my firm belief that the reason
for this is that Postgresql JDBC driver does not support BLOB:s, it is
simply not implemented, hence the message. Check out the WebCVS and see
for yourselves.
/Marcus
On Fri, 2001-06-22 at 20:42, Phillip Ross wrote:
Your
Magnus,
This does occur using 1.5.3
Cheers
Ray
--- Magnus Rydin [EMAIL PROTECTED] wrote:
Are you using 1.5.3?
We noticed this prior to releasing 1.5.3 and fixed it, I was under the
impression that this worked fine?
WR
-Ursprungligt meddelande-
Från: [EMAIL PROTECTED]
I'm having issues with my EAR deployment all of a sudden -- when Orion
attempts to unpack and deploy the EAR, it throws an exception:
Auto-deploying thesquare-ejb.jar (ejb-jar.xml had been touched since the
previou
s deployment)... java.lang.IllegalArgumentException: Cannot convert from
class j
Title: RE: please take me off the list, thanks!
NEVER
BEING ON THIS LIST IS LIKE BEING IN THE MAFIA YOU ARE ON IT FOR LIFE!!!
WOH GO ORION GOO
-Original Message-
From: Liang, Hua [mailto:[EMAIL PROTECTED]]
Sent: Wednesday, November 21, 2001 11:21 AM
To:
I'll verify this and make sure that the fix will be available with the next
build.
WR
-Ursprungligt meddelande-
Fran: [EMAIL PROTECTED]
[mailto:[EMAIL PROTECTED]]For Ray Harrison
Skickat: den 21 november 2001 17:39
Till: Orion-Interest
Amne: Re: SV: A word of warning: SwiftMQ and
My 2 cents worth is this is the order of importance of documentation
that is
needed right now to do REAL professional deployments and developments
with Orion/OC4J
1) Orion specific deployment settings explained
these are not really explained anywhere right now.
My
My 2 cents worth is this is the order of importance of documentation
that is
needed right now to do REAL professional deployments and developments
with Orion/OC4J
1) Orion specific deployment settings explained
these are not really explained anywhere right now.
My
I've put an orion-ejb-jar.xml in the EJB Jar's META-INF. If I clean out the
Orion/application-deployment and Orion/applications versions of the
application, and deploy to Orion, the file copies into the appropriate place
and takes effect. If I deploy on top of an existing EAR, the redeploy
Title: RE: Deployment Exception
shutdown the server
delete the .ear file in applications
delete the directory in applications
delete the directory(ies) in application-deployments
startup the server ( it should complain about not finding the ear )
shut it down
copy .ear file to applications
Actually the Postgres driver does support blobs in a number of ways. The
7.1 driver supports BLOBs using OIDs (a postgres specific measure) and
the latest driver from CVS (due out with 7.2 shortly) supports bytea
datatypes (which is a long byte array up to 1 gig in size) which is much
nicer than
Geoffrey,
This is the expected behaviour. The deployment descriptors are only
copied from the EAR after a clean deploy. Otherwise Orion might
overwrite deployment descriptors that you had edited.
Cheers,
Mike
--
Mike Cannon-Brookes :: [EMAIL PROTECTED]
Atlassian :: http://www.atlassian.com
hi,
i'm trying to ensure that the only time a session
is created is after a successful user login.
is there any other way apart from
HttpServletRequest.getSession( ), or HttpServletRequest.getSession( boolean
create) that a HttpSession can be created?
i've trawled through the J2EE API but
Suggestions? Is the Java Web Start environment (classloader,
security manager, etc) interfering with Orion?
IIRC this is an old issue discussed a lot at the java web start forums on
forums.java.sun.com.
Try to do a search on Java Web Start + Weblogic/J2EE/EJB, and I think you will
probably
From servlets there is only one way of creating
HttpSession request.getSession(boolean create).
If you write JSP pages the session object will be
automatically created unless you specify session=false.
If you want to make sure that you create
HttpSession Object only after successful login
19 matches
Mail list logo