Hi,
I don't know exactly your situation, please check the following conditions:
- you deployed a EJB 3.0 application in an xxx-ejb.jar
- you configured an openejb-jar.xml deployment plan where you set an artifactId
for your app, let's say MyApp
- you have a session bean you want connect to,
Hello,
I followed the discussion about using XDoclet with great interest. I
have been using XDoclet for the last four years to generate EJB
applications and it has been very usefull all the time. But meanwhile
(since EJB 3) I think the situation has changed dramatically. Most of
what I have done
Many thanks to all who answered.
To the (minor) issue concerning the LIKE operator with ESCAPE clause:
The MySQL version I use supports this kind of select. Using the appropriate
property inside the persistance.xml (as Peter said) is an interesting hint
(thanks). But this is a more static way
Hello,
meanwhile I got along a bit further in deploying and using an EJB 3.0
application on g2 (M6). But there still remain some open questions:
1. I did openJPA enhancing on build time (via ant script) to compare the
results with enhancing on deploy time.
In both cases I didn't manage to use
openJPA
On Jul 17, 2007, at 9:25 AM, Ueberbach, Michael wrote:
Hi Jacek,
I had to make a little break, now I'm trying to get back to the last
situation.
Following your last advices:
reducing the persistance.xml to the neccessary elements works for
deploying, but does not help in fetching
works as expected.
As result it seems to me that if there isn't an error inside the deployed code
that jboss does not find, there must be something wrong with parsing the
classes annotations in geronimo resp. openjpa.
regards
Michael
-Ursprüngliche Nachricht-
Von: Ueberbach, Michael
Hi Lukasz,
I don't know exactly your situation, please check the following
conditions:
- you deployed a EJB 3.0 application in an xxx-ejb.jar
- you configured an openejb-jar.xml deployment plan where you set an
artifactId for your app, let's say MyApp
- you have a session bean you want
Did you really use localhost with success calling geronimo 1.2 ?
To my experience localhost doesn't work. Maybe 127.0.0.1 is better.
Michael
-Ursprüngliche Nachricht-
Von: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED] Im Auftrag von Jacek Laskowski
Gesendet: Donnerstag, 12. Juli 2007
Hello Francisco,
I got the same exception when connecting to geronimo from an remote client
(standalone java app).
In my case it helped simply not to specify any principal. So see what happens
if you ommit the two properties
java.naming.security.principal = system
as possible.
Michael
-Ursprüngliche Nachricht-
Von: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED] Im Auftrag von Jacek Laskowski
Gesendet: Dienstag, 10. Juli 2007 11:19
An: user@geronimo.apache.org
Betreff: Re: Problems using openJPA
On 7/10/07, Ueberbach, Michael [EMAIL PROTECTED] wrote
Hello all,
I have some problems using openJPA with Geronimo V2 (M6RC1). The application
(stateless session beans and entity beans) is written in EJB3-Style
using only annotations (persistence.xml is the only descriptor) and is deployed
succesfully.
When trying to fetch some data the following
. Juli 2007 11:49
An: user@geronimo.apache.org
Betreff: Re: Problems using openJPA
On 7/9/07, Ueberbach, Michael [EMAIL PROTECTED] wrote:
23:38:42,637 ERROR [OpenEJB] The bean instances business method
encountered a system exception: Could not locate metadata for the
class using alias Person
Hello,
I'm looking for a NPE which I get while deploying an EJB3 application.
The exception is thrown in class PersistenceUnitBuilder in executing the
method buildPersistenceUnits( ) (line 115). I had a look at the source
code (geronimo-2.0-M3-src) to see what's probably missing.
From the stack
it in your persistence.xml file. with the
jta-data-source element
e.g. jta-data-sourcejava:comp/env/MyTestPool/jta-data-source
On 3/28/07, Ueberbach, Michael [EMAIL PROTECTED] wrote:
Hello,
I need some help in finding out
Hello,
I need some help in finding out the right way to deploy an
ejb-application in Geronimo 2.0M3.
Szenario is as follows:
There is a connection-pool already deployed to an existing
MySQL-Database, let's say MyTestPool.
The application has some entity beans and stateless session beans using
-sourcejava:comp/env/MyTestPool/jta-data-source
On 3/28/07, Ueberbach, Michael [EMAIL PROTECTED] wrote:
Hello,
I need some help in finding out the right way to deploy an
ejb-application in Geronimo 2.0M3.
Szenario is as follows
Hello,
I'm porting an application (self-ejbs-aj.jar) from G 1.1.1 to G 2.0M3.
Deployment of the application (one stateless session bean, some entity
beans) seems to work fine as the boot log shows:
Module 29/29 lama/de.lama.self/1.0/jar
897 INFO [main] openjpa.MetaData - Found 7 classes with
I had a little, but nevertheless important problem using 2.0M3 instead of 1.1.1.
When I tried to migrate to 2.0M3 I couldn't manage to deploy a database pool
using the console. This was no problem in 1.1.1.
Maybe this will be solved in the next milestone?
Regards
Michael
-Ursprüngliche
:36 AM, Ueberbach, Michael wrote:
Hello,
I'm trying to use Geronimo 2-M2 for existing EJB applications that work
well on Geronimo 1.1.1. I use exactly the same jar (consisting of some entity
and session beans in EJB 2.1 style) and the same deployment plan (see the
following
Hallo Hans,
ich antworte hier mal direkt auf Deutsch, da ich annehme, dass es verstanden
wird (jedenfalls besser als mein Englisch).
Ich sehe eine gewisse Ähnlichkeit zu der Situation, in der wir uns hier
befinden. Wir haben mehrere produktive Anwendungen
laufen (einerseits auf dem
hello,
a long time ago (nearly a year or so ...) I started working with geronimo.
Mostly I'm working on EJB applications on the server side and swing based
clients. Meanwhile I have come up to geronimo 1.1.1, and I'm very satisfied
with it.
Recently I found out, that I'm still using some
Hello Milan,
as far as I can see there seem's to be an misunderstandig of the transaction
attribute Required. Setting this attribute means that there has to be an open
transaction already, otherwhile the container will throw this exception. If
Required ist set the caller of the method is
T1
error N/A
-Original Message-
From: Ueberbach, Michael [mailto:[EMAIL PROTECTED]
Sent: po 7. 8. 2006 9:30
To: user@geronimo.apache.org
Subject: AW: container-transaction attributes per method
Hello
try
starting the server with option -verbose:gc -XX:+PrintDetails (works on
java 1.4)
regards
Michael
-Ursprüngliche Nachricht-Von:
[EMAIL PROTECTED]
[mailto:[EMAIL PROTECTED]Gesendet: Freitag, 14. Juli 2006
13:01An: user@geronimo.apache.orgBetreff: Re: stress
test
Hello Markus,
following the spec ejbRemove will be called by the container if the client
wants to remove the entity (normally by calling the remove method on the
interface of the entity bean). In case of BMP one has to code the database
access (deleting the corresponding row) inside the
Hello *,
after a certain delay I tried to migrate my test ejb-application from 1.0 to
1.1. It took only three little trials and everything went fine.
According to the neccessary changes in deployment plans I would like to say
that the upgrade tool is very usefull, but one should have a close
items I've heard is that CMP is not that prevalent in the
world in terms of adoption. I'd be curious to get your feedback on how you use
CMPs and their ubiquity in your environment.
Thanks
Matt
Ueberbach, Michael wrote:
Hello Matt,
yes, this works. Thanks for the hint.
I think geronimo
line.
ejb-ql-compiler-factoryorg.tranql.ejbqlcompiler.OracleQLCompilerFactory/ejb-ql-compiler-factory
db-syntax-factoryorg.tranql.sql.oracle.OracleDBSyntaxFactory/db-syntax-factory
--
These go after the cmp-connection factory. Let me know if this fixes the
problem.
Ueberbach, Michael wrote
hello matt,
It seems so as if I have found a solution to the problem. I undeployed the used
connection pool for the Oracle database and deployed it again this time not
using the console but the command line tool.
In the deployment plan I explicitly set the option CommitBeforeAutocommit to
true
hello all,
while testing some ejb-apps on geronimo I encountered a significant difference
between different databases as connection pools.
Using a local MySQL database all transactions (inserting, updating etc) work
well. Changing to a separate Oracle database the behaviour is different.
?
Ueberbach, Michael wrote:
hello all,
while testing some ejb-apps on geronimo I encountered a significant
difference between different databases as connection pools.
Using a local MySQL database all transactions (inserting, updating etc) work
well. Changing to a separate Oracle database
/explanation here:
http://www.openejb.org/faq_openejb-jar.html
Regards
Preben
Ueberbach, Michael wrote:
hello,
I'm using geronimo M5 and have a question about the deploying of an EJB
application.
I already delpoyed a J2EE connector as a global connection to an existing
Mysql database.
Also I
32 matches
Mail list logo
