Hi, The Elephant walker.
Sure the error says domain was null, but the situation is that the
servlet is just an another stand-alone program (not part of deployed Hello
Session Bean) residing in
D:\Oracle\iSuites\j2ee\home\default-web-app\WEB-INF\classes\trg\HelloServlet
directory and from
If you are trying to get the ejb which deployed in another application
You lookup should be directly the JNDI name of the ejb.
context.lookup("ejb/HelloHome"); instead of java:comp/env/xxx.
If your EJB in the same application then only you can lookup from the env.
- Original Message -
Just re-validating a design requirement for BMP that I think
I read somewhere:
Dependant objects behind an Entity that uses DAOs for each
parent and child objects.
- for container managed transactions to work, must all DAOs
use the same Connection?
I.E.
myBeanMethod (,,,)
{
Connectio
Title: dAHHH ... BLOODY CLOB!
Joe,
go to
www.elephantwalker.com, join (its
free) and post your code. We use clobs and blobs from slsb's and cmp/ejb's,
and have solved these problems.
regards,
the
elephantwalker
www.elephantwalker.com
-Original Message-From:
[EMAIL PROTE
You could also try closing the result set explicitly even though the
statement should close the result set when it is closed.
-Original Message-
From: [EMAIL PROTECTED]
[mailto:[EMAIL PROTECTED]]On Behalf Of Ian S. Hagen
Sent: 11 September 2001 13:42
To: Orion-Interest
Subject: SV: OC4J d
Title: dAHHH ... BLOODY CLOB!
OK i have taken all your advice ... and i changed it to a clob ... set up a binary stream ... wohoo ... good to go right? well WRONG! i keep getting marshalling exceptions
Exception: ProjectAdd.saveInfo(): Transaction was rolled back: javax.transaction.SystemExce
Prashant,
You cannot initialize the context within the servlet. Use web.xml with the
following entries with your values:
theName
theValue
The description
theContextParam
com.the.TypeOfResource
CONTAINER|SERVLET
Darryl,
First off (and I know you have probably already checked this but just
in case) have you uncommented the jms.xml attribute in your server.xml
file? Next if you are using Queues and QueueConnectionFactories inside
orion's jms implementation you do not need to use resource-ref tag in
All of out JDBC is done in a try-catch-finally block where the prepared
statement and connection are closed in the finally block.
Transactions are managed using CMT, and CMP is not used as stateless
session EJBs make more sense in the design. Autocommit is off, allowing
the container to handle co
- Original Message -
From: "Vinay Khandelwal" <[EMAIL PROTECTED]>
To: "Orion-Interest" <[EMAIL PROTECTED]>
Sent: Saturday, September 08, 2001 5:46 AM
Subject: UNSUSCRIBE
>
>
>
> __
> Do You Yahoo!?
> Get email alerts & NEW webcam video ins
Hi All
I am implementing the Session Facade design pattern in an application along
with the DAOs. The deviation being no use of Entity beans. What I have
apparently is as follows:
1. A Session Facade bean which has 'open new account method' for which i
have defined RequiresNew transaction attribu
First, if the servlet and ejb are in the same application, you don't need to
use properties to initialize your contextbut if you did, it looks like
you left off the domain in the properties.
Regards,
the elephantwalker
-Original Message-
From: [EMAIL PROTECTED]
[mailto:[EMAIL PROTE
When you get the connection you will need to put it in a try and catch.
At the end use a finally to return the connection.
e.g.
try
{
Connection c = YourClass.getConnection();
}
catch (SQLException ex)
{
//Do something with the exception
}
finally
{
YourClass.returnJDBCCon
HI Friends,
I'm having a serious problem in my code and am unable to
understand. I've deployed a simple Hello bean on the orion container and
want to access it from a servlet. I have the servlet in
D:\Oracle\iSuites\j2ee\home\default-web-app\WEB-INF\classes\trg\HelloServlet
. Following
You need a finally at the end of the try block's to make sure your
connections close. What could be happening is your connections are not being
closed from time to time. Most Oracle ora.ini files are set up for only 30
or so open connections (this is usually ok), but should never be more than
300
Hi,
I am currently part of a project developing a servlet/stateless EJB
solution to be run on the Orion platform. We are experiencing some
problems using our datasource connection to our Oracle 9i database. The
server will on occasion leak connections, which eventually results in
both the Orion
16 matches
Mail list logo
