Hide Forgot
Date of First Response: 2010-05-18 10:54:09 project_key: JBEPP Seam has a bug in EAP 5.0 that makes it generate AS 5 incompatible pages. JBPAPP-4259 fixes it in EAP 5.1 but for Seam to work with JBDS 5.0.x should be fixed too. (was asked to report this in downstream products by EAP production team)
Link: Added: This issue depends JBPAPP-4259
Clarification: te fix will already be included in the EAP/EWP 5.1.0 so the only concern is with EPP based on EAP 5.0.x editions
I believe Seam-gen templates using resource:// is one part of the problem that Thomas have seen, but that should "only" result in a stylesheets being non-transformed. The hard error that have been reported by QA and Thomas H. I believe is what is captured in PBR-148 which is similar but not a real duplicate as far as I can see.
Link: Added: This issue related PBR-148
Assigned to Wesley for definitive answer on this issue. It looks like there are several issues at the end.
What exactly are you wanting my answer on? Do you want verification that resource:// should only be used for classpath or RF based resources - and not for stuff coming from the web/view? Or should I be verifying that resource:// using a local resource does not cause a hard error in EPP 5.0.0 - and that we need to do something to fix it for 5.0.1?
I’m trying to develop a POC with jboss-epp-5.0.0.GA, but this issue is blocking me. As version 5.0.1.GA may be some time away, is there any workaround?
There are too many different problems described in the details of this jira regarding loadstyle. What is your problem exactly?
Ok, thanks for your prompt reply. With jbdevstudio-win32-3.0.1 patched from http://download.eclipse.org/webtools/updates, I've created a new Dynamic Web Project configured to include following facets: JBoss Core Portlet 2.0, JBoss JSF Portlet 1.0, JavaServer Faces 1.2, JBoss Seam Portlet 1.0 and Seam 2.2. In addition, the Portlet Implementation Library is configured to Portlet Target Runtime Provider and all other settings are defaults. To this project I've then added a new JBoss JSF/Seam Portlet and run on default EPP server with following VM arguments: -Dprogram.name="JBossTools: jboss-epp-5.0 Runtime" -Xms1303m -Xmx1303m -XX:MaxPermSize=256m -Dsun.rmi.dgc.client.gcInterval=3600000 -Dsun.rmi.dgc.server.gcInterval=3600000 -Djava.endorsed.dirs="C:\JBoss\jboss-epp-5.0\jboss-as\lib\endorsed". From a browser, I've logged in as Administrator, accessed Application Registry, imported applications, set access permission for the portlet to public and added it to the portal with the site layout editor and upon saving the attached relevant log errors are generated.
Attachment: Added: Relevant Server Log.txt
Release Notes Docs Status: Added: Not Required