[JBoss JIRA] (AS7-3115) Immediate EL syntax does not work with JSF 1.2
by Rajesh Rajasekaran (JIRA)
[ https://issues.jboss.org/browse/AS7-3115?page=com.atlassian.jira.plugin.s... ]
Rajesh Rajasekaran closed AS7-3115.
-----------------------------------
Fix Version/s: No Release
(was: 7.1.0.Final)
Resolution: Rejected
EL 2.2 parser included in JBossWeb correctly figures out that "the dot part" (new) is a Java keyword and thus throws the exception.
This check is not performed by default in implementation provided by EWS1 and EAP5, thus the exception.
Note: For Tomcat 6, the check can be enforced by specifying following property:
One has to set org.apache.el.parser.SKIP_IDENTIFIER_CHECK property to "false".
Closed as not a bug.
> Immediate EL syntax does not work with JSF 1.2
> ----------------------------------------------
>
> Key: AS7-3115
> URL: https://issues.jboss.org/browse/AS7-3115
> Project: Application Server 7
> Issue Type: Bug
> Components: Web
> Affects Versions: 7.1.0.Beta1b
> Reporter: Karel Piwko
> Assignee: Remy Maucherat
> Fix For: No Release
>
> Attachments: petclinic-hibernate4.zip
>
>
> Following code is broken for AS7, however it works on Tomcat 5 and Tomcat 6:
> {code:xml}
> <h2><c:if test="${owner.new}">New </c:if>Owner:</h2>
> {code}
> where Owner is a POJO/Hibernate Entity and isNew() boolean is available on its ancestor.
> Failure:
> {code}
> org.apache.jasper.JasperException: /WEB-INF/jsp/ownerForm.jsp(4,4) "${owner.new}" contains invalid expression(s): javax.el.ELException: Failed to parse the expression [${owner.new}]
> org.apache.jasper.compiler.DefaultErrorHandler.jspError(DefaultErrorHandler.java:40)
> org.apache.jasper.compiler.ErrorDispatcher.dispatch(ErrorDispatcher.java:407)
> org.apache.jasper.compiler.ErrorDispatcher.jspError(ErrorDispatcher.java:198)
> org.apache.jasper.compiler.Validator$ValidateVisitor.checkXmlAttributes(Validator.java:1216)
> org.apache.jasper.compiler.Validator$ValidateVisitor.visit(Validator.java:862)
> org.apache.jasper.compiler.Node$CustomTag.accept(Node.java:1530)
> org.apache.jasper.compiler.Node$Nodes.visit(Node.java:2377)
> org.apache.jasper.compiler.Node$Visitor.visitBody(Node.java:2427)
> org.apache.jasper.compiler.Node$Visitor.visit(Node.java:2433)
> org.apache.jasper.compiler.Node$Root.accept(Node.java:495)
> org.apache.jasper.compiler.Node$Nodes.visit(Node.java:2377)
> org.apache.jasper.compiler.Validator.validateExDirectives(Validator.java:1793)
> org.apache.jasper.compiler.Compiler.generateJava(Compiler.java:211)
> org.apache.jasper.compiler.Compiler.compile(Compiler.java:360)
> org.apache.jasper.compiler.Compiler.compile(Compiler.java:340)
> org.apache.jasper.compiler.Compiler.compile(Compiler.java:327)
> org.apache.jasper.JspCompilationContext.compile(JspCompilationContext.java:607)
> org.apache.jasper.servlet.JspServletWrapper.service(JspServletWrapper.java:312)
> org.apache.jasper.servlet.JspServlet.serviceJspFile(JspServlet.java:326)
> org.apache.jasper.servlet.JspServlet.service(JspServlet.java:253)
> javax.servlet.http.HttpServlet.service(HttpServlet.java:847)
> org.springframework.web.servlet.view.InternalResourceView.renderMergedOutputModel(InternalResourceView.java:238)
> org.springframework.web.servlet.view.AbstractView.render(AbstractView.java:262)
> org.springframework.web.servlet.DispatcherServlet.render(DispatcherServlet.java:1157)
> org.springframework.web.servlet.DispatcherServlet.doDispatch(DispatcherServlet.java:927)
> org.springframework.web.servlet.DispatcherServlet.doService(DispatcherServlet.java:827)
> org.springframework.web.servlet.FrameworkServlet.processRequest(FrameworkServlet.java:882)
> org.springframework.web.servlet.FrameworkServlet.doGet(FrameworkServlet.java:778)
> javax.servlet.http.HttpServlet.service(HttpServlet.java:734)
> javax.servlet.http.HttpServlet.service(HttpServlet.java:847)
> {code}
> Note that deferred syntax #{owner.new} works correctly there.
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.jboss.org/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira
14 years, 3 months
[JBoss JIRA] (AS7-3199) RESTEasy: Can't deploy WebApp if more than one subclass of javax.ws.rs.Application is present
by Rajesh Rajasekaran (JIRA)
[ https://issues.jboss.org/browse/AS7-3199?page=com.atlassian.jira.plugin.s... ]
Rajesh Rajasekaran updated AS7-3199:
------------------------------------
Fix Version/s: 7.1.0.Final
Priority: Critical (was: Blocker)
Labels: eap6_prd_req (was: )
Assignee: Stuart Douglas (was: Weinan Li)
This item in the spec is obviously not covered in the JAX-RS tck, and we are focusing on integration tests that target all SPEC requirements.
> RESTEasy: Can't deploy WebApp if more than one subclass of javax.ws.rs.Application is present
> ---------------------------------------------------------------------------------------------
>
> Key: AS7-3199
> URL: https://issues.jboss.org/browse/AS7-3199
> Project: Application Server 7
> Issue Type: Bug
> Components: REST
> Affects Versions: 7.1.0.CR1b
> Reporter: Pavel Janousek
> Assignee: Stuart Douglas
> Priority: Critical
> Labels: eap6_prd_req
> Fix For: 7.1.0.Final
>
> Attachments: ExampleJAXRS.war
>
>
> If I packed WAR WebApp with more that one subclass of javax.ws.rs.Application, deployment fails with "JBAS011232: Only one JAX-RS Application Class allowed."
> This is not correct because it is against JAX-RS 1.1. specs where invalid situation (in section 2.3.2) is only when "It is a n error for
> more than one application to be deployed +at the same effective servlet mapping+".
> If you have any objections, please compare to reference JEE6 and JAX-RS implementation represented by the GlassFish Prelude 3.1.1 application server with already +fully JEE6 platform support+.
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.jboss.org/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira
14 years, 3 months
[JBoss JIRA] (AS7-3039) User Documentation part of description "How to re-configure AS7 for working in IPv6 environment" is missing
by Rajesh Rajasekaran (JIRA)
[ https://issues.jboss.org/browse/AS7-3039?page=com.atlassian.jira.plugin.s... ]
Rajesh Rajasekaran closed AS7-3039.
-----------------------------------
Resolution: Duplicate Issue
Documentation items will be done by the EAP6 docs team which will be tracked by the linked JBPAPP jira. Closing this AS7 jira as duplicate.
> User Documentation part of description "How to re-configure AS7 for working in IPv6 environment" is missing
> -----------------------------------------------------------------------------------------------------------
>
> Key: AS7-3039
> URL: https://issues.jboss.org/browse/AS7-3039
> Project: Application Server 7
> Issue Type: Bug
> Components: Documentation
> Affects Versions: 7.1.0.Beta1
> Reporter: Pavel Janousek
> Assignee: EAP 5 Docs Lead
> Priority: Blocker
>
> Default configuration of AS7 is distributed as force to use IPv4 network stack only (even IPv6 network stack is available on hosting platform). There is several steps and requirements to re-configure AS7 installed instance to allow it utilizing the IPv6 network stack and environment too (or use it exclusively).
> This is very important in pure IPv6 network stack environment, because in a such environment default installation isn't able to start at all.
> The issue is that there isn't +any+ User Guide or other documentation *how* user should re-configure its AS7 instance to work in an IPv6 environment.
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.jboss.org/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira
14 years, 3 months
[JBoss JIRA] (AS7-2572) Cannot run JAXR drop tables script on shutdown
by Thomas Diesler (Created) (JIRA)
Cannot run JAXR drop tables script on shutdown
----------------------------------------------
Key: AS7-2572
URL: https://issues.jboss.org/browse/AS7-2572
Project: Application Server 7
Issue Type: Bug
Components: JAXR
Reporter: Thomas Diesler
Assignee: Kurt Stam
Fix For: 7.1.0.CR1
{code}
09:20:34,685 ERROR [org.jboss.as.jaxr.service.JAXRBootstrapService] Cannot start JUDDI service: org.h2.jdbc.JdbcSQLException: Database is already closed (to disable automatic closing at VM shutdown, add ";DB_CLOSE_ON_EXIT=FALSE" to the db URL) [90121-145]
at org.h2.message.DbException.getJdbcSQLException(DbException.java:327)
at org.h2.message.DbException.get(DbException.java:167)
at org.h2.message.DbException.get(DbException.java:144)
at org.h2.message.DbException.get(DbException.java:133)
at org.h2.jdbc.JdbcConnection.checkClosed(JdbcConnection.java:1333)
at org.h2.jdbc.JdbcConnection.checkClosed(JdbcConnection.java:1308)
at org.h2.jdbc.JdbcConnection.createStatement(JdbcConnection.java:164)
at org.jboss.jca.adapters.jdbc.WrappedConnection.createStatement(WrappedConnection.java:301)
at org.jboss.as.jaxr.service.JAXRBootstrapService.runScript(JAXRBootstrapService.java:172) [jboss-as-jaxr-7.1.0.Alpha2-SNAPSHOT.jar:7.1.0.Alpha2-SNAPSHOT]
at org.jboss.as.jaxr.service.JAXRBootstrapService.locateAndRunScript(JAXRBootstrapService.java:156) [jboss-as-jaxr-7.1.0.Alpha2-SNAPSHOT.jar:7.1.0.Alpha2-SNAPSHOT]
at org.jboss.as.jaxr.service.JAXRBootstrapService.runDrop(JAXRBootstrapService.java:138) [jboss-as-jaxr-7.1.0.Alpha2-SNAPSHOT.jar:7.1.0.Alpha2-SNAPSHOT]
at org.jboss.as.jaxr.service.JAXRBootstrapService.stop(JAXRBootstrapService.java:128)
{code}
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.jboss.org/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira
14 years, 3 months