February 2007 - jboss-jira - Jboss List Archives

[JBoss JIRA] Created: (JBAOP-327) Caller Annotation

by Flavia Rainone (JIRA)

Caller Annotation ----------------- Key: JBAOP-327 URL: http://jira.jboss.com/jira/browse/JBAOP-327 Project: JBoss AOP Issue Type: Sub-task Reporter: Flavia Rainone Assigned To: Flavia Rainone -- 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, 2 months

2
3
0 / 0

[JBoss JIRA] Created: (JBAOP-326) Target Annotation

by Flavia Rainone (JIRA)

Target Annotation ----------------- Key: JBAOP-326 URL: http://jira.jboss.com/jira/browse/JBAOP-326 Project: JBoss AOP Issue Type: Sub-task Reporter: Flavia Rainone Assigned To: Flavia Rainone -- 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, 2 months

2
4
0 / 0

[JBoss JIRA] Created: (JBAOP-321) JoinPoint annotation

by Flavia Rainone (JIRA)

JoinPoint annotation -------------------- Key: JBAOP-321 URL: http://jira.jboss.com/jira/browse/JBAOP-321 Project: JBoss AOP Issue Type: Sub-task Affects Versions: 2.1.0.GA, 2.0.0.alpha3 Reporter: Flavia Rainone Assigned To: Flavia Rainone -- 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, 2 months

2
2
0 / 0

[JBoss JIRA] Created: (JBAOP-322) Return annotation

by Flavia Rainone (JIRA)

Return annotation ----------------- Key: JBAOP-322 URL: http://jira.jboss.com/jira/browse/JBAOP-322 Project: JBoss AOP Issue Type: Sub-task Affects Versions: 2.1.0.GA, 2.0.0.alpha3 Reporter: Flavia Rainone -- 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, 2 months

2
2
0 / 0

[JBoss JIRA] Created: (JBAOP-319) Arg Annotation

by Flavia Rainone (JIRA)

Arg Annotation -------------- Key: JBAOP-319 URL: http://jira.jboss.com/jira/browse/JBAOP-319 Project: JBoss AOP Issue Type: Sub-task Affects Versions: 2.1.0.GA, 2.0.0.alpha3 Reporter: Flavia Rainone Assigned To: Flavia Rainone Support of @Arg parameter annotation -- 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, 2 months

2
2
0 / 0

[JBoss JIRA] Created: (JBAOP-323) Invocation Annotation

by Flavia Rainone (JIRA)

Invocation Annotation --------------------- Key: JBAOP-323 URL: http://jira.jboss.com/jira/browse/JBAOP-323 Project: JBoss AOP Issue Type: Sub-task Affects Versions: 2.1.0.GA, 2.0.0.alpha3 Reporter: Flavia Rainone Still need to decide a better name for this, to avoid name crashes (org.jboss.aop.advice.annotation.Invocation vs org.jboss.aop.joinpoint.Invocation) -- 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, 2 months

2
3
0 / 0

[JBoss JIRA] Created: (JBAOP-362) JBoss AOP does not bind interceptors to introduced interfaces consistently

by Flavia Rainone (JIRA)

JBoss AOP does not bind interceptors to introduced interfaces consistently -------------------------------------------------------------------------- Key: JBAOP-362 URL: http://jira.jboss.com/jira/browse/JBAOP-362 Project: JBoss AOP Issue Type: Bug Security Level: Public (Everyone can see) Reporter: Flavia Rainone Assigned To: Flavia Rainone Fix For: 1.5.4.SP1, 2.0.0.alpha3 Scenario: - Class A extends class B - C is an interface introduced to both A and B - Bind an interceptor I1 to methods introduced to B - Bind another different interceptor I2 to methods introduced to A Problem: if A is loaded before B, its introduced methods are intercepted by I2; if B is loaded before, on the other hand, A introduced methods are intercepted by I1. We want that the resultant behavior is always the same, regardless of the class loading order. -- 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, 2 months

2
4
0 / 0

[JBoss JIRA] Created: (JBMESSAGING-863) Bisocket test fails with socket listen security violation on client-side

by Ovidiu Feodorov (JIRA)

Bisocket test fails with socket listen security violation on client-side ------------------------------------------------------------------------ Key: JBMESSAGING-863 URL: http://jira.jboss.com/jira/browse/JBMESSAGING-863 Project: JBoss Messaging Issue Type: Bug Components: JMS Remoting Reporter: Ovidiu Feodorov Assigned To: Ron Sigal Priority: Blocker Fix For: 1.2.0.CR1 Caused by: java.lang.SecurityException: ConfigurableSecurityManager[4f9fdc] does not allow (java.net.SocketPermission localhost:2183 listen,resolve), action listen at org.jboss.test.messaging.tools.misc.ConfigurableSecurityManager.checkPermission(ConfigurableSecurityManager.java:83) at java.lang.SecurityManager.checkListen(SecurityManager.java:1112) at java.net.ServerSocket.bind(ServerSocket.java:317) at java.net.ServerSocket.<init>(ServerSocket.java:185) at org.jboss.remoting.transport.PortUtil.checkPort(PortUtil.java:65) at org.jboss.remoting.transport.PortUtil.getFreePort(PortUtil.java:123) at org.jboss.remoting.transport.PortUtil.findFreePort(PortUtil.java:101) at org.jboss.remoting.ServerInvoker.assignPort(ServerInvoker.java:1012) at org.jboss.remoting.ServerInvoker.setup(ServerInvoker.java:911) at org.jboss.remoting.transport.socket.SocketServerInvoker.setup(SocketServerInvoker.java:140) at org.jboss.remoting.transport.bisocket.BisocketServerInvoker.setup(BisocketServerInvoker.java:244) at org.jboss.remoting.ServerInvoker.create(ServerInvoker.java:756) ... 35 more -- 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, 2 months

1
3
0 / 0

[JBoss JIRA] Created: (JBAS-4126) failing org.jboss.test.aop.test tests

by Dimitris Andreadis (JIRA)

failing org.jboss.test.aop.test tests ------------------------------------- Key: JBAS-4126 URL: http://jira.jboss.com/jira/browse/JBAS-4126 Project: JBoss Application Server Issue Type: Sub-task Security Level: Public (Everyone can see) Components: AOP Reporter: Dimitris Andreadis Assigned To: Kabir Khan Priority: Blocker Fix For: JBossAS-4.2.0.CR1 3 failing tests: ScopedAttachUnitTestCase(aop-scoped) ScopedEarWithClassesInWebInfTestCase(aop-scoped) ScopedUnitTestCase(aop-scoped) e.g: unknown Error N/A javax.management.RuntimeErrorException at org.jboss.mx.interceptor.ReflectedDispatcher.handleInvocationExceptions(ReflectedDispatcher.java:178) at org.jboss.mx.interceptor.AttributeDispatcher.invoke(AttributeDispatcher.java:140) at org.jboss.mx.server.Invocation.dispatch(Invocation.java:94) at org.jboss.mx.server.Invocation.invoke(Invocation.java:86) at org.jboss.mx.interceptor.ModelMBeanAttributeInterceptor.invoke(ModelMBeanAttributeInterceptor.java:103) at org.jboss.mx.interceptor.PersistenceInterceptor.invoke(PersistenceInterceptor.java:76) at org.jboss.mx.server.Invocation.invoke(Invocation.java:88) at org.jboss.mx.server.AbstractMBeanInvoker.setAttribute(AbstractMBeanInvoker.java:461) at org.jboss.mx.server.MBeanServerImpl.setAttribute(MBeanServerImpl.java:608) at org.jboss.jmx.connector.invoker.InvokerAdaptorService.invoke(InvokerAdaptorService.java:266) at org.jboss.mx.interceptor.ReflectedDispatcher.invoke(ReflectedDispatcher.java:155) at org.jboss.mx.server.Invocation.dispatch(Invocation.java:94) at org.jboss.mx.interceptor.AbstractInterceptor.invoke(AbstractInterceptor.java:133) at org.jboss.mx.server.Invocation.invoke(Invocation.java:88) at org.jboss.mx.interceptor.ModelMBeanOperationInterceptor.invoke(ModelMBeanOperationInterceptor.java:142) at org.jboss.jmx.connector.invoker.SerializableInterceptor.invoke(SerializableInterceptor.java:74) at org.jboss.mx.server.Invocation.invoke(Invocation.java:88) at org.jboss.mx.server.AbstractMBeanInvoker.invoke(AbstractMBeanInvoker.java:264) at org.jboss.mx.server.MBeanServerImpl.invoke(MBeanServerImpl.java:659) at org.jboss.invocation.jrmp.server.JRMPProxyFactory.invoke(JRMPProxyFactory.java:179) at org.jboss.mx.interceptor.ReflectedDispatcher.invoke(ReflectedDispatcher.java:155) at org.jboss.mx.server.Invocation.dispatch(Invocation.java:94) at org.jboss.mx.server.Invocation.invoke(Invocation.java:86) at org.jboss.mx.server.AbstractMBeanInvoker.invoke(AbstractMBeanInvoker.java:264) at org.jboss.mx.server.MBeanServerImpl.invoke(MBeanServerImpl.java:659) at org.jboss.invocation.jrmp.server.JRMPInvoker$MBeanServerAction.invoke(JRMPInvoker.java:819) at org.jboss.invocation.jrmp.server.JRMPInvoker.invoke(JRMPInvoker.java:420) at sun.rmi.server.UnicastServerRef.dispatch(UnicastServerRef.java:294) at sun.rmi.transport.Transport$1.run(Transport.java:153) at java.security.AccessController.doPrivileged(Native Method) at sun.rmi.transport.Transport.serviceCall(Transport.java:149) at sun.rmi.transport.tcp.TCPTransport.handleMessages(TCPTransport.java:466) at sun.rmi.transport.tcp.TCPTransport$ConnectionHandler.run(TCPTransport.java:707) at java.lang.Thread.run(Thread.java:595) Caused by: java.lang.NoClassDefFoundError: org/jboss/aop/standalone/PluggableInstrumentor at org.jboss.aop.deployment.AspectManagerServiceJDK5.attachTranslator(AspectManagerServiceJDK5.java:42) at org.jboss.aop.deployment.AspectManagerService.setEnableLoadtimeWeaving(AspectManagerService.java:581) at org.jboss.mx.interceptor.AttributeDispatcher.invoke(AttributeDispatcher.java:136) ... 48 more -- 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, 2 months

2
1
0 / 0

[JBoss JIRA] Commented: (JBAS-2676) ClassLoader getResources() omits directory but finds files in the directory - this affects Facelets *.taglib.xml auto-loading

by Howard Lewis Ship (JIRA)

[ http://jira.jboss.com/jira/browse/JBAS-2676?page=comments#action_12353729 ] Howard Lewis Ship commented on JBAS-2676: ----------------------------------------- No workaround for me, since JBoss doesn't unpack the WEB-INF/classes folder out of the WAR. Is there a way to get JBoss to unpack the WAR? > ClassLoader getResources() omits directory but finds files in the directory - this affects Facelets *.taglib.xml auto-loading > ----------------------------------------------------------------------------------------------------------------------------- > > Key: JBAS-2676 > URL: http://jira.jboss.com/jira/browse/JBAS-2676 > Project: JBoss Application Server > Issue Type: Bug > Security Level: Public(Everyone can see) > Components: Web (Tomcat) service > Affects Versions: JBossAS-4.0.3 SP1 > Environment: Windows XP, JDK 1.5.0_04 > Reporter: David Richmond > Assigned To: Remy Maucherat > > Using JSF and Facelets. > Have a JAR file in my WebApps WEB-INF/lib, JAR file contains META-INF/faces-config.xml and META-INF/isalib.taglib.xml > Using the Thread.currentThread().getContextClassLoader() classloader: > .getResources("META-INF/faces-config.xml") finds the file in the JAR > .getResources("META-INF/") does not find the directory in the JAR > This is quite important, since Facelets scans the classpath for "META-INF/" dircetories and searches for *.taglib.xml files therein - this allows Facelets to auto-load the files it finds. > One work around is to copy the taglib.xml file into my web-app and point the facelets.LIBRARIES context parameter at the file. Another workaround is to put the taglib.xml file into the Web-App's META-INF directory (since WAR files are on the classpath - is this an error?). However, the taglib.xml definitions belong to the JAR and can change when the JAR source code changes - so loading from the JAR is prefered. -- 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, 2 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 February 2007