I use raw Spring DM.

After tons of pains , currently I cam make my demo works by reference your s2ap example again and again. There are three bundles:
1) Modal bundle contain the entities.
2) Dao bundle which has an injected EntityManager and export the dao service.
3) A DaoConsume bundle which consume the dao service.

Howver, in s2ap example, the entityManagerFactory is "LocalContainerEntityManagerFactory". In my demo, I have to change it to "LocalEntityManagerFactory". Since with the former I kept get the exception that loadtimeweaver related.
I think DM Server provides support for the load-time-weaver. But how will it be with DM? Is it possible?

Hope you could shed a light on this.

cheers

Are you using dm Server or raw Spring DM? The ClassLoader management in dm Server is more sophisticated and helps to alleviate problems such as the one you are encountering.

Regards,

Rob

I am new to spring dm. I rewrite a demo after read your example.
If I get the EntityManager using these code, things goes well.:
>>>>>>>
HashMap properties = new HashMap();
properties.put(PersistenceUnitProperties.CLASSLOADER, this.getClass()
.getClassLoader());
EntityManagerFactory emf = new PersistenceProvider()
.createEntityManagerFactory("authentication_system", properties);
EntityManager em = emf.createEntityManager();
>>>>>>>
However, if I use annotation to inject EntityManager:
>>>>>>>
@PersistenceContext
private EntityManager em;
>>>>>>>
I get this error, "Employee" is an Enity of my own:
com.mxb.model.Employee cannot be cast to com.mxb.model.Employee

I think it is because of the classloading.
My application.xml is as follow:

I am struggling how to get it to work. Help is highly appricated.

You're an absolute champion!

I had bundled the spring-agent-2.5.4.jar with the WAR – and were also starting the maven/jetty pointing to a copy of the same jar.

I removed the agent from the WAR, and now everything works perfectly!

thankyou so much. One thing I did find with your sample, is that it won't work with spring 2.5.5, but does on 2.5.4. This is due to an error introduced with a fix for http://jira.springframework.org/browse/SPR-4524

cheers

Matt.

You look to be doing the right with respect to trying to configure the Java agent. From the error message though it looks pretty clear that Spring can't detect the agent. One issue here could be classloading – make sure that you don't have two versions of the agent classes on the classpath – they should be on the boot class path only, if they are packaged in your WAR that might cause problems.

Rob

I've upload my petclinic cutdown version based on Jetty to the following location
http://rapidshare.com/files/136814768/petclinic_oracle.zip

rapidshare.com/files/136814768/petclinic_oracle.zip

It's only 33k.

Rob/anyone skilled with spring/eclipselink – any chance you could take a quick look.

All it requires is maven2, all dependencies will load automatically.

there is a readme file as well inside zip.

I would be very greatful for any help.

cheers

Matt.

Thanks for the article. I'm new to spring, having an ejb background.

I've attempted to re-port your code over to maven/jetty (j2se). Although I've had no luck.

I start maven jetty:run with the following set:
set MAVEN_OPTS=-javaagent:"C:\Documents and Settings\Administrator\.m2\repository\org\springframework\spring-agent\2.5.4\spring-agent-2.5.4.jar"

However, it bombs out with exception due to the following line:

It fails stating that

2008-08-13 01:11:52.111:/:INFO: Initializing Spring root WebApplicationContext
(16 ms) [main] ERROR: org.springframework.web.context.ContextLoader#initWebApplicationContext : Context initialization failed
org.springframework.beans.factory.BeanCreationException: Error creating bean with name 'org.springframework.context.weaving.AspectJWeavingEnabler#0': Initialization of bean failed; nested exception is org.springframework.beans.factory.BeanCreationException: Error creating bean with name 'loadTimeWeaver': Initialization of bean failed; nested exception is java.lang.IllegalStateException: ClassLoader [org.mortbay.jetty.webapp.WebAppClassLoader] does NOT provide an 'addTransformer(ClassFileTransformer)' method. Specify a custom LoadTimeWeaver or start your Java virtual machine with Spring's agent: -javaagent:spring-agent.jar
at org.springframework.beans.factory.support.AbstractAutowireCapableBeanFactory.doCreateBean(AbstractAutowireCapableBeanFactory.java:478)
…

If i change the line to be

It gives the error

java.lang.IllegalStateException: Must start with Java agent to use InstrumentationLoadTimeWeaver. See Spring documentation.

If i comment the line out entirely… I get the error

[EL Config]: 2008.08.13 01:17:38.796–ServerSession(15703940)–Thread(Thread[main,5,main])–The alias name for the entity class [class org.springframework.petclinic.domain.PetType] is being defaulted to: PetType.
[EL Config]: 2008.08.13 01:17:38.843–ServerSession(15703940)–Thread(Thread[main,5,main])–The column name for element
[private java.lang.String org.springframework.petclinic.domain.NamedEntity.name] is being defaulted to: NAME.
[EL Config]: 2008.08.13 01:17:38.843–ServerSession(15703940)–Thread(Thread[main,5,main])–The column name for element
[private java.lang.Integer org.springframework.petclinic.domain.BaseEntity.id] is being defaulted to: ID.
(15 ms) [main] ERROR: org.springframework.web.context.ContextLoader#initWebApplicationContext : Context initialization failed
org.springframework.beans.factory.BeanCreationException: Error creating bean with name 'org.springframework.dao.annotation.PersistenceExceptionTranslationPostProcessor#0' defined in ServletContext resource [/WEB-INF/applicationContext-persistence.xml]: Initialization of bean failed; nested exception is org.springframework.beans.factory.BeanCreationException:
Error creating bean with name 'entityManagerFactory' defined in ServletContext resource [/WEB-INF/applicationContext-persistence.xml]: Invocation of init method failed; nested exception is javax.persistence.PersistenceException: Exception
[EclipseLink-28018] (Eclipse Persistence Services – 1.0 (Build 1.0 – 20080707)): org.eclipse.persistence.exceptions.EntityManagerSetupException
Exception Description: Predeployment of PersistenceUnit [PetClinic] failed.
Internal Exception: Exception [EclipseLink-7161] (Eclipse Persistence Services – 1.0 (Build 1.0 – 20080707)): org.eclipse.persistence.exceptions.ValidationException
Exception Description: Entity class [class org.springframework.petclinic.domain.PetType] has no primary key specified. It
should define either an @Id, @EmbeddedId or an @IdClass. If you have defined PK using any of these annotations then please make sure that you do not have mixed access-type (both fields and properties annotated) in your entity class hierarchy.
at org.springframework.beans.factory.support.AbstractAutowireCapableBeanFactory.doCreateBean(AbstractAutowireCapableBeanFactory.java:478)

Thus I'm stumped!

In your particular 1.2.0 petclinic code sample, how is aspectj actually leveraged?
Is some type of transformation supposed to take place so that the @MappedSuperclass
public class BaseEntity / NamedEntity.java properties automatically get pushed to the subclass entities?

Is there any reason your code should not run from a standard jvm (via jetty)?

At this stage, all i'm trying to do is get the domain and repository objects to function.

The only change I have made is to BaseEntity to leverage a sequence generator (seeing that I'm running on an Oracle database):

@Id
@GeneratedValue(generator="IdSeq")
@SequenceGenerator(name="IdSeq",sequenceName="ID_SEQ", initialValue=1000)

My applicationContext-persistence.xml looks like …

–>

Oracle
none
FINE
true
true
true
true
INFO
Oracle-JDBC

My persistence.xml looks like ….

org.springframework.petclinic.domain.BaseEntity
org.springframework.petclinic.domain.NamedEntity
org.springframework.petclinic.domain.Owner
org.springframework.petclinic.domain.Person
org.springframework.petclinic.domain.Pet
org.springframework.petclinic.domain.PetType
org.springframework.petclinic.domain.Specialty
org.springframework.petclinic.domain.Vet
org.springframework.petclinic.domain.Visit

true

My persistence.properties file looks like …

jpa.eclipselink.databasePlatform=org.eclipse.persistence.platform.database.oracle.OraclePlatform
jpa.showSql=true

jdbc.driverClassName=oracle.jdbc.driver.OracleDriver
jdbc.url=jdbc:oracle:thin:@localhost:1521:xe
jdbc.username=petclinic
jdbc.password=petclinic

cheers

Matt.

Cheers,
Jawher.