June 2007 - jboss-jira - Jboss List Archives

[JBoss JIRA] Updated: (JBAOP-259) Make AOP testsuite test run with all main weaving types

by Kabir Khan (JIRA)

[ http://jira.jboss.com/jira/browse/JBAOP-259?page=all ] Kabir Khan updated JBAOP-259: ----------------------------- Fix Version/s: (was: 2.0.0.alpha6) > Make AOP testsuite test run with all main weaving types > ------------------------------------------------------- > > Key: JBAOP-259 > URL: http://jira.jboss.com/jira/browse/JBAOP-259 > Project: JBoss AOP > Issue Type: Task > Reporter: Kabir Khan > Assigned To: Kabir Khan > -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: http://jira.jboss.com/jira/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira

19 years, 1 month

1
0
0 / 0

[JBoss JIRA] Closed: (JBAOP-259) Make AOP testsuite test run with all main weaving types

by Kabir Khan (JIRA)

[ http://jira.jboss.com/jira/browse/JBAOP-259?page=all ] Kabir Khan closed JBAOP-259. ---------------------------- Resolution: Done This is now covered by the runs on cc and hudson > Make AOP testsuite test run with all main weaving types > ------------------------------------------------------- > > Key: JBAOP-259 > URL: http://jira.jboss.com/jira/browse/JBAOP-259 > Project: JBoss AOP > Issue Type: Task > Reporter: Kabir Khan > Assigned To: Kabir Khan > -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: http://jira.jboss.com/jira/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira

19 years, 1 month

1
0
0 / 0

[JBoss JIRA] Created: (JBAS-4483) Validation error messages from TagLibraryValidator

by Prashant Kothawade (JIRA)

Validation error messages from TagLibraryValidator -------------------------------------------------- Key: JBAS-4483 URL: http://jira.jboss.com/jira/browse/JBAS-4483 Project: JBoss Application Server Issue Type: Bug Security Level: Public (Everyone can see) Affects Versions: JBossAS-4.0.5.GA Environment: WIndows as well as Linux Reporter: Prashant Kothawade Fix For: JBossAS-4.0.5.GA The JSP which runs on JBoss 4.0.4 does not run on JBoss 4.0.5. I got the following error : 2007-06-08 06:37:02,278 ERROR [org.apache.catalina.core.ContainerBase.[jboss.web].[localhost].[/infinity-beta].[action]] Servlet.service() for servlet action threw exception javax.servlet.jsp.JspException: ServletException in '/solutionreg/sla/serviceLevelAdd.jsp': <h3>Validation error messages from TagLibraryValidator for c in /solutionreg/sla/serviceLevelAdd.jsp</h3><p>null: org.xml.sax.SAXParseException: An invalid XML character (Unicode: 0x1b) was found in the CDATA section.</p><h3>Validation error messages from TagLibraryValidator for fmt in /solutionreg/sla/serviceLevelAdd.jsp</h3><p>null: org.xml.sax.SAXParseException: An invalid XML character (Unicode: 0x1b) was found in the CDATA section.</p> at org.apache.struts.taglib.tiles.InsertTag$InsertHandler.doEndTag(InsertTag.java:923) at org.apache.struts.taglib.tiles.InsertTag.doEndTag(InsertTag.java:462) at org.apache.jsp.csa.layout.mainLayout_jsp._jspx_meth_tiles_get_6(mainLayout_jsp.java:1564) at org.apache.jsp.csa.layout.mainLayout_jsp._jspx_meth_c_otherwise_2(mainLayout_jsp.java:1537) at org.apache.jsp.csa.layout.mainLayout_jsp._jspx_meth_c_choose_2(mainLayout_jsp.java:1373) at org.apache.jsp.csa.layout.mainLayout_jsp._jspService(mainLayout_jsp.java:252) at org.apache.jasper.runtime.HttpJspBase.service(HttpJspBase.java:97) at javax.servlet.http.HttpServlet.service(HttpServlet.java:810) at org.apache.jasper.servlet.JspServletWrapper.service(JspServletWrapper.java:334) at org.apache.jasper.servlet.JspServlet.serviceJspFile(JspServlet.java:314) at org.apache.jasper.servlet.JspServlet.service(JspServlet.java:264) at javax.servlet.http.HttpServlet.service(HttpServlet.java:810) at org.apache.catalina.core.ApplicationFilterChain.internalDoFilter(ApplicationFilterChain.java:252) at org.apache.catalina.core.ApplicationFilterChain.doFilter(ApplicationFilterChain.java:173) at org.apache.catalina.core.ApplicationDispatcher.invoke(ApplicationDispatcher.java:672) Snippet of the java code created for the JSP by JBoss : private boolean _jspx_meth_tiles_get_6(javax.servlet.jsp.tagext.JspTag _jspx_th_c_otherwise_2, PageContext _jspx_page_context) throws Throwable { PageContext pageContext = _jspx_page_context; JspWriter out = _jspx_page_context.getOut(); // tiles:get org.apache.struts.taglib.tiles.GetTag _jspx_th_tiles_get_6 = (org.apache.struts.taglib.tiles.GetTag) _jspx_tagPool_tiles_get_name_nobody.get(org.apache.struts.taglib.tiles.GetTag.class); _jspx_th_tiles_get_6.setPageContext(_jspx_page_context); _jspx_th_tiles_get_6.setParent((javax.servlet.jsp.tagext.Tag) _jspx_th_c_otherwise_2); _jspx_th_tiles_get_6.setName("content"); int _jspx_eval_tiles_get_6 = _jspx_th_tiles_get_6.doStartTag(); if (_jspx_th_tiles_get_6.doEndTag() == javax.servlet.jsp.tagext.Tag.SKIP_PAGE) {---------------LINE 1564 _jspx_tagPool_tiles_get_name_nobody.reuse(_jspx_th_tiles_get_6); return true; } _jspx_tagPool_tiles_get_name_nobody.reuse(_jspx_th_tiles_get_6); return false; } See the Line 1564, which is giving the problem. As mentioned earlier, the same code works on JBoss' earlier version i.e. JBoss 4.0.4 Has JBoss become more stringent in interpreting the TLDs which is causing this problem? This issue is critical for us as we are planning to use JBoss 4.0.5 GA in production. -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: http://jira.jboss.com/jira/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira

19 years, 1 month

2
1
0 / 0

[JBoss JIRA] Created: (JBAOP-417) Update quick reference

by Kabir Khan (JIRA)

Update quick reference ---------------------- Key: JBAOP-417 URL: http://jira.jboss.com/jira/browse/JBAOP-417 Project: JBoss AOP Issue Type: Feature Request Security Level: Public (Everyone can see) Reporter: Kabir Khan Fix For: 2.0.0.alpha6 -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: http://jira.jboss.com/jira/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira

19 years, 1 month

1
1
0 / 0

[JBoss JIRA] Created: (JBPORTAL-1347) URLNavigator test improvements

by Julien Viet (JIRA)

URLNavigator test improvements ------------------------------ Key: JBPORTAL-1347 URL: http://jira.jboss.com/jira/browse/JBPORTAL-1347 Project: JBoss Portal Issue Type: Task Security Level: Public (Everyone can see) Reporter: Julien Viet Assigned To: Matt Wringe Fix For: 2.6.CR2 -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: http://jira.jboss.com/jira/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira

19 years, 1 month

2
3
0 / 0

[JBoss JIRA] Created: (JBMESSAGING-964) Enable all security tests

by Tim Fox (JIRA)

Enable all security tests ------------------------- Key: JBMESSAGING-964 URL: http://jira.jboss.com/jira/browse/JBMESSAGING-964 Project: JBoss Messaging Issue Type: Task Reporter: Tim Fox Fix For: 1.2.1.CR1 Some tests in jms/SecurityTest are commented out (pre configured client ids) - they should be re-enabled. -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: http://jira.jboss.com/jira/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira

19 years, 1 month

2
5
0 / 0

[JBoss JIRA] Created: (JBAOP-419) Update the ReadMe-AS4.txt files

by Kabir Khan (JIRA)

Update the ReadMe-AS4.txt files ------------------------------- Key: JBAOP-419 URL: http://jira.jboss.com/jira/browse/JBAOP-419 Project: JBoss AOP Issue Type: Feature Request Security Level: Public (Everyone can see) Reporter: Kabir Khan Fix For: 2.0.0.alpha6 -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: http://jira.jboss.com/jira/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira

19 years, 1 month

1
1
0 / 0

[JBoss JIRA] Created: (JBAOP-418) Update version in user guide

by Kabir Khan (JIRA)

Update version in user guide ---------------------------- Key: JBAOP-418 URL: http://jira.jboss.com/jira/browse/JBAOP-418 Project: JBoss AOP Issue Type: Feature Request Security Level: Public (Everyone can see) Reporter: Kabir Khan Fix For: 2.0.0.alpha6 -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: http://jira.jboss.com/jira/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira

19 years, 1 month

1
1
0 / 0

[JBoss JIRA] Created: (JBAS-4487) Checking of Transaction Complete is missing rolled back transactions

by Adrian Brock (JIRA)

Checking of Transaction Complete is missing rolled back transactions -------------------------------------------------------------------- Key: JBAS-4487 URL: http://jira.jboss.com/jira/browse/JBAS-4487 Project: JBoss Application Server Issue Type: Sub-task Security Level: Public (Everyone can see) Components: Transaction Manager Affects Versions: JBossAS-4.2.0.GA Reporter: Adrian Brock Fix For: JBossAS-4.2.1.CR1 Checking of transaction complete is trapping threads that have been rolled back but not removed from the transaction context of the thread. e.g. 1) the transaction timed out and was rolled back 2) the user used the Transaction rather than TransactionManager api which did does not remove the thread association In org.jboss.ejb.plugins.AbstractTxInterceptorBMT and org.jboss.web.tomcat.service.jca.CachedConnectionValve There needs to be extra code (after the incomplete check) that says that if the tx status is not NO_TRANSACTION is does TransactionManager.suspend(transaction) to remove the thread assocation. -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: http://jira.jboss.com/jira/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira

19 years, 1 month

2
6
0 / 0

[JBoss JIRA] Created: (JBPORTAL-1355) PortletSecurityException throws ClassCastException

by Prabhat Jha (JIRA)

PortletSecurityException throws ClassCastException -------------------------------------------------- Key: JBPORTAL-1355 URL: http://jira.jboss.com/jira/browse/JBPORTAL-1355 Project: JBoss Portal Issue Type: Bug Security Level: Public (Everyone can see) Affects Versions: 2.6.CR1 Reporter: Prabhat Jha Assigned To: Julien Viet Fix For: 2.6.CR2 PortletSecurityException test in test page throws ClassCastException. avax.servlet.ServletException org.jboss.portal.server.servlet.PortalServlet.service(PortalServlet.java:406) javax.servlet.http.HttpServlet.service(HttpServlet.java:810) org.jboss.web.tomcat.filters.ReplyHeaderFilter.doFilter(ReplyHeaderFilter.java:96) root cause java.lang.ClassCastException org.jboss.portal.core.model.portal.PortalObjectResponseHandler.processCommandResponse(PortalObjectResponseHandler.java:63) org.jboss.portal.core.controller.classic.ClassicResponseHandler.processHandlers(ClassicResponseHandler.java:96) org.jboss.portal.core.controller.classic.ClassicResponseHandler.processCommandResponse(ClassicResponseHandler.java:70) sun.reflect.GeneratedMethodAccessor311.invoke(Unknown Source) sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25) java.lang.reflect.Method.invoke(Method.java:324) org.jboss.mx.interceptor.ReflectedDispatcher.invoke(ReflectedDispatcher.java:155) org.jboss.mx.server.Invocation.dispatch(Invocation.java:94) org.jboss.mx.interceptor.AbstractInterceptor.invoke(AbstractInterceptor.java:133) org.jboss.mx.server.Invocation.invoke(Invocation.java:88) org.jboss.mx.interceptor.ModelMBeanOperationInterceptor.invoke(ModelMBeanOperationInterceptor.java:142) org.jboss.mx.server.Invocation.invoke(Invocation.java:88) org.jboss.mx.server.AbstractMBeanInvoker.invoke(AbstractMBeanInvoker.java:264) org.jboss.mx.server.MBeanServerImpl.invoke(MBeanServerImpl.java:659) org.jboss.mx.util.MBeanProxyExt.invoke(MBeanProxyExt.java:210) $Proxy118.processCommandResponse(Unknown Source) org.jboss.portal.core.controller.ResponseHandlerSelector.processCommandResponse(ResponseHandlerSelector.java:69) sun.reflect.GeneratedMethodAccessor310.invoke(Unknown Source) sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25) java.lang.reflect.Method.invoke(Method.java:324) org.jboss.mx.interceptor.ReflectedDispatcher.invoke(ReflectedDispatcher.java:155) org.jboss.mx.server.Invocation.dispatch(Invocation.java:94) org.jboss.mx.interceptor.AbstractInterceptor.invoke(AbstractInterceptor.java:133) org.jboss.mx.server.Invocation.invoke(Invocation.java:88) org.jboss.mx.interceptor.ModelMBeanOperationInterceptor.invoke(ModelMBeanOperationInterceptor.java:142) org.jboss.mx.server.Invocation.invoke(Invocation.java:88) org.jboss.mx.server.AbstractMBeanInvoker.invoke(AbstractMBeanInvoker.java:264) org.jboss.mx.server.MBeanServerImpl.invoke(MBeanServerImpl.java:659) org.jboss.mx.util.MBeanProxyExt.invoke(MBeanProxyExt.java:210) $Proxy129.processCommandResponse(Unknown Source) org.jboss.portal.core.controller.Controller.processCommandResponse(Controller.java:263) org.jboss.portal.core.controller.Controller.processCommand(Controller.java:251) org.jboss.portal.core.controller.Controller.processHandlerResponse(Controller.java:286) -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: http://jira.jboss.com/jira/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira

19 years, 1 month

2
3
0 / 0

2026

2025

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

2009

2008

2007

2006

jboss-jira June 2007