good to hear about that. where is the state of your work ? I saw you both commited to
head and 1.1, can you report about it please ?
View the original post :
http://www.jboss.org/index.html?module=bb&op=viewtopic&p=3850294#3850294
Reply to the post :
http://www.jboss.org/index.html?module=bb&o
To close out this thread, it turned out to be a bug in XDoclet (I've submitted a
patch), so there's no further action needed by the Nukes team.
View the original post :
http://www.jboss.org/index.html?module=bb&op=viewtopic&p=3850292#3850292
Reply to the post :
http://www.jboss.org/index.html?
you can do it with log4j.xml, afair :
set CONSOLE level as DEBUG
set category org.jboss to INFO
set category org.jboss.ejb.cmp.jdbc to DEBUG
View the original post :
http://www.jboss.org/index.html?module=bb&op=viewtopic&p=3849753#3849753
Reply to the post :
http://www.jboss.org/index.html?m
Ok, then there's a bug in there somewhere since it's not generating Oracle compatible
SQL for the SQL I cited. I'll setup some debug hooks and find the root cause. Thanks
Julien.
View the original post :
http://www.jboss.org/index.html?module=bb&op=viewtopic&p=3849750#3849750
Reply to the post
this is EJBQL or JBossQL so it is portable accross different database since it is
compiled by CMP2 into the good SQL dialect by the engine.
"mlavergn" wrote : Ok, some SQL statements used in the EJB xdoclet defs extend beyond
SQL92 causing portability issues. To cite a particular example, from
