July 2006 - jboss-jira - Jboss List Archives

[JBoss JIRA] Resolved: (JBCACHE-85) PojoCache object event listener

by Ben Wang (JIRA)

[ http://jira.jboss.com/jira/browse/JBCACHE-85?page=all ] Ben Wang resolved JBCACHE-85. ----------------------------- Resolution: Done > PojoCache object event listener > ------------------------------- > > Key: JBCACHE-85 > URL: http://jira.jboss.com/jira/browse/JBCACHE-85 > Project: JBoss Cache > Issue Type: Feature Request > Components: PojoCache > Reporter: Ben Wang > Assigned To: Ben Wang > Fix For: POJOCache > > Original Estimate: 2 weeks > Remaining Estimate: 2 weeks > > Need to add a TreeCacheAop object event listener. Currently we have TreeCache listener to listen for individual node event. We need to listen the event at the object level instead. User may not be interested to listen at the node level. > We should have events for: > * Object level > * Field level > 1. We will need to define a PojoCacheListener that has all these callbacks. > 2. We should use annotation for user to denote interested points, e.g., a la EJB3 style call back > Class Pojo > { > int key; > @preCreated(pojoEvent) > @preModified(pojoEvent) > void someHandler(); > } > where > Interface preModified { > getPojoEvent(); > } -- 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, 10 months

1
0
0 / 0

[JBoss JIRA] Assigned: (JBAS-2225) FCI.getTargets() should be Immutable

by Ben Wang (JIRA)

[ http://jira.jboss.com/jira/browse/JBAS-2225?page=all ] Ben Wang reassigned JBAS-2225: ------------------------------ Assignee: Brian Stansberry (was: Ben Wang) > FCI.getTargets() should be Immutable > ------------------------------------ > > Key: JBAS-2225 > URL: http://jira.jboss.com/jira/browse/JBAS-2225 > Project: JBoss Application Server > Issue Type: Sub-task > Security Level: Public(Everyone can see) > Components: Clustering > Affects Versions: JBossAS-4.0.3RC2 > Reporter: Adrian Brock > Assigned To: Brian Stansberry > Fix For: JBossAS-4.0.5.CR1 > > > The targets returned from the FamilyClusterInfoImpl.getTargets() should not be modified, > otherwise you can cause ConcurrentModificationException. > To better trap people introducing errors in this area, make a subclass of ArrayList > called ImmutableArrayList and return an implementation of this class from getTargets. -- 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, 10 months

1
0
0 / 0

[JBoss JIRA] Created: (JBAS-3429) JSP Pages are broken with tomcat6 snapshot

by Scott M Stark (JIRA)

JSP Pages are broken with tomcat6 snapshot ------------------------------------------ Key: JBAS-3429 URL: http://jira.jboss.com/jira/browse/JBAS-3429 Project: JBoss Application Server Issue Type: Bug Security Level: Public (Everyone can see) Components: Web (Tomcat) service Reporter: Scott M Stark Assigned To: Remy Maucherat Priority: Blocker Fix For: JBossAS-5.0.0.Beta Something is screwed up with the current tomcat6 snapshot as I can't even load a jsp page from the jxm-console.war due to missing classes: java.lang.NoClassDefFoundError: org/apache/commons/el/ExpressionEvaluatorImpl org.apache.jasper.compiler.JspUtil.<clinit>(JspUtil.java:61) org.apache.jasper.JspCompilationContext.getServletClassName(JspCompilati onContext.java:334) org.apache.jasper.JspCompilationContext.getClassFileName(JspCompilationC ontext.java:484) org.apache.jasper.compiler.Compiler.isOutDated(Compiler.java:379) org.apache.jasper.compiler.Compiler.isOutDated(Compiler.java:332) org.apache.jasper.JspCompilationContext.compile(JspCompilationContext.java:560) org.apache.jasper.servlet.JspServletWrapper.service(JspServletWrapper.java:303) org.apache.jasper.servlet.JspServlet.serviceJspFile(JspServlet.java:314) org.apache.jasper.servlet.JspServlet.service(JspServlet.java:264) javax.servlet.http.HttpServlet.service(HttpServlet.java:802) org.jboss.web.tomcat.filters.ReplyHeaderFilter.doFilter(ReplyHeaderFilter.java:96) The ExpressionEvaluatorImpl should be org.apache.jasper.el.ExpressionEvaluatorImpl coming from the jasper.jar rather than this commons thing. [starksm@banshee9100 jbossweb-tomcat6.sar]$ for j in *.jar; do echo $j; jar -tf $j | grep ExpressionEvaluatorImpl; done catalina-ant.jar catalina-manager.jar catalina-optional.jar catalina.jar commons-modeler.jar el-api.jar jasper-compiler-jdt.jar jasper-compiler.jar jasper-el.jar jasper-jdt.jar jasper-runtime.jar jasper.jar org/apache/jasper/el/ExpressionEvaluatorImpl.class jboss-web-metamodel.jar jsp-api.jar jstl.jar naming-resources.jar servlet-api.jar servlets-default.jar servlets-invoker.jar servlets-webdav.jar tomcat-ajp.jar tomcat-apr.jar tomcat-coyote.jar tomcat-dbcp.jar tomcat-http.jar tomcat-i18n-es.jar tomcat-i18n-fr.jar tomcat-i18n-ja.jar tomcat-util.jar tomcat6-service.jar The problem is that there are two org.apache.jasper.compiler.JspUtil classes, and the one from jasper-compiler.jar which is loaded is referencing the [starksm@banshee9100 jbossweb-tomcat6.sar]$ javap -c -classpath jasper-compiler.jar org.apache.jasper.compiler.JspUtil >JspUtil.javap Compiled from "JspUtil.java" public class org.apache.jasper.compiler.JspUtil extends java.lang.Object{ public static final int CHUNKSIZE; ... public static void validateExpressions(org.apache.jasper.compiler.Mark, java.lang.String, java.lang.Class, javax.servlet.jsp.el.FunctionMapper, org.apache.jasper.compiler.ErrorDispatcher) throws org.apache.jasper.JasperException; Code: 0: getstatic #143; //Field expressionEvaluator:Lorg/apache/commons/el/ExpressionEvaluatorImpl; ... -- 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, 10 months

1
2
0 / 0

[JBoss JIRA] Updated: (JBAS-3234) Make testsuite use installer to create server configs

by Ryan Campbell (JIRA)

[ http://jira.jboss.com/jira/browse/JBAS-3234?page=all ] Ryan Campbell updated JBAS-3234: -------------------------------- Fix Version/s: JBossAS-4.0.6.CR1 (was: JBossAS-4.0.5.CR1) Deferred until 4.0.6.CR1 > Make testsuite use installer to create server configs > ----------------------------------------------------- > > Key: JBAS-3234 > URL: http://jira.jboss.com/jira/browse/JBAS-3234 > Project: JBoss Application Server > Issue Type: Task > Security Level: Public(Everyone can see) > Components: Test Suite > Affects Versions: JBossAS-4.0.4.GA > Reporter: Alex Pinkin > Assigned To: Alex Pinkin > Fix For: JBossAS-4.0.6.CR1 > > > We currently use ant script to create server distributions while installer uses another mechanism. We should create distribution using installer. -- 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, 10 months

1
0
0 / 0

[JBoss JIRA] Commented: (JBAS-3220) ejb3.deployer lost the javassit bytecode provider changes

by Alex Pinkin (JIRA)

[ http://jira.jboss.com/jira/browse/JBAS-3220?page=comments#action_12340056 ] Alex Pinkin commented on JBAS-3220: ----------------------------------- Yes. JEMS installer 1.2.0.BETA1 includes EJB3 1.0.0.CR8 which addressed this (confirmed by Bill). > ejb3.deployer lost the javassit bytecode provider changes > --------------------------------------------------------- > > Key: JBAS-3220 > URL: http://jira.jboss.com/jira/browse/JBAS-3220 > Project: JBoss Application Server > Issue Type: Bug > Security Level: Public(Everyone can see) > Components: EJB3 > Affects Versions: JBossAS-4.0.4.GA > Reporter: Scott M Stark > Assigned To: Alex Pinkin > Fix For: JBossAS-4.0.5.CR1 > > > The changes made to the ejb3.deployer to set javassist as the bytecode provider were dropped in the merge from head even though head had these changes. This was further obfuscated by the ejb3/build-test.xml having the cglib classpath when this was dropped from other build scripts. -- 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, 10 months

1
0
0 / 0

[JBoss JIRA] Resolved: (JBREM-423) document how remoting identity works and how to configure

by Tom Elrod (JIRA)

[ http://jira.jboss.com/jira/browse/JBREM-423?page=all ] Tom Elrod resolved JBREM-423. ------------------------------ Resolution: Done > document how remoting identity works and how to configure > --------------------------------------------------------- > > Key: JBREM-423 > URL: http://jira.jboss.com/jira/browse/JBREM-423 > Project: JBoss Remoting > Issue Type: Task > Security Level: Public(Everyone can see) > Components: general > Affects Versions: 2.0.0.Beta1 > Reporter: Tom Elrod > Assigned To: Tom Elrod > Fix For: 2.0.0.CR1 (Boon) > > -- 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, 10 months

1
0
0 / 0

[JBoss JIRA] Commented: (JBAS-3234) Make testsuite use installer to create server configs

by Dimitris Andreadis (JIRA)

[ http://jira.jboss.com/jira/browse/JBAS-3234?page=comments#action_12340051 ] Dimitris Andreadis commented on JBAS-3234: ------------------------------------------ If it can be done by Aug/4th fine, otherwise move it to the next release, thanks. > Make testsuite use installer to create server configs > ----------------------------------------------------- > > Key: JBAS-3234 > URL: http://jira.jboss.com/jira/browse/JBAS-3234 > Project: JBoss Application Server > Issue Type: Task > Security Level: Public(Everyone can see) > Components: Test Suite > Affects Versions: JBossAS-4.0.4.GA > Reporter: Alex Pinkin > Assigned To: Alex Pinkin > Fix For: JBossAS-4.0.5.CR1 > > > We currently use ant script to create server distributions while installer uses another mechanism. We should create distribution using installer. -- 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, 10 months

1
0
0 / 0

[JBoss JIRA] Resolved: (JBRULES-323) Generate warning when trying to install the plugin for older eclipse versions

by Kris Verlaenen (JIRA)

[ http://jira.jboss.com/jira/browse/JBRULES-323?page=all ] Kris Verlaenen resolved JBRULES-323. ------------------------------------ Fix Version/s: 3.0.3 (was: 3.1-m1) Resolution: Done Plugin now defines it requires eclipse 3.2 or equivalent. This basically prevents users using lower versions of eclipse from installing the plugin using the update site. An appropriate warning is shown when trying so. > Generate warning when trying to install the plugin for older eclipse versions > ----------------------------------------------------------------------------- > > Key: JBRULES-323 > URL: http://jira.jboss.com/jira/browse/JBRULES-323 > Project: JBoss Rules > Issue Type: Feature Request > Security Level: Public(Everyone can see) > Components: Eclipse IDE > Reporter: Kris Verlaenen > Assigned To: Kris Verlaenen > Fix For: 3.0.3 > > > Generate warning when trying to install the plugin for older eclipse versions (which is less than 3.2M6). > Preferably before downloading the plugin when using the update manager. -- 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, 10 months

1
0
0 / 0

[JBoss JIRA] Assigned: (JBAS-3233) Web services debug logging is causing the classloader to be switched

by Dimitris Andreadis (JIRA)

[ http://jira.jboss.com/jira/browse/JBAS-3233?page=all ] Dimitris Andreadis reassigned JBAS-3233: ---------------------------------------- Assignee: Darran Lofthouse (was: Scott M Stark) Darran, is this still happening, after jboss 4.0.x is updated to use jbossws 1.0.1 (which has the fix)? The offending class is not even part of the 4.0.x source tree now, I think. I'm assigning this to you, if you can handle it. > Web services debug logging is causing the classloader to be switched > -------------------------------------------------------------------- > > Key: JBAS-3233 > URL: http://jira.jboss.com/jira/browse/JBAS-3233 > Project: JBoss Application Server > Issue Type: Bug > Security Level: Public(Everyone can see) > Components: ClassLoading > Affects Versions: JBossAS-4.0.4.GA > Reporter: Darran Lofthouse > Assigned To: Darran Lofthouse > Fix For: JBossAS-4.0.5.CR1 > > Attachments: ComplexReturnEJB_DocLit.ear > > > Web services debug logging is causing the classloader to be switched. > Currently the web services stack does not correctly set the classloader for web services deployments when deployed as part of an ear with an issolated classloader (see JBWS-941). However debug logging in the web services code is incorectly causing the deployment to work! > In the class 'org.jboss.ws.server.ServiceEndpoint' there is a method called 'postProcessResponse', this method contains some logging wrapped with a 'log.isDebugEnabled': - > // debug the outgoing message > if(log.isDebugEnabled()) > { > resMessage.saveChanges(); > SOAPEnvelope soapEnv = resMessage.getSOAPPart().getEnvelope(); > String envStr = DOMWriter.printNode(soapEnv, true); > log.debug("Outgoing SOAPMessage\n" + envStr); > } > If this logging is remove the ClassNotFoundException is thrown regardless of the log4j configuration. > The ClassNotFoundException is good and shows that the classloader has not been switched. > I will attach a deployment that can be used to reproduce this. -- 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, 10 months

1
0
0 / 0

[JBoss JIRA] Updated: (JBAS-3206) Quartz resource adaptor integration

by Dimitris Andreadis (JIRA)

[ http://jira.jboss.com/jira/browse/JBAS-3206?page=all ] Dimitris Andreadis updated JBAS-3206: ------------------------------------- JBoss Forum Reference: http://www.jboss.com/index.html?module=bb&op=viewtopic&t=86667 Added the forum link. AFAIK, we didn't reach a conclusion for this? Maybe should be deferred, anyway. > Quartz resource adaptor integration > ----------------------------------- > > Key: JBAS-3206 > URL: http://jira.jboss.com/jira/browse/JBAS-3206 > Project: JBoss Application Server > Issue Type: Feature Request > Security Level: Public(Everyone can see) > Components: JCA service, Build System > Reporter: Scott M Stark > Assigned To: Weston Price > Fix For: JBossAS-4.0.5.CR1 > > > A quartz inflow resource adaptor showed up at the last minute in the 4.0.4.GA release process. It has been excluded from that release and needs discussion, testcases and docs for inclusion into 4.0.5.GA. -- 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, 10 months

1
0
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 July 2006