Christian Friedl schrieb:
> org.jboss.deployment.DeploymentException: Error compiling EJB-QL
> statement 'select object(o) from Customer as o where o.svrnr
> =?1'; - nested throwable:
> (org.jboss.ejb.plugins.cmp.ejbql.ParseException: Encountered "1" at line
> 1, column 52.
BigDecimal and BigInteger are not supported by EJBQL. If I remember
correctly there is support for it in the current 3.2.2 release. Check
this first.
-marek
Christian Friedl - 26 Nov 2003 07:39 GMT
> [...]
> BigDecimal and BigInteger are not supported by EJBQL.
Ok, I discovered this myself. But what I wondred about was, that
finbyPrimaryKey(), which in my example also utilizes BigDecimals worked
correctly. Any ideas why?
Chris
Christian Friedl - 27 Nov 2003 10:10 GMT
> BigDecimal and BigInteger are not supported by EJBQL. If I remember
> correctly there is support for it in the current 3.2.2 release. Check
> this first.
>
> -marek
Hi!
I didn't check it up to now, but the change notes between 3.2.2 and
3.2.2RC4 contain the following hint:
---> added java.math.BigDecimal and java.math.BigInteger to QL numeric types
Probably your assumption is right! Thanks...
By the way, does anybody know where the change http and ssl port, as
this has also changed within the new release?
Chris
Marek Lange - 27 Nov 2003 15:01 GMT
> >
> > BigDecimal and BigInteger are not supported by EJBQL. If I remember
[quoted text clipped - 15 lines]
> By the way, does anybody know where the change http and ssl port, as
> this has also changed within the new release?
Check out the jboss-service.xml in the corresponding web container
(deploy/jbossweb.sar/META-INF or deploy/jbosstomcat41.sar/META-INF). The
configs of the ports should be there.
-marek
Christian Friedl - 27 Nov 2003 15:00 GMT
[...]
> Check out the jboss-service.xml in the corresponding web container
> (deploy/jbossweb.sar/META-INF or deploy/jbosstomcat41.sar/META-INF). The
> configs of the ports should be there.
Sorry, I didn't mention, that I’m using JBoss with the Jetty servlet
container . I downloaded version jboss-3.2.3RC1-jetty-4.2.14. Since
version 3.2.1 the specific config file changed.
Chris
Christian Friedl - 27 Nov 2003 15:52 GMT
Cause jbossweb-jetty.sar is packed after downloading, file explorer
couldn't find the config files, which specify http nad ssl ports.
Chris
Christian Friedl - 28 Nov 2003 12:32 GMT
> If I remember
> correctly there is support for it in the current 3.2.2 release. Check
> this first.
>
> -marek
Eureka - it works! I just got it working with JBoss-Jetty v 3.2.3 RC1.
Chris
Marek Lange - 28 Nov 2003 21:40 GMT
Christian Friedl schrieb:
>> If I remember correctly there is support for it in the current 3.2.2
>> release. Check this first.
>>
>> -marek
>
> Eureka - it works! I just got it working with JBoss-Jetty v 3.2.3 RC1.
Great! JBoss rules.
-marek