Portal environment differences

[blandahl]

Is there a pointer as to what feature(s) in JBoss AS 4.03 is required to support Portal 2.2?

Using Portal 2.2 (+) under JBoss AS 4.02 leads to errors such as:

.......
org.jboss.util.NestedRuntimeException: Error creating MBeanProxy: portal:mapper=PrefixDelegating; - nested throwable: (javax.management.InstanceNotFoundException: portal:mapper=PrefixDelegating is not registered.)
at org.jboss.mx.util.MBeanProxyExt.(MBeanProxyExt.java:78)
at org.jboss.mx.util.MBeanProxyExt.create(MBeanProxyExt.java:342)
......
Caused by: javax.management.InstanceNotFoundException: portal:mapper=PrefixDelegating is not registered.
at org.jboss.mx.server.registry.BasicMBeanRegistry.get(BasicMBeanRegistry.java:509)
at org.jboss.mx.server.MBeanServerImpl.getMBeanInfo(MBeanServerImpl.java:651)
at org.jboss.mx.util.MBeanProxyExt.(MBeanProxyExt.java:70)
......

I'm stuck at 4.02 for a while, so checking out Portal 2.0 (which does run). But, I would like to understand the constraints, so pointers as to where to begin studying will be appreciated.

[roy.russo]

Portal 2.2 must be deployed in 4.0.3SP1 or higher.

[blandahl]

Yes, that was clearly documented and in fact worked well in a (test) JBoss installation.

I'm looking to get a better understanding of how JBoss AS & Portal work together. As such, I'm looking for a place to start to in order see why 4.03SP1 is required. May any sense? thanks

[roy.russo]

As far as 2.2 goes, if I can remember correctly, it had to do with changes in Hibernate.

Honestly, I can't remember exactly what dependencies with Hibernate we had that we had to make the jump. I believe 4.0.3SP1 has hib3 and 4.0.2 had hib 2.

[blandahl]

Got it! I appreciate the quick response.