mwringe, could you please elaborate more on the last paragraph?
When and how does Red Hat plan to support Portal under JBoss 5?
I hope it won't take as long as JBoss 5 itself,-)
There is also currently no enterprise version of JBoss Portal that runs on
JBoss 5, are there any plans, maybe to
Thank you Thomas for your quick reply! This was very informative, and I'm
looking forward to the integration of the two portal projects, must have missed
that one... (blame my Vista RSS-gadget,-)
If the method in the howto is not supported (neither officially nor
inofficially) it does not seem
Great to see cross-container-compatibility! Even if we use only JBoss for now,
it's a big plus regarding standards-compliance and code quality.
Also good to hear the commitment to the portlet bridge, after a Google-esk
beta-cycle,-)
Wink noted and directed to my colleague responsible for the
The only thing that helped was to replace the Spring-JARs that come with
JBoss-WS/CXF (spring-beans, -context and -core) with pristine JARs from a clean
Spring distribution. The ones that come with JBoss-WS seem to be borked somehow.
View the original post :
Unfortunately I stumble across the same issue but the proposed solution did not
help, double-checked my classpath and tried different Spring-versions, even
replacing spring-jars in jbossws.sar, but still get the same error, using JBoss
4.2.3.GA + jbossws-cxf-3.1.0.GA on Windows Vista, JDK
another reason for not wanting to isolate the EAR would be
application-server-interoperability. OC4J e.g. offers no simple way to isolate
classloaders like JBoss, so this is a major PITA if you have to support both
AS-platforms.
So I would also be interested in an elegant solution to this
Glad I am not alone with this... I get the same error here, with the following
taglibs (as you can see this is a Struts-webapp):
%@ taglib uri=/WEB-INF/tld/struts-html.tld prefix=html%
| %@ taglib uri=/WEB-INF/tld/struts-bean.tld prefix=bean%
I am on Java 1.4.2 and JBoss 4.0.4.GA_p1 (also tried
