-
1. Re: Migration from JBP 2.6.6 to JBP 2.7.2 ...
prabhat.jha May 8, 2009 11:34 AM (in response to souravm)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. ;) -
2. Re: Migration from JBP 2.6.6 to JBP 2.7.2 ...
souravm May 8, 2009 2:18 PM (in response to 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 -
3. Re: Migration from JBP 2.6.6 to JBP 2.7.2 ...
prabhat.jha May 8, 2009 2:23 PM (in response to souravm)You should be fine.
-
4. Re: Migration from JBP 2.6.6 to JBP 2.7.2 ...
soon5 Jun 9, 2009 4:29 AM (in response to souravm)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 -
5. Re: Migration from JBP 2.6.6 to JBP 2.7.2 ...
soon5 Jun 10, 2009 1:25 AM (in response to souravm)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