[jboss-user] [EJB 3.0] - Re: Entity bean @Post... lifecycle methods that call SLSB ha
I am not an expert at this, but i think this is what is happening: - SLSB calls some method with transaction T1. In this T1 transaction, the entity is inserted/updated (but not yet commited because the transaction is not complete). During this flow, the @PostUpdate lifecycle method is called in the same transaction context T1. - Now this @PostUpdate lifecycle method calls a SLSB method probably which has the @RequiresNew transaction attribute. As a result a new transaction T2 is created and in this T2 transaction context the SLSB issues a select statement on the same entity. Since these 2 queries are being fired from 2 different transaction contexts (remember that the transaction T1 is not yet committed), this probably is resulting in this issue. You could try changing the transaction attribute of the second SLSB method to @Required and see if it fixes the problem. View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=4182173#4182173 Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=4182173 ___ jboss-user mailing list jboss-user@lists.jboss.org https://lists.jboss.org/mailman/listinfo/jboss-user
[jboss-user] [EJB 3.0] - Re: Entity bean @Post... lifecycle methods that call SLSB ha
I have determined that the problem is more general than I have stated. Simply put: there is an SQL Server request that is not completing and it is blocking any requests to the same table made after it. I see a page level lock. I can see a statement that is blocking/sleeping and then the one that hangs/is blocked by the first. They are both requesting a lcok on the same page (should be okay). The first statement is an insert generated by the EJB3 framework. Why would it be in a state of sleeping/awaiting command? I assume there is some incompatibility between EJB3 subsystem and SQL server or I have something miss-configured. >From the SQL server management studio: THIS ONE IS status=sleeping command = awaiting command (@P0 int,@P1 nvarchar(4000),@P2 nvarchar(4000),@P3 int,@P4 int)insert into eventfactory (srcEvtCode, factoryClass, parms, resultEvent, userModel) values ( @P0 , @P1 , @P2 , @P3 , @P4 ) SELECT SCOPE_IDENTITY() AS ID THIS ONE is waiting on above one to complete: status=suspended command=select ()select eventfacto0_.ik as ik0_, eventfacto0_.srcEvtCode as srcEvtCode0_, eventfacto0_.factoryClass as factoryC2_0_, eventfacto0_.parms as parms0_, eventfacto0_.resultEvent as resultEv6_0_, eventfacto0_.userModel as userModel0_ from eventfactory eventfacto0_ order by eventfacto0_.srcEvtCode asc Makes no sense. There is nothing else happening in the SQL server. View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=4181976#4181976 Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=4181976 ___ jboss-user mailing list jboss-user@lists.jboss.org https://lists.jboss.org/mailman/listinfo/jboss-user
[jboss-user] [EJB 3.0] - Re: Entity Bean Package Modification (javax.persistence.Pers
Are you sure your EAR does not have references to the old jar? Also post the code of your entity along with the package declaration. Please post the persistence.xml too. While posting the logs or xml content or code, remember to wrap it in a code block using the Code button in the message editor window and please hit the Preview button to make sure your post is correctly formatted View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=4159975#4159975 Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=4159975 ___ jboss-user mailing list jboss-user@lists.jboss.org https://lists.jboss.org/mailman/listinfo/jboss-user
[jboss-user] [EJB 3.0] - Re: Entity bean cascade design issue
anonymous wrote : I was searching info about ON DELETE SET NULL equivalent in EJB. All I found is that (probably) this is not implemented. Is this true? For some incomprehensible reason, Hibernate devs consider this functionality "bad design", even though RDMSs have supported it for a long time now. I've never heard an explanation for this, but in practice they've left us hanging. This approach was the best substitute I could think of. View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=4152757#4152757 Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=4152757 ___ jboss-user mailing list jboss-user@lists.jboss.org https://lists.jboss.org/mailman/listinfo/jboss-user
[jboss-user] [EJB 3.0] - Re: Entity bean cascade design issue
Hi!! I was searching info about ON DELETE SET NULL equivalent in EJB. All I found is that (probably) this is not implemented. Is this true? The approach commented this post (with @PreRemove annotation) is correctly working. Can anybody post an example of an interceptor for this? What are the pros and cons of each one? Thanks in advance! View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=4152752#4152752 Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=4152752 ___ jboss-user mailing list jboss-user@lists.jboss.org https://lists.jboss.org/mailman/listinfo/jboss-user
[jboss-user] [EJB 3.0] - Re: entity bean
i got the solution thanks jaikiran View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=4135082#4135082 Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=4135082 ___ jboss-user mailing list jboss-user@lists.jboss.org https://lists.jboss.org/mailman/listinfo/jboss-user
[jboss-user] [EJB 3.0] - Re: entity bean
do you deploy your ejb component into a "jar" other into an "ear"? View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=4135073#4135073 Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=4135073 ___ jboss-user mailing list jboss-user@lists.jboss.org https://lists.jboss.org/mailman/listinfo/jboss-user
[jboss-user] [EJB 3.0] - Re: entity bean
I don't see any obvious problems with the configurations or the jndi-name you are using. The jndi listing that you posted, is it from the "Global JNDI Namespace"? And is there anything more in the exception stacktrace than what you have posted so far? Also, how do you start JBoss? Are you passing any -b option or -Djboss.bind.address while starting JBoss? I see that the client is being invoked through a build script. Are you sure that when this client is being called, the bean has already been deployed and available in the JNDI tree? View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=4135071#4135071 Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=4135071 ___ jboss-user mailing list jboss-user@lists.jboss.org https://lists.jboss.org/mailman/listinfo/jboss-user
[jboss-user] [EJB 3.0] - Re: entity bean
this jndi.proprties file java.naming.factory.initial=org.jnp.interfaces.NamingContextFactory | java.naming.factory.url.pkgs=org.jboss.naming:org.jnp.interfaces | java.naming.provider.url=localhost View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=4135065#4135065 Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=4135065 ___ jboss-user mailing list jboss-user@lists.jboss.org https://lists.jboss.org/mailman/listinfo/jboss-user
[jboss-user] [EJB 3.0] - Re: entity bean
"arrojusrikanth" wrote : jndi name is same in jmx console | | +- EmployeeBean (class: org.jnp.interfaces.NamingContext) | | +- remote (proxy: $Proxy67 implements interface x.EmployeeDao,interface org.jboss.ejb3.JBossProxy,interface javax.ejb.EJBObject) | | This is from the Global JNDI Namespace, right? View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=4135059#4135059 Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=4135059 ___ jboss-user mailing list jboss-user@lists.jboss.org https://lists.jboss.org/mailman/listinfo/jboss-user
[jboss-user] [EJB 3.0] - Re: entity bean
anonymous wrote : iam using jndi.properties file What are the contents of the jndi.properties file. Please post it here. And remember, whenever you are posting logs, code or xml content in the forum please remember to wrap the contents in a code block using the Code button in the message editor window. Also use the Preview button to make sure that the contents show up fine. View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=4135058#4135058 Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=4135058 ___ jboss-user mailing list jboss-user@lists.jboss.org https://lists.jboss.org/mailman/listinfo/jboss-user
[jboss-user] [EJB 3.0] - Re: entity bean
this is the client code
public static void main(String[] args) throws Exception
{
InitialContext ctx=new InitialContext();
EmployeeDao ed=(EmployeeDao)ctx.lookup("EmployeeBean/remote");
System.out.println("Before Create");
int j=ed.create(10,"sat",1);
int k=ed.create(11,"sat",2);
System.out.println("After Create="+j);
List names=ed.findByName("sat");
System.out.println("we have "+names.size()+"sats");
/*Employee e=ed.find(j);
e.setName("hello");
ed.merge(e);
List name1=ed.findByName("sat");
System.out.println("we have "+names.size()+"sats");*/
}
}
View the original post :
http://www.jboss.com/index.html?module=bb&op=viewtopic&p=4135056#4135056
Reply to the post :
http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=4135056
___
jboss-user mailing list
jboss-user@lists.jboss.org
https://lists.jboss.org/mailman/listinfo/jboss-user
[jboss-user] [EJB 3.0] - Re: entity bean
exception stack trace [java] Exception in thread "main" javax.naming.NameNotFoundException: remot e not bound [java] at org.jnp.server.NamingServer.getBinding(NamingServer.java:529) [java] at org.jnp.server.NamingServer.getBinding(NamingServer.java:537) [java] at org.jnp.server.NamingServer.getObject(NamingServer.java:543) [java] at org.jnp.server.NamingServer.lookup(NamingServer.java:296) [java] at org.jnp.server.NamingServer.lookup(NamingServer.java:270) [java] at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method) [java] at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAcces sorImpl.java:39) [java] at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMet hodAccessorImpl.java:25) [java] at java.lang.reflect.Method.invoke(Method.java:597) [java] at sun.rmi.server.UnicastServerRef.dispatch(UnicastServerRef.jav a:305) [java] at sun.rmi.transport.Transport$1.run(Transport.java:159) [java] at java.security.AccessController.doPrivileged(Native Method) [java] at sun.rmi.transport.Transport.serviceCall(Transport.java:155) [java] at sun.rmi.transport.tcp.TCPTransport.handleMessages(TCPTranspor t.java:535) [java] at sun.rmi.transport.tcp.TCPTransport$ConnectionHandler.run0(TCP Transport.java:790) [java] at sun.rmi.transport.tcp.TCPTransport$ConnectionHandler.run(TCPT ransport.java:649) [java] at java.util.concurrent.ThreadPoolExecutor$Worker.runTask(Thread PoolExecutor.java:885) [java] at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPool Executor.java:907) [java] at java.lang.Thread.run(Thread.java:619) [java] at sun.rmi.transport.StreamRemoteCall.exceptionReceivedFromServe r(StreamRemoteCall.java:255) [java] at sun.rmi.transport.StreamRemoteCall.executeCall(StreamRemoteCa ll.java:233) [java] at sun.rmi.server.UnicastRef.invoke(UnicastRef.java:142) [java] at org.jnp.server.NamingServer_Stub.lookup(Unknown Source) [java] at org.jnp.interfaces.NamingContext.lookup(NamingContext.java:62 5) [java] at org.jnp.interfaces.NamingContext.lookup(NamingContext.java:58 7) [java] at javax.naming.InitialContext.lookup(InitialContext.java:392) [java] at x.Client.main(Client.java:12) [java] Java Result: 1 BUILD SUCCESSFUL Total time: 3 minutes 42 seconds iam using jndi.properties file View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=4135055#4135055 Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=4135055 ___ jboss-user mailing list jboss-user@lists.jboss.org https://lists.jboss.org/mailman/listinfo/jboss-user
[jboss-user] [EJB 3.0] - Re: entity bean
Please post the entire exception stacktrace and the entire lookup code that you are using. Do you have any jndi.properties file in your classpath or are you passing any properties while creating the InitialContext object? View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=4135054#4135054 Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=4135054 ___ jboss-user mailing list jboss-user@lists.jboss.org https://lists.jboss.org/mailman/listinfo/jboss-user
[jboss-user] [EJB 3.0] - Re: entity bean
jndi name is same in jmx console
+- EmployeeBean (class: org.jnp.interfaces.NamingContext)
| +- remote (proxy: $Proxy67 implements interface x.EmployeeDao,interface
org.jboss.ejb3.JBossProxy,interface javax.ejb.EJBObject)
and in client program
EmployeeDao ed=(EmployeeDao)ctx.lookup("EmployeeBean/remote");
View the original post :
http://www.jboss.com/index.html?module=bb&op=viewtopic&p=4135053#4135053
Reply to the post :
http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=4135053
___
jboss-user mailing list
jboss-user@lists.jboss.org
https://lists.jboss.org/mailman/listinfo/jboss-user
[jboss-user] [EJB 3.0] - Re: entity bean
A NameNotFoundException is usually because you are not using the correct name for the jndi lookup. Follow the steps mentioned at http://wiki.jboss.org/wiki/Wiki.jsp?page=DisplayTheJDNITreeWithTheJMXConsole and figure out the jndi-name of the bean you are trying to lookup. Then use that jndi-name while doing the lookup. View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=4135049#4135049 Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=4135049 ___ jboss-user mailing list jboss-user@lists.jboss.org https://lists.jboss.org/mailman/listinfo/jboss-user
[jboss-user] [EJB 3.0] - Re: entity bean to a view?
I have found the solution.remove this entry from your persistence.xml | validate | Looks like a bug in hibernate View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=4094175#4094175 Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=4094175 ___ jboss-user mailing list jboss-user@lists.jboss.org https://lists.jboss.org/mailman/listinfo/jboss-user
[jboss-user] [EJB 3.0] - Re: entity bean to a view?
Has anyone know of a fix for this problem I have the same issue View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=4093633#4093633 Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=4093633 ___ jboss-user mailing list jboss-user@lists.jboss.org https://lists.jboss.org/mailman/listinfo/jboss-user
[jboss-user] [EJB 3.0] - Re: entity bean name in ejb3 RC7
Hi,
I am developing a seam application integrated with JBPM. I am using Seam
1.0.1.GA on Jboss 4.0.4.GA with JBPM 3.1 I have a combined persistnace for JBMP
and my application objects.
When I do a create query as follows:
User found =
(User) em.createQuery("from JBPM_ID_USER u where u.ID__ =
:userName and u.PASSWORD_ = :password")
.setParameter("userName", username)
.setParameter("password", password)
.getSingleResult();
I get the following error:
15:08:26,080 ERROR [STDERR] javax.persistence.PersistenceException:
org.hibernat
e.hql.ast.QuerySyntaxException: JBPM_ID_USER is not mapped [select NAME_ from
JBPM_ID_USER]
I have copied the jbpm-identity-3.1.jar into ejb3 folder for the ear
have the following entires in the hibernate.cfg.xml
mapping resource="org/jbpm/identity/User.hbm.xml"
mapping resource="org/jbpm/identity/Group.hbm.xml"
mapping resource="org/jbpm/identity/Membership.hbm.xml"
I hve tried both the ways mentioned above,but both ways failed to solve the
issue.
Can anybody throw some light on this.
Thanks,
Ikram
View the original post :
http://www.jboss.com/index.html?module=bb&op=viewtopic&p=3969224#3969224
Reply to the post :
http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=3969224
___
jboss-user mailing list
jboss-user@lists.jboss.org
https://lists.jboss.org/mailman/listinfo/jboss-user
[jboss-user] [EJB 3.0] - Re: entity bean name in ejb3 RC7
I've tried it and it should work but it doesn't :( . There is a bug that incorrectly generates the wrong path to the jar file. I hope they fix this soon. I do however have a workaround. You can use the class property to list all the persistence classes that you want to have available in the persistence manager. Example: | ... | java:/MyDS | yPackage.User | yPackage.SomeOtherEntity | | ... | It isn't really nice, but it works. I tested it. View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=3967196#3967196 Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=3967196 ___ jboss-user mailing list jboss-user@lists.jboss.org https://lists.jboss.org/mailman/listinfo/jboss-user
[jboss-user] [EJB 3.0] - Re: entity bean name in ejb3 RC7
OK, I'll check it today. View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=3967166#3967166 Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=3967166 ___ jboss-user mailing list jboss-user@lists.jboss.org https://lists.jboss.org/mailman/listinfo/jboss-user
[jboss-user] [EJB 3.0] - Re: entity bean name in ejb3 RC7
I found something, which I unfortunatelly don't have to time to check right now. There should be line: | ... | java:/UMKDS | ../data.jar | | ... | at persistence.xml, where data.jar is jar with entities. If you check it, I will appreciate if you could tell If it works. regards Michal View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=3967155#3967155 Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=3967155 ___ jboss-user mailing list jboss-user@lists.jboss.org https://lists.jboss.org/mailman/listinfo/jboss-user
[jboss-user] [EJB 3.0] - Re: entity bean name in ejb3 RC7
I am having the same problem. Somehow Hibernate can't find the entitity classes in a different ejb package within the same ear package. I would really like to now how to fix this. View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=3967114#3967114 Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=3967114 ___ jboss-user mailing list jboss-user@lists.jboss.org https://lists.jboss.org/mailman/listinfo/jboss-user
[jboss-user] [EJB 3.0] - Re: Entity bean state not rolled back on TX rollback:
Just for any that are interested in this thread, here is what the spec says about this: anonymous wrote : | EJB3 Persistence Specification, page 54 | | 3.3.2 Transaction Rollback | | For both transaction-scoped and extended persistence contexts, transaction rollback causes all pre-existing managed instances and removed instances [15] to become detached. The instances? state will be the state of the instances at the point at which the transaction was rolledback. Transaction rollback typically causes the persistence context to be in an inconsistent state at the point of rollback. Inparticular, the state of version attributes and generated state (e.g., generated primary keys) may be inconsistent. | Instances that were formerly managed by the persistence context (including new instances that were made persistent in that transaction) may therefore not be reusable in the same manner as other detached | objects?for example, they may fail when passed to the merge operation.[16] | | ... | | [16] It is unspecified as to whether instances that were not persistent in the database behave as new instances or detached instances after rollback. This may be implementation-dependent. | I personally am curious why full blown @Entity property rollback isn't in the spec. Perhaps in the big picture it's not as useful as I think it is. View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=3958274#3958274 Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=3958274 ___ jboss-user mailing list jboss-user@lists.jboss.org https://lists.jboss.org/mailman/listinfo/jboss-user
[jboss-user] [EJB 3.0] - Re: Entity bean state not rolled back on TX rollback:
This is a real pain to workaround since if a transaction is rolled back because of a database deadlock, entities with @GeneratedValue @Ids end up with bogus @Ids since the generated database values have been rolled back in the database, but not in the entities. Therefore, an automatic retry of the transaction will not work because the entities are now technically "detached" entities and em.persist() will fail. Even if full blown entity property rollback isn't implemented, it seems that at the very least @GeneratedValue @Id should be. Here is a possible workaround I can try: 1) Mark the entities in the entity graph which do not have @GeneratedValue @Id values set using a @PrePersist entity callback/listener. 2) Add an EJB3 Interceptor that wraps the CMT demarcation point. This could catch EJB3TransactionRolledbackException, traverse the entity graph in the EntityManager and unset the @Ids of the marked entities, then rethrow the EJB3TransactionRolledbackException. Does anyone have any better ideas? This solution seems rather dirty. Also, it may not even be possible to get a list of the currently managed entities from the EntityManager (I don't see any interface in EntityManager or org.hibernate.Session). Of course, it sure would be nice to have real entity bean property rollback semantics... ;) View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=3958236#3958236 Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=3958236 ___ jboss-user mailing list jboss-user@lists.jboss.org https://lists.jboss.org/mailman/listinfo/jboss-user
[jboss-user] [EJB 3.0] - Re: Entity bean state not rolled back on TX rollback:
"[EMAIL PROTECTED]" wrote : we could possible put this in, but it would not be portable behavior. The spec doesn't require rollback of entity state. OK, thanks for the response. I was mistaken and thought this was required by the spec. In your book, EJB 3.0 5th edition (which is awesome btw!), on the last paragraph page 370, it says this: "As a transaction monitor, an EJB3 server watches each method call in the transaction. If any of the updates fail, all the updates to the EJBs and entities will be reversed or rolled back." ... View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=3958096#3958096 Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=3958096 ___ jboss-user mailing list jboss-user@lists.jboss.org https://lists.jboss.org/mailman/listinfo/jboss-user
[jboss-user] [EJB 3.0] - Re: Entity bean state not rolled back on TX rollback:
we could possible put this in, but it would not be portable behavior. The spec doesn't require rollback of entity state. View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=3958089#3958089 Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=3958089 ___ jboss-user mailing list jboss-user@lists.jboss.org https://lists.jboss.org/mailman/listinfo/jboss-user
[jboss-user] [EJB 3.0] - Re: Entity bean state not rolled back on TX rollback:
Also, I am using CMT (container managed transactions) View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=3958069#3958069 Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=3958069 ___ jboss-user mailing list jboss-user@lists.jboss.org https://lists.jboss.org/mailman/listinfo/jboss-user
[jboss-user] [EJB 3.0] - Re: Entity bean state not rolled back on TX rollback:
Sorry... I am running JBoss 4.0.4.GA (w/ EJB3 RC7) View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=3957917#3957917 Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=3957917 ___ jboss-user mailing list jboss-user@lists.jboss.org https://lists.jboss.org/mailman/listinfo/jboss-user
[jboss-user] [EJB 3.0] - Re: Entity Bean behaves strangely with @OneToMany
afaik this is by design - see also: http://www.jboss.com/index.html?module=bb&op=viewtopic&p=3953231#3953231 and http://www.jboss.com/index.html?module=bb&op=viewtopic&p=3945085#3945085 View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=3957375#3957375 Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=3957375 ___ jboss-user mailing list jboss-user@lists.jboss.org https://lists.jboss.org/mailman/listinfo/jboss-user
[jboss-user] [EJB 3.0] - Re: Entity Bean behaves strangely with @OneToMany
Hi Andi, thanks for your reply Neither the Javadoc (from Sun) nor the O'Reilly EJB 3 book mentiones this. I presume this is a JBoss specific issue? Mike View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=3956923#3956923 Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=3956923 ___ jboss-user mailing list jboss-user@lists.jboss.org https://lists.jboss.org/mailman/listinfo/jboss-user
