For the first problem:
- i think that you just jumped over to the third argument that is not defined for that finder
- try to put some paranthesis around the conditions
For the second:
<<JBossQL is a superset of EJB-QL that is designed to address some of the inadequacies of
EJB-QL. In addition to a more flexible syntax, new functions, key words, and clauses have been
added to JBossQL.>>
For more on this i think you must subscribe to the documentation of JBoss.
Note: i am not working at jboss.
There are only solutions
>For the first problem:
>- i think that you just jumped over to the third argument >that is not defined for that finder
--> It's an error of me, the real code is :
FROM CurrentMessage AS o
WHERE o.nombre = ?1 AND o.strId = ?2
>- try to put some paranthesis around the conditions
--> I've done it without but it still wrong.
>For more on this i think you must subscribe to the documentation of JBoss.
--> I agree with you but for the moment I can't. It doesn't depend on me ...
But I really wonder if the BigDecimal type is supported by JBoss .... cause, if I put 2 string it runs, if I put an integer, it also runs ...
Thanks for your help.
Which is your DB.
With MSSQLSERVER2000 big decimal is translated as you can see in your jbosscmpjdbc.xml in the conf directory of your server.
Tell me if it helps
I've seen your previous message ...
I'm using Oracle 9i.
>With MSSQLSERVER2000 big decimal is translated as you can see in your jbosscmpjdbc.xml in the conf directory of your server.
--> ahhhhhhhh !!!!!
I didn't know that file !!!!
So here is the part interesting for me in the standardjbosscmp-jdbc.xml :
So Jboss accep it .... good !
My question is know : What should I do with that file ?
Should I copy it in my server\deploy directory ?
Should I change my ejb-ql request and write DECIMAL or NUMBER(38,15) ?
That the first time i use it so i don't really know how to do ...
Thanks for your help.
1) The files here describe the default behavior of JBoss.
Each one can be overload in your deployment descriptors (web & EJB).
2) as far as we talk about type mapping, you have to think that it's the way JBoss knows how to translate java type in your finders (or selects) to SQL depending on the DB you configure in your datasources. So you have to check if your database column type you use is compatible with the one JBoss will use (in your case NUMBER(38,15) ).
3) It's good to know that people from Atos Origin are interested in this kind of product and not only on big brands' ones.