[JBoss-user] [JBoss Seam] - Re: java.lang.NoSuchMethodError: org.jboss.seam.core.Interpo

2006-06-30 Thread jajansen
I am having the same problem. It is a critical bug for me. Is there a workaround? View the original post : http://www.jboss.com/index.html?module=bbop=viewtopicp=3954626#3954626 Reply to the post : http://www.jboss.com/index.html?module=bbop=postingmode=replyp=3954626 Using Tomcat but need

[JBoss-user] [JBoss Seam] - Re: Some thoughts about the conversations

2006-06-02 Thread jajansen
lcoetzee wrote : The idea of starting with a new conversation every time the user selects a new sidebar menu item (e.g. User Management, Add new Issue ...) is very important to me. Same here! I am very interested to hear thought on how to solve this scenario. Do we have a workaround or do I

[JBoss-user] [JCA/JBoss] - ClassCastException with ActiveMQ RA

2006-02-11 Thread jajansen
Hi, I am trying to integrate ActiveMQ 3.2.1 RA into Jboss 4.0.4RC1. I've used the Sonic MQ example for configuration of JCA 1.5 inflow support. When I deploy my MBean I get the following exception: | Caused by: java.lang.ClassCastException: org.activemq.message.ActiveMQTopic | at

[JBoss-user] [EJB 3.0] - Re: New scoping of EntityManager and SessionBeans

2006-02-01 Thread jajansen
Bill, I understand your point on the scoping being spec mandated. But the spec is not final yet, I believe, so do you think that this should be repared in the final spec? Or do you see benifits of scoping to the JAR instead of the EAR level? Your suggestion on repacking sound a lot like what

[JBoss-user] [EJB 3.0] - Re: New scoping of EntityManager and SessionBeans

2006-02-01 Thread jajansen
Ok, guess I have to live with it then ;-) Thanks for the elaboration. View the original post : http://www.jboss.com/index.html?module=bbop=viewtopicp=3920995#3920995 Reply to the post : http://www.jboss.com/index.html?module=bbop=postingmode=replyp=3920995

[JBoss-user] [EJB 3.0] - New scoping of EntityManager and SessionBeans

2006-01-31 Thread jajansen
Is it just me, or is the new (RC4) way of default JNDI names for scoping EntityManagers and SessionBeans plain ugly? EntityManagers are scoped with their jar name, something like @PersistenceContext (name=../domain.jar/em) I think this is wrong, because I don't want to have the name of the jar

[JBoss-user] [EJB 3.0] - Re: FATAL [org.hibernate.ejb.packaging.PersistenceXmlLoader]

2006-01-29 Thread jajansen
I've seen this too, and looked it up in the source code. It can be safely ignored. The author of the code probably used FATAL to make sure it appeared in the logs, while developing the code. It should have been a DEBUG log statement IMHO. Cheers View the original post :

[JBoss-user] [EJB/JBoss] - EJB3 @EmbeddableSuperclass

2005-07-06 Thread jajansen
I've tried to do the following: | @EmbeddableSuperclass | public class DomainObject implements Serializable | { | private Long id; | | public Long getId() | { | return id; | } | | public void setId(Long id) | { | this.id = id; | } | } |

[JBoss-user] [EJB/JBoss] - Re: EJB3 @EmbeddableSuperclass

2005-07-06 Thread jajansen
Oops. The code fragement should be: | @EmbeddableSuperclass | public class DomainObject implements Serializable | { | private Long id; | | @Id (generate = GeneratorType.AUTO) | public Long getId() | { | return id; | } | | public void setId(Long id) |