Migration from JBP 2.6.6 to JBP 2.7.2 ...

[souravm]

Hi Guys,

We are planning to migrate couple of our applications from JSR 168 (JBP 2.6.6 container) to JSR 286 (JBP 2.7.2 container).

If anyone has a list of typical issues faced/to be watched for that would be really helpful.

Any other pointer in this regard also would be highly appreciated.

Regards,
Sourav

[prabhat.jha]

There is one compatibility issue and we talk about that in chapter 4 of 2.7.2 reference guide regarding use of JBossActionRequest

In terms spec, there are few things to be aware of:

- URL is XML escaped by default. This behavior can be changed .
- Some changes in when you have multiple values for a single paramater.
and so on..

For more, you would have to read the spec. It's lots of fun. ;)

[souravm]

Hi Prabhat,

I've checked the reference guide you have mentioned.

From there what I could gather is unless any of my existing JSR 168 portlets use JBossActionRequest, all those JSR 168 portlets would run as is in 2.7.2.

I just wanted to confirm this understanding. Please note that I don't want the JSR 286 features available in my existing JSR 168 portlets.

Regards,
Sourav

[prabhat.jha]

You should be fine.

[soon5]

Hy,

I'm posing here, because it matches my Topic.
I'm currently trying to switch from JBP 2.6.6 to 2.7.2. I compared the two versions and moved the changes i made (like adding Themes) to the new XML Files.

After deployment, i get several ClassNotFound Exceptions, i can't understand.

No ClassLoaders found for: org.jboss.hibernate.jbc.cacheprovider.OptimisticJBCCache$NonLockingDataVersion

No ClassLoaders found for: org.apache.jackrabbit.core.query.HTMLTextFilter

I searched in the JARs provided with 2.7.2 and found the "missing" org.jboss.hibernate.jbc.. Cache in the hibernate-jbc-cacheprovider.jar File. I don't understand why it is not loaded.

I am using JBoss 4.2.1.GA and the HA Version of JBP 2.6.6 / JBP 2.7.2.

Thanks so far

Regards

Soon5

[soon5]

Hy out there,

Just wanted to reply that I found the Problem. It wasn't a problem with JBP 2.7.2. I had another Server with JBP 2.6.6 running in the same Subnet, so the Caches of the Servers wanted to synchronise each other. And the Exceptions i saw were not from JBP 2.7.2, they were from the other Server which (actualy logical) didn't found the classes to load.

Regards

Soon5