Adding the following to the EJB3Deployer:
protected void startService() throws Exception
{
// todo this should be coming from the DefaultProperties
System.setProperty(hibernate.bytecode.provider, javassist);
results in the Bytecode provider name : javassist, but cglib is still
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
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
What I mean is externalizing the org.jboss.hibernate.jmx.Hibernate call:
protected void createService() throws Exception
{
log.trace( forcing bytecode provider - javassist );
// todo : really need a much better solution for this...
System.setProperty(
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
Scott M Stark wrote:
Looks much better. I'm going to make the bytecode provider a
configurable option on the ejb3 deployer and har mbean rather
scratch that, just read steve's email.
Bill Burke wrote:
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
Scott M Stark wrote:
Looks much better. I'm going to make the bytecode provider a
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
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
I added the following to the head deployer. Once this can be passed in
via the pm properties the system property set can be dropped.
/**
* Overriden to set the hibernate.bytecode.provider from the
*
* @throws Exception
*/
protected void createService() throws Exception
{
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;
10 matches
Mail list logo
