View results here -> http://cruisecontrol.jboss.com/cc/buildresults/hibernate-sybase-testsuite?log=log20060711234837
-
Using Tomcat but need to do more? Need to support web services, security?
Get stuff done quickly w
Hi list,
Migrating a test project from one dialect to another I've stumbled across
something that looks to me like a coding mistake, but not beeing very familiar
with Derby, I wonder if I simply overlooked something?
Here's the code: (from org.hibernate.dialect.DerbyDialect)
public Cla
The DerbyDialect was contributed by an external party.
If you have a better implementation patches are welcome in our jira.
But it would be nice to know why the external contributor choose
to use tablehilo as the default and have that "fun" identitycolumnstring.
The original contributor was Simo
javac works fine, but eclipse chokes on casting Properties to Map
I've bugged eclipse about it to see what they provide as explanation.
https://bugs.eclipse.org/bugs/show_bug.cgi?id=150362
--
--
Max Rydahl Andersen
callto://max.rydahl.andersen
Hibernate
[EMAIL PROTECTED]
http://hibernate.org
That is a rather basic generics error that is a bug in javac since
Properties is typed as Map, not Map. You
are asking to be able to do (replacing ? with String to be more
concrete):
Map m1 = ...;
Map m2 = (Map) m1;
javac disallows this as it should since one would be able to do the
following oth
yes, i realized this (also explained on the bug).
What tricked me was that neither I or emmanuel must have been using
the latest javac ;)
/max
> That is a rather basic generics error that is a bug in javac since
> Properties is typed as Map, not Map. You
> are asking to be able to do (replacing
This is the issue with generics. I have seen both javac and eclipse with
compiler bugs that allowed unsafe usage of collections. There still
really are no guarentees, only better static analysis of possible
misuse.
> -Original Message-
> From: Max Andersen
> Sent: Wednesday, July 12, 2006
Scott M Stark wrote:
> This is the issue with generics. I have seen both javac and eclipse with
> compiler bugs that allowed unsafe usage of collections. There still
> really are no guarentees, only better static analysis of possible
> misuse.
There are runtime guarantees if you use java.util.Coll
View results here -> http://cruisecontrol.jboss.com/cc/buildresults/hibernate-timesten-testsuite?log=log20060713010012
TESTS FAILEDAnt Error Message: /home/cruisecontrol/work/scripts/build-hibernate-db-matrix.xml:94: The following error occurred while executing this line: /home/cruisecontrol/work/
