Re: [Hibernate] eclipse chokes on current annotations code

, July 12, 2006 10:40 AM > To: Scott M Stark; Hibernate development > Subject: Re: [Hibernate] eclipse chokes on current annotations code > > > yes, i realized this (also explained on the bug). > > What tricked me was that neither I or emmanuel must have been > us

Re: [Hibernate] eclipse chokes on current annotations code

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

Re: [Hibernate] questions regarding development setup

Then we need to fix it. http://jira.jboss.com/jira/browse/JBQA-383 > -Original Message- > From: Max Andersen > Sent: Saturday, June 10, 2006 10:21 AM > To: Scott M Stark; Szczepan Faber > Cc: hibernate-devel@lists.sourceforge.net > Subject: RE: [Hibernate] q

Re: [Hibernate] questions regarding development setup

Its more a limitation of the testing environment than project structure. One should be able to annotate known tests as failing at either the test or ci layer to achieve a simple boolean overall result as to whether the testsuite is in an expected state. > -Original Message- > From: [EMAIL

RE: [Hibernate] Do antlr exception leak to users?

used for the ejb3 query language parser. Antlr should not be a required jar in the jboss client jars for ejb3 usage. > -Original Message- > From: Steve Ebersole > Sent: Wednesday, February 08, 2006 6:52 AM > To: Max Andersen; Scott M Stark; > jboss-development@lists.source

RE: [Hibernate] Do antlr exception leak to users?

> which it isn't afaik. the antlr version started to include > more data in the exception over time. > Including additional data is not an incompatible serialzable change generally. Its optional data that will be ignored and cannot affect the legacy implementation. > >> calling printStackTrace(

[Hibernate] jacc-1_0-fr.jar source

Where did the jacc-1_0-fr.jar come from? --- This SF.net email is sponsored by: Splunk Inc. Do you grep through log files for problems? Stop! Download the new AJAX search engine that makes searching your log files as easy as surfing the w

[Hibernate] Is Proxol actually needed in the dist?

Is the Proxool library actually used? It uses the old bsd style license that has a silly requirement regarding all advertising acknowledgment: http://proxool.sourceforge.net/licence.html 3. All advertising materials mentioning features or use of this software must display the following acknow

RE: [Hibernate] Do antlr exception leak to users?

> fixing the antlr exception svuid won't help us if the client > is using an older version, right ? > It will if the serialVersionUID is set to the implicit value from the previous version. This can be done if the version is still serializable compatible. > calling printStackTrace() on every exc

RE: [Hibernate] Release naming conventions

ECTED] On > Behalf Of Scott M Stark > Sent: Tuesday, February 07, 2006 10:22 AM > To: Max Andersen; Christian Bauer; development Hibernate; > [EMAIL PROTECTED] > Cc: jboss-development@lists.sourceforge.net > Subject: RE: [Hibernate] Release naming conventions > > Any place the vers

RE: [Hibernate] Do antlr exception leak to users?

; throw new Xception(msg); } > -Original Message- > From: Max Andersen > Sent: Tuesday, February 07, 2006 10:34 AM > To: Scott M Stark; jboss-development@lists.sourceforge.net; > Hibernate development > Subject: Re: [Hibernate] Do antlr exception leak to users? >

RE: [Hibernate] Do antlr exception leak to users?

nday, February 06, 2006 11:53 AM > To: Scott M Stark; jboss-development@lists.sourceforge.net; > Hibernate development > Subject: Re: [Hibernate] Do antlr exception leak to users? > > On Mon, 06 Feb 2006 20:49:08 +0100, Scott M Stark > <[EMAIL PROTECTED]> > wrote: &

RE: [Hibernate] Release naming conventions

file should be where a project makes version changes and this should just propagated to artifacts based on the build tools. > -Original Message- > From: Max Andersen > Sent: Tuesday, February 07, 2006 10:14 AM > To: Scott M Stark; Christian Bauer; development Hibernat

RE: [Hibernate] Release naming conventions

This has nothing to do with the actual jar names. The version in the jar name is a poor convention as it propagates the version to users unnecessarily, and is not verifiable via a signed manifest. The jars checked into the repository should not have any explicit version information in the name. I d

[Hibernate] Do antlr exception leak to users?

I’m seeing some incompatible serial version uid changes in the latest antlr, but I don’t know if antlr exceptions every leak to users outside of the vm such that this is an issue. Do the ql grammar exception get exposed or are they always converted to a hibernate exception?   serialVersio

RE: [Hibernate] ClassLoader injection

t browsing through the current ejb3 spec. -Original Message- From: Max Andersen Sent: Thursday, February 02, 2006 3:09 PM To: Scott M Stark; Emmanuel Bernard; Bill Burke Cc: Hibernate development Subject: Re: [Hibernate] ClassLoader injection hi, Why is the tcl not the right one even when

RE: [Hibernate] ClassLoader injection

for resources and do annotation searching. -Original Message- From: Max Andersen Sent: Tuesday, January 31, 2006 11:53 PM To: Emmanuel Bernard; Bill Burke Cc: Hibernate development; Scott M Stark Subject: Re: [Hibernate] ClassLoader injection Hi, to bill, yes I know ctx current thread

RE: [Hibernate] Hibernate 3.1.2 released

This has been added to the repository.jboss.com contents and the org.jboss.test.hibernate.test.HibernateIntgUnitTestCase is now passing. -Original Message- From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED] On Behalf Of Steve Ebersole Sent: Saturday, January 28, 2006 6:47 AM To: hibernate-d

Re: [Hibernate] you just gotta love sf.net....

We should move the cvs repo to the jboss hosted one. Max Rydahl Andersen wrote: ...when you do an update and their sucky cvs server is suddenly in lock-mode and I lose 5 files and can't compile my hibernate3 anymore FYI http://sourceforge.net/tracker/?group_id=1&atid=21 has about the

RE: [Hibernate] QuerySyntaxException not always serializable

No, as when this happens its deep in some serialization stack that has no ability to know that an improperly written subclass can be safely replaced with an instance of its baseclass. This is definitely a bug in antlr and a common mistake since the contract for Serializable was is often introduced

[Hibernate] Is this dependency realistic?

Bill created a dependency on a hibernate 3.1 final release for the jboss-4.0.3 release: http://jira.jboss.com/jira/browse/JBAS-1951 I would guess this also affects the har deployer. We want to get jboss-4.0.3 out end of this week, no latter than end of next week. Is this dependency realistic? -

RE: Fw: RE: [Hibernate] Complex class loaders hierarchy

The class loading structure of a j2ee app is vendor specific. For any given component the correct starting point is the thread context class loader. That class loader should have visibility into parent class loaders as needed. > -Original Message- > From: [EMAIL PROTECTED] > [mailto:[EMA

RE: [Hibernate] 3.0.4

Correct. We can certainly extend the JACC service api to allow for configuration and even custom permissions, but then you are deep into a specific JACC provider and far from portable. > -Original Message- > From: [EMAIL PROTECTED] > [mailto:[EMAIL PROTECTED] On > Behalf Of Steve Ebersol

[Hibernate] Safe Query Objects

>From a potential JOSF member: We're very keen to promote a standardization of a truly object-oriented, native API for both, ORMs and ODBMS, distinct from JDO and JDBC. Hibernate and db4o have similar, but proprietary interfaces. If there was a standardized API, people could switch back from ORM