RE: [JBoss-dev] Re: FW: jboss-4.0.4 portal-2.2 issue

[Steve Ebersole]

If I recall correctly, they tried that setup initially but ran into the
locking issues that plagued the earlier Hibernate/JBossCache
integrations.  

Conceivably they could try with the new optimistic-locking-based
provider, but we really need some performance numbers here to see how a
local, optimistic JBossCache configuration performs against EhCache...



Good point - why doesn't Portal ship with Hibernate configured with  
JBoss Cache?

On 12 May 2006, at 19:34, Adrian Brock wrote:

SNIP /


 The solutions are:
 1) JBoss Portal's session factory is configured to use JBoss Cache
 not EhCache

SNIP /


---
Using Tomcat but need to do more? Need to support web services, security?
Get stuff done quickly with pre-integrated technology to make your job easier
Download IBM WebSphere Application Server v.1.0.1 based on Apache Geronimo
http://sel.as-us.falkag.net/sel?cmd=lnkkid0709bid3057dat1642
___
JBoss-Development mailing list
JBoss-Development@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/jboss-development

[JBoss-dev] RE: cglib still being seen as bytecode provider

[Steve Ebersole]

How will this be done on the har mbean?  It cannot be a managed
attribute, in that changing it at runtime will have no effect (basically
the same for ejb3, since it uses the same underlying machinery).  This
setting needs to be defined appropriately before the
org.hibernate.cfg.Environment static initializers kick in

-Original Message-
From: Scott M Stark 
Sent: Wednesday, May 10, 2006 9:49 AM
To: Emmanuel Bernard
Cc: Dev - JBossSeam; dev-ejb3; jboss-development@lists.sourceforge.net
Subject: RE: cglib still being seen as bytecode provider

Looks much better. I'm going to make the bytecode provider a
configurable option on the ejb3 deployer and har mbean rather than using
a hard-coded setting.

[EMAIL PROTECTED] ~]$ cd /cvs/JBoss4.0/jboss-4.0.x/ejb3
[EMAIL PROTECTED] ejb3]$ ant -buildfile build-test.xml
no-start-jboss-ejb-te
sts
Buildfile: build-test.xml

init:

no-start-jboss-ejb-tests:

init:

test:

test-with-jvmargs:
   [delete] Deleting:
C:\cvs\JBoss4.0\jboss-4.0.x\ejb3\output\log\test.log
[junit] Running org.jboss.ejb3.test.webservices.unit.WsUnitTestCase
[junit] Tests run: 1, Failures: 0, Errors: 0, Time elapsed: 3.094
sec

init:

test:

test-with-jvmargs:
   [delete] Deleting:
C:\cvs\JBoss4.0\jboss-4.0.x\ejb3\output\log\test.log
[junit] Running
org.jboss.ejb3.test.regression.ejbthree454.unit.RemoteUnitTe
stCase
[junit] Tests run: 1, Failures: 0, Errors: 0, Time elapsed: 3.297
sec

init:

test:

test-with-jvmargs:
   [delete] Deleting:
C:\cvs\JBoss4.0\jboss-4.0.x\ejb3\output\log\test.log
[junit] Running
org.jboss.ejb3.test.regression.salesforce7123.unit.NotSuppor
tedUnitTestCase
[junit] Tests run: 1, Failures: 0, Errors: 0, Time elapsed: 2.922
sec

init:

test:

test-with-jvmargs:
   [delete] Deleting:
C:\cvs\JBoss4.0\jboss-4.0.x\ejb3\output\log\test.log
[junit] Running
org.jboss.ejb3.test.regression.scopedclassloader.unit.ScopeU
nitTestCase
[junit] Tests run: 1, Failures: 0, Errors: 0, Time elapsed: 1.781
sec

init:

test:

test-with-jvmargs:
   [delete] Deleting:
C:\cvs\JBoss4.0\jboss-4.0.x\ejb3\output\log\test.log
[junit] Running
org.jboss.ejb3.test.dependency.unit.DependencyUnitTestCase
[junit] Tests run: 4, Failures: 0, Errors: 0, Time elapsed: 3.5 sec

init:

test:

test-with-jvmargs:
   [delete] Deleting:
C:\cvs\JBoss4.0\jboss-4.0.x\ejb3\output\log\test.log
[junit] Running org.jboss.ejb3.test.bmt.unit.BMTUnitTestCase
[junit] Tests run: 4, Failures: 0, Errors: 0, Time elapsed: 1.984
sec

init:

test:

test-with-jvmargs:
   [delete] Deleting:
C:\cvs\JBoss4.0\jboss-4.0.x\ejb3\output\log\test.log
[junit] Running
org.jboss.ejb3.test.regression.ejbthree249.unit.Dependencies
UnitTestCase
[junit] Tests run: 1, Failures: 0, Errors: 0, Time elapsed: 0.641
sec

init:

test:

test-with-jvmargs:
   [delete] Deleting:
C:\cvs\JBoss4.0\jboss-4.0.x\ejb3\output\log\test.log
[junit] Running
org.jboss.ejb3.test.regression.ejbthree316.unit.StatefulUnit
TestCase
[junit] Before DOIT testStateful
[junit] After DOIT testStateful
[junit] After find testStateful
[junit] Tests run: 3, Failures: 0, Errors: 0, Time elapsed: 16.593
sec

init:

test:

test-with-jvmargs:
   [delete] Deleting:
C:\cvs\JBoss4.0\jboss-4.0.x\ejb3\output\log\test.log
[junit] Running
org.jboss.ejb3.test.regression.ejbthree231.unit.StatefulUnit
TestCase
[junit] Tests run: 1, Failures: 0, Errors: 0, Time elapsed: 6.016
sec

init:

test:

test-with-jvmargs:
   [delete] Deleting:
C:\cvs\JBoss4.0\jboss-4.0.x\ejb3\output\log\test.log

init:

test:

test-with-jvmargs:
[junit] Running
org.jboss.ejb3.test.interceptors2.unit.InterceptorsTestCase
[junit] Tests run: 12, Failures: 0, Errors: 0, Time elapsed: 8.437
sec

init:

test:

test-with-jvmargs:
   [delete] Deleting:
C:\cvs\JBoss4.0\jboss-4.0.x\ejb3\output\log\test.log
[junit] Running
org.jboss.ejb3.test.interceptors.unit.RemoteUnitTestCase
[junit] Tests run: 1, Failures: 0, Errors: 0, Time elapsed: 1.453
sec 

 -Original Message-
 From: Emmanuel Bernard [mailto:[EMAIL PROTECTED] 
 Sent: Wednesday, May 10, 2006 6:57 AM
 To: Scott M Stark
 Cc: Dev - JBossSeam; dev-ejb3; jboss-development@lists.sourceforge.net
 Subject: Re: cglib still being seen as bytecode provider
 
 I've track down the leak
 http://opensource.atlassian.com/projects/hibernate/browse/ANN-340
 
 The new hibernate-annotations.jar (version 3.2.0.CR1) has 
 been updated in repository.jboss.com (CVS).
 
 I haven't found other dependecies to CGLIB, in HA and HEM, let me know
 


---
Using Tomcat but need to do more? Need to support web services, security?
Get stuff done quickly with pre-integrated technology to make your job easier
Download IBM WebSphere Application Server v.1.0.1 based on Apache Geronimo
http://sel.as-us.falkag.net/sel?cmd=lnkkid0709bid3057dat1642
___
JBoss-Development mailing list

[JBoss-dev] RE: cglib still being seen as bytecode provider

[Steve Ebersole]

Hibernate effectively only recognizes system properties for this setting
right now (there are actually a few like this).  Changing this is *very*
intensive, but obviously something I'd like to do anyway at some point.

BTW, I need to upload a hibernate-3.2.0.cr3 for use in this release as
the previous one had an incompatibility with the new annotations jar
that emmanuel needs to upload.

-Original Message-
From: Scott M Stark 
Sent: Wednesday, May 10, 2006 10:59 AM
To: Bill Burke
Cc: Emmanuel Bernard; Dev - JBossSeam; dev-ejb3;
jboss-development@lists.sourceforge.net
Subject: RE: cglib still being seen as bytecode provider

I'm doing it in head now and synching up the hibernate/javassist
versions as they are out of date with respect to the 4.0 branch. We do
need to be able to pass this in as a persistence engine property rather
than a system property for the final release. 

 -Original Message-
 From: Bill Burke 
 Sent: Wednesday, May 10, 2006 8:52 AM
 To: Scott M Stark
 Cc: Emmanuel Bernard; Dev - JBossSeam; dev-ejb3; 
 jboss-development@lists.sourceforge.net
 Subject: Re: cglib still being seen as bytecode provider
 
 there is a default.persistence.properties file for this kind 
 of stuff. 
 Please change it in head as I will be backmerging everything 
 on thursday.
 
 Bill
 


---
Using Tomcat but need to do more? Need to support web services, security?
Get stuff done quickly with pre-integrated technology to make your job easier
Download IBM WebSphere Application Server v.1.0.1 based on Apache Geronimo
http://sel.as-us.falkag.net/sel?cmd=lnkkid0709bid3057dat1642
___
JBoss-Development mailing list
JBoss-Development@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/jboss-development

[JBoss-dev] RE: cglib still being seen as bytecode provider

[Steve Ebersole]

Scratch the 3.2.0.cr3 bit.  Emmanuel simply replaced the version he
uploaded before instead of creating a new release version.  So we're
good...

-Original Message-
From: Steve Ebersole 
Sent: Wednesday, May 10, 2006 11:50 AM
To: Dev - JBossSeam; dev-ejb3; 'jboss-development@lists.sourceforge.net'
Subject: RE: cglib still being seen as bytecode provider

Hibernate effectively only recognizes system properties for this setting
right now (there are actually a few like this).  Changing this is *very*
intensive, but obviously something I'd like to do anyway at some point.

BTW, I need to upload a hibernate-3.2.0.cr3 for use in this release as
the previous one had an incompatibility with the new annotations jar
that emmanuel needs to upload.

-Original Message-
From: Scott M Stark 
Sent: Wednesday, May 10, 2006 10:59 AM
To: Bill Burke
Cc: Emmanuel Bernard; Dev - JBossSeam; dev-ejb3;
jboss-development@lists.sourceforge.net
Subject: RE: cglib still being seen as bytecode provider

I'm doing it in head now and synching up the hibernate/javassist
versions as they are out of date with respect to the 4.0 branch. We do
need to be able to pass this in as a persistence engine property rather
than a system property for the final release. 

 -Original Message-
 From: Bill Burke 
 Sent: Wednesday, May 10, 2006 8:52 AM
 To: Scott M Stark
 Cc: Emmanuel Bernard; Dev - JBossSeam; dev-ejb3; 
 jboss-development@lists.sourceforge.net
 Subject: Re: cglib still being seen as bytecode provider
 
 there is a default.persistence.properties file for this kind 
 of stuff. 
 Please change it in head as I will be backmerging everything 
 on thursday.
 
 Bill
 


---
Using Tomcat but need to do more? Need to support web services, security?
Get stuff done quickly with pre-integrated technology to make your job easier
Download IBM WebSphere Application Server v.1.0.1 based on Apache Geronimo
http://sel.as-us.falkag.net/sel?cmd=lnkkid0709bid3057dat1642
___
JBoss-Development mailing list
JBoss-Development@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/jboss-development

[JBoss-dev] RE: Hibernate, HA, ,HEM, antlr versions in Branch_4_0

[Steve Ebersole]

No objections.  I just have not switched over hibernate-int yet because
of the outstanding question of cglib/javassist.  They are basically
unrelated, but just wanted to get that committed all together.

I'll commit that stuff this morning.

-Original Message-
From: Dimitris Andreadis 
Sent: Monday, May 08, 2006 3:49 AM
To: Emmanuel Bernard; Steve Ebersole; Scott M Stark; Bill Burke
Cc: jboss-development@lists.sourceforge.net
Subject: Hibernate, HA, ,HEM, antlr versions in Branch_4_0

In Branch_4_0 we have:

componentref name=hibernate version=3.2.0.CR1/
componentref name=hibernate-annotations version=3.1beta9/
componentref name=hibernate-entitymanager version=3.1beta7/
componentref name=antlr version=2.7.6rc1/

We agree we want those to become:

H - 3.2.0.CR2
HA - 3.2.0.CR1
HEM - 3.2.0.CR1
Antlr - 2.7.6.ga

Objections?


---
Using Tomcat but need to do more? Need to support web services, security?
Get stuff done quickly with pre-integrated technology to make your job easier
Download IBM WebSphere Application Server v.1.0.1 based on Apache Geronimo
http://sel.as-us.falkag.net/sel?cmd=lnkkid0709bid3057dat1642
___
JBoss-Development mailing list
JBoss-Development@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/jboss-development

RE: [JBoss-dev] RE: Hibernate, HA, ,HEM, antlr versions in Branch_4_0

[Steve Ebersole]

So I've run into problems trying to remove the dependency upon cglib for
hibernate.  The hibernate component-info has historically, for whatever
reason, to define a dependency on asm (this was never a direct
dependency).  So I defined the component-info for hibernate-3.2.0.cr2
as:

   component id=hibernate
  licenseType=lgpl
  version=3.2.0.CR2
  projectHome=http://hibernate.org/;
  description=ultra-high performance object/relational
persistence

  artifact id=hibernate3.jar/

  import componentref=antlr
  compatible version=2.7.5H3/
  compatible version=2.7.6rc1/
  compatible version=2.7.6.ga/
  /import

  export
 include input=hibernate3.jar/
   /export

   /component

However, that now leads to failures when trying to build because asm is
no longer defined as a dependency.  Seems logical that cglib really
should be pulling in this dependency, since it is cglib which has this
as a direct dependency.

So it depends on whether cglib-2.1.2jboss (the current dep level for
JBoss AS) has been used in a previous build.  Ideally, we should modify
that cglib component-info to pull in this dependency.  If that has been
used in a previously AS release, then I guess we'll need to put this asm
dependency at the AS level.

-Original Message-
From: [EMAIL PROTECTED]
[mailto:[EMAIL PROTECTED] On Behalf Of
Steve Ebersole
Sent: Monday, May 08, 2006 8:40 AM
To: Dimitris Andreadis; Emmanuel Bernard; Scott M Stark; Bill Burke
Cc: jboss-development@lists.sourceforge.net
Subject: [JBoss-dev] RE: Hibernate, HA, ,HEM, antlr versions in
Branch_4_0

No objections.  I just have not switched over hibernate-int yet because
of the outstanding question of cglib/javassist.  They are basically
unrelated, but just wanted to get that committed all together.

I'll commit that stuff this morning.

-Original Message-
From: Dimitris Andreadis 
Sent: Monday, May 08, 2006 3:49 AM
To: Emmanuel Bernard; Steve Ebersole; Scott M Stark; Bill Burke
Cc: jboss-development@lists.sourceforge.net
Subject: Hibernate, HA, ,HEM, antlr versions in Branch_4_0

In Branch_4_0 we have:

componentref name=hibernate version=3.2.0.CR1/
componentref name=hibernate-annotations version=3.1beta9/
componentref name=hibernate-entitymanager version=3.1beta7/
componentref name=antlr version=2.7.6rc1/

We agree we want those to become:

H - 3.2.0.CR2
HA - 3.2.0.CR1
HEM - 3.2.0.CR1
Antlr - 2.7.6.ga

Objections?


---
Using Tomcat but need to do more? Need to support web services,
security?
Get stuff done quickly with pre-integrated technology to make your job
easier
Download IBM WebSphere Application Server v.1.0.1 based on Apache
Geronimo
http://sel.as-us.falkag.net/sel?cmd=kkid0709bid3057dat1642
___
JBoss-Development mailing list
JBoss-Development@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/jboss-development


---
Using Tomcat but need to do more? Need to support web services, security?
Get stuff done quickly with pre-integrated technology to make your job easier
Download IBM WebSphere Application Server v.1.0.1 based on Apache Geronimo
http://sel.as-us.falkag.net/sel?cmd=lnkkid0709bid3057dat1642
___
JBoss-Development mailing list
JBoss-Development@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/jboss-development

RE: [JBoss-dev] RE: Hibernate, HA, ,HEM, antlr versions in Branch_4_0

[Steve Ebersole]

Agreed.  However, has cglib-2.1.2jboss been used in a previous release
as of yet?

If so, perhaps another option is a new copy of cglib-2.1.2jboss -
cglib-2.1.2jboss+asm?


-Original Message-
From: Scott M Stark 
Sent: Monday, May 08, 2006 10:18 AM
To: Steve Ebersole; 'jboss-development@lists.sourceforge.net'; Dimitris
Andreadis; 'Emmanuel Bernard'; Bill Burke
Subject: RE: [JBoss-dev] RE: Hibernate, HA, ,HEM, antlr versions in
Branch_4_0

There is no direct use of asm in jbossas so the dependency should be
moved to the cglib components. 

 -Original Message-
 From: Steve Ebersole 
 Sent: Monday, May 08, 2006 8:13 AM
 To: jboss-development@lists.sourceforge.net; Dimitris 
 Andreadis; Emmanuel Bernard; Scott M Stark; Bill Burke
 Subject: RE: [JBoss-dev] RE: Hibernate, HA, ,HEM, antlr 
 versions in Branch_4_0
 
 So I've run into problems trying to remove the dependency 
 upon cglib for hibernate.  The hibernate component-info has 
 historically, for whatever reason, to define a dependency on 
 asm (this was never a direct dependency).  So I defined the 
 component-info for hibernate-3.2.0.cr2 as:
 
component id=hibernate
   licenseType=lgpl
   version=3.2.0.CR2
   projectHome=http://hibernate.org/;
   description=ultra-high performance 
 object/relational persistence
 
   artifact id=hibernate3.jar/
 
   import componentref=antlr
   compatible version=2.7.5H3/
   compatible version=2.7.6rc1/
   compatible version=2.7.6.ga/
   /import
 
   export
  include input=hibernate3.jar/
/export
 
/component
 
 However, that now leads to failures when trying to build 
 because asm is no longer defined as a dependency.  Seems 
 logical that cglib really should be pulling in this 
 dependency, since it is cglib which has this as a direct dependency.
 
 So it depends on whether cglib-2.1.2jboss (the current dep 
 level for JBoss AS) has been used in a previous build.  
 Ideally, we should modify that cglib component-info to pull 
 in this dependency.  If that has been used in a previously AS 
 release, then I guess we'll need to put this asm dependency 
 at the AS level.


---
Using Tomcat but need to do more? Need to support web services, security?
Get stuff done quickly with pre-integrated technology to make your job easier
Download IBM WebSphere Application Server v.1.0.1 based on Apache Geronimo
http://sel.as-us.falkag.net/sel?cmd=lnkkid0709bid3057dat1642
___
JBoss-Development mailing list
JBoss-Development@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/jboss-development

RE: [JBoss-dev] RE: Hibernate, HA, ,HEM, antlr versions in Branch_4_0

[Steve Ebersole]

I found I also needed to modify build/build-distr.xml (target
_module-hibernate-int-most tries to explicitly copy cglib and asm jars).
Would that be expected?

-Original Message-
From: Scott M Stark 
Sent: Monday, May 08, 2006 10:38 AM
To: Steve Ebersole; 'jboss-development@lists.sourceforge.net'; Dimitris
Andreadis; 'Emmanuel Bernard'; Bill Burke
Subject: RE: [JBoss-dev] RE: Hibernate, HA, ,HEM, antlr versions in
Branch_4_0

Yes it was used. Its use should't matter though as long as the
cglib-2.1.2jboss declares a depdendency consistent with what was in the
release. I'll test this with an existing release.

Also, cglib has been bumped up to 2.1.3 in the
jbossas/build-thirdparty.xml anyway so just focus on that for the
current release.

 -Original Message-
 From: Steve Ebersole 
 Sent: Monday, May 08, 2006 8:25 AM
 To: Scott M Stark; 'jboss-development@lists.sourceforge.net'; 
 Dimitris Andreadis; 'Emmanuel Bernard'; Bill Burke
 Subject: RE: [JBoss-dev] RE: Hibernate, HA, ,HEM, antlr 
 versions in Branch_4_0
 
 Agreed.  However, has cglib-2.1.2jboss been used in a 
 previous release as of yet?
 
 If so, perhaps another option is a new copy of 
 cglib-2.1.2jboss - cglib-2.1.2jboss+asm?
 
 


---
Using Tomcat but need to do more? Need to support web services, security?
Get stuff done quickly with pre-integrated technology to make your job easier
Download IBM WebSphere Application Server v.1.0.1 based on Apache Geronimo
http://sel.as-us.falkag.net/sel?cmd=lnkkid0709bid3057dat1642
___
JBoss-Development mailing list
JBoss-Development@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/jboss-development

RE: [JBoss-dev] RE: Hibernate, HA, ,HEM, antlr versions in Branch_4_0

[Steve Ebersole]

So where should that move to now?

-Original Message-
From: [EMAIL PROTECTED]
[mailto:[EMAIL PROTECTED] On Behalf Of Ruel
Loehr
Sent: Monday, May 08, 2006 11:15 AM
To: jboss-development@lists.sourceforge.net; Scott M Stark; Dimitris
Andreadis; Emmanuel Bernard; Bill Burke
Subject: RE: [JBoss-dev] RE: Hibernate, HA, ,HEM, antlr versions in
Branch_4_0

Yes.   Hibernate-int is the entity that has been managing where those
jars should be placed in the server dist.

Ruel Loehr
JBoss QA
 
-
512-342-7840 ext 2011
Yahoo: ruelloehr
Skype: ruelloehr
AOL: dokoruel

-Original Message-
From: [EMAIL PROTECTED]
[mailto:[EMAIL PROTECTED] On Behalf Of
Steve Ebersole
Sent: Monday, May 08, 2006 11:12 AM
To: Scott M Stark; jboss-development@lists.sourceforge.net; Dimitris
Andreadis; Emmanuel Bernard; Bill Burke
Subject: RE: [JBoss-dev] RE: Hibernate, HA, ,HEM, antlr versions in
Branch_4_0

I found I also needed to modify build/build-distr.xml (target
_module-hibernate-int-most tries to explicitly copy cglib and asm jars).
Would that be expected?

-Original Message-
From: Scott M Stark 
Sent: Monday, May 08, 2006 10:38 AM
To: Steve Ebersole; 'jboss-development@lists.sourceforge.net'; Dimitris
Andreadis; 'Emmanuel Bernard'; Bill Burke
Subject: RE: [JBoss-dev] RE: Hibernate, HA, ,HEM, antlr versions in
Branch_4_0

Yes it was used. Its use should't matter though as long as the
cglib-2.1.2jboss declares a depdendency consistent with what was in the
release. I'll test this with an existing release.

Also, cglib has been bumped up to 2.1.3 in the
jbossas/build-thirdparty.xml anyway so just focus on that for the
current release.

 -Original Message-
 From: Steve Ebersole 
 Sent: Monday, May 08, 2006 8:25 AM
 To: Scott M Stark; 'jboss-development@lists.sourceforge.net'; 
 Dimitris Andreadis; 'Emmanuel Bernard'; Bill Burke
 Subject: RE: [JBoss-dev] RE: Hibernate, HA, ,HEM, antlr 
 versions in Branch_4_0
 
 Agreed.  However, has cglib-2.1.2jboss been used in a 
 previous release as of yet?
 
 If so, perhaps another option is a new copy of 
 cglib-2.1.2jboss - cglib-2.1.2jboss+asm?
 
 


---
Using Tomcat but need to do more? Need to support web services,
security?
Get stuff done quickly with pre-integrated technology to make your job
easier
Download IBM WebSphere Application Server v.1.0.1 based on Apache
Geronimo
http://sel.as-us.falkag.net/sel?cmd=kkid0709bid3057dat1642
___
JBoss-Development mailing list
JBoss-Development@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/jboss-development


---
Using Tomcat but need to do more? Need to support web services,
security?
Get stuff done quickly with pre-integrated technology to make your job
easier
Download IBM WebSphere Application Server v.1.0.1 based on Apache
Geronimo
http://sel.as-us.falkag.net/sel?cmd=kkid0709bid3057dat1642
___
JBoss-Development mailing list
JBoss-Development@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/jboss-development


---
Using Tomcat but need to do more? Need to support web services, security?
Get stuff done quickly with pre-integrated technology to make your job easier
Download IBM WebSphere Application Server v.1.0.1 based on Apache Geronimo
http://sel.as-us.falkag.net/sel?cmd=lnkkid0709bid3057dat1642
___
JBoss-Development mailing list
JBoss-Development@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/jboss-development

RE: [JBoss-dev] RE: Hibernate, HA, ,HEM, antlr versions in Branch_4_0

[Steve Ebersole]

I understand that.  What I am asking is how should cglib and asm jars be
moved into the dist directories now?  



  target name=_module-hibernate-int-most
property name=_module.name value=hibernate-int
override=true/
property name=_module.output override=true
value=${project.root}/${_module.name}/output/

mkdir dir=${install.all.lib}/

!-- The hibernate-int module output --
copy todir=${install.all.lib} filtering=no
  fileset dir=${_module.output}/lib includes=*.jar /
/copy

!-- The hibernate jar --
copy todir=${install.all.lib} filtering=no
  fileset dir=${hibernate.lib} includes=*.jar /
/copy

!-- ASM jars (cglib dependency)
copy todir=${install.all.lib} filtering=no
  fileset dir=${asm.asm.lib} includes=*.jar /
/copy
--

!-- ANTLR jar --
copy todir=${install.all.lib} filtering=no
  fileset dir=${antlr.antlr.lib} includes=*.jar /
/copy

!-- CGLIB jar
copy todir=${install.all.lib} filtering=no
  fileset dir=${cglib.lib} includes=*.jar/
/copy
--

!-- Commons collections jar --
copy todir=${install.all.lib} filtering=no
  fileset dir=${apache.collections.lib} includes=*.jar/
/copy

  /target


Where should those 2 copies happen now?  Should I just leave it there (I
commented it out because it fails unless cglib and asm are dependencies
of the hibernate component).


-Original Message-
From: Scott M Stark 
Sent: Monday, May 08, 2006 11:53 AM
To: Steve Ebersole; 'jboss-development@lists.sourceforge.net'; Dimitris
Andreadis; 'Emmanuel Bernard'; Bill Burke
Subject: RE: [JBoss-dev] RE: Hibernate, HA, ,HEM, antlr versions in
Branch_4_0

The _module-hibernate-int-most still has to handle the base hibernate
jars needed for the har deployer. Config specific to the javaee5
jpa/ejb3 needs to be in the setup-ejb3-dist target that is only run when
building with java5.

 -Original Message-
 From: Steve Ebersole 
 Sent: Monday, May 08, 2006 9:37 AM
 To: jboss-development@lists.sourceforge.net; Scott M Stark; 
 Dimitris Andreadis; Emmanuel Bernard; Bill Burke
 Subject: RE: [JBoss-dev] RE: Hibernate, HA, ,HEM, antlr 
 versions in Branch_4_0
 
 So where should that move to now?
 
 -Original Message-
 From: [EMAIL PROTECTED] 
 [mailto:[EMAIL PROTECTED] On 
 Behalf Of Ruel Loehr
 Sent: Monday, May 08, 2006 11:15 AM
 To: jboss-development@lists.sourceforge.net; Scott M Stark; 
 Dimitris Andreadis; Emmanuel Bernard; Bill Burke
 Subject: RE: [JBoss-dev] RE: Hibernate, HA, ,HEM, antlr 
 versions in Branch_4_0
 
 Yes.   Hibernate-int is the entity that has been managing where those
 jars should be placed in the server dist.
 
 Ruel Loehr
 JBoss QA
  
 -
 512-342-7840 ext 2011
 Yahoo: ruelloehr
 Skype: ruelloehr
 AOL: dokoruel


---
Using Tomcat but need to do more? Need to support web services, security?
Get stuff done quickly with pre-integrated technology to make your job easier
Download IBM WebSphere Application Server v.1.0.1 based on Apache Geronimo
http://sel.as-us.falkag.net/sel?cmd=lnkkid0709bid3057dat1642
___
JBoss-Development mailing list
JBoss-Development@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/jboss-development

RE: [JBoss-dev] RE: Hibernate, HA, ,HEM, antlr versions in Branch_4_0

[Steve Ebersole]

But that's what I am trying to change ;)  I am trying to make the
bundled Hibernate use the Javassist bytecode provider stuff.

But, if I simply remove the Hibernate - cglib/asm dependency (from the
hibernate component-info), then the AS build fails.

-Original Message-
From: Scott M Stark 
Sent: Monday, May 08, 2006 12:32 PM
To: Steve Ebersole; 'jboss-development@lists.sourceforge.net'; Dimitris
Andreadis; 'Emmanuel Bernard'; Bill Burke
Subject: RE: [JBoss-dev] RE: Hibernate, HA, ,HEM, antlr versions in
Branch_4_0

They should remain in the _module-hibernate-int-most if hibernate as
integrated into jbossas has these dependencies. 

 -Original Message-
 From: Steve Ebersole 
 Sent: Monday, May 08, 2006 10:23 AM
 To: Scott M Stark; 'jboss-development@lists.sourceforge.net'; 
 Dimitris Andreadis; 'Emmanuel Bernard'; Bill Burke
 Subject: RE: [JBoss-dev] RE: Hibernate, HA, ,HEM, antlr 
 versions in Branch_4_0
 
 I understand that.  What I am asking is how should cglib and 
 asm jars be moved into the dist directories now?  
 
 
 
   target name=_module-hibernate-int-most
 property name=_module.name value=hibernate-int 
 override=true/
 property name=_module.output override=true
 value=${project.root}/${_module.name}/output/
 
 mkdir dir=${install.all.lib}/
 
 !-- The hibernate-int module output --
 copy todir=${install.all.lib} filtering=no
   fileset dir=${_module.output}/lib includes=*.jar /
 /copy
 
 !-- The hibernate jar --
 copy todir=${install.all.lib} filtering=no
   fileset dir=${hibernate.lib} includes=*.jar /
 /copy
 
 !-- ASM jars (cglib dependency)
 copy todir=${install.all.lib} filtering=no
   fileset dir=${asm.asm.lib} includes=*.jar /
 /copy
 --
 
 !-- ANTLR jar --
 copy todir=${install.all.lib} filtering=no
   fileset dir=${antlr.antlr.lib} includes=*.jar /
 /copy
 
 !-- CGLIB jar
 copy todir=${install.all.lib} filtering=no
   fileset dir=${cglib.lib} includes=*.jar/
 /copy
 --
 
 !-- Commons collections jar --
 copy todir=${install.all.lib} filtering=no
   fileset dir=${apache.collections.lib} includes=*.jar/
 /copy
 
   /target
 
 
 Where should those 2 copies happen now?  Should I just leave 
 it there (I commented it out because it fails unless cglib 
 and asm are dependencies of the hibernate component).


---
Using Tomcat but need to do more? Need to support web services, security?
Get stuff done quickly with pre-integrated technology to make your job easier
Download IBM WebSphere Application Server v.1.0.1 based on Apache Geronimo
http://sel.as-us.falkag.net/sel?cmd=lnkkid0709bid3057dat1642
___
JBoss-Development mailing list
JBoss-Development@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/jboss-development

RE: [JBoss-dev] RE: Hibernate, HA, ,HEM, antlr versions in Branch_4_0

[Steve Ebersole]

Hmmm.  This time it built fine for me in that it did not fail; not
sure what was going on before.

However, I get strange results:
- server/default/lib contains cglib, although it is missing asm
- server/all/lib contains neither

Just kicked off a clean build, so lets see if that fixes it...

-Original Message-
From: Scott M Stark 
Sent: Monday, May 08, 2006 1:02 PM
To: Steve Ebersole; 'jboss-development@lists.sourceforge.net'; Dimitris
Andreadis; 'Emmanuel Bernard'; Bill Burke
Subject: RE: [JBoss-dev] RE: Hibernate, HA, ,HEM, antlr versions in
Branch_4_0

So that produces the question: where is the build failing? If removing
the copy of the libs from dist, removing the build-thirdparty.xml refs
to the unused cglib/asm jars results in a build failure, we must have
some unspecified dependency on these. 

 -Original Message-
 From: Steve Ebersole 
 Sent: Monday, May 08, 2006 10:56 AM
 To: Scott M Stark; 'jboss-development@lists.sourceforge.net'; 
 Dimitris Andreadis; 'Emmanuel Bernard'; Bill Burke
 Subject: RE: [JBoss-dev] RE: Hibernate, HA, ,HEM, antlr 
 versions in Branch_4_0
 
 But that's what I am trying to change ;)  I am trying to make 
 the bundled Hibernate use the Javassist bytecode provider stuff.
 
 But, if I simply remove the Hibernate - cglib/asm dependency 
 (from the hibernate component-info), then the AS build fails.
 
 -Original Message-
 From: Scott M Stark
 Sent: Monday, May 08, 2006 12:32 PM
 To: Steve Ebersole; 
 'jboss-development@lists.sourceforge.net'; Dimitris 
 Andreadis; 'Emmanuel Bernard'; Bill Burke
 Subject: RE: [JBoss-dev] RE: Hibernate, HA, ,HEM, antlr 
 versions in Branch_4_0
 
 They should remain in the _module-hibernate-int-most if 
 hibernate as integrated into jbossas has these dependencies. 


---
Using Tomcat but need to do more? Need to support web services, security?
Get stuff done quickly with pre-integrated technology to make your job easier
Download IBM WebSphere Application Server v.1.0.1 based on Apache Geronimo
http://sel.as-us.falkag.net/sel?cmd=lnkkid0709bid3057dat1642
___
JBoss-Development mailing list
JBoss-Development@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/jboss-development

[JBoss-dev] bumping Hibernate Antlr dependency to 2.7.6

[Steve Ebersole]

Are there any 4.0 components using Antlr other than Hibernate?

I want to bump the Antlr version from 2.7.6rc1 to 2.7.6.  Will that
impact anyone?


---
Using Tomcat but need to do more? Need to support web services, security?
Get stuff done quickly with pre-integrated technology to make your job easier
Download IBM WebSphere Application Server v.1.0.1 based on Apache Geronimo
http://sel.as-us.falkag.net/sel?cmd=lnkkid0709bid3057dat1642
___
JBoss-Development mailing list
JBoss-Development@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/jboss-development

RE: [JBoss-dev] bumping Hibernate Antlr dependency to 2.7.6

[Steve Ebersole]

Both their generated parser classes and AST tree nodes extend from some
antlr supplied base classes.
 
-Original Message-
From: [EMAIL PROTECTED]
[mailto:[EMAIL PROTECTED] On Behalf Of
Scott M Stark
Sent: Friday, May 05, 2006 12:31 PM
To: jboss-development@lists.sourceforge.net
Subject: RE: [JBoss-dev] bumping Hibernate Antlr dependency to 2.7.6

I think most other components use javacc which produces no runtime
requirements. What aspects of antlr are required at runtime? Perhaps
they are not bundling the lexer/parser boilerplate classes with the code
specific to the grammar?

-Original Message-
From: [EMAIL PROTECTED]
[mailto:[EMAIL PROTECTED] On Behalf Of Ruel
Loehr
Sent: Friday, May 05, 2006 9:49 AM
To: jboss-development@lists.sourceforge.net
Subject: RE: [JBoss-dev] bumping Hibernate Antlr dependency to 2.7.6

Looks like no other components currently use it.

[EMAIL PROTECTED] thirdparty]$ find . -name 'component-info.xml' | grep
'antlr'
./antlr/component-info.xml

Ruel Loehr
JBoss QA
 
-
512-342-7840 ext 2011
Yahoo: ruelloehr
Skype: ruelloehr
AOL: dokoruel

-Original Message-
From: [EMAIL PROTECTED]
[mailto:[EMAIL PROTECTED] On Behalf Of
Steve Ebersole
Sent: Friday, May 05, 2006 11:43 AM
To: jboss-development@lists.sourceforge.net
Subject: [JBoss-dev] bumping Hibernate Antlr dependency to 2.7.6

Are there any 4.0 components using Antlr other than Hibernate?

I want to bump the Antlr version from 2.7.6rc1 to 2.7.6.  Will that
impact anyone?


---
Using Tomcat but need to do more? Need to support web services,
security?
Get stuff done quickly with pre-integrated technology to make your job
easier
Download IBM WebSphere Application Server v.1.0.1 based on Apache
Geronimo
http://sel.as-us.falkag.net/sel?cmd=kkid0709bid3057dat1642
___
JBoss-Development mailing list
JBoss-Development@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/jboss-development


---
Using Tomcat but need to do more? Need to support web services,
security?
Get stuff done quickly with pre-integrated technology to make your job
easier
Download IBM WebSphere Application Server v.1.0.1 based on Apache
Geronimo
http://sel.as-us.falkag.net/sel?cmd=kkid0709bid3057dat1642
___
JBoss-Development mailing list
JBoss-Development@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/jboss-development


---
Using Tomcat but need to do more? Need to support web services,
security?
Get stuff done quickly with pre-integrated technology to make your job
easier
Download IBM WebSphere Application Server v.1.0.1 based on Apache
Geronimo
http://sel.as-us.falkag.net/sel?cmd=kkid0709bid3057dat1642
___
JBoss-Development mailing list
JBoss-Development@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/jboss-development


---
Using Tomcat but need to do more? Need to support web services, security?
Get stuff done quickly with pre-integrated technology to make your job easier
Download IBM WebSphere Application Server v.1.0.1 based on Apache Geronimo
http://sel.as-us.falkag.net/sel?cmd=lnkkid0709bid3057dat1642
___
JBoss-Development mailing list
JBoss-Development@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/jboss-development

RE: [JBoss-dev] Upgrading cglib dependency to version 2.1.3 in 4.0branch

[Steve Ebersole]

Quick question about this actually.

3.2.0.CR2 exists in the respository, specifying cglib, as a dependency
and has already been used in one of the 4.0.3 CR releases, correct?

So what is the policy on changing the component def of a component when
that particular release has already been used in a AS release?  Meaning,
is it kosher for me to simply change hibernate/3.2.0.CR2/component.xml
to reference javassist instead of cglib at this point?  Or do I copy
hibernate/3.2.0.CR2 into a new hibernate/3.2.0.CR3 (same stuff as
before) and modify that component.xml to reference javassist?

-Original Message-
From: [EMAIL PROTECTED]
[mailto:[EMAIL PROTECTED] On Behalf Of
Steve Ebersole
Sent: Tuesday, April 25, 2006 1:29 PM
To: jboss-development@lists.sourceforge.net
Subject: RE: [JBoss-dev] Upgrading cglib dependency to version 2.1.3 in
4.0branch

Based on previous discussions, we actually plan on making Javassist the
utilized provider within JBoss AS.

http://jira.jboss.com/jira/browse/HIBERNATE-34

I was unable to assign this to a particular release, however it should
get done prior to 4.0.4 goes GA.

-Original Message-
From: [EMAIL PROTECTED]
[mailto:[EMAIL PROTECTED] On Behalf Of
Adrian Brock
Sent: Tuesday, April 25, 2006 9:59 AM
To: jboss-development@lists.sourceforge.net
Subject: Re: [JBoss-dev] Upgrading cglib dependency to version 2.1.3 in
4.0branch

The Hibernate team should decide this.
They are its biggest consumers, they know what they have
tested against.

On Tue, 2006-04-25 at 09:40 -0500, Ruel Loehr wrote:
 This has been bounced around a few times without resolution.  I'm
 going to increment the version cglib unless someone speaks up with a
 compelling reason not to.
 
  
 
  
 
 http://jira.jboss.com/jira/browse/JBAS-3061
 
  
 
 Ruel Loehr
 
 JBoss QA
 
  
 
  
 
 
-- 

Adrian Brock
Chief Scientist
JBoss Inc.




---
Using Tomcat but need to do more? Need to support web services,
security?
Get stuff done quickly with pre-integrated technology to make your job
easier
Download IBM WebSphere Application Server v.1.0.1 based on Apache
Geronimo
http://sel.as-us.falkag.net/sel?cmd=kkid0709bid3057dat1642
___
JBoss-Development mailing list
JBoss-Development@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/jboss-development


---
Using Tomcat but need to do more? Need to support web services,
security?
Get stuff done quickly with pre-integrated technology to make your job
easier
Download IBM WebSphere Application Server v.1.0.1 based on Apache
Geronimo
http://sel.as-us.falkag.net/sel?cmd=kkid0709bid3057dat1642
___
JBoss-Development mailing list
JBoss-Development@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/jboss-development


---
Using Tomcat but need to do more? Need to support web services, security?
Get stuff done quickly with pre-integrated technology to make your job easier
Download IBM WebSphere Application Server v.1.0.1 based on Apache Geronimo
http://sel.as-us.falkag.net/sel?cmd=lnkkid0709bid3057dat1642
___
JBoss-Development mailing list
JBoss-Development@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/jboss-development

RE: [JBoss-dev] Upgrading cglib dependency to version 2.1.3 in 4.0branch

[Steve Ebersole]

Right, that's the other part to this.  I'd need to change the
hibernate-int module to depend on this new hibernate release.  Then it
is a matter of specifying to use javassist over cglib as a config
parameter.  The interesting thing here, though, is that this setting is
global to a classloader (scoped by a static variable).  Should this be
something we make a JBoss config option?  Otherwise, I could just set a
system property when the MBean first starts up and hope that no one has
yet loaded that particular class.

Bill/Emmanuel, will need to do the similiar for the ejb3 module.

BTW, anyone have intellij projects files for 4x and head they would
share?

-Original Message-
From: [EMAIL PROTECTED]
[mailto:[EMAIL PROTECTED] On Behalf Of
Scott M Stark
Sent: Wednesday, April 26, 2006 10:08 AM
To: jboss-development@lists.sourceforge.net
Subject: RE: [JBoss-dev] Upgrading cglib dependency to version 2.1.3 in
4.0branch

The binaries in the repository have to be treated as releases. As soon a
version is out there you have to consider that its being used and that
any change to it will break existing usage. If 3.2.0.CR2 is just
repacked with different configurations/dependencies I would call it
3.2.0.CR2-jboss or perhaps 3.2.0.CR2-javassist(qualifiers to the base
are allowed). How does the javassist reference magically configure
hibernate to use the javassist bytecode generation by default? Based on
Steve's previous comments this still requires additional configuration
in jbossas, and so a 3.2.0.CR2-javassist or 3.2.0.CR3 that expresses a
dependency on javassist in of itself seems broken because simply pulling
this version into jbossas will not work?

I linked the JBAS-3101 issue to the HIBERNATE-34 issue to tie it into
the 4.0.4.GA release.

 -Original Message-
 From: [EMAIL PROTECTED] 
 [mailto:[EMAIL PROTECTED] On 
 Behalf Of Ruel Loehr
 Sent: Wednesday, April 26, 2006 7:48 AM
 To: jboss-development@lists.sourceforge.net
 Subject: RE: [JBoss-dev] Upgrading cglib dependency to 
 version 2.1.3 in 4.0branch
 
 You would want to create a new version.The older version 
 which uses
 cglib should remain for historic reasons.  
 
 For example if 4.0.3.SP1 uses a hibernate version that is 
 dependent upon cglib, we may want to reproduce that build 
 sometime in the future (doing a service pack). 
 
 Modifying the component-info.xml of 3.2.0.CR2 if it has 
 previously been included in a release will break the repeatability.
 
 Ruel Loehr
 JBoss QA
  
 -Original Message-
 From: [EMAIL PROTECTED]
 [mailto:[EMAIL PROTECTED] On 
 Behalf Of Steve Ebersole
 Sent: Wednesday, April 26, 2006 9:31 AM
 To: jboss-development@lists.sourceforge.net
 Subject: RE: [JBoss-dev] Upgrading cglib dependency to 
 version 2.1.3 in 4.0branch
 
 Quick question about this actually.
 
 3.2.0.CR2 exists in the respository, specifying cglib, as a 
 dependency and has already been used in one of the 4.0.3 CR 
 releases, correct?
 
 So what is the policy on changing the component def of a 
 component when that particular release has already been used 
 in a AS release?  Meaning, is it kosher for me to simply 
 change hibernate/3.2.0.CR2/component.xml to reference 
 javassist instead of cglib at this point?  Or do I copy
 hibernate/3.2.0.CR2 into a new hibernate/3.2.0.CR3 (same stuff as
 before) and modify that component.xml to reference javassist?
 
 -Original Message-
 From: [EMAIL PROTECTED]
 [mailto:[EMAIL PROTECTED] On 
 Behalf Of Steve Ebersole
 Sent: Tuesday, April 25, 2006 1:29 PM
 To: jboss-development@lists.sourceforge.net
 Subject: RE: [JBoss-dev] Upgrading cglib dependency to 
 version 2.1.3 in 4.0branch
 
 Based on previous discussions, we actually plan on making 
 Javassist the utilized provider within JBoss AS.
 
 http://jira.jboss.com/jira/browse/HIBERNATE-34
 
 I was unable to assign this to a particular release, however 
 it should get done prior to 4.0.4 goes GA.


---
Using Tomcat but need to do more? Need to support web services,
security?
Get stuff done quickly with pre-integrated technology to make your job
easier
Download IBM WebSphere Application Server v.1.0.1 based on Apache
Geronimo
http://sel.as-us.falkag.net/sel?cmd=kkid0709bid3057dat1642
___
JBoss-Development mailing list
JBoss-Development@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/jboss-development


---
Using Tomcat but need to do more? Need to support web services, security?
Get stuff done quickly with pre-integrated technology to make your job easier
Download IBM WebSphere Application Server v.1.0.1 based on Apache Geronimo
http://sel.as-us.falkag.net/sel?cmd=lnkkid0709bid3057dat1642
___
JBoss-Development mailing list
JBoss-Development@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/jboss

RE: [JBoss-dev] Upgrading cglib dependency to version 2.1.3 in 4.0branch

[Steve Ebersole]

Based on previous discussions, we actually plan on making Javassist the
utilized provider within JBoss AS.

http://jira.jboss.com/jira/browse/HIBERNATE-34

I was unable to assign this to a particular release, however it should
get done prior to 4.0.4 goes GA.

-Original Message-
From: [EMAIL PROTECTED]
[mailto:[EMAIL PROTECTED] On Behalf Of
Adrian Brock
Sent: Tuesday, April 25, 2006 9:59 AM
To: jboss-development@lists.sourceforge.net
Subject: Re: [JBoss-dev] Upgrading cglib dependency to version 2.1.3 in
4.0branch

The Hibernate team should decide this.
They are its biggest consumers, they know what they have
tested against.

On Tue, 2006-04-25 at 09:40 -0500, Ruel Loehr wrote:
 This has been bounced around a few times without resolution.  I'm
 going to increment the version cglib unless someone speaks up with a
 compelling reason not to.
 
  
 
  
 
 http://jira.jboss.com/jira/browse/JBAS-3061
 
  
 
 Ruel Loehr
 
 JBoss QA
 
  
 
  
 
 
-- 

Adrian Brock
Chief Scientist
JBoss Inc.




---
Using Tomcat but need to do more? Need to support web services,
security?
Get stuff done quickly with pre-integrated technology to make your job
easier
Download IBM WebSphere Application Server v.1.0.1 based on Apache
Geronimo
http://sel.as-us.falkag.net/sel?cmd=kkid0709bid3057dat1642
___
JBoss-Development mailing list
JBoss-Development@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/jboss-development


---
Using Tomcat but need to do more? Need to support web services, security?
Get stuff done quickly with pre-integrated technology to make your job easier
Download IBM WebSphere Application Server v.1.0.1 based on Apache Geronimo
http://sel.as-us.falkag.net/sel?cmd=lnkkid0709bid3057dat1642
___
JBoss-Development mailing list
JBoss-Development@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/jboss-development

RE: [JBoss-dev] Should 4.0.4 have cgilib in jbossall-client.jar

[Steve Ebersole]

I would guess that actually breaks regardless as the thing that gets
serialized in the two cases is completely different under the covers
between those two versions of hibernate because of the introduction of
the javassist capability.  If this situation is really a requirement, we
will probably need to add some serious deserialization logic to the
serializable-proxy.

As for needing a version of hibernate where javassist is the default
bytecode library, I don't get why.  For the hibernate-int code we could
handle that specifically in the MBean.  For the EJB3 case, we should be
able to do something similar.  I am very against changing this default
in Hibernate itself.

-Original Message-
From: [EMAIL PROTECTED]
[mailto:[EMAIL PROTECTED] On Behalf Of
Scott M Stark
Sent: Thursday, April 13, 2006 12:34 PM
To: jboss-development@lists.sourceforge.net
Subject: RE: [JBoss-dev] Should 4.0.4 have cgilib in jbossall-client.jar

In terms of backward compatibility, I suppose a jboss-4.0.3SP1 hosted
client of a 4.0.4.GA hosted hibernate component needs to have a cglib
based proxy?


 -Original Message-
 From: [EMAIL PROTECTED] 
 [mailto:[EMAIL PROTECTED] On 
 Behalf Of Scott M Stark
 Sent: Thursday, April 13, 2006 10:29 AM
 To: jboss-development@lists.sourceforge.net
 Subject: RE: [JBoss-dev] Should 4.0.4 have cgilib in 
 jbossall-client.jar
 
 So we need a hibernate version that has javassist set as the 
 default proxy factory/byte code manipulation framework. Can 
 we do this for the base release or does it need to be a jboss 
 specific release? A container issue for reducing the client 
 side dependencies to only javassist is:
 
 http://jira.jboss.com/jira/browse/JBAS-3101 
 
  -Original Message-
  From: [EMAIL PROTECTED]
  [mailto:[EMAIL PROTECTED] On Behalf Of 
  Max Rydahl Andersen
  Sent: Thursday, April 13, 2006 10:21 AM
  To: jboss-development@lists.sourceforge.net
  Subject: Re: [JBoss-dev] Should 4.0.4 have cgilib in 
  jbossall-client.jar
  
  On Thu, 13 Apr 2006 18:58:25 +0200, Scott M Stark 
  [EMAIL PROTECTED]
  wrote:
  
   cglib should not be the default proxy framework as of the 
 hibernate
   3.2 release. I thought this was the case. Propagation of multiple 
   libraries doing the same thing needs to be cleaned up.
  
  hibernate default is still cglib.
  
  but we can run on javaassist. just need to set a property.
  
  /max
  
  
   -Original Message-
   From: [EMAIL PROTECTED]
   [mailto:[EMAIL PROTECTED] On
  Behalf Of
   Bill Burke
   Sent: Thursday, April 13, 2006 9:53 AM
   To: jboss-development@lists.sourceforge.net
   Subject: Re: [JBoss-dev] Should 4.0.4 have cgilib in 
   jbossall-client.jar
  
   cglib should be in client as Hibernate needs them on 
 serialization.
  
   Jason T. Greene wrote:
jboss-head has cglib classes in the jbossall-client.jar,
  however,
jboss-4.0 does not, which one is correct?
   

Jason T. Greene
Developer - Web Services
JBoss Inc.

   
   
   
---
This SF.Net email is sponsored by xPML, a groundbreaking
  scripting
language that extends applications into web and mobile
   media. Attend
the live webcast and join the prime developer group
   breaking into this new coding territory!

 http://sel.as-us.falkag.net/sel?cmd=kkid0944bid$1720dat1642
___
JBoss-Development mailing list
JBoss-Development@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/jboss-development
   
  
   --
   Bill Burke
   Chief Architect
   JBoss Inc.
  
  
   ---
   This SF.Net email is sponsored by xPML, a groundbreaking 
 scripting 
   language that extends applications into web and mobile
  media. Attend
   the live webcast and join the prime developer group 
 breaking into 
   this new coding territory!
   http://sel.as-us.falkag.net/sel?cmd=lnkkid=110944bid=241720;
   dat=121642
   ___
   JBoss-Development mailing list
   JBoss-Development@lists.sourceforge.net
   https://lists.sourceforge.net/lists/listinfo/jboss-development
  
  
  
   ---
   This SF.Net email is sponsored by xPML, a groundbreaking 
 scripting 
   language that extends applications into web and mobile
  media. Attend
   the live webcast and join the prime developer group
  breaking into this
   new coding territory!
   http://sel.as-us.falkag.net/sel?cmd=lnkkid0944bid$1720dat1642
   ___
   JBoss-Development mailing list
   JBoss-Development@lists.sourceforge.net
   https://lists.sourceforge.net/lists/listinfo/jboss-development
  
  
  
  --
  --
  Max Rydahl Andersen
  callto://max.rydahl.andersen
  
  Hibernate
  [EMAIL PROTECTED]
  http://hibernate.org
  
  JBoss Inc
  

[JBoss-dev] RE: Toward JBoss v4.0.4.GA - Part 2 - Build/thirdparty Issues

[Steve Ebersole]

Hibernate will stay at a CR; it will not go final until the EBJ3 spec is 
final...

BTW, what is with Javassist being at the same exact version?  Is that just 
coincidence?


-Original Message-
From: Dimitris Andreadis 
Sent: Wednesday, April 05, 2006 5:33 AM
To: jboss-development
Cc: The Core
Subject: Toward JBoss v4.0.4.GA - Part 2 - Build/thirdparty Issues
Importance: High


Various Issues
--

- Breakage of jboss commons. Is this the right time, or should do for 4.0.5. 
Aren't we already overloaded? Who  How?

- Which thirdparty libs can be removed? So far I've noticed apache-wss4j  
apache-jaxme.

- JBoss.Net is not even included in the docs/examples now. Should it be removed 
from the 4.0.x module checkout?

- The following jboss lists are *NOT* final (GA). What will be updated for 
4.0.4.GA? Project leads speak!

  componentref name=hibernate version=3.2.0.CR1/
  componentref name=hibernate-annotations version=3.1beta9/
  componentref name=hibernate-entitymanager version=3.1beta7/
  componentref name=javassist version=3.2.0.CR1/ 
  componentref name=hibernate version=3.2.0.CR1/
  componentref name=hibernate-annotations version=3.1beta9/
  componentref name=hibernate-entitymanager version=3.1beta7/
  componentref name=jboss/jbossretro version=1.0.0.CR1/
  componentref name=jboss/jbossws version=1.0.0.CR6/
  componentref name=jboss/jbossws14 version=1.0.0.CR6/
  componentref name=jboss/jbossxb version=1.0.0.CR3/
  componentref name=jboss/serialization version=1.0.0.CR4/




--
xxx
Dimitris Andreadis
Core Developer
JBoss Europe SàRL
xxx


---
This SF.Net email is sponsored by xPML, a groundbreaking scripting language
that extends applications into web and mobile media. Attend the live webcast
and join the prime developer group breaking into this new coding territory!
http://sel.as-us.falkag.net/sel?cmd=lnkkid0944bid$1720dat1642
___
JBoss-Development mailing list
JBoss-Development@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/jboss-development

RE: [JBoss-dev] Unassigned for 4.0.4

[Steve Ebersole]

Just so it is perfectly clear:

Hibernate does not use its cache providers in any way, shape or form for
implementing the first level cache.  As Max mentioned, the first
level cache is really just a particular aspect of the role fulfilled by
the org.hibernate.engine.PersistenceContext implementation which
internally uses a series of maps.

Thus, no need to bundle ehcache at all unless a user wants to use that
as their second level cache.

-Original Message-
From: [EMAIL PROTECTED]
[mailto:[EMAIL PROTECTED] On Behalf Of
Scott Marlow
Sent: Tuesday, April 04, 2006 10:12 AM
To: jboss-development@lists.sourceforge.net
Subject: Re: [JBoss-dev] Unassigned for 4.0.4

On Tue, 2006-04-04 at 15:56 +0200, Max Rydahl Andersen wrote:
 On Tue, 04 Apr 2006 15:44:51 +0200, Scott Marlow  
 [EMAIL PROTECTED] wrote:
 
  Sounds good to me.  My next question is how do we tell Hibernate to
use
  JBoss Cache as the first level cache?
 
 *first* level cache ? Why would you ever want that ?
 
 You mean second level cache, right ?
I mean first level cache, which by default is using ehcache-1.1.jar
(jira JBAS-2868).  We don't include ehcache-1.1.jar with the 4.0.4 as
release which is why it cannot be resolved.  I would like to use jboss
cache instead as the first level cache but am not sure if Hibernate
allows that.





---
This SF.Net email is sponsored by xPML, a groundbreaking scripting
language
that extends applications into web and mobile media. Attend the live
webcast
and join the prime developer group breaking into this new coding
territory!
http://sel.as-us.falkag.net/sel?cmd=lnkkid=110944bid=241720dat=121642
___
JBoss-Development mailing list
JBoss-Development@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/jboss-development


---
This SF.Net email is sponsored by xPML, a groundbreaking scripting language
that extends applications into web and mobile media. Attend the live webcast
and join the prime developer group breaking into this new coding territory!
http://sel.as-us.falkag.net/sel?cmd=lnkkid0944bid$1720dat1642
___
JBoss-Development mailing list
JBoss-Development@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/jboss-development

RE: [JBoss-dev] 4.0.4

[Steve Ebersole]

Just to keep y'all up-to-date, I have one more piece of code to do
before I cut the Hibernate release for use with 4.0.4.  It'll be done
today...


-Original Message-
From: [EMAIL PROTECTED]
[mailto:[EMAIL PROTECTED] On Behalf Of
Scott M Stark
Sent: Tuesday, March 21, 2006 12:38 AM
To: jboss-development@lists.sourceforge.net
Subject: RE: [JBoss-dev] 4.0.4

Just do a 4.0.5 soon after than. I don't want to push the 4.0.4.GA as
Dimitris said people have been waiting on it for a while.

-Original Message-
From: [EMAIL PROTECTED]
[mailto:[EMAIL PROTECTED] On Behalf Of Bill
Burke
Sent: Monday, March 20, 2006 6:54 PM
To: jboss-development@lists.sourceforge.net
Subject: Re: [JBoss-dev] 4.0.4

It would be cool if we could push GA a bit further after CR2.  I would 
like to do a big push for EJB3 final draft(and my book) compliance with 
4.0.4 and need more than 2 weeks as I'm on vacation for 10 days in
between.

Scott M Stark wrote:
 Ok. We want the 4.0.4.CR2 out this week and the GA two weeks latter.
 
 
-Original Message-
From: [EMAIL PROTECTED] 
[mailto:[EMAIL PROTECTED] On 
Behalf Of Steve Ebersole
Sent: Monday, March 20, 2006 2:17 PM
To: jboss-development@lists.sourceforge.net
Subject: RE: [JBoss-dev] 4.0.4

So provided we do not cause issues with portal, I say we go 
with a 3.2 final.  Specific reasons:
(1) Less issues with the version differences between AS and EJB3
(2) JBossCache optimistic locking support (only in 3.2)
(3) Javassist support (only in 3.2)
(4) Some performance enhancements relating to aggressive 
connection releasing on JBoss (although this is in 3.1.3 also).

The only other real difference between 3.1.3 and 3.2 is the 
non-transactional stuff.

The installer/build option seems a bit late in the game 
considering a release next week (#1).
 
 
 
 ---
 This SF.Net email is sponsored by xPML, a groundbreaking scripting
language
 that extends applications into web and mobile media. Attend the live
webcast
 and join the prime developer group breaking into this new coding
territory!
 http://sel.as-us.falkag.net/sel?cmd=kkid0944bid$1720dat1642
 ___
 JBoss-Development mailing list
 JBoss-Development@lists.sourceforge.net
 https://lists.sourceforge.net/lists/listinfo/jboss-development
 

-- 
Bill Burke
Chief Architect
JBoss Inc.


---
This SF.Net email is sponsored by xPML, a groundbreaking scripting
language
that extends applications into web and mobile media. Attend the live
webcast
and join the prime developer group breaking into this new coding
territory!
http://sel.as-us.falkag.net/sel?cmd=lnkkid=110944bid=241720dat=121642
___
JBoss-Development mailing list
JBoss-Development@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/jboss-development


---
This SF.Net email is sponsored by xPML, a groundbreaking scripting
language
that extends applications into web and mobile media. Attend the live
webcast
and join the prime developer group breaking into this new coding
territory!
http://sel.as-us.falkag.net/sel?cmd=kkid0944bid$1720dat1642
___
JBoss-Development mailing list
JBoss-Development@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/jboss-development


---
This SF.Net email is sponsored by xPML, a groundbreaking scripting language
that extends applications into web and mobile media. Attend the live webcast
and join the prime developer group breaking into this new coding territory!
http://sel.as-us.falkag.net/sel?cmd=lnkkid0944bid$1720dat1642
___
JBoss-Development mailing list
JBoss-Development@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/jboss-development

[JBoss-dev] 4.0.4

[Steve Ebersole]

I am trying to nail down a short-term release schedule for Hibernate
3.2.x.  Due to some of the changes made there specifically for EJB3
persistence support, I need to have a stable version of 3.2 done before
AS goes 4.0.4 as 4.0.4 will ship with 3.2.x moving forward.

Is there an anticipated release date for 4.0.4 GA at this point?


---
This SF.Net email is sponsored by xPML, a groundbreaking scripting language
that extends applications into web and mobile media. Attend the live webcast
and join the prime developer group breaking into this new coding territory!
http://sel.as-us.falkag.net/sel?cmd=lnkkid0944bid$1720dat1642
___
JBoss-Development mailing list
JBoss-Development@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/jboss-development

RE: [JBoss-dev] 4.0.4

[Steve Ebersole]

No way I'll have a 3.2 final this week ;)

And it is not a simple matter of re-target for 4.0.5.  EJB3 relies on
changes made in the current alphas of 3.2 due to the latest changes in
the spec (specifically the joinTransaction() stuff)...

-Original Message-
From: [EMAIL PROTECTED]
[mailto:[EMAIL PROTECTED] On Behalf Of
Dimitris Andreadis
Sent: Monday, March 20, 2006 11:24 AM
To: jboss-development@lists.sourceforge.net
Subject: RE: [JBoss-dev] 4.0.4


But you need to get your changes with 4.0.4.CR2 (due out this week) so
they get tested!

After CR2 you'll need to target 4.0.5 

 -Original Message-
 From: [EMAIL PROTECTED] 
 [mailto:[EMAIL PROTECTED] On 
 Behalf Of Dimitris Andreadis
 Sent: 20 March, 2006 19:09
 To: jboss-development@lists.sourceforge.net
 Subject: RE: [JBoss-dev] 4.0.4
 
 
 3rd April (give or take) 
 
  -Original Message-
  From: [EMAIL PROTECTED]
  [mailto:[EMAIL PROTECTED] On Behalf Of 
  Steve Ebersole
  Sent: 20 March, 2006 19:03
  To: jboss-development@lists.sourceforge.net
  Subject: [JBoss-dev] 4.0.4
  
  I am trying to nail down a short-term release schedule for 
 Hibernate 
  3.2.x.  Due to some of the changes made there specifically for EJB3 
  persistence support, I need to have a stable version of 3.2 done 
  before AS goes 4.0.4 as 4.0.4 will ship with 3.2.x moving forward.
  
  Is there an anticipated release date for 4.0.4 GA at this point?
  
  
  ---
  This SF.Net email is sponsored by xPML, a groundbreaking scripting 
  language that extends applications into web and mobile 
 media. Attend 
  the live webcast and join the prime developer group 
 breaking into this 
  new coding territory!
  http://sel.as-us.falkag.net/sel?cmd=kkid0944bid$1720dat1642
  ___
  JBoss-Development mailing list
  JBoss-Development@lists.sourceforge.net
  https://lists.sourceforge.net/lists/listinfo/jboss-development
  
 
 
 ---
 This SF.Net email is sponsored by xPML, a groundbreaking 
 scripting language that extends applications into web and 
 mobile media. Attend the live webcast and join the prime 
 developer group breaking into this new coding territory!
 http://sel.as-us.falkag.net/sel?cmd=kkid0944bid$1720dat1642
 ___
 JBoss-Development mailing list
 JBoss-Development@lists.sourceforge.net
 https://lists.sourceforge.net/lists/listinfo/jboss-development
 


---
This SF.Net email is sponsored by xPML, a groundbreaking scripting
language
that extends applications into web and mobile media. Attend the live
webcast
and join the prime developer group breaking into this new coding
territory!
http://sel.as-us.falkag.net/sel?cmd=kkid0944bid$1720dat1642
___
JBoss-Development mailing list
JBoss-Development@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/jboss-development


---
This SF.Net email is sponsored by xPML, a groundbreaking scripting language
that extends applications into web and mobile media. Attend the live webcast
and join the prime developer group breaking into this new coding territory!
http://sel.as-us.falkag.net/sel?cmd=lnkkid0944bid$1720dat1642
___
JBoss-Development mailing list
JBoss-Development@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/jboss-development

RE: [JBoss-dev] 4.0.4

[Steve Ebersole]

Well, its *possible* to have a final release whenever I want ;)

But at a bare minimum there is one more feature that EJB3 will require
which still needs to be implemented; and it is an ugly one.  I need to
release 3.1.3 today/tomorrow (this needs to be done for reasons
extraneous to this discussion).  I can then come back to work on this
particular feature.  All that I can get done by next week.

But that is not all I had initially targeted for 3.2 final (nor even
beta).  And I do not like leaving off planned features just to get to a
3.2 final.

For me it comes down to whether this is a planned final release for
EJB3.  If so, I guess I could be persuaded to cut a 3.2 final after
implementing the above mentioned feature and then start on 3.2.1 or
whatever.  

 
-Original Message-
From: [EMAIL PROTECTED]
[mailto:[EMAIL PROTECTED] On Behalf Of
Dimitris Andreadis
Sent: Monday, March 20, 2006 11:42 AM
To: jboss-development@lists.sourceforge.net
Subject: RE: [JBoss-dev] 4.0.4


I love those dependencies ;)

Is it possible to have a final next week ? 

 -Original Message-
 From: [EMAIL PROTECTED] 
 [mailto:[EMAIL PROTECTED] On 
 Behalf Of Steve Ebersole
 Sent: 20 March, 2006 19:33
 To: jboss-development@lists.sourceforge.net
 Subject: RE: [JBoss-dev] 4.0.4
 
 No way I'll have a 3.2 final this week ;)
 
 And it is not a simple matter of re-target for 4.0.5.  EJB3 
 relies on changes made in the current alphas of 3.2 due to 
 the latest changes in the spec (specifically the 
 joinTransaction() stuff)...
 
 -Original Message-
 From: [EMAIL PROTECTED]
 [mailto:[EMAIL PROTECTED] On 
 Behalf Of Dimitris Andreadis
 Sent: Monday, March 20, 2006 11:24 AM
 To: jboss-development@lists.sourceforge.net
 Subject: RE: [JBoss-dev] 4.0.4
 
 
 But you need to get your changes with 4.0.4.CR2 (due out this 
 week) so they get tested!
 
 After CR2 you'll need to target 4.0.5 
 
  -Original Message-
  From: [EMAIL PROTECTED]
  [mailto:[EMAIL PROTECTED] On Behalf Of 
  Dimitris Andreadis
  Sent: 20 March, 2006 19:09
  To: jboss-development@lists.sourceforge.net
  Subject: RE: [JBoss-dev] 4.0.4
  
  
  3rd April (give or take)
  
   -Original Message-
   From: [EMAIL PROTECTED]
   [mailto:[EMAIL PROTECTED] On 
 Behalf Of 
   Steve Ebersole
   Sent: 20 March, 2006 19:03
   To: jboss-development@lists.sourceforge.net
   Subject: [JBoss-dev] 4.0.4
   
   I am trying to nail down a short-term release schedule for
  Hibernate
   3.2.x.  Due to some of the changes made there 
 specifically for EJB3 
   persistence support, I need to have a stable version of 3.2 done 
   before AS goes 4.0.4 as 4.0.4 will ship with 3.2.x moving forward.
   
   Is there an anticipated release date for 4.0.4 GA at this point?
   
   
   ---
   This SF.Net email is sponsored by xPML, a groundbreaking 
 scripting 
   language that extends applications into web and mobile
  media. Attend
   the live webcast and join the prime developer group
  breaking into this
   new coding territory!
   http://sel.as-us.falkag.net/sel?cmd=kkid0944bid$1720dat1642
   ___
   JBoss-Development mailing list
   JBoss-Development@lists.sourceforge.net
   https://lists.sourceforge.net/lists/listinfo/jboss-development
   
  
  
  ---
  This SF.Net email is sponsored by xPML, a groundbreaking scripting 
  language that extends applications into web and mobile 
 media. Attend 
  the live webcast and join the prime developer group 
 breaking into this 
  new coding territory!
  http://sel.as-us.falkag.net/sel?cmd=kkid0944bid$1720dat1642
  ___
  JBoss-Development mailing list
  JBoss-Development@lists.sourceforge.net
  https://lists.sourceforge.net/lists/listinfo/jboss-development
  
 
 
 ---
 This SF.Net email is sponsored by xPML, a groundbreaking 
 scripting language that extends applications into web and 
 mobile media. Attend the live webcast and join the prime 
 developer group breaking into this new coding territory!
 http://sel.as-us.falkag.net/sel?cmd=kkid0944bid$1720dat1642
 ___
 JBoss-Development mailing list
 JBoss-Development@lists.sourceforge.net
 https://lists.sourceforge.net/lists/listinfo/jboss-development
 
 
 ---
 This SF.Net email is sponsored by xPML, a groundbreaking 
 scripting language that extends applications into web and 
 mobile media. Attend the live webcast and join the prime 
 developer group breaking into this new coding territory!
 http://sel.as-us.falkag.net/sel?cmd=kkid0944bid$1720dat1642
 ___
 JBoss-Development mailing list
 JBoss-Development@lists.sourceforge.net
 https://lists.sourceforge.net/lists/listinfo/jboss-development

RE: [JBoss-dev] 4.0.4

[Steve Ebersole]

Yep.

Ok, so I'll implement that one mentioned feature and cut alpha3 which we
can use in 4.0.4...


-Original Message-
From: [EMAIL PROTECTED]
[mailto:[EMAIL PROTECTED] On Behalf Of Bill
Burke
Sent: Monday, March 20, 2006 12:45 PM
To: jboss-development@lists.sourceforge.net
Subject: Re: [JBoss-dev] 4.0.4

we just need something stable for hibernate in 4.0.4 GA.

Steve Ebersole wrote:
 Well, its *possible* to have a final release whenever I want ;)
 
 But at a bare minimum there is one more feature that EJB3 will require
 which still needs to be implemented; and it is an ugly one.  I need to
 release 3.1.3 today/tomorrow (this needs to be done for reasons
 extraneous to this discussion).  I can then come back to work on this
 particular feature.  All that I can get done by next week.
 
 But that is not all I had initially targeted for 3.2 final (nor even
 beta).  And I do not like leaving off planned features just to get to
a
 3.2 final.
 
 For me it comes down to whether this is a planned final release for
 EJB3.  If so, I guess I could be persuaded to cut a 3.2 final after
 implementing the above mentioned feature and then start on 3.2.1 or
 whatever.  
 
  
 -Original Message-
 From: [EMAIL PROTECTED]
 [mailto:[EMAIL PROTECTED] On Behalf Of
 Dimitris Andreadis
 Sent: Monday, March 20, 2006 11:42 AM
 To: jboss-development@lists.sourceforge.net
 Subject: RE: [JBoss-dev] 4.0.4
 
 
 I love those dependencies ;)
 
 Is it possible to have a final next week ? 
 
 
-Original Message-
From: [EMAIL PROTECTED] 
[mailto:[EMAIL PROTECTED] On 
Behalf Of Steve Ebersole
Sent: 20 March, 2006 19:33
To: jboss-development@lists.sourceforge.net
Subject: RE: [JBoss-dev] 4.0.4

No way I'll have a 3.2 final this week ;)

And it is not a simple matter of re-target for 4.0.5.  EJB3 
relies on changes made in the current alphas of 3.2 due to 
the latest changes in the spec (specifically the 
joinTransaction() stuff)...

-Original Message-
From: [EMAIL PROTECTED]
[mailto:[EMAIL PROTECTED] On 
Behalf Of Dimitris Andreadis
Sent: Monday, March 20, 2006 11:24 AM
To: jboss-development@lists.sourceforge.net
Subject: RE: [JBoss-dev] 4.0.4


But you need to get your changes with 4.0.4.CR2 (due out this 
week) so they get tested!

After CR2 you'll need to target 4.0.5 


-Original Message-
From: [EMAIL PROTECTED]
[mailto:[EMAIL PROTECTED] On Behalf Of 
Dimitris Andreadis
Sent: 20 March, 2006 19:09
To: jboss-development@lists.sourceforge.net
Subject: RE: [JBoss-dev] 4.0.4


3rd April (give or take)


-Original Message-
From: [EMAIL PROTECTED]
[mailto:[EMAIL PROTECTED] On 

Behalf Of 

Steve Ebersole
Sent: 20 March, 2006 19:03
To: jboss-development@lists.sourceforge.net
Subject: [JBoss-dev] 4.0.4

I am trying to nail down a short-term release schedule for

Hibernate

3.2.x.  Due to some of the changes made there 

specifically for EJB3 

persistence support, I need to have a stable version of 3.2 done 
before AS goes 4.0.4 as 4.0.4 will ship with 3.2.x moving forward.

Is there an anticipated release date for 4.0.4 GA at this point?


---
This SF.Net email is sponsored by xPML, a groundbreaking 

scripting 

language that extends applications into web and mobile

media. Attend

the live webcast and join the prime developer group

breaking into this

new coding territory!
http://sel.as-us.falkag.net/sel?cmd=kkid0944bid$1720dat1642
___
JBoss-Development mailing list
JBoss-Development@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/jboss-development



---
This SF.Net email is sponsored by xPML, a groundbreaking scripting 
language that extends applications into web and mobile 

media. Attend 

the live webcast and join the prime developer group 

breaking into this 

new coding territory!
http://sel.as-us.falkag.net/sel?cmd=kkid0944bid$1720dat1642
___
JBoss-Development mailing list
JBoss-Development@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/jboss-development



---
This SF.Net email is sponsored by xPML, a groundbreaking 
scripting language that extends applications into web and 
mobile media. Attend the live webcast and join the prime 
developer group breaking into this new coding territory!
http://sel.as-us.falkag.net/sel?cmd=kkid0944bid$1720dat1642
___
JBoss-Development mailing list
JBoss-Development@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/jboss-development


---
This SF.Net email is sponsored by xPML, a groundbreaking 
scripting language that extends applications into web and 
mobile media. Attend the live webcast and join the prime 
developer group breaking into this new coding

RE: [JBoss-dev] 4.0.4

[Steve Ebersole]

This goes back to the previous discussion sometime last week.  

JBoss itself *should* keep bundling 3.1.x - preferably 3.1.3 as soon as
I release it today/tomorrow; that is the stable release cycle.  But that
screws EJB3 for the previously mentioned reasons. 

So what's the solution?

Here's the roadmap:
http://opensource2.atlassian.com/projects/hibernate/browse/HHH?report=co
m.atlassian.jira.plugin.system.project:roadmap-panel

As you can see, I am nowhere near even a beta according to any known
definition of beta of which I am aware.


-Original Message-
From: [EMAIL PROTECTED]
[mailto:[EMAIL PROTECTED] On Behalf Of
Dimitris Andreadis
Sent: Monday, March 20, 2006 12:54 PM
To: jboss-development@lists.sourceforge.net
Subject: RE: [JBoss-dev] 4.0.4


Exactly. Something stable, that can be tested with 4.0.4.CR2 (which is
delayed until Friday 24th or Monday 27th max), that satisfies Bill, and
won't require an immediate 4.0.4.SP1 release for fixes :)

There are many-many people waiting for 4.0.4 for quite some time and we
are already delayed, so please try to get a stable release out. Users
won't like at all running jboss 4.0.4 on a hibernate alpha.

 -Original Message-
 From: [EMAIL PROTECTED] 
 [mailto:[EMAIL PROTECTED] On 
 Behalf Of Bill Burke
 Sent: 20 March, 2006 20:45
 To: jboss-development@lists.sourceforge.net
 Subject: Re: [JBoss-dev] 4.0.4
 
 we just need something stable for hibernate in 4.0.4 GA.
 
 Steve Ebersole wrote:
  Well, its *possible* to have a final release whenever I want ;)
  
  But at a bare minimum there is one more feature that EJB3 
 will require 
  which still needs to be implemented; and it is an ugly one. 
  I need to 
  release 3.1.3 today/tomorrow (this needs to be done for reasons 
  extraneous to this discussion).  I can then come back to 
 work on this 
  particular feature.  All that I can get done by next week.
  
  But that is not all I had initially targeted for 3.2 final 
 (nor even 
  beta).  And I do not like leaving off planned features just 
 to get to 
  a
  3.2 final.
  
  For me it comes down to whether this is a planned final 
 release for 
  EJB3.  If so, I guess I could be persuaded to cut a 3.2 final after 
  implementing the above mentioned feature and then start on 3.2.1 or 
  whatever.
  
   
  -Original Message-
  From: [EMAIL PROTECTED]
  [mailto:[EMAIL PROTECTED] On Behalf Of 
  Dimitris Andreadis
  Sent: Monday, March 20, 2006 11:42 AM
  To: jboss-development@lists.sourceforge.net
  Subject: RE: [JBoss-dev] 4.0.4
  
  
  I love those dependencies ;)
  
  Is it possible to have a final next week ? 
  
  
 -Original Message-
 From: [EMAIL PROTECTED]
 [mailto:[EMAIL PROTECTED] On Behalf Of 
 Steve Ebersole
 Sent: 20 March, 2006 19:33
 To: jboss-development@lists.sourceforge.net
 Subject: RE: [JBoss-dev] 4.0.4
 
 No way I'll have a 3.2 final this week ;)
 
 And it is not a simple matter of re-target for 4.0.5.  EJB3 
 relies on 
 changes made in the current alphas of 3.2 due to the latest 
 changes in 
 the spec (specifically the
 joinTransaction() stuff)...
 
 -Original Message-
 From: [EMAIL PROTECTED]
 [mailto:[EMAIL PROTECTED] On Behalf Of 
 Dimitris Andreadis
 Sent: Monday, March 20, 2006 11:24 AM
 To: jboss-development@lists.sourceforge.net
 Subject: RE: [JBoss-dev] 4.0.4
 
 
 But you need to get your changes with 4.0.4.CR2 (due out this
 week) so they get tested!
 
 After CR2 you'll need to target 4.0.5
 
 
 -Original Message-
 From: [EMAIL PROTECTED]
 [mailto:[EMAIL PROTECTED] On 
 Behalf Of 
 Dimitris Andreadis
 Sent: 20 March, 2006 19:09
 To: jboss-development@lists.sourceforge.net
 Subject: RE: [JBoss-dev] 4.0.4
 
 
 3rd April (give or take)
 
 
 -Original Message-
 From: [EMAIL PROTECTED]
 [mailto:[EMAIL PROTECTED] On
 
 Behalf Of
 
 Steve Ebersole
 Sent: 20 March, 2006 19:03
 To: jboss-development@lists.sourceforge.net
 Subject: [JBoss-dev] 4.0.4
 
 I am trying to nail down a short-term release schedule for
 
 Hibernate
 
 3.2.x.  Due to some of the changes made there
 
 specifically for EJB3
 
 persistence support, I need to have a stable version of 3.2 done 
 before AS goes 4.0.4 as 4.0.4 will ship with 3.2.x moving forward.
 
 Is there an anticipated release date for 4.0.4 GA at this point?
 
 
 ---
 This SF.Net email is sponsored by xPML, a groundbreaking
 
 scripting
 
 language that extends applications into web and mobile
 
 media. Attend
 
 the live webcast and join the prime developer group
 
 breaking into this
 
 new coding territory!
 http://sel.as-us.falkag.net/sel?cmd=kkid0944bid$1720dat1642
 ___
 JBoss-Development mailing list
 JBoss-Development@lists.sourceforge.net
 https://lists.sourceforge.net/lists/listinfo/jboss-development
 
 
 
 ---
 This SF.Net email is sponsored by xPML, a groundbreaking scripting 
 language

RE: [JBoss-dev] 4.0.4

[Steve Ebersole]

Sure, I do this also; but:

(1) I prefer not adding brand new features in a point release, if
possible.
(2) The query parser re-work represents a significant change in the
code-base, which I'd also prefer to not include in a point release.

Another option, I guess, is to cut a 3.2 final after this last feature
needed for EJB3, and then immediately start on 3.3...


-Original Message-
From: [EMAIL PROTECTED]
[mailto:[EMAIL PROTECTED] On Behalf Of Bill
Burke
Sent: Monday, March 20, 2006 1:21 PM
To: jboss-development@lists.sourceforge.net
Subject: Re: [JBoss-dev] 4.0.4



Steve Ebersole wrote:
 This goes back to the previous discussion sometime last week.  
 
 JBoss itself *should* keep bundling 3.1.x - preferably 3.1.3 as soon
as
 I release it today/tomorrow; that is the stable release cycle.  But
that
 screws EJB3 for the previously mentioned reasons. 
 
 So what's the solution?
 
 Here's the roadmap:

http://opensource2.atlassian.com/projects/hibernate/browse/HHH?report=co
 m.atlassian.jira.plugin.system.project:roadmap-panel
 
 As you can see, I am nowhere near even a beta according to any known
 definition of beta of which I am aware.
 

What exactly is preventing a 3.2 FINAL and deferring bugs/features until

3.2.1?  I do this with EJB3 all the time.  If there is a date I have to 
make, I drop bugs/features from the release to make the date, or move 
the date if this isn't possible.

Bill



 
 -Original Message-
 From: [EMAIL PROTECTED]
 [mailto:[EMAIL PROTECTED] On Behalf Of
 Dimitris Andreadis
 Sent: Monday, March 20, 2006 12:54 PM
 To: jboss-development@lists.sourceforge.net
 Subject: RE: [JBoss-dev] 4.0.4
 
 
 Exactly. Something stable, that can be tested with 4.0.4.CR2 (which is
 delayed until Friday 24th or Monday 27th max), that satisfies Bill,
and
 won't require an immediate 4.0.4.SP1 release for fixes :)
 
 There are many-many people waiting for 4.0.4 for quite some time and
we
 are already delayed, so please try to get a stable release out. Users
 won't like at all running jboss 4.0.4 on a hibernate alpha.
 
 
-Original Message-
From: [EMAIL PROTECTED] 
[mailto:[EMAIL PROTECTED] On 
Behalf Of Bill Burke
Sent: 20 March, 2006 20:45
To: jboss-development@lists.sourceforge.net
Subject: Re: [JBoss-dev] 4.0.4

we just need something stable for hibernate in 4.0.4 GA.

Steve Ebersole wrote:

Well, its *possible* to have a final release whenever I want ;)

But at a bare minimum there is one more feature that EJB3 

will require 

which still needs to be implemented; and it is an ugly one. 

 I need to 

release 3.1.3 today/tomorrow (this needs to be done for reasons 
extraneous to this discussion).  I can then come back to 

work on this 

particular feature.  All that I can get done by next week.

But that is not all I had initially targeted for 3.2 final 

(nor even 

beta).  And I do not like leaving off planned features just 

to get to 

a
3.2 final.

For me it comes down to whether this is a planned final 

release for 

EJB3.  If so, I guess I could be persuaded to cut a 3.2 final after 
implementing the above mentioned feature and then start on 3.2.1 or 
whatever.

 
-Original Message-
From: [EMAIL PROTECTED]
[mailto:[EMAIL PROTECTED] On Behalf Of 
Dimitris Andreadis
Sent: Monday, March 20, 2006 11:42 AM
To: jboss-development@lists.sourceforge.net
Subject: RE: [JBoss-dev] 4.0.4


I love those dependencies ;)

Is it possible to have a final next week ? 



-Original Message-
From: [EMAIL PROTECTED]
[mailto:[EMAIL PROTECTED] On Behalf Of 
Steve Ebersole
Sent: 20 March, 2006 19:33
To: jboss-development@lists.sourceforge.net
Subject: RE: [JBoss-dev] 4.0.4

No way I'll have a 3.2 final this week ;)

And it is not a simple matter of re-target for 4.0.5.  EJB3 

relies on 

changes made in the current alphas of 3.2 due to the latest 

changes in 

the spec (specifically the
joinTransaction() stuff)...

-Original Message-
From: [EMAIL PROTECTED]
[mailto:[EMAIL PROTECTED] On Behalf Of 
Dimitris Andreadis
Sent: Monday, March 20, 2006 11:24 AM
To: jboss-development@lists.sourceforge.net
Subject: RE: [JBoss-dev] 4.0.4


But you need to get your changes with 4.0.4.CR2 (due out this
week) so they get tested!

After CR2 you'll need to target 4.0.5



-Original Message-
From: [EMAIL PROTECTED]
[mailto:[EMAIL PROTECTED] On 

Behalf Of 

Dimitris Andreadis
Sent: 20 March, 2006 19:09
To: jboss-development@lists.sourceforge.net
Subject: RE: [JBoss-dev] 4.0.4


3rd April (give or take)



-Original Message-
From: [EMAIL PROTECTED]
[mailto:[EMAIL PROTECTED] On

Behalf Of


Steve Ebersole
Sent: 20 March, 2006 19:03
To: jboss-development@lists.sourceforge.net
Subject: [JBoss-dev] 4.0.4

I am trying to nail down a short-term release schedule for

Hibernate


3.2.x.  Due to some of the changes made there

specifically for EJB3


persistence support, I need to have a stable version of 3.2 done 
before AS goes 4.0.4 as 4.0.4 will ship with 3.2.x moving

RE: [JBoss-dev] 4.0.4

[Steve Ebersole]

It is up to y'all.  I am fine with cutting a 3.2 final and then
continuing HEAD development as 3.3.  But the 3.2 release introduced some
fairly different behavior in terms of non-transactional access more
in-line with what is defined in the EJB3 spec.  These changes are
stricter than what Hibernate had previously allowed in these scenarios.
I think everyone agrees that these are better behaviors, but certainly
there are probably some users relying on the old bad behaviors.


-Original Message-
From: [EMAIL PROTECTED]
[mailto:[EMAIL PROTECTED] On Behalf Of
Scott M Stark
Sent: Monday, March 20, 2006 1:39 PM
To: jboss-development@lists.sourceforge.net
Subject: RE: [JBoss-dev] 4.0.4

It seems like ejb3 should only be brining in a latter hibernate
dependency via the installer and a custom build for testing. The
default/all should not be bumped up to track ejb3 issues to an untested
hibernate release. 

 -Original Message-
 From: [EMAIL PROTECTED] 
 [mailto:[EMAIL PROTECTED] On 
 Behalf Of Dimitris Andreadis
 Sent: Monday, March 20, 2006 10:54 AM
 To: jboss-development@lists.sourceforge.net
 Subject: RE: [JBoss-dev] 4.0.4
 
 
 Exactly. Something stable, that can be tested with 4.0.4.CR2 
 (which is delayed until Friday 24th or Monday 27th max), that 
 satisfies Bill, and won't require an immediate 4.0.4.SP1 
 release for fixes :)
 
 There are many-many people waiting for 4.0.4 for quite some 
 time and we are already delayed, so please try to get a 
 stable release out. Users won't like at all running jboss 
 4.0.4 on a hibernate alpha.
 
  -Original Message-
  From: [EMAIL PROTECTED]
  [mailto:[EMAIL PROTECTED] On Behalf Of 
  Bill Burke
  Sent: 20 March, 2006 20:45
  To: jboss-development@lists.sourceforge.net
  Subject: Re: [JBoss-dev] 4.0.4
  
  we just need something stable for hibernate in 4.0.4 GA.
  
  Steve Ebersole wrote:
   Well, its *possible* to have a final release whenever I want ;)
   
   But at a bare minimum there is one more feature that EJB3
  will require
   which still needs to be implemented; and it is an ugly one. 
   I need to
   release 3.1.3 today/tomorrow (this needs to be done for reasons 
   extraneous to this discussion).  I can then come back to
  work on this
   particular feature.  All that I can get done by next week.
   
   But that is not all I had initially targeted for 3.2 final
  (nor even
   beta).  And I do not like leaving off planned features just
  to get to
   a
   3.2 final.
   
   For me it comes down to whether this is a planned final
  release for
   EJB3.  If so, I guess I could be persuaded to cut a 3.2 
 final after 
   implementing the above mentioned feature and then start 
 on 3.2.1 or 
   whatever.
   

   -Original Message-
   From: [EMAIL PROTECTED]
   [mailto:[EMAIL PROTECTED] On 
 Behalf Of 
   Dimitris Andreadis
   Sent: Monday, March 20, 2006 11:42 AM
   To: jboss-development@lists.sourceforge.net
   Subject: RE: [JBoss-dev] 4.0.4
   
   
   I love those dependencies ;)
   
   Is it possible to have a final next week ? 


---
This SF.Net email is sponsored by xPML, a groundbreaking scripting
language
that extends applications into web and mobile media. Attend the live
webcast
and join the prime developer group breaking into this new coding
territory!
http://sel.as-us.falkag.net/sel?cmd=kkid0944bid$1720dat1642
___
JBoss-Development mailing list
JBoss-Development@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/jboss-development


---
This SF.Net email is sponsored by xPML, a groundbreaking scripting language
that extends applications into web and mobile media. Attend the live webcast
and join the prime developer group breaking into this new coding territory!
http://sel.as-us.falkag.net/sel?cmd=lnkkid0944bid$1720dat1642
___
JBoss-Development mailing list
JBoss-Development@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/jboss-development

RE: [JBoss-dev] 4.0.4

[Steve Ebersole]

Well the other piece to the puzzle is the differences between that
Hibernate version you mentioned and 3.1.3.  If the differences there are
drastic enough, then I see even more of an argument to move to 3.2 for
the AS bundle.  Another thing to consider is portal (which AFAIK is
still the only other bundled user of the deployer stuff).
Specifically, will the non-transactional access changes cause them
problems?  Julien; Roy?

I'll go back and analyze the changes made since the bundled 3.1rc2jboss.

-Original Message-
From: [EMAIL PROTECTED]
[mailto:[EMAIL PROTECTED] On Behalf Of
Scott M Stark
Sent: Monday, March 20, 2006 2:37 PM
To: jboss-development@lists.sourceforge.net
Subject: RE: [JBoss-dev] 4.0.4

Your input is a large factor as well since I don't really know how
different the hibernate 3.1rc2jboss version that was shipped with
4.0.3SP1 and the current version needed for ejb3. The first question, is
what do you want bundled in terms of stability/support?

If this is not what is needed for ejb3 then we need to decouple the
jbossas build from the ejb3 hibernate dependency and deal with ejb3 as a
separate component integrated into the installer with a separate
hibernate dependency that replaces/differs from the default/all version.


 -Original Message-
 From: [EMAIL PROTECTED] 
 [mailto:[EMAIL PROTECTED] On 
 Behalf Of Steve Ebersole
 Sent: Monday, March 20, 2006 12:11 PM
 To: jboss-development@lists.sourceforge.net
 Subject: RE: [JBoss-dev] 4.0.4
 
 It is up to y'all.  I am fine with cutting a 3.2 final and 
 then continuing HEAD development as 3.3.  But the 3.2 release 
 introduced some fairly different behavior in terms of 
 non-transactional access more in-line with what is defined in 
 the EJB3 spec.  These changes are stricter than what 
 Hibernate had previously allowed in these scenarios.
 I think everyone agrees that these are better behaviors, but 
 certainly there are probably some users relying on the old 
 bad behaviors.
 
 
 -Original Message-
 From: [EMAIL PROTECTED]
 [mailto:[EMAIL PROTECTED] On 
 Behalf Of Scott M Stark
 Sent: Monday, March 20, 2006 1:39 PM
 To: jboss-development@lists.sourceforge.net
 Subject: RE: [JBoss-dev] 4.0.4
 
 It seems like ejb3 should only be brining in a latter 
 hibernate dependency via the installer and a custom build for 
 testing. The default/all should not be bumped up to track 
 ejb3 issues to an untested hibernate release. 
 
  -Original Message-
  From: [EMAIL PROTECTED]
  [mailto:[EMAIL PROTECTED] On Behalf Of 
  Dimitris Andreadis
  Sent: Monday, March 20, 2006 10:54 AM
  To: jboss-development@lists.sourceforge.net
  Subject: RE: [JBoss-dev] 4.0.4
  
  
  Exactly. Something stable, that can be tested with 
 4.0.4.CR2 (which is 
  delayed until Friday 24th or Monday 27th max), that satisfies Bill, 
  and won't require an immediate 4.0.4.SP1 release for fixes :)
  
  There are many-many people waiting for 4.0.4 for quite some 
 time and 
  we are already delayed, so please try to get a stable release out. 
  Users won't like at all running jboss
  4.0.4 on a hibernate alpha.
  
   -Original Message-
   From: [EMAIL PROTECTED]
   [mailto:[EMAIL PROTECTED] On 
 Behalf Of 
   Bill Burke
   Sent: 20 March, 2006 20:45
   To: jboss-development@lists.sourceforge.net
   Subject: Re: [JBoss-dev] 4.0.4
   
   we just need something stable for hibernate in 4.0.4 GA.
   
   Steve Ebersole wrote:
Well, its *possible* to have a final release whenever 
 I want ;)

But at a bare minimum there is one more feature that EJB3
   will require
which still needs to be implemented; and it is an ugly one. 
I need to
release 3.1.3 today/tomorrow (this needs to be done for reasons 
extraneous to this discussion).  I can then come back to
   work on this
particular feature.  All that I can get done by next week.

But that is not all I had initially targeted for 3.2 final
   (nor even
beta).  And I do not like leaving off planned features just
   to get to
a
3.2 final.

For me it comes down to whether this is a planned final
   release for
EJB3.  If so, I guess I could be persuaded to cut a 3.2
  final after
implementing the above mentioned feature and then start
  on 3.2.1 or
whatever.

 
-Original Message-
From: [EMAIL PROTECTED]
[mailto:[EMAIL PROTECTED] On
  Behalf Of
Dimitris Andreadis
Sent: Monday, March 20, 2006 11:42 AM
To: jboss-development@lists.sourceforge.net
Subject: RE: [JBoss-dev] 4.0.4


I love those dependencies ;)

Is it possible to have a final next week ? 
 
 
 ---
 This SF.Net email is sponsored by xPML, a groundbreaking 
 scripting language that extends applications into web and 
 mobile media. Attend the live webcast and join the prime 
 developer group breaking into this new coding territory!
 http://sel.as-us.falkag.net/sel?cmd

RE: [JBoss-dev] 4.0.4

[Steve Ebersole]

So provided we do not cause issues with portal, I say we go with a 3.2
final.  Specific reasons:
(1) Less issues with the version differences between AS and EJB3
(2) JBossCache optimistic locking support (only in 3.2)
(3) Javassist support (only in 3.2)
(4) Some performance enhancements relating to aggressive connection
releasing on JBoss (although this is in 3.1.3 also).

The only other real difference between 3.1.3 and 3.2 is the
non-transactional stuff.

The installer/build option seems a bit late in the game considering a
release next week (#1).

-Original Message-
From: [EMAIL PROTECTED]
[mailto:[EMAIL PROTECTED] On Behalf Of
Steve Ebersole
Sent: Monday, March 20, 2006 3:19 PM
To: jboss-development@lists.sourceforge.net
Subject: RE: [JBoss-dev] 4.0.4

Well the other piece to the puzzle is the differences between that
Hibernate version you mentioned and 3.1.3.  If the differences there are
drastic enough, then I see even more of an argument to move to 3.2 for
the AS bundle.  Another thing to consider is portal (which AFAIK is
still the only other bundled user of the deployer stuff).
Specifically, will the non-transactional access changes cause them
problems?  Julien; Roy?

I'll go back and analyze the changes made since the bundled 3.1rc2jboss.

-Original Message-
From: [EMAIL PROTECTED]
[mailto:[EMAIL PROTECTED] On Behalf Of
Scott M Stark
Sent: Monday, March 20, 2006 2:37 PM
To: jboss-development@lists.sourceforge.net
Subject: RE: [JBoss-dev] 4.0.4

Your input is a large factor as well since I don't really know how
different the hibernate 3.1rc2jboss version that was shipped with
4.0.3SP1 and the current version needed for ejb3. The first question, is
what do you want bundled in terms of stability/support?

If this is not what is needed for ejb3 then we need to decouple the
jbossas build from the ejb3 hibernate dependency and deal with ejb3 as a
separate component integrated into the installer with a separate
hibernate dependency that replaces/differs from the default/all version.


 -Original Message-
 From: [EMAIL PROTECTED] 
 [mailto:[EMAIL PROTECTED] On 
 Behalf Of Steve Ebersole
 Sent: Monday, March 20, 2006 12:11 PM
 To: jboss-development@lists.sourceforge.net
 Subject: RE: [JBoss-dev] 4.0.4
 
 It is up to y'all.  I am fine with cutting a 3.2 final and 
 then continuing HEAD development as 3.3.  But the 3.2 release 
 introduced some fairly different behavior in terms of 
 non-transactional access more in-line with what is defined in 
 the EJB3 spec.  These changes are stricter than what 
 Hibernate had previously allowed in these scenarios.
 I think everyone agrees that these are better behaviors, but 
 certainly there are probably some users relying on the old 
 bad behaviors.
 
 
 -Original Message-
 From: [EMAIL PROTECTED]
 [mailto:[EMAIL PROTECTED] On 
 Behalf Of Scott M Stark
 Sent: Monday, March 20, 2006 1:39 PM
 To: jboss-development@lists.sourceforge.net
 Subject: RE: [JBoss-dev] 4.0.4
 
 It seems like ejb3 should only be brining in a latter 
 hibernate dependency via the installer and a custom build for 
 testing. The default/all should not be bumped up to track 
 ejb3 issues to an untested hibernate release. 
 
  -Original Message-
  From: [EMAIL PROTECTED]
  [mailto:[EMAIL PROTECTED] On Behalf Of 
  Dimitris Andreadis
  Sent: Monday, March 20, 2006 10:54 AM
  To: jboss-development@lists.sourceforge.net
  Subject: RE: [JBoss-dev] 4.0.4
  
  
  Exactly. Something stable, that can be tested with 
 4.0.4.CR2 (which is 
  delayed until Friday 24th or Monday 27th max), that satisfies Bill, 
  and won't require an immediate 4.0.4.SP1 release for fixes :)
  
  There are many-many people waiting for 4.0.4 for quite some 
 time and 
  we are already delayed, so please try to get a stable release out. 
  Users won't like at all running jboss
  4.0.4 on a hibernate alpha.
  
   -Original Message-
   From: [EMAIL PROTECTED]
   [mailto:[EMAIL PROTECTED] On 
 Behalf Of 
   Bill Burke
   Sent: 20 March, 2006 20:45
   To: jboss-development@lists.sourceforge.net
   Subject: Re: [JBoss-dev] 4.0.4
   
   we just need something stable for hibernate in 4.0.4 GA.
   
   Steve Ebersole wrote:
Well, its *possible* to have a final release whenever 
 I want ;)

But at a bare minimum there is one more feature that EJB3
   will require
which still needs to be implemented; and it is an ugly one. 
I need to
release 3.1.3 today/tomorrow (this needs to be done for reasons 
extraneous to this discussion).  I can then come back to
   work on this
particular feature.  All that I can get done by next week.

But that is not all I had initially targeted for 3.2 final
   (nor even
beta).  And I do not like leaving off planned features just
   to get to
a
3.2 final.

For me it comes down to whether this is a planned final
   release for
EJB3.  If so, I guess I could be persuaded to cut a 3.2
  final after

RE: [JBoss-dev] jdbc connection pool exception handling

[Steve Ebersole]

This is actually part of the JDBC4 spec too...

-Original Message-
From: [EMAIL PROTECTED]
[mailto:[EMAIL PROTECTED] On Behalf Of Max
Rydahl Andersen
Sent: Friday, March 10, 2006 4:59 PM
To: jboss-development@lists.sourceforge.net; Weston Price
Subject: Re: [JBoss-dev] jdbc connection pool exception handling

On Fri, 10 Mar 2006 17:31:21 +0100, Bill Burke [EMAIL PROTECTED] wrote:

 Spring has a nice feature to take a SQLException and turn it into a
more  
 concrete exception based on a hierarchy.  I.e.
SQLException.errorNumber  
 might be deadlock and it then converts it to a DeadlockException that

 inherits from SQLException (at least I think that's how it works).

 The idea would be to build this into our JCA Connection Pools.
Refactor  
 our JCA Connection Pools to work in any appserver, and we have a nice

 little project.

something like SQLExceptionConverter in Hibernate 3 ?


-- 
--
Max Rydahl Andersen
callto://max.rydahl.andersen

Hibernate
[EMAIL PROTECTED]
http://hibernate.org

JBoss Inc
[EMAIL PROTECTED]


---
This SF.Net email is sponsored by xPML, a groundbreaking scripting
language
that extends applications into web and mobile media. Attend the live
webcast
and join the prime developer group breaking into this new coding
territory!
http://sel.as-us.falkag.net/sel?cmd=lnkkid=110944bid=241720dat=121642
___
JBoss-Development mailing list
JBoss-Development@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/jboss-development


---
This SF.Net email is sponsored by xPML, a groundbreaking scripting language
that extends applications into web and mobile media. Attend the live webcast
and join the prime developer group breaking into this new coding territory!
http://sel.as-us.falkag.net/sel?cmd=lnkkid0944bid$1720dat1642
___
JBoss-Development mailing list
JBoss-Development@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/jboss-development

RE: [JBoss-dev] client libraries on EJB3

[Steve Ebersole]

Well unfortunately serialization is used in two distinct scenarios that
have vastly different de-serialization needs.  The current code is
written to handle both scenarios.  

The first scenario is serialization of the Hibernate Session itself such
that when that Session is then de-serialized all the proxies are
properly re-attached and usable.  

The other scenario is serialization specifically to send across a
class-loader boundary.  Theoretically we could just replace the proxy
with some stand-in object that just always throws a
LazyInitializationException.  But this thing still needs to be typed
correctly upon de-serialization in order to fulfill this role, so not
sure how to do that without the library being used for lazy proxy
generation being available on the client-side anyway.

Hibernate 3.2 does have the ability to use Javassist as the bytecode
library instead of CGLIB.  Hibernate 3.2 is the version I am expecting
to be used in EJB3 moving forward, so there is no problem if you are
fine with requiring Javassist on the client-side...

BTW, even with collections there is a possibility to still need access
to the proxy generation library on de-serialization.  This is because it
is *possible* to have a collection containing proxies in the case of
many-to-many associations.

-Original Message-
From: Scott M Stark 
Sent: Thursday, February 16, 2006 2:08 AM
To: jboss-development@lists.sourceforge.net
Cc: Steve Ebersole
Subject: RE: [JBoss-dev] client libraries on EJB3

But here we are talking about what exists after the object in question
has been serialized outside of the jvm. Does what your talking about
still apply in that situation? Regardless, I think this discussion just
further pushes for a unified javassist based proxy framework sometime
before ejb3 is finalized. 

 -Original Message-
 From: [EMAIL PROTECTED] 
 [mailto:[EMAIL PROTECTED] On 
 Behalf Of Max Rydahl Andersen
 Sent: Wednesday, February 15, 2006 11:56 PM
 To: jboss-development@lists.sourceforge.net
 Cc: Steve Ebersole
 Subject: Re: [JBoss-dev] client libraries on EJB3
 
 Hi guys,
 
 Just bumping in here to tell the whole story about the 
 needed dependencies.
 
 Here are the reasons for ever neededing any hibernate 
 specific stuff on a client side:
 
 1. Managing persistent collections
 To track how a collection mutates so when the object 
 comes back to the server
 hibernate can be more efficient when detecting and 
 executing changes.
 
 2. Handle lazy loaded objects
 If lazy=true on a class (it is by default) the object 
 can be a simple proxied
 shell only containing the id. This allows us to use the 
 object in associations
 without loading it (e.g. child.setParent(proxiedParent);) 
 and to throw an exception
 if it is accessed without being previously loaded or in a 
 session (e.g.  
 proxiedParent.getName() goes boom)
 
 #1 does not require proxy libraries AFAIK but I have not tested it.
 
 #2 requires the proxy libraries (in 3.2 either javaassist or 
 cglib), I don't know if it is feasible
 to generate something that is not dependent on the proxy 
 library and still be able to reassociate it
 when it comes back to the server.
 
 These are important issues that should be handled in 
 Hibernate 3.2 if at all possible. (cc'ed steve)
 
 /max


---
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  web.  DOWNLOAD SPLUNK!
http://sel.as-us.falkag.net/sel?cmd=lnkkid3432bid#0486dat1642
___
JBoss-Development mailing list
JBoss-Development@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/jboss-development

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

[Steve Ebersole]

The thing that we discussed (and I have just not yet had time to
implement) is actually converting QueryExceptions that contain antlr
stuff during serialization by either writeReplace() or writeObject().
Initially we had discussed just stripping the cause in the case of antrl
exception, but perhaps another option is to simply write a replacement
for the antlr exception during writeObject() on the QueryException.

Yet another option would be to handle this as we recognize antrl
exceptions in the translator/parser and decompose that information.  I
don't think the stack trace of the antlr exceptions themselves are
really that vital to users anyway so we could just log the antlr
exceptions for debug purposes.

-Original Message-
From: [EMAIL PROTECTED]
[mailto:[EMAIL PROTECTED] On Behalf Of Max
Rydahl Andersen
Sent: Tuesday, February 07, 2006 2:02 PM
To: Scott M Stark; jboss-development@lists.sourceforge.net; Hibernate
development
Subject: Re: [Hibernate] Do antlr exception leak to users?

On Tue, 07 Feb 2006 20:55:52 +0100, Scott M Stark
[EMAIL PROTECTED]  
wrote:

 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.

which it isn't afaik. the antlr version started to include more data in

the exception over time.

 calling printStackTrace() on every exception sounds overkill
 for me...and will turn basic logging into something very verbose.

 Should be no different from now as logging generally includes the
cause.

well, for me that is showing the exception message in a dialog in the ui
I  
would be very
disappointed to have a full stack trace in the message output.

 I understand the issue, but don't find the suggested
 solutions any good ;(

 Would be nice to have an option to have any exposed remote
 exception do the serialization of the cause.
 Would make it a non-issue where it actually matters.

 This can't be done without modifying the exception either via source
or
 bytecode manipulation.

And bytecode manipulation or simple modification of the exception in the

jboss serialization/remoting layer
have that option, correct ?


-- 
--
Max Rydahl Andersen
callto://max.rydahl.andersen

Hibernate
[EMAIL PROTECTED]
http://hibernate.org

JBoss Inc
[EMAIL PROTECTED]


---
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  web.  DOWNLOAD SPLUNK!
http://sel.as-us.falkag.net/sel?cmd=lnkkid=103432bid=230486dat=121642
___
hibernate-devel mailing list
hibernate-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/hibernate-devel


---
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  web.  DOWNLOAD SPLUNK!
http://sel.as-us.falkag.net/sel?cmd=lnkkid3432bid#0486dat1642
___
JBoss-Development mailing list
JBoss-Development@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/jboss-development

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

[Steve Ebersole]

Well I think the distinction here is that Hibernate constitutes a hard
dependency on Antlr.  The users choice to use Oracle is completely
within their control.

 
-Original Message-
From: Max Andersen 
Sent: Wednesday, February 08, 2006 8:41 AM
To: Steve Ebersole; Scott M Stark;
jboss-development@lists.sourceforge.net; Hibernate development
Subject: Re: [Hibernate] Do antlr exception leak to users?

Hi,

antlr exceptions can probably be contained by some of the methods
mentioned below - no problem.

I'm just wondering what to do with other exceptions ? They will have the
same/similar problem correct? e.g. a ocracle driver specific exception  
occurs
which is pretty good to have as the cause...that will spill to other  
clients too.

/max

 The thing that we discussed (and I have just not yet had time to
 implement) is actually converting QueryExceptions that contain antlr
 stuff during serialization by either writeReplace() or writeObject().
 Initially we had discussed just stripping the cause in the case of
antrl
 exception, but perhaps another option is to simply write a replacement
 for the antlr exception during writeObject() on the QueryException.

 Yet another option would be to handle this as we recognize antrl
 exceptions in the translator/parser and decompose that information.
I
 don't think the stack trace of the antlr exceptions themselves are
 really that vital to users anyway so we could just log the antlr
 exceptions for debug purposes.

 -Original Message-
 From: [EMAIL PROTECTED]
 [mailto:[EMAIL PROTECTED] On Behalf Of Max
 Rydahl Andersen
 Sent: Tuesday, February 07, 2006 2:02 PM
 To: Scott M Stark; jboss-development@lists.sourceforge.net; Hibernate
 development
 Subject: Re: [Hibernate] Do antlr exception leak to users?

 On Tue, 07 Feb 2006 20:55:52 +0100, Scott M Stark
 [EMAIL PROTECTED]
 wrote:

 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.

 which it isn't afaik. the antlr version started to include more data
in

 the exception over time.

 calling printStackTrace() on every exception sounds overkill
 for me...and will turn basic logging into something very verbose.

 Should be no different from now as logging generally includes the
 cause.

 well, for me that is showing the exception message in a dialog in the
ui
 I
 would be very
 disappointed to have a full stack trace in the message output.

 I understand the issue, but don't find the suggested
 solutions any good ;(

 Would be nice to have an option to have any exposed remote
 exception do the serialization of the cause.
 Would make it a non-issue where it actually matters.

 This can't be done without modifying the exception either via source
 or
 bytecode manipulation.

 And bytecode manipulation or simple modification of the exception in
the

 jboss serialization/remoting layer
 have that option, correct ?





-- 
--
Max Rydahl Andersen
callto://max.rydahl.andersen

Hibernate
[EMAIL PROTECTED]
http://hibernate.org

JBoss Inc
[EMAIL PROTECTED]


---
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  web.  DOWNLOAD SPLUNK!
http://sel.as-us.falkag.net/sel?cmd=lnkkid3432bid#0486dat1642
___
JBoss-Development mailing list
JBoss-Development@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/jboss-development

RE: [JBoss-dev] cglib vs javassit for proxies

[Steve Ebersole]

I sent this to a number of other lists, but forgot this one.  Apologies.
I actually just today checked in a pluggable bytecode API into
Hibernate.  Hibernate does now support either CGLIB or Javassist for all
bytecode services.

As an aside, our experience with CGLIB has been very good.  Juozas (one
of the CGLIB developers) is very active in the Hibernate community and
is always extremely responsive to any needs we might encounter.  My $.02

The reason for allowing Javassist to be used instead of CGLIB was merely
to allow a user choice.  Especially in the case of JBoss where Javassist
is used in a lot of places, it just makes sense to have the option to
not have to bundle yet another jar.

-Original Message-
From: [EMAIL PROTECTED]
[mailto:[EMAIL PROTECTED] On Behalf Of Bill
Burke
Sent: Friday, February 03, 2006 8:39 PM
To: jboss-development@lists.sourceforge.net
Subject: Re: [JBoss-dev] cglib vs javassit for proxies

Javassist is pretty good, problem is that it doesn't have a junit
testsuite.

Jason T. Greene wrote:
 I should clarify, for WS, we just need plain javabean generation. So I

 can add that to our list of things to do. BTW I was too harsh, there
are 
 nice things about cglib. I just ran into a lot of bugs.
 
  
 
 -Jason
 
  
 


 
 *From:* [EMAIL PROTECTED] 
 [mailto:[EMAIL PROTECTED] *On Behalf Of 
 *Jason T. Greene
 *Sent:* Friday, February 03, 2006 7:56 PM
 *To:* jboss-development@lists.sourceforge.net
 *Subject:* RE: [JBoss-dev] cglib vs javassit for proxies
 
  
 
 I am all for this, cglib sucks...
 
  
 
 -Jason
 
  
 


 
 *From:* [EMAIL PROTECTED] 
 [mailto:[EMAIL PROTECTED] *On Behalf Of 
 *Scott M Stark
 *Sent:* Friday, February 03, 2006 1:47 PM
 *To:* jboss-development@lists.sourceforge.net
 *Subject:* [JBoss-dev] cglib vs javassit for proxies
 
  
 
 So I have to introduce a proxy for a javax.net.SSLServerSocket which
is 
 an abstract class and so have to use cglib or javassist. I see some 
 proxy working in the head javassist, but this is not in the 4.0 branch

 version. We also don't bundle javassist with 4.0 currently. I assume
we 
 would rather have javassist be the only bytecode manipulation
framework 
 in jboss. Is there a timeframe for completing the javassist proxy so
we 
 can think about moving hibernate, webservices, cmp2.x, etc over to it?
 
  
 

-- 
Bill Burke
Chief Architect
JBoss Inc.


---
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  web.  DOWNLOAD SPLUNK!
http://sel.as-us.falkag.net/sel?cmd=kkid3432bid#0486dat1642
___
JBoss-Development mailing list
JBoss-Development@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/jboss-development


---
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  web.  DOWNLOAD SPLUNK!
http://sel.as-us.falkag.net/sel?cmd=lnkkid3432bid#0486dat1642
___
JBoss-Development mailing list
JBoss-Development@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/jboss-development

RE: [JBoss-dev] cglib vs javassit for proxies

[Steve Ebersole]

Define replace code for you...  You mean as in replace the class def
*in the classloader*?

Currently field interception (using either) is only
implemented/available via build task.

-Original Message-
From: [EMAIL PROTECTED]
[mailto:[EMAIL PROTECTED] On Behalf Of Bill
Burke
Sent: Friday, February 03, 2006 9:04 PM
To: jboss-development@lists.sourceforge.net
Subject: Re: [JBoss-dev] cglib vs javassit for proxies

You'll find that Javassist gives you a lot more flexibilty as it has a 
built in javacompiler and can replace code for you.  With Javassist it 
should be really easy to intercept field access for the EJB 3.0 
requirements.

Steve Ebersole wrote:
 I sent this to a number of other lists, but forgot this one.
Apologies.
 I actually just today checked in a pluggable bytecode API into
 Hibernate.  Hibernate does now support either CGLIB or Javassist for
all
 bytecode services.
 
 As an aside, our experience with CGLIB has been very good.  Juozas
(one
 of the CGLIB developers) is very active in the Hibernate community and
 is always extremely responsive to any needs we might encounter.  My
$.02
 
 The reason for allowing Javassist to be used instead of CGLIB was
merely
 to allow a user choice.  Especially in the case of JBoss where
Javassist
 is used in a lot of places, it just makes sense to have the option to
 not have to bundle yet another jar.
 
 -Original Message-
 From: [EMAIL PROTECTED]
 [mailto:[EMAIL PROTECTED] On Behalf Of
Bill
 Burke
 Sent: Friday, February 03, 2006 8:39 PM
 To: jboss-development@lists.sourceforge.net
 Subject: Re: [JBoss-dev] cglib vs javassit for proxies
 
 Javassist is pretty good, problem is that it doesn't have a junit
 testsuite.
 
 Jason T. Greene wrote:
 
I should clarify, for WS, we just need plain javabean generation. So I
 
 
can add that to our list of things to do. BTW I was too harsh, there
 
 are 
 
nice things about cglib. I just ran into a lot of bugs.

 

-Jason

 


 


 
*From:* [EMAIL PROTECTED] 
[mailto:[EMAIL PROTECTED] *On Behalf Of 
*Jason T. Greene
*Sent:* Friday, February 03, 2006 7:56 PM
*To:* jboss-development@lists.sourceforge.net
*Subject:* RE: [JBoss-dev] cglib vs javassit for proxies

 

I am all for this, cglib sucks...

 

-Jason

 


 


 
*From:* [EMAIL PROTECTED] 
[mailto:[EMAIL PROTECTED] *On Behalf Of 
*Scott M Stark
*Sent:* Friday, February 03, 2006 1:47 PM
*To:* jboss-development@lists.sourceforge.net
*Subject:* [JBoss-dev] cglib vs javassit for proxies

 

So I have to introduce a proxy for a javax.net.SSLServerSocket which
 
 is 
 
an abstract class and so have to use cglib or javassist. I see some 
proxy working in the head javassist, but this is not in the 4.0 branch
 
 
version. We also don't bundle javassist with 4.0 currently. I assume
 
 we 
 
would rather have javassist be the only bytecode manipulation
 
 framework 
 
in jboss. Is there a timeframe for completing the javassist proxy so
 
 we 
 
can think about moving hibernate, webservices, cmp2.x, etc over to it?

 

 
 

-- 
Bill Burke
Chief Architect
JBoss Inc.


---
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  web.  DOWNLOAD SPLUNK!
http://sel.as-us.falkag.net/sel?cmd=lnkkid=103432bid=230486dat=121642
___
JBoss-Development mailing list
JBoss-Development@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/jboss-development


---
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  web.  DOWNLOAD SPLUNK!
http://sel.as-us.falkag.net/sel?cmd=lnkkid3432bid#0486dat1642
___
JBoss-Development mailing list
JBoss-Development@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/jboss-development

[JBoss-dev] RE: EJB 3 release slipping

[Steve Ebersole]

Looking at the roadmap for 3.1.1, I am fine with pushing some of the
open issues out till 3.1.2.

I absolutely want to get the following into 3.1.1:
1) http://opensource2.atlassian.com/projects/hibernate/browse/HHH-1019
2) http://opensource2.atlassian.com/projects/hibernate/browse/HHH-1290
3) http://opensource2.atlassian.com/projects/hibernate/browse/HHH-1349
4) http://opensource2.atlassian.com/projects/hibernate/browse/HHH-1302

Additionally, I'd really like to get these into 3.1.1:
5) http://opensource2.atlassian.com/projects/hibernate/browse/HHH-476
6) http://opensource2.atlassian.com/projects/hibernate/browse/HHH-721
7) http://opensource2.atlassian.com/projects/hibernate/browse/HHH-1248

#5 and #6 are documentation tasks that have already been pushed a few
times now.  #7 is specifically for a customer (although I won't lose
sleep if this slips as it is pretty involved).

Anyone feel like stepping up and taking on #5 or #6?  That way I can
focus on the code changes for #1 - #4 and maybe even get time to fix #7
and get this ready by the 16th...


-Original Message-
From: Emmanuel Bernard 
Sent: Tuesday, January 10, 2006 5:43 AM
To: Gavin King
Cc: Scott M Stark; Bill Burke; jboss-development@lists.sourceforge.net;
dev-ejb3; Steve Ebersole
Subject: Re: EJB 3 release slipping

BTW,
That'd be cool to have 3.1.1 for this date too.
I personally did break the compatibility between HA head and H3.1.0 but 
I've fixed a couple of annoying bugs when working with a mix of hbm and 
annotated classes.

Gavin King wrote:

Well, Bill is targeting 16th as a release date for EJB3. So please cut
releases of HA and HEM to go along with that. I guess it does not
matter
if not everything is done.

Seam *is* working against current jboss head. Only problem is I can't
get embeddable ejb working on tomcat. But I'm confident that can get
sorted out.


-Original Message-
From: Emmanuel Bernard 
Sent: Tuesday, January 10, 2006 8:17 PM
To: Scott M Stark
Cc: Gavin King; Bill Burke; jboss-development@lists.sourceforge.net;
dev-ejb3
Subject: Re: EJB 3 release slipping

After HA beta7, HEM beta5 I switched to the PFD APIs, hence the
incompatibilities.
2 solutions:
  - (1) use the EJB3 last module release wich should be compatible with
the latest released versions as Gavin experienced
  - (2) hurry in PFD compatibility this week

(1) the appropriate ejb3-persistence can be found in the HEM beta5
distribution if we need to find it back
(2) That was my plan anyway for this week but I cannot guaranty. I have
some personal constraints preventing me working 7/7 If we do (2) the
docs will need to wait, anyway. All the EJB3 examples will clash with
the new release.

Scott M Stark wrote:

  

HEM 3.1beta5 is not a valid release as it references a 
ejb3-persistence.jar that does not exist in the repository.jboss.com.
I



  

tried the following latest releases:

componentref name=antlr version=2.7.6rc1/ componentref 
name=hibernate version=3.1/ componentref 
name=hibernate-annotations version=3.1beta8-dev/ componentref 
name=hibernate-entitymanager version=3.1beta6-dev/

but the ejb3 module will not compile due to changes in ejb3 apis 
(PersistenceInfo - PersistenceUnitInfo for example).

 



-Original Message-
From: Gavin King
Sent: Friday, January 06, 2006 3:16 PM
To: Bill Burke
Cc: Scott M Stark; jboss-development@lists.sourceforge.net; dev-ejb3
Subject: RE: EJB 3 release slipping

Yep. Hibernate 3.1, HA 3.1 beta 7, HEM 3.1 beta 5. 

-Original Message-
From: Bill Burke
Sent: Saturday, January 07, 2006 10:06 AM
To: Gavin King
Cc: Scott M Stark; jboss-development@lists.sourceforge.net; dev-ejb3
Subject: Re: EJB 3 release slipping

HEM and annotations?

Gavin King wrote:
   

  

I am running JBoss AS 4.0.3SP1 with the latest Hibernate jars every 
day, and it works smoothly.

-Original Message-
From: Bill Burke



 



Can the hibernate jars be updated in the 4.0 branch without
   

  

breaking
   

  

the
ejb3 tests and seam?
   

  

annotations ans HEM cannot be updated, I think Hibernate
 



can, not sure. 
   

  

 Ask EMmanuel.


 



--
Bill Burke
Chief Architect
JBoss Inc.

   

  


  




---
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  web.  DOWNLOAD SPLUNK!
http://ads.osdn.com/?ad_idv37alloc_id865op=click
___
JBoss-Development mailing list
JBoss-Development@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/jboss-development

RE: [JBoss-dev] JMX console

[Steve Ebersole]

AFAICT, this would require the following changes:

1) org.jboss.util.propertyeditor.BooleanEditor so that:
   public void setAsText(final String text)
   {
  Object newValue = Boolean.valueOf(text);
  setValue(newValue);
   }
becomes: 
   public void setAsText(final String text) {
  if ( text == null || .equals( text ) || null.equals( text ) )
{
 setValue( null );
  }
  else {
 setValue( Boolean.valueOf( text ) );
  }
   }
(or whatever we deem is valid null string representation)

In my testing, that's it.  A lookup on boolean vs. java.lang.Boolean
returns different editors; sun.beans.editors.BoolEditor (primitive) vs.
org.jboss.util.propertyeditor.BooleanEditor (wrapper).  Not sure whether
there is existing code which exposes java.lang.Boolean attributes and
relies on this behavior of never getting null values (not sure why they
expose the wrapper type anyway though if that is the case).

Test code:

public static void main(String[] args) {

// snipped and modified from 
// org.jboss.util.propertyeditor.PropertyEditors
String[] currentPath = PropertyEditorManager.getEditorSearchPath();
int length = currentPath != null ? currentPath.length : 0;
String[] newPath = new String[length + 1];
System.arraycopy( currentPath, 0, newPath, 1, length );
// register my local package with modified BooleanEditor
newPath[0] = booleaneditor;
PropertyEditorManager.setEditorSearchPath( newPath );

// prepare for tests
PropertyEditor editor = null;
PropertyChangeListener listener = new PropertyChangeListener() {
public void propertyChange(PropertyChangeEvent evt) {
PropertyEditor editor = ( PropertyEditor ) evt.getSource();
System.out.println( 
editor.getValue() == null ? [null] :
editor.getValue() 
);
}
};

// start tests...

try {
System.out.println( standard boolean editor ... );
System.out.println( --- );
editor = PropertyEditorManager.findEditor( boolean.class );
System.out.println( editor =  + editor );
editor.addPropertyChangeListener( listener );
editor.setAsText(  );
editor.setAsText( null );
editor.setAsText( null );
editor.removePropertyChangeListener( listener );
}
catch ( IllegalArgumentException e ) {
System.out.println( IAE error occured (as expected) );
}

System.out.println();
System.out.println( standard Boolean editor ... );
System.out.println( --- );
editor = PropertyEditorManager.findEditor( Boolean.class );
System.out.println( editor =  + editor );
editor.addPropertyChangeListener( listener );
editor.setAsText(  );
editor.setAsText( null );
editor.setAsText( null );
editor.removePropertyChangeListener( listener );
}


Results in:

standard boolean editor ...
---
editor = [EMAIL PROTECTED]
IAE error occured (as expected)

standard Boolean editor ...
---
editor = [EMAIL PROTECTED]
[null]
[null]
[null]


Which all seems reasonable behavior.


-Original Message-
From: [EMAIL PROTECTED]
[mailto:[EMAIL PROTECTED] On Behalf Of
Steve Ebersole
Sent: Thursday, August 04, 2005 4:08 PM
To: jboss-development@lists.sourceforge.net
Subject: RE: [JBoss-dev] JMX console

Not sure what you mean by supports null.  If certainly understands the
difference between boolean and java.lang.Boolean during display.  The
jsp just explicitly chooses to render the input controls the same in
both instances:
if( attrType.equals(boolean) || attrType.equals(java.lang.Boolean) )
{
...
}

Also, there is a call to AttrResultInfo.getAsText() which just calls a
PropertyEditor; now unfortunately, that
org.jboss.util.propertyeditor.BooleanEditor does not support null (it
just always calls Boolean.valueOf() which *never* returns null).

So the situation is that I recently converted the HibernateMBean to use
smarter types.  It used to expose everything as string (now I think I
see why).  I wanted this to change so that it exposed a more type-safe
interface.  For the majority of the booleans though, Hibernate uses
various default values if the user does not specify a value; but in
JBoss, if they go through the jmx-console as it stands now, they will
never be able to not specify something because null is not an
option.

-Original Message-
From: [EMAIL PROTECTED]
[mailto:[EMAIL PROTECTED] On Behalf Of
Adrian Brock
Sent: Thursday, August 04, 2005 3:41 PM
To: jboss-development@lists.sourceforge.net
Subject: Re: [JBoss-dev] JMX console

I don't think the JMX console supports null at all does it?

Julien's console in the nukes codebase is much better at handling
attribute changes.

On Thu, 2005-08-04 at 16:32, Steve Ebersole wrote:
 Just wondering if there is a particular reason that in the JMX console
 java.lang.Boolean

RE: [JBoss-dev] JMX console

[Steve Ebersole]

P.S. Sorry if this stuff should go in the forums.  I just could not find
one related to the jmx-console.

If it should go in one of the forums, please just point me to which one
:)


-Original Message-
From: [EMAIL PROTECTED]
[mailto:[EMAIL PROTECTED] On Behalf Of
Steve Ebersole
Sent: Friday, August 05, 2005 10:06 AM
To: jboss-development@lists.sourceforge.net
Subject: RE: [JBoss-dev] JMX console

AFAICT, this would require the following changes:

1) org.jboss.util.propertyeditor.BooleanEditor so that:
   public void setAsText(final String text)
   {
  Object newValue = Boolean.valueOf(text);
  setValue(newValue);
   }
becomes: 
   public void setAsText(final String text) {
  if ( text == null || .equals( text ) || null.equals( text ) )
{
 setValue( null );
  }
  else {
 setValue( Boolean.valueOf( text ) );
  }
   }
(or whatever we deem is valid null string representation)

In my testing, that's it.  A lookup on boolean vs. java.lang.Boolean
returns different editors; sun.beans.editors.BoolEditor (primitive) vs.
org.jboss.util.propertyeditor.BooleanEditor (wrapper).  Not sure whether
there is existing code which exposes java.lang.Boolean attributes and
relies on this behavior of never getting null values (not sure why they
expose the wrapper type anyway though if that is the case).

Test code:

public static void main(String[] args) {

// snipped and modified from 
// org.jboss.util.propertyeditor.PropertyEditors
String[] currentPath = PropertyEditorManager.getEditorSearchPath();
int length = currentPath != null ? currentPath.length : 0;
String[] newPath = new String[length + 1];
System.arraycopy( currentPath, 0, newPath, 1, length );
// register my local package with modified BooleanEditor
newPath[0] = booleaneditor;
PropertyEditorManager.setEditorSearchPath( newPath );

// prepare for tests
PropertyEditor editor = null;
PropertyChangeListener listener = new PropertyChangeListener() {
public void propertyChange(PropertyChangeEvent evt) {
PropertyEditor editor = ( PropertyEditor ) evt.getSource();
System.out.println( 
editor.getValue() == null ? [null] :
editor.getValue() 
);
}
};

// start tests...

try {
System.out.println( standard boolean editor ... );
System.out.println( --- );
editor = PropertyEditorManager.findEditor( boolean.class );
System.out.println( editor =  + editor );
editor.addPropertyChangeListener( listener );
editor.setAsText(  );
editor.setAsText( null );
editor.setAsText( null );
editor.removePropertyChangeListener( listener );
}
catch ( IllegalArgumentException e ) {
System.out.println( IAE error occured (as expected) );
}

System.out.println();
System.out.println( standard Boolean editor ... );
System.out.println( --- );
editor = PropertyEditorManager.findEditor( Boolean.class );
System.out.println( editor =  + editor );
editor.addPropertyChangeListener( listener );
editor.setAsText(  );
editor.setAsText( null );
editor.setAsText( null );
editor.removePropertyChangeListener( listener );
}


Results in:

standard boolean editor ...
---
editor = [EMAIL PROTECTED]
IAE error occured (as expected)

standard Boolean editor ...
---
editor = [EMAIL PROTECTED]
[null]
[null]
[null]


Which all seems reasonable behavior.


-Original Message-
From: [EMAIL PROTECTED]
[mailto:[EMAIL PROTECTED] On Behalf Of
Steve Ebersole
Sent: Thursday, August 04, 2005 4:08 PM
To: jboss-development@lists.sourceforge.net
Subject: RE: [JBoss-dev] JMX console

Not sure what you mean by supports null.  If certainly understands the
difference between boolean and java.lang.Boolean during display.  The
jsp just explicitly chooses to render the input controls the same in
both instances:
if( attrType.equals(boolean) || attrType.equals(java.lang.Boolean) )
{
...
}

Also, there is a call to AttrResultInfo.getAsText() which just calls a
PropertyEditor; now unfortunately, that
org.jboss.util.propertyeditor.BooleanEditor does not support null (it
just always calls Boolean.valueOf() which *never* returns null).

So the situation is that I recently converted the HibernateMBean to use
smarter types.  It used to expose everything as string (now I think I
see why).  I wanted this to change so that it exposed a more type-safe
interface.  For the majority of the booleans though, Hibernate uses
various default values if the user does not specify a value; but in
JBoss, if they go through the jmx-console as it stands now, they will
never be able to not specify something because null is not an
option.

-Original Message-
From: [EMAIL PROTECTED]
[mailto:[EMAIL PROTECTED] On Behalf Of
Adrian Brock
Sent

RE: [JBoss-dev] JMX console

[Steve Ebersole]

Ok, sure, if your going to get technical... ;)

-Original Message-
From: [EMAIL PROTECTED]
[mailto:[EMAIL PROTECTED] On Behalf Of
Adrian Brock
Sent: Friday, August 05, 2005 11:24 AM
To: jboss-development@lists.sourceforge.net
Subject: RE: [JBoss-dev] JMX console

One obvious bug is that you need a text.trim() if you are going
to use equals(String). :-)

On Fri, 2005-08-05 at 11:05, Steve Ebersole wrote:
 AFAICT, this would require the following changes:
 
 1) org.jboss.util.propertyeditor.BooleanEditor so that:
public void setAsText(final String text)
{
   Object newValue = Boolean.valueOf(text);
   setValue(newValue);
}
 becomes: 
public void setAsText(final String text) {
   if ( text == null || .equals( text ) || null.equals( text )
)
 {
  setValue( null );
   }
   else {
  setValue( Boolean.valueOf( text ) );
   }
}
 (or whatever we deem is valid null string representation)
 
 In my testing, that's it.  A lookup on boolean vs. java.lang.Boolean
 returns different editors; sun.beans.editors.BoolEditor (primitive)
vs.
 org.jboss.util.propertyeditor.BooleanEditor (wrapper).  Not sure
whether
 there is existing code which exposes java.lang.Boolean attributes and
 relies on this behavior of never getting null values (not sure why
they
 expose the wrapper type anyway though if that is the case).
 
 Test code:
 
 public static void main(String[] args) {
 
 // snipped and modified from 
 // org.jboss.util.propertyeditor.PropertyEditors
 String[] currentPath =
PropertyEditorManager.getEditorSearchPath();
 int length = currentPath != null ? currentPath.length : 0;
 String[] newPath = new String[length + 1];
 System.arraycopy( currentPath, 0, newPath, 1, length );
 // register my local package with modified BooleanEditor
 newPath[0] = booleaneditor;
 PropertyEditorManager.setEditorSearchPath( newPath );
 
 // prepare for tests
 PropertyEditor editor = null;
 PropertyChangeListener listener = new PropertyChangeListener() {
 public void propertyChange(PropertyChangeEvent evt) {
 PropertyEditor editor = ( PropertyEditor )
evt.getSource();
 System.out.println( 
 editor.getValue() == null ? [null] :
 editor.getValue() 
 );
 }
 };
 
 // start tests...
 
 try {
 System.out.println( standard boolean editor ... );
 System.out.println( --- );
 editor = PropertyEditorManager.findEditor( boolean.class );
 System.out.println( editor =  + editor );
 editor.addPropertyChangeListener( listener );
 editor.setAsText(  );
 editor.setAsText( null );
 editor.setAsText( null );
 editor.removePropertyChangeListener( listener );
 }
 catch ( IllegalArgumentException e ) {
 System.out.println( IAE error occured (as expected) );
 }
 
 System.out.println();
 System.out.println( standard Boolean editor ... );
 System.out.println( --- );
 editor = PropertyEditorManager.findEditor( Boolean.class );
 System.out.println( editor =  + editor );
 editor.addPropertyChangeListener( listener );
 editor.setAsText(  );
 editor.setAsText( null );
 editor.setAsText( null );
 editor.removePropertyChangeListener( listener );
 }
 
 
 Results in:
 
 standard boolean editor ...
 ---
 editor = [EMAIL PROTECTED]
 IAE error occured (as expected)
 
 standard Boolean editor ...
 ---
 editor = [EMAIL PROTECTED]
 [null]
 [null]
 [null]
 
 
 Which all seems reasonable behavior.
 
 
 -Original Message-
 From: [EMAIL PROTECTED]
 [mailto:[EMAIL PROTECTED] On Behalf Of
 Steve Ebersole
 Sent: Thursday, August 04, 2005 4:08 PM
 To: jboss-development@lists.sourceforge.net
 Subject: RE: [JBoss-dev] JMX console
 
 Not sure what you mean by supports null.  If certainly understands
the
 difference between boolean and java.lang.Boolean during display.  The
 jsp just explicitly chooses to render the input controls the same in
 both instances:
 if( attrType.equals(boolean) || attrType.equals(java.lang.Boolean)
)
 {
 ...
 }
 
 Also, there is a call to AttrResultInfo.getAsText() which just calls a
 PropertyEditor; now unfortunately, that
 org.jboss.util.propertyeditor.BooleanEditor does not support null
(it
 just always calls Boolean.valueOf() which *never* returns null).
 
 So the situation is that I recently converted the HibernateMBean to
use
 smarter types.  It used to expose everything as string (now I think
I
 see why).  I wanted this to change so that it exposed a more type-safe
 interface.  For the majority of the booleans though, Hibernate uses
 various default values if the user does not specify a value; but in
 JBoss, if they go through the jmx-console as it stands now, they will
 never be able to not specify something

[JBoss-dev] [JBoss JIRA] Commented: (HIBERNATE-12) HibernateContext JDBC Connection

[Steve Ebersole (JIRA)]

 [ 
http://jira.jboss.com/jira/browse/HIBERNATE-12?page=comments#action_12316785 ]
 
Steve Ebersole commented on HIBERNATE-12:
-

Sorry if I was not clear.  The new code integration code I have locally 
upgrading the support to Hibernate3 will not be commited until *after* 4.0.2 is 
released.

 HibernateContext JDBC Connection
 

  Key: HIBERNATE-12
  URL: http://jira.jboss.com/jira/browse/HIBERNATE-12
  Project: Hibernate
 Type: Bug
  Environment: Mac OSX, JBoss 4.01sp1
 Reporter: Stephen Pearson
 Assignee: Steve Ebersole


 Original Estimate: 1 hour
 Remaining: 1 hour

 When using the HibernateContext getSession() function call, all works well 
 until the function call has finished, and then the underlying JDBC connection 
 is not closed.  Therefore with each call to getSession within my EJB I 
 promptly receieve a  Closing a connection for you.  Please close them 
 yourself. warning from the CachedConnectionManager.
 Can the TransactionSynch call please close the JDBC connection when it 
 flushes and closes the Hibernate Session.

-- 
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators:
   http://jira.jboss.com/jira/secure/Administrators.jspa
-
If you want more information on JIRA, or have a bug to report see:
   http://www.atlassian.com/software/jira



---
SF email is sponsored by - The IT Product Guide
Read honest  candid reviews on hundreds of IT Products from real users.
Discover which products truly live up to the hype. Start reading now.
http://ads.osdn.com/?ad_id=6595alloc_id=14396op=click
___
JBoss-Development mailing list
JBoss-Development@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/jboss-development

[JBoss-dev] [JBoss JIRA] Resolved: (HIBERNATE-5) jmx transaction flush swallows exception

[Steve Ebersole (JIRA)]

 [ http://jira.jboss.com/jira/browse/HIBERNATE-5?page=history ]
 
Steve Ebersole resolved HIBERNATE-5:


Resolution: Done

After further thought, this particular one is a trivial change so I went ahead 
and did this for 4.0.2.  An exception during flush processing in 
TransactionSynch now throws a TransactionSynch.FlushException.

 jmx transaction flush swallows exception
 

  Key: HIBERNATE-5
  URL: http://jira.jboss.com/jira/browse/HIBERNATE-5
  Project: Hibernate
 Type: Bug
  Environment: jboss-4.0.1  
 winxp
 postgresql
 Reporter: Ben Litchfield
 Assignee: Steve Ebersole



 A database exception, such as constraint violation, doesn't happen until a 
 session.flush().  In the JMX code this happens in the 
 org.jboss.hibernate.session.TransactionSynch.beforeCompletion() method, but 
 the exception is swallowed.  
 This needs to be changed to throw an exception to the user.  Otherwise no 
 exception is thrown to the user.
 Ben

-- 
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators:
   http://jira.jboss.com/jira/secure/Administrators.jspa
-
If you want more information on JIRA, or have a bug to report see:
   http://www.atlassian.com/software/jira



---
SF email is sponsored by - The IT Product Guide
Read honest  candid reviews on hundreds of IT Products from real users.
Discover which products truly live up to the hype. Start reading now.
http://ads.osdn.com/?ad_id=6595alloc_id=14396op=click
___
JBoss-Development mailing list
JBoss-Development@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/jboss-development

[JBoss-dev] [JBoss JIRA] Resolved: (JBAS-1576) Hibernate TransactionSynch should rollback transaction on session.flush exception

[Steve Ebersole (JIRA)]

 [ http://jira.jboss.com/jira/browse/JBAS-1576?page=history ]
 
Steve Ebersole resolved JBAS-1576:
--

 Resolution: Done
Fix Version: JBossAS-4.0.2 Final

After further thought, this particular one is a trivial change so I went ahead 
and did this for 4.0.2. An exception during flush processing in 
TransactionSynch now throws a TransactionSynch.FlushException. 

 Hibernate TransactionSynch should rollback transaction on session.flush 
 exception
 -

  Key: JBAS-1576
  URL: http://jira.jboss.com/jira/browse/JBAS-1576
  Project: JBoss Application Server
 Type: Bug
   Components: Hibernate service
 Versions:  JBossAS-4.0.1 SP1, JBossAS-4.0.1RC1, JBossAS-4.0.1 Final, 
 JBossAS-4.0.0 Final
  Environment: jboss 4, hibernate 2.2
 Reporter: Armin Haaf
 Assignee: Steve Ebersole
  Fix For: JBossAS-4.0.2 Final



 org.jboss.hibernate.session.TransactionSynch only logs a error on session 
 flush in beforeCompletion:
  try
  {
 log.trace(Flushing Session);
 session.flush();
  }
  catch(Throwable t)
  {
 log.warn(Error flushing session);
  }
 This leads to inconsistent transactions. A transaction is commited, but 
 should be rollbacked on a session.flush problem. In my opinion it should 
 throw a RuntimeException to rollback the transaction. 

-- 
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators:
   http://jira.jboss.com/jira/secure/Administrators.jspa
-
If you want more information on JIRA, or have a bug to report see:
   http://www.atlassian.com/software/jira



---
SF email is sponsored by - The IT Product Guide
Read honest  candid reviews on hundreds of IT Products from real users.
Discover which products truly live up to the hype. Start reading now.
http://ads.osdn.com/?ad_id=6595alloc_id=14396op=click
___
JBoss-Development mailing list
JBoss-Development@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/jboss-development

[JBoss-dev] [JBoss JIRA] Commented: (HIBERNATE-13) testEjbInterception Unit Test failure

[Steve Ebersole (JIRA)]

 [ 
http://jira.jboss.com/jira/browse/HIBERNATE-13?page=comments#action_12316779 ]
 
Steve Ebersole commented on HIBERNATE-13:
-

No the real issue happens (or was happening) well before that.  The service 
fails to start, hence nothing is ever put into JNDI and thus never found ;)

I'll just (try to) do a clean checkout of 4.0 tonight and look at it myself.  
I'm not able to simply update because I have a *lot* of pending changes waiting 
for 4.0.2 to be released.  

Note, I've not been able to grab a full checkout from CVS using my dev login 
for almost 4 weeks of trying now;  I always end up having to use Clebert's 
trick of doing an anon checkout and manually updating the local CVS meta files.

Ryan, maybe I could just do a anon checkout and do the fix and send you the 
patch to apply (if I am unable to get a developer checkout)?

 testEjbInterception Unit Test failure
 -

  Key: HIBERNATE-13
  URL: http://jira.jboss.com/jira/browse/HIBERNATE-13
  Project: Hibernate
 Type: Bug
  Environment: win xp sp2
 Reporter: Pushkala Iyer
 Assignee: Steve Ebersole



 The following test is failing in the 4.0 branch and needs to be resolved 
 before the 4.0.2 Final release.  We've tested this in multiple environments 
 and received the same error.
 Test Case: org.jboss.test.hibernate.test.HibernateIntgUnitTestCase
 Test : testEjbInterception
 Stack Trace: 
 RemoteException occurred in server thread; nested exception is: 
 java.rmi.ServerException: RuntimeException; nested exception is: 
 org.jboss.util.NestedRuntimeException: Unable to retreive Session; - nested 
 throwable: (net.sf.hibernate.HibernateException: Unable to locate 
 SessionFactory in JNDI under name [java:/hibernate/SessionFactory])
 java.rmi.ServerException: RemoteException occurred in server thread; nested 
 exception is: 
   java.rmi.ServerException: RuntimeException; nested exception is: 
   org.jboss.util.NestedRuntimeException: Unable to retreive Session; - 
 nested throwable: (net.sf.hibernate.HibernateException: Unable to locate 
 SessionFactory in JNDI under name [java:/hibernate/SessionFactory])
   at sun.rmi.server.UnicastServerRef.dispatch(UnicastServerRef.java:292)
   at sun.rmi.transport.Transport$1.run(Transport.java:148)
   at java.security.AccessController.doPrivileged(Native Method)
   at sun.rmi.transport.Transport.serviceCall(Transport.java:144)
   at 
 sun.rmi.transport.tcp.TCPTransport.handleMessages(TCPTransport.java:460)
   at 
 sun.rmi.transport.tcp.TCPTransport$ConnectionHandler.run(TCPTransport.java:701)
   at java.lang.Thread.run(Thread.java:534)
   at 
 sun.rmi.transport.StreamRemoteCall.exceptionReceivedFromServer(StreamRemoteCall.java:247)
   at 
 sun.rmi.transport.StreamRemoteCall.executeCall(StreamRemoteCall.java:223)
   at sun.rmi.server.UnicastRef.invoke(UnicastRef.java:133)
   at org.jboss.invocation.jrmp.server.JRMPInvoker_Stub.invoke(Unknown 
 Source)
   at 
 org.jboss.invocation.jrmp.interfaces.JRMPInvokerProxy.invoke(JRMPInvokerProxy.java:118)
   at 
 org.jboss.invocation.InvokerInterceptor.invokeInvoker(InvokerInterceptor.java:227)
   at 
 org.jboss.invocation.InvokerInterceptor.invoke(InvokerInterceptor.java:167)
   at 
 org.jboss.proxy.TransactionInterceptor.invoke(TransactionInterceptor.java:46)
   at 
 org.jboss.proxy.SecurityInterceptor.invoke(SecurityInterceptor.java:55)
   at 
 org.jboss.proxy.ejb.StatelessSessionInterceptor.invoke(StatelessSessionInterceptor.java:97)
   at org.jboss.proxy.ClientContainer.invoke(ClientContainer.java:86)
   at $Proxy2.storeUser(Unknown Source)
   at 
 org.jboss.test.hibernate.test.HibernateIntgUnitTestCase.testEjbInterception(HibernateIntgUnitTestCase.java:54)
   at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
   at 
 sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:39)
   at 
 sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25)
   at junit.extensions.TestDecorator.basicRun(TestDecorator.java:22)
   at junit.extensions.TestSetup$1.protect(TestSetup.java:19)
   at junit.extensions.TestSetup.run(TestSetup.java:23)
 Caused by: java.rmi.ServerException: RuntimeException; nested exception is: 
   org.jboss.util.NestedRuntimeException: Unable to retreive Session; - 
 nested throwable: (net.sf.hibernate.HibernateException: Unable to locate 
 SessionFactory in JNDI under name [java:/hibernate/SessionFactory])
   at 
 org.jboss.ejb.plugins.LogInterceptor.handleException(LogInterceptor.java:386)
   at org.jboss.ejb.plugins.LogInterceptor.invoke(LogInterceptor.java:196)
   at 
 org.jboss.ejb.plugins.ProxyFactoryFinderInterceptor.invoke(ProxyFactoryFinderInterceptor.java:122)
   at 
 org.jboss.ejb.SessionContainer.internalInvoke(SessionContainer.java:624

[JBoss-dev] [JBoss JIRA] Commented: (HIBERNATE-13) testEjbInterception Unit Test failure

[Steve Ebersole (JIRA)]

 [ 
http://jira.jboss.com/jira/browse/HIBERNATE-13?page=comments#action_12316783 ]
 
Steve Ebersole commented on HIBERNATE-13:
-

So did somebody change something?

I finally was able to get a clean check out (yaay!).  I built and ran the tests 
(sans any cheanges other than the ones from yesterday that Ryan mentions) and 
it ran fine.

 testEjbInterception Unit Test failure
 -

  Key: HIBERNATE-13
  URL: http://jira.jboss.com/jira/browse/HIBERNATE-13
  Project: Hibernate
 Type: Bug
  Environment: win xp sp2
 Reporter: Pushkala Iyer
 Assignee: Steve Ebersole



 The following test is failing in the 4.0 branch and needs to be resolved 
 before the 4.0.2 Final release.  We've tested this in multiple environments 
 and received the same error.
 Test Case: org.jboss.test.hibernate.test.HibernateIntgUnitTestCase
 Test : testEjbInterception
 Stack Trace: 
 RemoteException occurred in server thread; nested exception is: 
 java.rmi.ServerException: RuntimeException; nested exception is: 
 org.jboss.util.NestedRuntimeException: Unable to retreive Session; - nested 
 throwable: (net.sf.hibernate.HibernateException: Unable to locate 
 SessionFactory in JNDI under name [java:/hibernate/SessionFactory])
 java.rmi.ServerException: RemoteException occurred in server thread; nested 
 exception is: 
   java.rmi.ServerException: RuntimeException; nested exception is: 
   org.jboss.util.NestedRuntimeException: Unable to retreive Session; - 
 nested throwable: (net.sf.hibernate.HibernateException: Unable to locate 
 SessionFactory in JNDI under name [java:/hibernate/SessionFactory])
   at sun.rmi.server.UnicastServerRef.dispatch(UnicastServerRef.java:292)
   at sun.rmi.transport.Transport$1.run(Transport.java:148)
   at java.security.AccessController.doPrivileged(Native Method)
   at sun.rmi.transport.Transport.serviceCall(Transport.java:144)
   at 
 sun.rmi.transport.tcp.TCPTransport.handleMessages(TCPTransport.java:460)
   at 
 sun.rmi.transport.tcp.TCPTransport$ConnectionHandler.run(TCPTransport.java:701)
   at java.lang.Thread.run(Thread.java:534)
   at 
 sun.rmi.transport.StreamRemoteCall.exceptionReceivedFromServer(StreamRemoteCall.java:247)
   at 
 sun.rmi.transport.StreamRemoteCall.executeCall(StreamRemoteCall.java:223)
   at sun.rmi.server.UnicastRef.invoke(UnicastRef.java:133)
   at org.jboss.invocation.jrmp.server.JRMPInvoker_Stub.invoke(Unknown 
 Source)
   at 
 org.jboss.invocation.jrmp.interfaces.JRMPInvokerProxy.invoke(JRMPInvokerProxy.java:118)
   at 
 org.jboss.invocation.InvokerInterceptor.invokeInvoker(InvokerInterceptor.java:227)
   at 
 org.jboss.invocation.InvokerInterceptor.invoke(InvokerInterceptor.java:167)
   at 
 org.jboss.proxy.TransactionInterceptor.invoke(TransactionInterceptor.java:46)
   at 
 org.jboss.proxy.SecurityInterceptor.invoke(SecurityInterceptor.java:55)
   at 
 org.jboss.proxy.ejb.StatelessSessionInterceptor.invoke(StatelessSessionInterceptor.java:97)
   at org.jboss.proxy.ClientContainer.invoke(ClientContainer.java:86)
   at $Proxy2.storeUser(Unknown Source)
   at 
 org.jboss.test.hibernate.test.HibernateIntgUnitTestCase.testEjbInterception(HibernateIntgUnitTestCase.java:54)
   at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
   at 
 sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:39)
   at 
 sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25)
   at junit.extensions.TestDecorator.basicRun(TestDecorator.java:22)
   at junit.extensions.TestSetup$1.protect(TestSetup.java:19)
   at junit.extensions.TestSetup.run(TestSetup.java:23)
 Caused by: java.rmi.ServerException: RuntimeException; nested exception is: 
   org.jboss.util.NestedRuntimeException: Unable to retreive Session; - 
 nested throwable: (net.sf.hibernate.HibernateException: Unable to locate 
 SessionFactory in JNDI under name [java:/hibernate/SessionFactory])
   at 
 org.jboss.ejb.plugins.LogInterceptor.handleException(LogInterceptor.java:386)
   at org.jboss.ejb.plugins.LogInterceptor.invoke(LogInterceptor.java:196)
   at 
 org.jboss.ejb.plugins.ProxyFactoryFinderInterceptor.invoke(ProxyFactoryFinderInterceptor.java:122)
   at 
 org.jboss.ejb.SessionContainer.internalInvoke(SessionContainer.java:624)
   at org.jboss.ejb.Container.invoke(Container.java:873)
   at sun.reflect.GeneratedMethodAccessor315.invoke(Unknown Source)
   at 
 sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25)
   at 
 org.jboss.mx.interceptor.ReflectedDispatcher.invoke(ReflectedDispatcher.java:141)
   at org.jboss.mx.server.Invocation.dispatch(Invocation.java:80)
   at org.jboss.mx.server.Invocation.invoke(Invocation.java:72

[JBoss-dev] [JBoss JIRA] Assigned: (HIBERNATE-13) testEjbInterception Unit Test failure

[Steve Ebersole (JIRA)]

 [ http://jira.jboss.com/jira/browse/HIBERNATE-13?page=history ]

Steve Ebersole reassigned HIBERNATE-13:
---

Assign To: Ryan Campbell  (was: Steve Ebersole)

 testEjbInterception Unit Test failure
 -

  Key: HIBERNATE-13
  URL: http://jira.jboss.com/jira/browse/HIBERNATE-13
  Project: Hibernate
 Type: Bug
  Environment: win xp sp2
 Reporter: Pushkala Iyer
 Assignee: Ryan Campbell



 The following test is failing in the 4.0 branch and needs to be resolved 
 before the 4.0.2 Final release.  We've tested this in multiple environments 
 and received the same error.
 Test Case: org.jboss.test.hibernate.test.HibernateIntgUnitTestCase
 Test : testEjbInterception
 Stack Trace: 
 RemoteException occurred in server thread; nested exception is: 
 java.rmi.ServerException: RuntimeException; nested exception is: 
 org.jboss.util.NestedRuntimeException: Unable to retreive Session; - nested 
 throwable: (net.sf.hibernate.HibernateException: Unable to locate 
 SessionFactory in JNDI under name [java:/hibernate/SessionFactory])
 java.rmi.ServerException: RemoteException occurred in server thread; nested 
 exception is: 
   java.rmi.ServerException: RuntimeException; nested exception is: 
   org.jboss.util.NestedRuntimeException: Unable to retreive Session; - 
 nested throwable: (net.sf.hibernate.HibernateException: Unable to locate 
 SessionFactory in JNDI under name [java:/hibernate/SessionFactory])
   at sun.rmi.server.UnicastServerRef.dispatch(UnicastServerRef.java:292)
   at sun.rmi.transport.Transport$1.run(Transport.java:148)
   at java.security.AccessController.doPrivileged(Native Method)
   at sun.rmi.transport.Transport.serviceCall(Transport.java:144)
   at 
 sun.rmi.transport.tcp.TCPTransport.handleMessages(TCPTransport.java:460)
   at 
 sun.rmi.transport.tcp.TCPTransport$ConnectionHandler.run(TCPTransport.java:701)
   at java.lang.Thread.run(Thread.java:534)
   at 
 sun.rmi.transport.StreamRemoteCall.exceptionReceivedFromServer(StreamRemoteCall.java:247)
   at 
 sun.rmi.transport.StreamRemoteCall.executeCall(StreamRemoteCall.java:223)
   at sun.rmi.server.UnicastRef.invoke(UnicastRef.java:133)
   at org.jboss.invocation.jrmp.server.JRMPInvoker_Stub.invoke(Unknown 
 Source)
   at 
 org.jboss.invocation.jrmp.interfaces.JRMPInvokerProxy.invoke(JRMPInvokerProxy.java:118)
   at 
 org.jboss.invocation.InvokerInterceptor.invokeInvoker(InvokerInterceptor.java:227)
   at 
 org.jboss.invocation.InvokerInterceptor.invoke(InvokerInterceptor.java:167)
   at 
 org.jboss.proxy.TransactionInterceptor.invoke(TransactionInterceptor.java:46)
   at 
 org.jboss.proxy.SecurityInterceptor.invoke(SecurityInterceptor.java:55)
   at 
 org.jboss.proxy.ejb.StatelessSessionInterceptor.invoke(StatelessSessionInterceptor.java:97)
   at org.jboss.proxy.ClientContainer.invoke(ClientContainer.java:86)
   at $Proxy2.storeUser(Unknown Source)
   at 
 org.jboss.test.hibernate.test.HibernateIntgUnitTestCase.testEjbInterception(HibernateIntgUnitTestCase.java:54)
   at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
   at 
 sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:39)
   at 
 sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25)
   at junit.extensions.TestDecorator.basicRun(TestDecorator.java:22)
   at junit.extensions.TestSetup$1.protect(TestSetup.java:19)
   at junit.extensions.TestSetup.run(TestSetup.java:23)
 Caused by: java.rmi.ServerException: RuntimeException; nested exception is: 
   org.jboss.util.NestedRuntimeException: Unable to retreive Session; - 
 nested throwable: (net.sf.hibernate.HibernateException: Unable to locate 
 SessionFactory in JNDI under name [java:/hibernate/SessionFactory])
   at 
 org.jboss.ejb.plugins.LogInterceptor.handleException(LogInterceptor.java:386)
   at org.jboss.ejb.plugins.LogInterceptor.invoke(LogInterceptor.java:196)
   at 
 org.jboss.ejb.plugins.ProxyFactoryFinderInterceptor.invoke(ProxyFactoryFinderInterceptor.java:122)
   at 
 org.jboss.ejb.SessionContainer.internalInvoke(SessionContainer.java:624)
   at org.jboss.ejb.Container.invoke(Container.java:873)
   at sun.reflect.GeneratedMethodAccessor315.invoke(Unknown Source)
   at 
 sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25)
   at 
 org.jboss.mx.interceptor.ReflectedDispatcher.invoke(ReflectedDispatcher.java:141)
   at org.jboss.mx.server.Invocation.dispatch(Invocation.java:80)
   at org.jboss.mx.server.Invocation.invoke(Invocation.java:72)
   at 
 org.jboss.mx.server.AbstractMBeanInvoker.invoke(AbstractMBeanInvoker.java:249)
   at org.jboss.mx.server.MBeanServerImpl.invoke(MBeanServerImpl.java:644)
   at 
 org.jboss.invocation.jrmp.server.JRMPInvoker

[JBoss-dev] [JBoss JIRA] Commented: (JBAS-1372) HIbernateContext does not work well with CachedConnectionManager

[Steve Ebersole (JIRA)]

 [ 
http://jira.jboss.com/jira/browse/JBAS-1372?page=comments#action_12316732 ]
 
Steve Ebersole commented on JBAS-1372:
--

This will be fixed in the next release of the Hibernate integration code.  The 
integration code will be getting upgraded to support Hibernate3.  Two things we 
did in Hibernate3 will come into play here:
1) release connections eagerly in JTA environments (basically after every use);
2) ability to track current sessions (by transaction) in Hibernate itself in 
JTA environments.

All the required changes are sitting in my local sandbox and will get commited 
after JBoss 4.0.2 gets released.

 HIbernateContext does not work well with CachedConnectionManager
 

  Key: JBAS-1372
  URL: http://jira.jboss.com/jira/browse/JBAS-1372
  Project: JBoss Application Server
 Type: Bug
   Components: JCA service, Hibernate service
 Versions: JBossAS-4.0.1 Final
  Environment: Jboss 4.0.1
 Windows 2000
 JDK 1.5
 Reporter: janssk1
 Assignee: Steve Ebersole



 I'm trying to use the HibernateContext to create an hibernate session that 
 will be automatically flushed on JTA transaction commit. This works well but 
 the jboss log files are getting filled with warning messages from the 
 CachedConnectionManager. see below for a log file 
 I have a simple CMT SSB that gets the hibernate session using 
 HibernateContext, updates an object and that' s it. My code does not do any 
 transaction management or explicit hibernate flush. 
 After the method is finished, the transaction invoker will kick in and commit 
 the transaction. Since the transaction contains some synchronization 
 listeners, these will be notified appropriatly. Two listeners are available. 
 One listener attached by the HibernateContext (this one will flush and close 
 the session) and another one added by the CachedConnectionManager. This one 
 will try to close the connection if it was not properly closed. When the 
 hibernate listener tries to close the session, the cachedconnectionmanager 
 will be notified that the connection is closed. This should normally remove 
 the connection from its internal caches and also remove the automatic close 
 on transaction termination from the current transaction. Since the connection 
 is explicity closed, it does not need to be closed implicitly anymore. 
 However, this does not work as expected (see the trace). A looked a bit in 
 the code and the problem seems to be related to the interceptor stack. In a 
 standard jboss installation, an ejb is configured with (among others) a 
 transaction interceptor followed by a cachedconnectioninterceptor. The 
 cachedconnectioninterceptor sets some context (metaAwareObject = bean) on the 
 cachedconnectionmanager. However, in the finally block of the transaction 
 interceptor, the cachcedconnection interceptor is already finished and the 
 context is no longer available. This explains the 'Trying to return an 
 unknown connection' exception. The 'Closing connection for you' message is 
 related (i think) to the fact that the current transaction is no longer 
 active when the cachedconnection manager is notified of the connection close. 
 It the transaction is not active anymore, the cachedconnection manager does 
 not remove the automatic close on transaction termination. So after the 
 hibernate listener is finshed (connection closed), the other listener 
 attached by the cached connection manager kicks in and closes it once more. 
 I was able to get rid of all the (unnecessary) warning by simply removing the 
 cached connection interceptor. However, i would like to keep it since it 
 provides me basic stupidy protection.

-- 
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators:
   http://jira.jboss.com/jira/secure/Administrators.jspa
-
If you want more information on JIRA, or have a bug to report see:
   http://www.atlassian.com/software/jira



---
SF email is sponsored by - The IT Product Guide
Read honest  candid reviews on hundreds of IT Products from real users.
Discover which products truly live up to the hype. Start reading now.
http://ads.osdn.com/?ad_ide95alloc_id396op=click
___
JBoss-Development mailing list
JBoss-Development@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/jboss-development

[JBoss-dev] [JBoss JIRA] Commented: (JBAS-1576) Hibernate TransactionSynch should rollback transaction on session.flush exception

[Steve Ebersole (JIRA)]

 [ 
http://jira.jboss.com/jira/browse/JBAS-1576?page=comments#action_12316735 ]
 
Steve Ebersole commented on JBAS-1576:
--

The TransactionSynch is no longer needed in the new integration code.  The new 
code will upgrade to Hibernate3, where we added the capability inside Hibernate 
itself to track current session (by transsaction).

The needed work is all done in my local sandbox, but unfortunately I cannot 
commit it until after 4.0.2 has been released.  I'll leave this case open util 
after I can commit this new stuff.

 Hibernate TransactionSynch should rollback transaction on session.flush 
 exception
 -

  Key: JBAS-1576
  URL: http://jira.jboss.com/jira/browse/JBAS-1576
  Project: JBoss Application Server
 Type: Bug
   Components: Hibernate service
 Versions:  JBossAS-4.0.1 SP1, JBossAS-4.0.1RC1, JBossAS-4.0.1 Final, 
 JBossAS-4.0.0 Final
  Environment: jboss 4, hibernate 2.2
 Reporter: Armin Haaf
 Assignee: Steve Ebersole



 org.jboss.hibernate.session.TransactionSynch only logs a error on session 
 flush in beforeCompletion:
  try
  {
 log.trace(Flushing Session);
 session.flush();
  }
  catch(Throwable t)
  {
 log.warn(Error flushing session);
  }
 This leads to inconsistent transactions. A transaction is commited, but 
 should be rollbacked on a session.flush problem. In my opinion it should 
 throw a RuntimeException to rollback the transaction. 

-- 
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators:
   http://jira.jboss.com/jira/secure/Administrators.jspa
-
If you want more information on JIRA, or have a bug to report see:
   http://www.atlassian.com/software/jira



---
SF email is sponsored by - The IT Product Guide
Read honest  candid reviews on hundreds of IT Products from real users.
Discover which products truly live up to the hype. Start reading now.
http://ads.osdn.com/?ad_id=6595alloc_id=14396op=click
___
JBoss-Development mailing list
JBoss-Development@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/jboss-development

[JBoss-dev] [JBoss JIRA] Commented: (JBAS-1298) HAR Deployer JBCache config

[Steve Ebersole (JIRA)]

 [ 
http://jira.jboss.com/jira/browse/JBAS-1298?page=comments#action_12316736 ]
 
Steve Ebersole commented on JBAS-1298:
--

This is all done in my local sandbox, and will get committed after 4.0.2 is 
released.  It will (actually is already) also get applied to jboss-head.

Note that the new integration code will upgrade hibernate support to Hibernate3 
also...

 HAR Deployer  JBCache config
 

  Key: JBAS-1298
  URL: http://jira.jboss.com/jira/browse/JBAS-1298
  Project: JBoss Application Server
 Type: Feature Request
   Components: Hibernate service
 Versions: JBossAS-4.0.1 Final, JBossAS-3.2.6 Final
 Reporter: Andrew Oliver
 Assignee: Steve Ebersole


 Original Estimate: 6 hours
 Remaining: 6 hours

 Presently HAR deployer picks up JBCache config from its classloader.  It does 
 not use an MBean.  It should use an MBean (and we should be able to get stats 
 from it).  

-- 
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators:
   http://jira.jboss.com/jira/secure/Administrators.jspa
-
If you want more information on JIRA, or have a bug to report see:
   http://www.atlassian.com/software/jira



---
SF email is sponsored by - The IT Product Guide
Read honest  candid reviews on hundreds of IT Products from real users.
Discover which products truly live up to the hype. Start reading now.
http://ads.osdn.com/?ad_id=6595alloc_id=14396op=click
___
JBoss-Development mailing list
JBoss-Development@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/jboss-development

[JBoss-dev] [JBoss JIRA] Commented: (HIBERNATE-7) CLONE -PropertyNotFoundException on runtime HAR deployment

[Steve Ebersole (JIRA)]

 [ 
http://jira.jboss.com/jira/browse/HIBERNATE-7?page=comments#action_12316737 ]
 
Steve Ebersole commented on HIBERNATE-7:


I have never been able to reproduce this.  The testsuite also now contains 
tests specifically testing a hot redploy; it passes.  I am also not able to 
reproduce this by manually deploying/redeploying the test ear file.

I need some more info on your exact app setup.  Is it a stand-alone HAR you 
drop in deploy?  Do you access the bound session factory from another app 
then?  Is that other app dependant on the har?  etc

 CLONE -PropertyNotFoundException on runtime HAR deployment
 --

  Key: HIBERNATE-7
  URL: http://jira.jboss.com/jira/browse/HIBERNATE-7
  Project: Hibernate
 Type: Bug
 Reporter: Chris Buckley
 Assignee: Steve Ebersole



 SourceForge Submitter: treinar .
 OS: Linux 2.4.22-36mdkenterprise (i386)
 JVM: 1.4.2_06-b03
 I have a HAR archive, with one class: Pesticide.class
 and its hibernate mapping file. Pesticide class has to
 properties: id and name (with getter/setter methods). A
 META-INF/hibernate-service.xml is also provided.
 When deploying a HAR archive when JBoss runs, the
 deployment fails. The following Exception is thrown:
 net.sf.hibernate.PropertyNotFoundException: Could not
 find a setter for property name in class
 no.planteforsk.pvmdb.persistent.Pesticide
 However, when JBoss is restarted, the HAR deploys fine. 
 The Exception is thrown in
 net.sf.hibernate.property.BasicPropertyAccessor, in the
 method getSetter. The cause of the exception is that no
 match between set method (setName) and property (name)
 is found in method setterMethod.
 I inserted a few debug outputs in
 BasicPropertyAccessor, and it turns out that when the
 HAR is deployed at runtime, the method setName in
 Pesticide is wrongly assumed to take no parameters,
 (methods[i].getParameterTypes().length returns 0). When
 jboss is restarted, and the deployment takes place on
 the same HAR file, setName is assumed to take 1
 parameter, which of course is correct.
 I'm not sure if this is a Java error or a JBoss error,
 or even a Hibernate error, but maybe you do. It does
 concern JBoss, however.

-- 
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators:
   http://jira.jboss.com/jira/secure/Administrators.jspa
-
If you want more information on JIRA, or have a bug to report see:
   http://www.atlassian.com/software/jira



---
SF email is sponsored by - The IT Product Guide
Read honest  candid reviews on hundreds of IT Products from real users.
Discover which products truly live up to the hype. Start reading now.
http://ads.osdn.com/?ad_id=6595alloc_id=14396op=click
___
JBoss-Development mailing list
JBoss-Development@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/jboss-development

[JBoss-dev] [JBoss JIRA] Commented: (JBAS-1304) Abillity to add DB-specific hints into Hibernate

[Steve Ebersole (JIRA)]

 [ 
http://jira.jboss.com/jira/browse/JBAS-1304?page=comments#action_12316738 ]
 
Steve Ebersole commented on JBAS-1304:
--

We already have an existing jira task to add this support.

 Abillity to add DB-specific hints into Hibernate
 --

  Key: JBAS-1304
  URL: http://jira.jboss.com/jira/browse/JBAS-1304
  Project: JBoss Application Server
 Type: Feature Request
   Components: Hibernate service
 Versions: JBossAS-4.0.1 Final, JBossAS-3.2.6 Final
 Reporter: Andrew Oliver
 Assignee: Steve Ebersole


 Original Estimate: 1 day
 Remaining: 1 day

 Customer has requested abillity to add hints to the underbelly of hibernate 
 esp for use with MViews.

-- 
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators:
   http://jira.jboss.com/jira/secure/Administrators.jspa
-
If you want more information on JIRA, or have a bug to report see:
   http://www.atlassian.com/software/jira



---
SF email is sponsored by - The IT Product Guide
Read honest  candid reviews on hundreds of IT Products from real users.
Discover which products truly live up to the hype. Start reading now.
http://ads.osdn.com/?ad_id=6595alloc_id=14396op=click
___
JBoss-Development mailing list
JBoss-Development@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/jboss-development

[JBoss-dev] [JBoss JIRA] Assigned: (HIBERNATE-10) DeployedTreeCacheProvider doesn't work with Hibernate 2.1.8+

[Steve Ebersole (JIRA)]

 [ http://jira.jboss.com/jira/browse/HIBERNATE-10?page=history ]

Steve Ebersole reassigned HIBERNATE-10:
---

Assign To: Steve Ebersole  (was: Gavin King)

 DeployedTreeCacheProvider doesn't work with Hibernate 2.1.8+
 

  Key: HIBERNATE-10
  URL: http://jira.jboss.com/jira/browse/HIBERNATE-10
  Project: Hibernate
 Type: Bug
 Reporter: youngm
 Assignee: Steve Ebersole



 DeployedTreeCacheProvider must be updated to support interface changes made 
 to net.sf.hibernate.cache.CacheProvider in 2.1.8.
 http://forum.hibernate.org/viewtopic.php?t=940501

-- 
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators:
   http://jira.jboss.com/jira/secure/Administrators.jspa
-
If you want more information on JIRA, or have a bug to report see:
   http://www.atlassian.com/software/jira



---
SF email is sponsored by - The IT Product Guide
Read honest  candid reviews on hundreds of IT Products from real users.
Discover which products truly live up to the hype. Start reading now.
http://ads.osdn.com/?ad_id=6595alloc_id=14396op=click
___
JBoss-Development mailing list
JBoss-Development@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/jboss-development

[JBoss-dev] [JBoss JIRA] Commented: (HIBERNATE-10) DeployedTreeCacheProvider doesn't work with Hibernate 2.1.8+

[Steve Ebersole (JIRA)]

 [ 
http://jira.jboss.com/jira/browse/HIBERNATE-10?page=comments#action_12316739 ]
 
Steve Ebersole commented on HIBERNATE-10:
-

As I mentoned on the forum, the DeployedTreeCacheProvider has been reworked.  
The code will be committed after JBoss 4.0.2 is released.

 DeployedTreeCacheProvider doesn't work with Hibernate 2.1.8+
 

  Key: HIBERNATE-10
  URL: http://jira.jboss.com/jira/browse/HIBERNATE-10
  Project: Hibernate
 Type: Bug
 Reporter: youngm
 Assignee: Steve Ebersole



 DeployedTreeCacheProvider must be updated to support interface changes made 
 to net.sf.hibernate.cache.CacheProvider in 2.1.8.
 http://forum.hibernate.org/viewtopic.php?t=940501

-- 
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators:
   http://jira.jboss.com/jira/secure/Administrators.jspa
-
If you want more information on JIRA, or have a bug to report see:
   http://www.atlassian.com/software/jira



---
SF email is sponsored by - The IT Product Guide
Read honest  candid reviews on hundreds of IT Products from real users.
Discover which products truly live up to the hype. Start reading now.
http://ads.osdn.com/?ad_id=6595alloc_id=14396op=click
___
JBoss-Development mailing list
JBoss-Development@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/jboss-development

[JBoss-dev] [JBoss JIRA] Assigned: (HIBERNATE-5) jmx transaction flush swallows exception

[Steve Ebersole (JIRA)]

 [ http://jira.jboss.com/jira/browse/HIBERNATE-5?page=history ]

Steve Ebersole reassigned HIBERNATE-5:
--

Assign To: Steve Ebersole  (was: Gavin King)

 jmx transaction flush swallows exception
 

  Key: HIBERNATE-5
  URL: http://jira.jboss.com/jira/browse/HIBERNATE-5
  Project: Hibernate
 Type: Bug
  Environment: jboss-4.0.1  
 winxp
 postgresql
 Reporter: Ben Litchfield
 Assignee: Steve Ebersole



 A database exception, such as constraint violation, doesn't happen until a 
 session.flush().  In the JMX code this happens in the 
 org.jboss.hibernate.session.TransactionSynch.beforeCompletion() method, but 
 the exception is swallowed.  
 This needs to be changed to throw an exception to the user.  Otherwise no 
 exception is thrown to the user.
 Ben

-- 
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators:
   http://jira.jboss.com/jira/secure/Administrators.jspa
-
If you want more information on JIRA, or have a bug to report see:
   http://www.atlassian.com/software/jira



---
SF email is sponsored by - The IT Product Guide
Read honest  candid reviews on hundreds of IT Products from real users.
Discover which products truly live up to the hype. Start reading now.
http://ads.osdn.com/?ad_id=6595alloc_id=14396op=click
___
JBoss-Development mailing list
JBoss-Development@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/jboss-development

[JBoss-dev] [JBoss JIRA] Assigned: (HIBERNATE-12) HibernateContext JDBC Connection

[Steve Ebersole (JIRA)]

 [ http://jira.jboss.com/jira/browse/HIBERNATE-12?page=history ]

Steve Ebersole reassigned HIBERNATE-12:
---

Assign To: Steve Ebersole  (was: Gavin King)

 HibernateContext JDBC Connection
 

  Key: HIBERNATE-12
  URL: http://jira.jboss.com/jira/browse/HIBERNATE-12
  Project: Hibernate
 Type: Bug
  Environment: Mac OSX, JBoss 4.01sp1
 Reporter: Stephen Pearson
 Assignee: Steve Ebersole


 Original Estimate: 1 hour
 Remaining: 1 hour

 When using the HibernateContext getSession() function call, all works well 
 until the function call has finished, and then the underlying JDBC connection 
 is not closed.  Therefore with each call to getSession within my EJB I 
 promptly receieve a  Closing a connection for you.  Please close them 
 yourself. warning from the CachedConnectionManager.
 Can the TransactionSynch call please close the JDBC connection when it 
 flushes and closes the Hibernate Session.

-- 
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators:
   http://jira.jboss.com/jira/secure/Administrators.jspa
-
If you want more information on JIRA, or have a bug to report see:
   http://www.atlassian.com/software/jira



---
SF email is sponsored by - The IT Product Guide
Read honest  candid reviews on hundreds of IT Products from real users.
Discover which products truly live up to the hype. Start reading now.
http://ads.osdn.com/?ad_id=6595alloc_id=14396op=click
___
JBoss-Development mailing list
JBoss-Development@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/jboss-development

[JBoss-dev] [JBoss JIRA] Commented: (HIBERNATE-12) HibernateContext JDBC Connection

[Steve Ebersole (JIRA)]

 [ 
http://jira.jboss.com/jira/browse/HIBERNATE-12?page=comments#action_12316740 ]
 
Steve Ebersole commented on HIBERNATE-12:
-

Its not that it does not close the Connection; its that the Connection gets 
closed too late.  This only happens when you nest ejb calls where the first ejb 
gets the session (the connection has not yet been obtained) and then call into 
another ejb which gets the session and uses it.

The JBoss CCM sees that the connection was obtained during ejb2's call, but was 
not returned to the data source prior to ejb2's return.

I am in the process of upgrading the inetgration code to Hibernate3, where we 
implemented releasing of the jdbc connections much more eagerly in JTA 
environment.  This new code will be available in CVS after JBoss 4.0.2 is 
released.

 HibernateContext JDBC Connection
 

  Key: HIBERNATE-12
  URL: http://jira.jboss.com/jira/browse/HIBERNATE-12
  Project: Hibernate
 Type: Bug
  Environment: Mac OSX, JBoss 4.01sp1
 Reporter: Stephen Pearson
 Assignee: Steve Ebersole


 Original Estimate: 1 hour
 Remaining: 1 hour

 When using the HibernateContext getSession() function call, all works well 
 until the function call has finished, and then the underlying JDBC connection 
 is not closed.  Therefore with each call to getSession within my EJB I 
 promptly receieve a  Closing a connection for you.  Please close them 
 yourself. warning from the CachedConnectionManager.
 Can the TransactionSynch call please close the JDBC connection when it 
 flushes and closes the Hibernate Session.

-- 
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators:
   http://jira.jboss.com/jira/secure/Administrators.jspa
-
If you want more information on JIRA, or have a bug to report see:
   http://www.atlassian.com/software/jira



---
SF email is sponsored by - The IT Product Guide
Read honest  candid reviews on hundreds of IT Products from real users.
Discover which products truly live up to the hype. Start reading now.
http://ads.osdn.com/?ad_id=6595alloc_id=14396op=click
___
JBoss-Development mailing list
JBoss-Development@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/jboss-development

[JBoss-dev] [JBoss JIRA] Assigned: (HIBERNATE-11) DeployedTreeCacheProvider must be updated to support JBossCache 1.2.1

[Steve Ebersole (JIRA)]

 [ http://jira.jboss.com/jira/browse/HIBERNATE-11?page=history ]

Steve Ebersole reassigned HIBERNATE-11:
---

Assign To: Steve Ebersole  (was: Gavin King)

 DeployedTreeCacheProvider must be updated to support JBossCache 1.2.1
 -

  Key: HIBERNATE-11
  URL: http://jira.jboss.com/jira/browse/HIBERNATE-11
  Project: Hibernate
 Type: Bug
 Reporter: youngm
 Assignee: Steve Ebersole
  Attachments: hibernate-cache.diff


 When retrieving JBossCache from JNDI DeployedTreeCacheProvider must cast the 
 returned instance to org.jboss.cache.TreeCacheMBean not 
 org.jboss.cache.TreeCache.
 Mike
 See stacktrace below:
 13:25:29,883 ERROR [Hibernate] Starting failed 
 jboss.har:service=am_data/HibernateFactory
 net.sf.hibernate.HibernateException: Could not instantiate Cache
   at 
 net.sf.hibernate.cfg.Configuration.configureCaches(Configuration.java:1138)
   at 
 net.sf.hibernate.cfg.Configuration.buildSessionFactory(Configuration.java:795)
   at 
 org.jboss.hibernate.jmx.Hibernate.buildSessionFactory(Hibernate.java:583)
   at org.jboss.hibernate.jmx.Hibernate.startService(Hibernate.java:551)
   at 
 org.jboss.system.ServiceMBeanSupport.jbossInternalStart(ServiceMBeanSupport.java:272)
   at 
 org.jboss.system.ServiceMBeanSupport.jbossInternalLifecycle(ServiceMBeanSupport.java:222)
   at sun.reflect.GeneratedMethodAccessor42.invoke(Unknown Source)
   at 
 sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25)
   at java.lang.reflect.Method.invoke(Method.java:585)
   at 
 org.jboss.mx.interceptor.ReflectedDispatcher.invoke(ReflectedDispatcher.java:144)
   at org.jboss.mx.server.Invocation.dispatch(Invocation.java:80)
   at org.jboss.mx.server.Invocation.invoke(Invocation.java:72)
   at 
 org.jboss.mx.server.AbstractMBeanInvoker.invoke(AbstractMBeanInvoker.java:249)
   at org.jboss.mx.server.MBeanServerImpl.invoke(MBeanServerImpl.java:644)
   at 
 org.jboss.system.ServiceController$ServiceProxy.invoke(ServiceController.java:911)
   at $Proxy0.start(Unknown Source)
   at org.jboss.system.ServiceController.start(ServiceController.java:416)
   at sun.reflect.GeneratedMethodAccessor5.invoke(Unknown Source)
   at 
 sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25)
   at java.lang.reflect.Method.invoke(Method.java:585)
   at 
 org.jboss.mx.interceptor.ReflectedDispatcher.invoke(ReflectedDispatcher.java:144)
   at org.jboss.mx.server.Invocation.dispatch(Invocation.java:80)
   at org.jboss.mx.server.Invocation.invoke(Invocation.java:72)
   at 
 org.jboss.mx.server.AbstractMBeanInvoker.invoke(AbstractMBeanInvoker.java:249)
   at org.jboss.mx.server.MBeanServerImpl.invoke(MBeanServerImpl.java:644)
   at org.jboss.mx.util.MBeanProxyExt.invoke(MBeanProxyExt.java:177)
   at $Proxy4.start(Unknown Source)
   at org.jboss.deployment.SARDeployer.start(SARDeployer.java:273)
   at org.jboss.deployment.MainDeployer.start(MainDeployer.java:964)
   at org.jboss.deployment.MainDeployer.start(MainDeployer.java:956)
   at org.jboss.deployment.MainDeployer.deploy(MainDeployer.java:775)
   at org.jboss.deployment.MainDeployer.deploy(MainDeployer.java:738)
   at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
   at 
 sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:39)
   at 
 sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25)
   at java.lang.reflect.Method.invoke(Method.java:585)
   at 
 org.jboss.mx.interceptor.ReflectedDispatcher.invoke(ReflectedDispatcher.java:144)
   at org.jboss.mx.server.Invocation.dispatch(Invocation.java:80)
   at 
 org.jboss.mx.interceptor.AbstractInterceptor.invoke(AbstractInterceptor.java:122)
   at org.jboss.mx.server.Invocation.invoke(Invocation.java:74)
   at 
 org.jboss.mx.interceptor.ModelMBeanOperationInterceptor.invoke(ModelMBeanOperationInterceptor.java:131)
   at org.jboss.mx.server.Invocation.invoke(Invocation.java:74)
   at 
 org.jboss.mx.server.AbstractMBeanInvoker.invoke(AbstractMBeanInvoker.java:249)
   at org.jboss.mx.server.MBeanServerImpl.invoke(MBeanServerImpl.java:644)
   at org.jboss.mx.util.MBeanProxyExt.invoke(MBeanProxyExt.java:177)
   at $Proxy7.deploy(Unknown Source)
   at 
 org.jboss.deployment.scanner.URLDeploymentScanner.deploy(URLDeploymentScanner.java:325)
   at 
 org.jboss.deployment.scanner.URLDeploymentScanner.scan(URLDeploymentScanner.java:483)
   at 
 org.jboss.deployment.scanner.AbstractDeploymentScanner$ScannerThread.doScan(AbstractDeploymentScanner.java:204)
   at 
 org.jboss.deployment.scanner.AbstractDeploymentScanner$ScannerThread.loop(AbstractDeploymentScanner.java:215

[JBoss-dev] [JBoss JIRA] Commented: (HIBERNATE-11) DeployedTreeCacheProvider must be updated to support JBossCache 1.2.1

[Steve Ebersole (JIRA)]

 [ 
http://jira.jboss.com/jira/browse/HIBERNATE-11?page=comments#action_12316741 ]
 
Steve Ebersole commented on HIBERNATE-11:
-

As I mentioned previously, this is fixed in my local saandbox.  It will be 
committed after 4.0.2 is released.

 DeployedTreeCacheProvider must be updated to support JBossCache 1.2.1
 -

  Key: HIBERNATE-11
  URL: http://jira.jboss.com/jira/browse/HIBERNATE-11
  Project: Hibernate
 Type: Bug
 Reporter: youngm
 Assignee: Steve Ebersole
  Attachments: hibernate-cache.diff


 When retrieving JBossCache from JNDI DeployedTreeCacheProvider must cast the 
 returned instance to org.jboss.cache.TreeCacheMBean not 
 org.jboss.cache.TreeCache.
 Mike
 See stacktrace below:
 13:25:29,883 ERROR [Hibernate] Starting failed 
 jboss.har:service=am_data/HibernateFactory
 net.sf.hibernate.HibernateException: Could not instantiate Cache
   at 
 net.sf.hibernate.cfg.Configuration.configureCaches(Configuration.java:1138)
   at 
 net.sf.hibernate.cfg.Configuration.buildSessionFactory(Configuration.java:795)
   at 
 org.jboss.hibernate.jmx.Hibernate.buildSessionFactory(Hibernate.java:583)
   at org.jboss.hibernate.jmx.Hibernate.startService(Hibernate.java:551)
   at 
 org.jboss.system.ServiceMBeanSupport.jbossInternalStart(ServiceMBeanSupport.java:272)
   at 
 org.jboss.system.ServiceMBeanSupport.jbossInternalLifecycle(ServiceMBeanSupport.java:222)
   at sun.reflect.GeneratedMethodAccessor42.invoke(Unknown Source)
   at 
 sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25)
   at java.lang.reflect.Method.invoke(Method.java:585)
   at 
 org.jboss.mx.interceptor.ReflectedDispatcher.invoke(ReflectedDispatcher.java:144)
   at org.jboss.mx.server.Invocation.dispatch(Invocation.java:80)
   at org.jboss.mx.server.Invocation.invoke(Invocation.java:72)
   at 
 org.jboss.mx.server.AbstractMBeanInvoker.invoke(AbstractMBeanInvoker.java:249)
   at org.jboss.mx.server.MBeanServerImpl.invoke(MBeanServerImpl.java:644)
   at 
 org.jboss.system.ServiceController$ServiceProxy.invoke(ServiceController.java:911)
   at $Proxy0.start(Unknown Source)
   at org.jboss.system.ServiceController.start(ServiceController.java:416)
   at sun.reflect.GeneratedMethodAccessor5.invoke(Unknown Source)
   at 
 sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25)
   at java.lang.reflect.Method.invoke(Method.java:585)
   at 
 org.jboss.mx.interceptor.ReflectedDispatcher.invoke(ReflectedDispatcher.java:144)
   at org.jboss.mx.server.Invocation.dispatch(Invocation.java:80)
   at org.jboss.mx.server.Invocation.invoke(Invocation.java:72)
   at 
 org.jboss.mx.server.AbstractMBeanInvoker.invoke(AbstractMBeanInvoker.java:249)
   at org.jboss.mx.server.MBeanServerImpl.invoke(MBeanServerImpl.java:644)
   at org.jboss.mx.util.MBeanProxyExt.invoke(MBeanProxyExt.java:177)
   at $Proxy4.start(Unknown Source)
   at org.jboss.deployment.SARDeployer.start(SARDeployer.java:273)
   at org.jboss.deployment.MainDeployer.start(MainDeployer.java:964)
   at org.jboss.deployment.MainDeployer.start(MainDeployer.java:956)
   at org.jboss.deployment.MainDeployer.deploy(MainDeployer.java:775)
   at org.jboss.deployment.MainDeployer.deploy(MainDeployer.java:738)
   at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
   at 
 sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:39)
   at 
 sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25)
   at java.lang.reflect.Method.invoke(Method.java:585)
   at 
 org.jboss.mx.interceptor.ReflectedDispatcher.invoke(ReflectedDispatcher.java:144)
   at org.jboss.mx.server.Invocation.dispatch(Invocation.java:80)
   at 
 org.jboss.mx.interceptor.AbstractInterceptor.invoke(AbstractInterceptor.java:122)
   at org.jboss.mx.server.Invocation.invoke(Invocation.java:74)
   at 
 org.jboss.mx.interceptor.ModelMBeanOperationInterceptor.invoke(ModelMBeanOperationInterceptor.java:131)
   at org.jboss.mx.server.Invocation.invoke(Invocation.java:74)
   at 
 org.jboss.mx.server.AbstractMBeanInvoker.invoke(AbstractMBeanInvoker.java:249)
   at org.jboss.mx.server.MBeanServerImpl.invoke(MBeanServerImpl.java:644)
   at org.jboss.mx.util.MBeanProxyExt.invoke(MBeanProxyExt.java:177)
   at $Proxy7.deploy(Unknown Source)
   at 
 org.jboss.deployment.scanner.URLDeploymentScanner.deploy(URLDeploymentScanner.java:325)
   at 
 org.jboss.deployment.scanner.URLDeploymentScanner.scan(URLDeploymentScanner.java:483)
   at 
 org.jboss.deployment.scanner.AbstractDeploymentScanner$ScannerThread.doScan(AbstractDeploymentScanner.java:204

[JBoss-dev] [JBoss JIRA] Closed: (HIBERNATE-9) local application of naming strategy

[Steve Ebersole (JIRA)]

 [ http://jira.jboss.com/jira/browse/HIBERNATE-9?page=history ]
 
Steve Ebersole closed HIBERNATE-9:
--

 Assign To: Steve Ebersole  (was: Gavin King)
Resolution: Rejected

Until the Hibernate JIRA is transferred over to this JIRA box, all requests for 
Hibernate-specific enhancements should be created in Hibernate's JIRA.

 local application of naming strategy
 

  Key: HIBERNATE-9
  URL: http://jira.jboss.com/jira/browse/HIBERNATE-9
  Project: Hibernate
 Type: Feature Request
 Reporter: Tom Baeyens
 Assignee: Steve Ebersole
 Priority: Minor



 It would be nice if users could apply a naming strategy on e.g. a hibernate 
 mapping file.  Now, the naming strategy can only be applied globally to the 
 whole configuration.  More general, it would be nice if users could specify 
 multiple naming strategies and for each strategy on which mappings they 
 apply.  Consider supporting multiple ways of specifying on which mappings a 
 naming strategy applies : by putting it in a mapping file, by specifying 
 class names or table name prefixes, 

-- 
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators:
   http://jira.jboss.com/jira/secure/Administrators.jspa
-
If you want more information on JIRA, or have a bug to report see:
   http://www.atlassian.com/software/jira



---
SF email is sponsored by - The IT Product Guide
Read honest  candid reviews on hundreds of IT Products from real users.
Discover which products truly live up to the hype. Start reading now.
http://ads.osdn.com/?ad_id=6595alloc_id=14396op=click
___
JBoss-Development mailing list
JBoss-Development@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/jboss-development

[JBoss-dev] [JBoss JIRA] Resolved: (HIBERNATE-8) configuration property for naming strategy

[Steve Ebersole (JIRA)]

 [ http://jira.jboss.com/jira/browse/HIBERNATE-8?page=history ]
 
Steve Ebersole resolved HIBERNATE-8:


 Assign To: Steve Ebersole  (was: Gavin King)
Resolution: Rejected

Until the Hibernate JIRA is transferred over to this JIRA box, all requests for 
Hibernate-specific enhancements should be created in Hibernate's JIRA. 

 configuration property for naming strategy
 --

  Key: HIBERNATE-8
  URL: http://jira.jboss.com/jira/browse/HIBERNATE-8
  Project: Hibernate
 Type: Feature Request
 Reporter: Tom Baeyens
 Assignee: Steve Ebersole
 Priority: Minor



 currently, it's only possible to specify a naming strategy programmatically.  
 it would be nice to have a configuration property for it.
 regards, tom.

-- 
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators:
   http://jira.jboss.com/jira/secure/Administrators.jspa
-
If you want more information on JIRA, or have a bug to report see:
   http://www.atlassian.com/software/jira



---
SF email is sponsored by - The IT Product Guide
Read honest  candid reviews on hundreds of IT Products from real users.
Discover which products truly live up to the hype. Start reading now.
http://ads.osdn.com/?ad_id=6595alloc_id=14396op=click
___
JBoss-Development mailing list
JBoss-Development@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/jboss-development

[JBoss-dev] [JBoss JIRA] Commented: (HIBERNATE-6) HibernateContext Interceptor

[Steve Ebersole (JIRA)]

 [ 
http://jira.jboss.com/jira/browse/HIBERNATE-6?page=comments#action_12316744 ]
 
Steve Ebersole commented on HIBERNATE-6:


Sure, just use the SessionFactoryInterceptor managed attribute on the 
org.jboss.hibernate.jmx.Hibernate mbean.

 HibernateContext Interceptor
 

  Key: HIBERNATE-6
  URL: http://jira.jboss.com/jira/browse/HIBERNATE-6
  Project: Hibernate
 Type: Feature Request
  Environment: All
 Reporter: Jess Marn
 Assignee: Gavin King



 is there a way to assign an Interceptor to a HibernateContext?
 I suppose that overloading getSession, getunmanagedSession and 
 generateSession is worth the effort. Like this:
public static Session getUnmanagedSession(String name, Interceptor 
 interceptor) throws HibernateException, IllegalStateException
{
   final Session managedSession = lookupSession(name);
   if (managedSession == null)
   {
  throw new IllegalStateException(No managed sessions found for 
 current context);
   }
   return managedSession.getSessionFactory().openSession( 
 managedSession.connection(), interceptor );
}
public static Session getSession(String name)
{
   return getSession(name, null);
}
public static Session getSession(String name, Interceptor interceptor)
{
   try
   {
  // Determine whether a session is already bound to the current 
 transaction.
  // If so, return that session; otherwise generate a new session, 
 bind, and
  // return it
  Session currentSession = lookupSession(name);
  if (currentSession == null)
  {
 currentSession = generateSession(name, interceptor);
 prepareSession(name, currentSession);
 bind(name, currentSession);
  }
  return currentSession;
   }
   catch(HibernateException e)
   {
  throw new NestedRuntimeException(Could not recover session, e);
   }
}
private static Session generateSession(String name, Interceptor 
 interceptor) throws HibernateException
{
   // Make sure there is an ongoing transaction prior to generating
   // a session in order to provide a usefull error message...
   checkTransactionStatus();
   SessionFactory factory = locateSessionFactory(name);
   if (interceptor == null) {
   return factory.openSession();
   } else {
   return factory.openSession(interceptor);
   }
}
 Perhaps there is a better way to chain an interceptor into a SessionFactory 
 using the current HibernateContext and I do not know how?

-- 
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators:
   http://jira.jboss.com/jira/secure/Administrators.jspa
-
If you want more information on JIRA, or have a bug to report see:
   http://www.atlassian.com/software/jira



---
SF email is sponsored by - The IT Product Guide
Read honest  candid reviews on hundreds of IT Products from real users.
Discover which products truly live up to the hype. Start reading now.
http://ads.osdn.com/?ad_ide95alloc_id396op=click
___
JBoss-Development mailing list
JBoss-Development@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/jboss-development

[JBoss-dev] [JBoss JIRA] Commented: (HIBERNATE-6) HibernateContext Interceptor

[Steve Ebersole (JIRA)]

 [ 
http://jira.jboss.com/jira/browse/HIBERNATE-6?page=comments#action_12316745 ]
 
Steve Ebersole commented on HIBERNATE-6:


Also note that session-scoped interceptors *do not* make sense in this type of 
managed session environment.

 HibernateContext Interceptor
 

  Key: HIBERNATE-6
  URL: http://jira.jboss.com/jira/browse/HIBERNATE-6
  Project: Hibernate
 Type: Feature Request
  Environment: All
 Reporter: Jess Marn
 Assignee: Gavin King



 is there a way to assign an Interceptor to a HibernateContext?
 I suppose that overloading getSession, getunmanagedSession and 
 generateSession is worth the effort. Like this:
public static Session getUnmanagedSession(String name, Interceptor 
 interceptor) throws HibernateException, IllegalStateException
{
   final Session managedSession = lookupSession(name);
   if (managedSession == null)
   {
  throw new IllegalStateException(No managed sessions found for 
 current context);
   }
   return managedSession.getSessionFactory().openSession( 
 managedSession.connection(), interceptor );
}
public static Session getSession(String name)
{
   return getSession(name, null);
}
public static Session getSession(String name, Interceptor interceptor)
{
   try
   {
  // Determine whether a session is already bound to the current 
 transaction.
  // If so, return that session; otherwise generate a new session, 
 bind, and
  // return it
  Session currentSession = lookupSession(name);
  if (currentSession == null)
  {
 currentSession = generateSession(name, interceptor);
 prepareSession(name, currentSession);
 bind(name, currentSession);
  }
  return currentSession;
   }
   catch(HibernateException e)
   {
  throw new NestedRuntimeException(Could not recover session, e);
   }
}
private static Session generateSession(String name, Interceptor 
 interceptor) throws HibernateException
{
   // Make sure there is an ongoing transaction prior to generating
   // a session in order to provide a usefull error message...
   checkTransactionStatus();
   SessionFactory factory = locateSessionFactory(name);
   if (interceptor == null) {
   return factory.openSession();
   } else {
   return factory.openSession(interceptor);
   }
}
 Perhaps there is a better way to chain an interceptor into a SessionFactory 
 using the current HibernateContext and I do not know how?

-- 
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators:
   http://jira.jboss.com/jira/secure/Administrators.jspa
-
If you want more information on JIRA, or have a bug to report see:
   http://www.atlassian.com/software/jira



---
SF email is sponsored by - The IT Product Guide
Read honest  candid reviews on hundreds of IT Products from real users.
Discover which products truly live up to the hype. Start reading now.
http://ads.osdn.com/?ad_ide95alloc_id396op=click
___
JBoss-Development mailing list
JBoss-Development@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/jboss-development

[JBoss-dev] [JBoss JIRA] Closed: (HIBERNATE-6) HibernateContext Interceptor

[Steve Ebersole (JIRA)]

 [ http://jira.jboss.com/jira/browse/HIBERNATE-6?page=history ]
 
Steve Ebersole closed HIBERNATE-6:
--

 Assign To: Steve Ebersole  (was: Gavin King)
Resolution: Done

 HibernateContext Interceptor
 

  Key: HIBERNATE-6
  URL: http://jira.jboss.com/jira/browse/HIBERNATE-6
  Project: Hibernate
 Type: Feature Request
  Environment: All
 Reporter: Jess Marn
 Assignee: Steve Ebersole



 is there a way to assign an Interceptor to a HibernateContext?
 I suppose that overloading getSession, getunmanagedSession and 
 generateSession is worth the effort. Like this:
public static Session getUnmanagedSession(String name, Interceptor 
 interceptor) throws HibernateException, IllegalStateException
{
   final Session managedSession = lookupSession(name);
   if (managedSession == null)
   {
  throw new IllegalStateException(No managed sessions found for 
 current context);
   }
   return managedSession.getSessionFactory().openSession( 
 managedSession.connection(), interceptor );
}
public static Session getSession(String name)
{
   return getSession(name, null);
}
public static Session getSession(String name, Interceptor interceptor)
{
   try
   {
  // Determine whether a session is already bound to the current 
 transaction.
  // If so, return that session; otherwise generate a new session, 
 bind, and
  // return it
  Session currentSession = lookupSession(name);
  if (currentSession == null)
  {
 currentSession = generateSession(name, interceptor);
 prepareSession(name, currentSession);
 bind(name, currentSession);
  }
  return currentSession;
   }
   catch(HibernateException e)
   {
  throw new NestedRuntimeException(Could not recover session, e);
   }
}
private static Session generateSession(String name, Interceptor 
 interceptor) throws HibernateException
{
   // Make sure there is an ongoing transaction prior to generating
   // a session in order to provide a usefull error message...
   checkTransactionStatus();
   SessionFactory factory = locateSessionFactory(name);
   if (interceptor == null) {
   return factory.openSession();
   } else {
   return factory.openSession(interceptor);
   }
}
 Perhaps there is a better way to chain an interceptor into a SessionFactory 
 using the current HibernateContext and I do not know how?

-- 
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators:
   http://jira.jboss.com/jira/secure/Administrators.jspa
-
If you want more information on JIRA, or have a bug to report see:
   http://www.atlassian.com/software/jira



---
SF email is sponsored by - The IT Product Guide
Read honest  candid reviews on hundreds of IT Products from real users.
Discover which products truly live up to the hype. Start reading now.
http://ads.osdn.com/?ad_ide95alloc_id396op=click
___
JBoss-Development mailing list
JBoss-Development@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/jboss-development

[JBoss-dev] [JBoss JIRA] Commented: (JBAS-1298) HAR Deployer JBCache config

[Steve Ebersole (JIRA)]

 [ 
http://jira.jboss.com/jira/browse/JBAS-1298?page=comments#action_12316747 ]
 
Steve Ebersole commented on JBAS-1298:
--

That last comment is a little ambigious as I read back over it.

Hibernate2 support will be getting removed from JBoss, and replaced with 
Hibernate3...

 HAR Deployer  JBCache config
 

  Key: JBAS-1298
  URL: http://jira.jboss.com/jira/browse/JBAS-1298
  Project: JBoss Application Server
 Type: Feature Request
   Components: Hibernate service
 Versions: JBossAS-4.0.1 Final, JBossAS-3.2.6 Final
 Reporter: Andrew Oliver
 Assignee: Steve Ebersole


 Original Estimate: 6 hours
 Remaining: 6 hours

 Presently HAR deployer picks up JBCache config from its classloader.  It does 
 not use an MBean.  It should use an MBean (and we should be able to get stats 
 from it).  

-- 
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators:
   http://jira.jboss.com/jira/secure/Administrators.jspa
-
If you want more information on JIRA, or have a bug to report see:
   http://www.atlassian.com/software/jira



---
SF email is sponsored by - The IT Product Guide
Read honest  candid reviews on hundreds of IT Products from real users.
Discover which products truly live up to the hype. Start reading now.
http://ads.osdn.com/?ad_id=6595alloc_id=14396op=click
___
JBoss-Development mailing list
JBoss-Development@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/jboss-development

[JBoss-dev] [JBoss JIRA] Commented: (JBAS-1298) HAR Deployer JBCache config

[Steve Ebersole (JIRA)]

 [ 
http://jira.jboss.com/jira/browse/JBAS-1298?page=comments#action_12315996 ]
 
Steve Ebersole commented on JBAS-1298:
--

I was not planning any mods to the jboss-3.2 module for the Hibernate intg code 
because jboss-4.0 and jboss-head will be made to use hibernate3.

However, this one is fairly trivial to back-port so I'll do this change back to 
3.2.x.

 HAR Deployer  JBCache config
 

  Key: JBAS-1298
  URL: http://jira.jboss.com/jira/browse/JBAS-1298
  Project: JBoss Application Server
 Type: Feature Request
   Components: Hibernate service
 Versions: JBossAS-4.0.1 Final, JBossAS-3.2.6 Final
 Reporter: Andrew Oliver
 Assignee: Steve Ebersole


 Original Estimate: 6 hours
 Remaining: 6 hours

 Presently HAR deployer picks up JBCache config from its classloader.  It does 
 not use an MBean.  It should use an MBean (and we should be able to get stats 
 from it).  

-- 
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators:
   http://jira.jboss.com/jira/secure/Administrators.jspa
-
If you want more information on JIRA, or have a bug to report see:
   http://www.atlassian.com/software/jira



---
SF email is sponsored by - The IT Product Guide
Read honest  candid reviews on hundreds of IT Products from real users.
Discover which products truly live up to the hype. Start reading now.
http://ads.osdn.com/?ad_id=6595alloc_id=14396op=click
___
JBoss-Development mailing list
JBoss-Development@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/jboss-development

[JBoss-dev] [JBoss JIRA] Commented: (JBAS-1299) No production-quality Cache Invalidation framework for Hibernate 2nd level cache

[Steve Ebersole (JIRA)]

 [ 
http://jira.jboss.com/jira/browse/JBAS-1299?page=comments#action_12315997 ]
 
Steve Ebersole commented on JBAS-1299:
--

I believe OSCache also supports the same invalidation model, although I am no 
cache expert and may be wrong here.

Regardless, this is not a Hibernate issue per-se.  Hibernate simply uses 
capabilities provided by the underlying cache providers.  We should either 
reassign this to the cache guys, or close.

 No production-quality Cache Invalidation framework for Hibernate 2nd level 
 cache
 

  Key: JBAS-1299
  URL: http://jira.jboss.com/jira/browse/JBAS-1299
  Project: JBoss Application Server
 Type: Feature Request
   Components: Hibernate service
 Versions: JBossAS-4.0.1 Final, JBossAS-3.2.6 Final
 Reporter: Andrew Oliver
 Assignee: Steve Ebersole


 Original Estimate: 2 days
 Remaining: 2 days

 This is 50/50 Hibernate-JBC.  Presently Hiberante only supports one 
 Cache-Invalidatable cache (Swarm) which isn't an ideal cache for running in 
 JBossAS.  There are some data structures that lend themself for a 2 
 configuration system.  Meaning I do read/write w/o 2nd level cache and reads 
 from second level cache and send messages to evict members from second level 
 cache (cluster-wide).  

-- 
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators:
   http://jira.jboss.com/jira/secure/Administrators.jspa
-
If you want more information on JIRA, or have a bug to report see:
   http://www.atlassian.com/software/jira



---
SF email is sponsored by - The IT Product Guide
Read honest  candid reviews on hundreds of IT Products from real users.
Discover which products truly live up to the hype. Start reading now.
http://ads.osdn.com/?ad_id=6595alloc_id=14396op=click
___
JBoss-Development mailing list
JBoss-Development@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/jboss-development

[JBoss-dev] [JBoss JIRA] Commented: (JBAS-1298) HAR Deployer JBCache config

[Steve Ebersole (JIRA)]

 [ 
http://jira.jboss.com/jira/browse/JBAS-1298?page=comments#action_12315674 ]
 
Steve Ebersole commented on JBAS-1298:
--

That actually depends upon which Hibernate CacheProvider implementation you 
specify.  The net.sf.hibernate.TreeCacheProvider does exactly what you mention; 
it looks for a file treecache.xml on the classpath.

As has already been discussed, depending upon the version of JBossCache in use, 
you might also use org.jboss.hibernate.cache.DeployedTreeCacheProvider to 
utilize a TreeCache instance bound into a JNDI location as the backing for the 
second-level cache within Hibernate.

I mention depending upon the version of JBossCache because automatic JNDI 
binding was a feature of the JBossCache MBean for a fleeting moment in time.  
Of course, anything *can* bind a TreeCache instance into JNDI; it does not 
necessarily need to be the JBossCache MBean.

At any rate, Ben Wang and I will talk next week to figure out a long term 
solution.

 HAR Deployer  JBCache config
 

  Key: JBAS-1298
  URL: http://jira.jboss.com/jira/browse/JBAS-1298
  Project: JBoss Application Server
 Type: Feature Request
   Components: Hibernate service
 Versions: JBossAS-4.0.1 Final, JBossAS-3.2.6 Final
 Reporter: Andrew Oliver
 Assignee: Steve Ebersole


 Original Estimate: 6 hours
 Remaining: 6 hours

 Presently HAR deployer picks up JBCache config from its classloader.  It does 
 not use an MBean.  It should use an MBean (and we should be able to get stats 
 from it).  

-- 
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators:
   http://jira.jboss.com/jira/secure/Administrators.jspa
-
If you want more information on JIRA, or have a bug to report see:
   http://www.atlassian.com/software/jira



---
SF email is sponsored by - The IT Product Guide
Read honest  candid reviews on hundreds of IT Products from real users.
Discover which products truly live up to the hype. Start reading now.
http://ads.osdn.com/?ad_id=6595alloc_id=14396op=click
___
JBoss-Development mailing list
JBoss-Development@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/jboss-development

[JBoss-dev] [JBoss JIRA] Closed: (HIBERNATE-2) Allow setting an interceptor when creating a session

[Steve Ebersole (JIRA)]

 [ http://jira.jboss.com/jira/browse/HIBERNATE-2?page=history ]
 
Steve Ebersole closed HIBERNATE-2:
--

Resolution: Done

Issue was transferred from sourceforge as open; closing.

 Allow setting an interceptor when creating a session
 

  Key: HIBERNATE-2
  URL: http://jira.jboss.com/jira/browse/HIBERNATE-2
  Project: Hibernate
 Type: Feature Request
 Reporter: SourceForge User
 Assignee: Steve Ebersole



 SourceForge Submitter: benlitchfield .
 It would be nice to specify in the hibernate session 
 factory jmx definition a hibernate interceptor(or maybe 
 list of interceptors) to use when creating the hibernate 
 session.
 For example
 mbean code=org.jboss.hibernate.jmx.Hibernate 
 name=jboss.har:service=Hibernate
 ...
 attribute 
 name=Interceptorcom.mycompany.hibernate.MyHibern
 ateInterceptor/attribute
 /mbean
 As far as I am aware it is not currently possible to use 
 an interceptor with the current jboss integration.

-- 
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators:
   http://jira.jboss.com/jira/secure/Administrators.jspa
-
If you want more information on JIRA, or have a bug to report see:
   http://www.atlassian.com/software/jira



---
The SF.Net email is sponsored by: Beat the post-holiday blues
Get a FREE limited edition SourceForge.net t-shirt from ThinkGeek.
It's fun and FREE -- well, almosthttp://www.thinkgeek.com/sfshirt
___
JBoss-Development mailing list
JBoss-Development@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/jboss-development

[JBoss-dev] [JBoss JIRA] Commented: (HIBERNATE-4) NPE in HibernateContext.prepareSession

[Steve Ebersole (JIRA)]

 [ 
http://jira.jboss.com/jira/browse/HIBERNATE-4?page=comments#action_12314714 ]
 
Steve Ebersole commented on HIBERNATE-4:


Are you *certain* you are making this call within an on-going JTA transaction?  
Is that transaction owned by the TransactionManager bound under 
java:/TransactionManager?

Line 171 (where you are getting this NPE) is attempting to register a 
transaction Synchronization with the current Transaction which it gets from the 
TransactionManager.  Either the Transaction or the TransactionManager are null 
here, which is a usage problem.

Later versions added better error messages on this condition.

 NPE in HibernateContext.prepareSession
 --

  Key: HIBERNATE-4
  URL: http://jira.jboss.com/jira/browse/HIBERNATE-4
  Project: Hibernate
 Type: Bug
 Reporter: SourceForge User
 Assignee: Steve Ebersole
 Priority: Minor



 SourceForge Submitter: pilhuhn .
 Hi,
 this might be a pilot error ...
 When I try to obtain a session like this:
 Session =
 HibernateContext.getSession(java:/hibernate/SessionFactory);
 I get a NPE
 Caused by: java.lang.NullPointerException
 at
 org.jboss.hibernate.session.HibernateContext.prepareSession(HibernateContext.java:171)
 at
 org.jboss.hibernate.session.HibernateContext.getSession(HibernateContext.java:99)
 at
 de.bsd.adb_hibernate.server.ServerFacade.beispiel(ServerFacade.java:22)
 If I do it the classical way 
   InitialContext ic = new InitialContext();
   Object o = ic.lookup(java:/hibernate/SessionFactory);
   sf = (SessionFactory)o;
 Session sess = sf.openSession()
 it works as intended.

-- 
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators:
   http://jira.jboss.com/jira/secure/Administrators.jspa
-
If you want more information on JIRA, or have a bug to report see:
   http://www.atlassian.com/software/jira



---
The SF.Net email is sponsored by: Beat the post-holiday blues
Get a FREE limited edition SourceForge.net t-shirt from ThinkGeek.
It's fun and FREE -- well, almosthttp://www.thinkgeek.com/sfshirt
___
JBoss-Development mailing list
JBoss-Development@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/jboss-development

[JBoss-dev] [JBoss JIRA] Closed: (HIBERNATE-4) NPE in HibernateContext.prepareSession

[Steve Ebersole (JIRA)]

 [ http://jira.jboss.com/jira/browse/HIBERNATE-4?page=history ]
 
Steve Ebersole closed HIBERNATE-4:
--

Resolution: Rejected

Usage error

 NPE in HibernateContext.prepareSession
 --

  Key: HIBERNATE-4
  URL: http://jira.jboss.com/jira/browse/HIBERNATE-4
  Project: Hibernate
 Type: Bug
 Reporter: SourceForge User
 Assignee: Steve Ebersole
 Priority: Minor



 SourceForge Submitter: pilhuhn .
 Hi,
 this might be a pilot error ...
 When I try to obtain a session like this:
 Session =
 HibernateContext.getSession(java:/hibernate/SessionFactory);
 I get a NPE
 Caused by: java.lang.NullPointerException
 at
 org.jboss.hibernate.session.HibernateContext.prepareSession(HibernateContext.java:171)
 at
 org.jboss.hibernate.session.HibernateContext.getSession(HibernateContext.java:99)
 at
 de.bsd.adb_hibernate.server.ServerFacade.beispiel(ServerFacade.java:22)
 If I do it the classical way 
   InitialContext ic = new InitialContext();
   Object o = ic.lookup(java:/hibernate/SessionFactory);
   sf = (SessionFactory)o;
 Session sess = sf.openSession()
 it works as intended.

-- 
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators:
   http://jira.jboss.com/jira/secure/Administrators.jspa
-
If you want more information on JIRA, or have a bug to report see:
   http://www.atlassian.com/software/jira



---
The SF.Net email is sponsored by: Beat the post-holiday blues
Get a FREE limited edition SourceForge.net t-shirt from ThinkGeek.
It's fun and FREE -- well, almosthttp://www.thinkgeek.com/sfshirt
___
JBoss-Development mailing list
JBoss-Development@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/jboss-development

[JBoss-dev] [JBoss JIRA] Resolved: (HIBERNATE-1) HibernateIntgUnitTestCase fails with hibernate-2.1.7c

[Steve Ebersole (JIRA)]

 [ http://jira.jboss.com/jira/browse/HIBERNATE-1?page=history ]
 
Steve Ebersole resolved HIBERNATE-1:


Resolution: Done

Gavin said he found a bug in 2.1.7 that would cause this.  It is fixed in CVS.  
we will need to apply the 2.1.7d release, not 2.1.7c.

 HibernateIntgUnitTestCase fails with hibernate-2.1.7c
 -

  Key: HIBERNATE-1
  URL: http://jira.jboss.com/jira/browse/HIBERNATE-1
  Project: Hibernate
 Type: Bug
  Environment: [EMAIL PROTECTED] testsuite]$ java -version
 java version 1.4.2_05
 Java(TM) 2 Runtime Environment, Standard Edition (build 1.4.2_05-b04)
 Java HotSpot(TM) Client VM (build 1.4.2_05-b04, mixed mode)
 Note that this requires an upto date snapshot of the 4.0 branch to pickup 
 treecache and the hibernate2.jar.
 Reporter: Scott M Stark
 Assignee: Steve Ebersole
 Priority: Blocker



 The latest jboss Branch_4_0 codebase has a failure in the 
 org.jboss.test.hibernate.test.HibernateIntgUnitTestCase when updating the 
 jboss-hibernate.deployer/hibernate2.jar to the 2.1.7c binary from 
 sourceforge. The following exception is seen on the console:
 10:19:47,265 INFO  [EARDeployer] Started J2EE application: 
 file:/C:/cvs/JBoss4.0
 /jboss-4.0/testsuite/output/lib/hib-test.ear
 10:19:47,609 WARN  [JDBCExceptionReporter] SQL Error: -22, SQLState: S0002
 10:19:47,609 ERROR [JDBCExceptionReporter] Table not found: user in statement 
 [select max(id) from user]
 10:19:47,625 ERROR [LogInterceptor] EJBException in method: public abstract 
 org.
 jboss.test.hibernate.model.User 
 org.jboss.test.hibernate.ejb.interfaces.ProfileService.storeUser(org.jboss.test.hibernate.model.User)
  throws java.rmi.RemoteException, causedBy:
 net.sf.hibernate.exception.SQLGrammarException: Could not save object
 at 
 net.sf.hibernate.exception.ErrorCodeConverter.convert(ErrorCodeConverter.java:69)
 at 
 net.sf.hibernate.exception.JDBCExceptionHelper.convert(JDBCExceptionHelper.java:30)
 at net.sf.hibernate.impl.SessionImpl.convert(SessionImpl.java:4110)
 at 
 net.sf.hibernate.impl.SessionImpl.saveWithGeneratedIdentifier(SessionImpl.java:792)
 at net.sf.hibernate.impl.SessionImpl.save(SessionImpl.java:747)
 at 
 net.sf.hibernate.impl.SessionImpl.saveOrUpdate(SessionImpl.java:1397)
 at 
 org.jboss.test.hibernate.ProfileService.storeUser(ProfileService.java:54)
 at 
 org.jboss.test.hibernate.ejb.ProfileBean.storeUser(ProfileBean.java:44)
 at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
 at 
 sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:39)
 at 
 sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25)
 at java.lang.reflect.Method.invoke(Method.java:324)
 at org.jboss.invocation.Invocation.performCall(Invocation.java:345)
 at 
 org.jboss.ejb.StatelessSessionContainer$ContainerInterceptor.invoke(StatelessSessionContainer.java:214)
 at 
 org.jboss.resource.connectionmanager.CachedConnectionInterceptor.invoke(CachedConnectionInterceptor.java:185)
 at 
 org.jboss.ejb.plugins.StatelessSessionInstanceInterceptor.invoke(StatelessSessionInstanceInterceptor.java:113)
 at 
 org.jboss.webservice.server.ServiceEndpointInterceptor.invoke(ServiceEndpointInterceptor.java:51)
 at 
 org.jboss.ejb.plugins.CallValidationInterceptor.invoke(CallValidationInterceptor.java:48)
 at 
 org.jboss.ejb.plugins.AbstractTxInterceptor.invokeNext(AbstractTxInterceptor.java:105)
 at 
 org.jboss.ejb.plugins.TxInterceptorCMT.runWithTransactions(TxInterceptorCMT.java:313)
 at 
 org.jboss.ejb.plugins.TxInterceptorCMT.invoke(TxInterceptorCMT.java:146)
 at 
 org.jboss.ejb.plugins.SecurityInterceptor.invoke(SecurityInterceptor.java:122)
 at 
 org.jboss.ejb.plugins.LogInterceptor.invoke(LogInterceptor.java:191)
 at 
 org.jboss.ejb.plugins.ProxyFactoryFinderInterceptor.invoke(ProxyFactoryFinderInterceptor.java:122)
 at 
 org.jboss.ejb.SessionContainer.internalInvoke(SessionContainer.java:624)
 at org.jboss.ejb.Container.invoke(Container.java:856)
 at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
 at 
 sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:39)
 at 
 sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25)
 at java.lang.reflect.Method.invoke(Method.java:324)
 at 
 org.jboss.mx.interceptor.ReflectedDispatcher.invoke(ReflectedDispatcher.java:144)
 at org.jboss.mx.server.Invocation.dispatch(Invocation.java:80)
 at org.jboss.mx.server.Invocation.invoke(Invocation.java:72)
 at 
 org.jboss.mx.server.AbstractMBeanInvoker.invoke(AbstractMBeanInvoker.java:249