[JBoss-user] [JBossWS] - wscompile and EJB3 Entities

2005-12-23 Thread rudifr
I am trying to transfer EJB3 Entity Beans with J2EE 1.4 Web Services. Since EJB3 Entity Beans are POJO's it should be possible to transfer them directly instead of writing additional value objects. When I create the WSDL with wscompile from JWSDP 1.6 it doesn't find the annotation classes e.g. j

[JBoss-user] [EJB/JBoss] - Re: Manifest Classpath Problem

2005-06-21 Thread rudifr
I had the same problem with JBoss 3.2.3 running under Java 1.4.2. In the ejb-jar were some classes compiled with JDK 1.5. Compiling all with JDK 1.4.2 fixed the problem. View the original post : http://www.jboss.org/index.html?module=bb&op=viewtopic&p=3882232#3882232 Reply to the post : http:/

[JBoss-user] [Messaging, JMS & JBossMQ] - Re: OIL connections increasing

2004-06-09 Thread rudifr
We have the same problem with JBoss 3.2.3 and Oracle 9i as persistence mechanism for JMS. The number of connections and the number of OIL Worker and OILClientILService threads are steadily increasing. View the original post : http://www.jboss.org/index.html?module=bb&op=viewtopic&p=3838075#3

[JBoss-user] [Persistence & CMP/JBoss] - Re: DB Update after a select

2004-03-02 Thread rudifr
All java.util.Date fields are updated. In Oracle9i they are TIMESTAMP(3). I've found a workaround for this problem in this forum: In jbosscmp-jdbc.xml, set to false for your non-primitive CMP fields. shipDate ship_date DATE DATE false It works great and I didn't have a deadlock sin

[JBoss-user] [Persistence & CMP/JBoss] - Re: DB Update after a select

2004-03-01 Thread rudifr
Hi, has anyone found a workaround for this problem so far? I'm using JBoss 3.2.3 and Oracle 9i and there are happening UPDATES in finder methods after the SELECT. This causes huge deadlock problems in the database (ORA-00060). I switched to the "1 instance per transaction" configuration to avoid