... to honor your work ...
It's one year ago, since I started evaluation of portals on behalf of our customer. The first impression of the portal design, its flexibility and easy understanding were good arguments to choose JBP as new portal base.
Since mid august we have successfully migrated b2b portals, formerly based on SAP Netwaver, to the new infrastructure - stability and performance are good arguments against remaining doubts...
So, well done portal team!
If your are interested in this success story (and the improvements we made to fit the needs) please let me know, of course, I have to get the confirmation from our customer first.
View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=4100567#4100567
Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=4100567
Rebuilt the metadata code on another box and I'm back to seeing this old error:
| Caused by: java.lang.RuntimeException: Error instantiating bean for org.jboss.metadata.common.ejb.IAssemblyDescriptorMetaData
| at org.jboss.xb.spi.AbstractBeanAdapter.construct(AbstractBeanAdapter.java:119)
| at org.jboss.xb.spi.AbstractBeanAdapter.ensureConstructed(AbstractBeanAdapter.java:129)
| at org.jboss.xb.spi.DefaultBeanAdapter.<init>(DefaultBeanAdapter.java:46)
| at org.jboss.xb.spi.DefaultBeanAdapterFactory.newInstance(DefaultBeanAdapterFactory.java:49)
| at org.jboss.xb.spi.DefaultBeanAdapterFactory.newInstance(DefaultBeanAdapterFactory.java:33)
| at org.jboss.xb.builder.runtime.BeanHandler.startParticle(BeanHandler.java:113)
| ... 35 more
| Caused by: org.jboss.joinpoint.spi.JoinpointException: Constructor not found org.jboss.metadata.common.ejb.IAssemblyDescriptorMetaData no constructors
| at org.jboss.joinpoint.plugins.Config.findConstructorInfo(Config.java:276)
| at org.jboss.joinpoint.plugins.Config.getConstructorJoinpoint(Config.java:150)
| at org.jboss.beans.info.plugins.AbstractBeanInfo.newInstance(AbstractBeanInfo.java:221)
| at org.jboss.beans.info.plugins.AbstractBeanInfo.newInstance(AbstractBeanInfo.java:216)
| at org.jboss.xb.spi.AbstractBeanAdapter.construct(AbstractBeanAdapter.java:115)
| ... 40 more
I have rebuilt the jbossxb and even changed to a non-snapshot version locally to make sure its using the expected version, and still see this error. I don't see the hudson stuff Carlo is running showing this problem though.
View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=4100519#4100519
Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=4100519
"scott.stark(a)jboss.org" wrote :
| Because its unnecessary busy work. What's the point of a multi-container kernel if you don't use multiple container types?
That's why I was asking if there is a tool to do this for you. :-)
Not all container shoes fit all container feet. ;-)
You don't want to push all features to all impls/legacy.
"scott.stark(a)jboss.org" wrote :
| If supply/demand are to be mc bean specific it simply cannot be used as a cross-container mechanism. It seems like this can be replaced with a dependency on an alias, in which case, that is how the mc supply/demand should be implemented.
Yes, this is a legit/current workaround.
You can add an alias to mbean, which will work as a supply for any MC bean.
View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=4100474#4100474
Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=4100474