"wolfc" wrote : How did you start the thread?
|
| I suspect that you're running a custom thread which has no transaction context. You could try using the EJB Timer Service, it starts business methods within the correct context.
In the start() method of my service:
| public void start() throws Exception {
| System.out.println("start");
| Thread thread = new Thread(this);
| thread.start();
| }
|
I had considered using a Timer for it but would that not be much more unnefficient using a Service for something that doesn't quite need it?
Thanks.
View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=3970706#3970706
Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=3970706
I used the following tags in my CMP entity class to generate jbosscmp deployment descriptor file.
@jboss.unknown-pk
* auto-increment = "true"
* column-name = "ID"
* filed-name="id"
* class = "java.lang.Integer"
* jdbc-type = "INTEGER"
* sql-type = "INTEGER"
It seems to generate fine and when deployed also generates the required table. However, the primary key which is suppose to have the identity attribute is not set to yes. Hence my code breaks down because NULL value is being inserted into the ID column by the code since it expects it to be an IDENTITY column.
Any help on how to get jboss to generate the original table with IDENTITY set to yes on MS SQLServer is highly appreciated.
View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=3970703#3970703
Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=3970703