[JBoss-user] [EJB 3.0] - Re: JBoss EJB 3.0 RC4 - PFD Released

2006-02-22 Thread ramazanyich
Hi, we had the same issue with mappedby and IndexColumn. We could solve it by using @JoinColumn in both classes. So in class Document we had: @OneToMany(fetch = FetchType.LAZY, cascade = CascadeType.ALL, mappedby="document") @BatchSize(size = 10) @IndexColumn(name="indexInDocument")

[JBoss-user] [EJB 3.0] - Re: JBoss EJB 3.0 RC4 - PFD Released

2006-02-02 Thread mpaltanwale
Here is what I tried after reading your response on the JBoss forum: 1. I reverted back to List for the relationships. Initially I did not remove the @IndexedColumn annotation. I got the same error message 'index column null' while trying to insert data into the tables.

[JBoss-user] [EJB 3.0] - Re: JBoss EJB 3.0 RC4 - PFD Released

2006-02-01 Thread [EMAIL PROTECTED]
anonymous wrote : I originally started with Set but then was getting ClassCastException when trying to retrieve VirtualRight object from the Set returned by the getVirtualRights() method fo the Application object. | Ok, let's start from here. What is your setup? Where is the ClassCassExcep

[JBoss-user] [EJB 3.0] - Re: JBoss EJB 3.0 RC4 - PFD Released

2006-02-01 Thread mpaltanwale
"[EMAIL PROTECTED]" wrote : AFAIK, only Collection, Set, Map, and List can be used for *ToMany relationship. Let's work from there... I originally started with Set but then was getting ClassCastException when trying to retrieve VirtualRight object from the Set returned by the getVirtualRights(

[JBoss-user] [EJB 3.0] - Re: JBoss EJB 3.0 RC4 - PFD Released

2006-02-01 Thread [EMAIL PROTECTED]
anonymous wrote : | We are running against time to solve this problem as the release date has already slipped. | This is why a support contract is invaluable. View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=3921067#3921067 Reply to the post : http://w

[JBoss-user] [EJB 3.0] - Re: JBoss EJB 3.0 RC4 - PFD Released

2006-02-01 Thread mpaltanwale
Hello, We have built our production application using EJB 3.0 on JBoss Application server 4.0.3 SP1. Here is the description of the problem we are encountering: The problem is really that JBoss can not load EJB 3.0 entity beans which map to more than one table in the database. Here is the real

[JBoss-user] [EJB 3.0] - Re: JBoss EJB 3.0 RC4 - PFD Released

2006-02-01 Thread [EMAIL PROTECTED]
AFAIK, only Collection, Set, Map, and List can be used for *ToMany relationship. Let's work from there... View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=3921066#3921066 Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=392

[JBoss-user] [EJB 3.0] - Re: JBoss EJB 3.0 RC4 - PFD Released

2006-01-31 Thread hxp
Good going, Bill Thanks! --Howard View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=3920828#3920828 Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=3920828 --- This SF.ne