Folks:
I am currently interested in using JBoss Portal for various sites that I want to create.
Unfortunately, what has prevented me from using JBoss Portal is the fact that I have several pre- existing applications that are using JEE 5. It is my understanding that only JBoss 5 supports JEE 5.
Is anyone planning on getting JBoss Portal to work on JBoss 5? If not, then I am going to have to stick with using Liferay/Sun Webspace...
Could someone give some idea if and when a JBoss 5 supported version of JBoss Portal is coming?
Thank you.
View the original post : http://www.jboss.org/index.html?module=bb&op=viewtopic&p=4244487#4244487
Reply to the post : http://www.jboss.org/index.html?module=bb&op=posting&mode=reply&p=4244487
Yeah, I don't buy this "implicit dependencies" business. The beauty of the MC deployer architecture is that when you deploy stuff, you can make dependencies which are implicit (as far as the user sees) translate to explicit dependencies before the container even sees the deployment.
As for "depending" on JNDI, I think that should always translate into a real explicit dependency, which is filled by a special bean deployment that represents the JNDI binding. These special deployments can be implicitly created by the EJB and JCA deployers, much like how I bind logging handlers to logger categories.
I think that the value of having a highly efficient (and simple) dependency resolution algorithm will far, far outweigh its support for edge cases that can be easily implemented in other ways.
View the original post : http://www.jboss.org/index.html?module=bb&op=viewtopic&p=4244482#4244482
Reply to the post : http://www.jboss.org/index.html?module=bb&op=posting&mode=reply&p=4244482
Please do not use large blocks of bold or colored text. That kind of highlighting should be reserved for pointing out specific items (like you did for the things you changed in the *-ds.xml file). Also, use the 'code' tags when posting xml text.
2) Maybe. If your settings are correct, that is all you need. But you will not know that until the first time your app attempts to get a connection.
1) Place the whole EAR (jar+war) into the deploy directory. Then start the app server. If you get any exceptions, post the full stack trace for only the first exception. And don't bold or color anything!
View the original post : http://www.jboss.org/index.html?module=bb&op=viewtopic&p=4244474#4244474
Reply to the post : http://www.jboss.org/index.html?module=bb&op=posting&mode=reply&p=4244474