Thanks Jay.
I added setters & getters and now the "deposit()" is working fine. You may
bring this up with OpenJPA forum. I will also join and add the comments.
Thanks again for help.
--Phani
On Fri, May 9, 2008 at 2:49 AM, Jay D. McHugh <[EMAIL PROTECTED]> wrote:
> Hello Phani,
>
> It looks lik
Hello Phani,
It looks like you are correct about not needing to specify container
managed persistence. It is the default.
After lots of playing with your Account and BankBean classes, it looks
like OpenJPA is fine with having your annotations (in Account.java) on
the fields (field access).
Hi,
In the BeankBean.java there is another method "update()" as follows.
___
public void update(Account a) {
manager.merge(a);
}
_
I called this method in the servle
After the step (4), please insert a row in the account table as follows.
"insert into account values (1, 'Owner Name1', 500, 1);"
Thanks
Phani B madgula
On Thu, May 8, 2008 at 10:14 AM, Phani Madgula <
[EMAIL PROTECTED]> wrote:
> Hi Jay,
> I have not explicitly declared transaction configurati
Hi Jay,
I have not explicitly declared transaction configuration. So, the server
should run the the method with "TxRequired". The same info has been logged
to geronimo.log.
I am attaching the apps 1) EJB app 2) WEB app to test ejb app. You may have
a look at the apps. The following are the steps t
Phani,
Are you specifying that you want to use container managed persistence in
your BankBean?
The way to do this with an annotation would be:
@TransactionManagement(TransactionManagementType.CONTAINER)
If you are specifying container managed persistence then you wouldn't
need to worry about
Hi,
I got past the above error but experiencing some strange results as follows.
In the BankBean.java, I have the following method.
*
public void deposit(int accountNumber, int amount) {
Account account = manager.find(Account.class, accountNumber);
account.bala
Hi,
I have an EJB application using JPA and a web application looking up ejbs in
EJB application. I am able to deploy both the applications on AG2.1 server.
But when I hit the servlet, I get the following error in the console.
*
Message: The bean encountered a non-application exception.; neste
Jay
You're right that it's not JPA problem. I've forget that arguments are
passed "by value" if i use remote interface to my Dao beans. So, second
update/persist of my Account object tried to save also parent Customer
object treaten as _NEW_ because daoremote.save() meth
