October 2007 - jboss-jira - Jboss List Archives

[JBoss JIRA] Created: (JBAOP-305) annotations not found for non-generic implementations of generic interface methods

by Havoc Pennington (JIRA)

annotations not found for non-generic implementations of generic interface methods ---------------------------------------------------------------------------------- Key: JBAOP-305 URL: http://jira.jboss.com/jira/browse/JBAOP-305 Project: JBoss AOP Issue Type: Bug Security Level: Public (Everyone can see) Reporter: Havoc Pennington I'm not sure if this is an AOP problem or a how-jboss-is-using-AOP-on-EJB3-session-beans problem, but I'll file it here to start. The original issue is TransactionAttribute(NEVER) being ignored on certain session bean methods, the test case / details on that are in this list post: http://groups.google.com/group/mugshot/browse_thread/thread/bc43e0dd34c8c... I made an AOP test case that either shows an AOP problem or shows a way jboss could easily misuse AOP. In the AOP test case, If there is an interface Foo<T> with method frobate(T t), then you look that up in AOP as resolveAnnotation("frobate", new Class[] { Object.class }) But if you implement that interface ("class FooImpl implements Foo<Double>") then you have to look that up in AOP as resolveAnnotation("frobate", new Class[] { Double.class }) - looking it up with the erasure (Object.class arg) will not work, it returns null for the annotation. So if someone were iterating over methods in the interface, looking each one up on the implementing class, they would not get the annotation for any generic methods in the interface implemented in the class. The case that's going wrong in EJB3 is a little bit more complicated, so maybe there is some attempt at handling this that isn't catching all the cases. It looks like further investigation requires messing with jboss TxInterceptor etc. itself, which is a little bit more than I think I can bite off, but hopefully this info is a helpful start. Thanks -- 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

18 years, 8 months

4
13
0 / 0

[JBoss JIRA] Created: (JBPORTAL-1353) Captcha support

by Julien Viet (JIRA)

Captcha support --------------- Key: JBPORTAL-1353 URL: http://jira.jboss.com/jira/browse/JBPORTAL-1353 Project: JBoss Portal Issue Type: Feature Request Security Level: Public (Everyone can see) Components: Portal Core Reporter: Julien Viet Assigned To: Julien Viet Fix For: 2.8 Final -- 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

18 years, 8 months

2
1
0 / 0

[JBoss JIRA] Created: (JBMICROCONT-188) Incomplete Deployment calculation should be done upfront

by Adrian Brock (JIRA)

Incomplete Deployment calculation should be done upfront -------------------------------------------------------- Key: JBMICROCONT-188 URL: http://jira.jboss.com/jira/browse/JBMICROCONT-188 Project: JBoss MicroContainer Issue Type: Task Reporter: Adrian Brock Fix For: JBossMC-2.0.0.GA Some of the calculation of the IncompleteDeploymentException is done in the exception class itself when it should be done in the Incomplete processing upfront. -- 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

18 years, 8 months

3
5
0 / 0

[JBoss JIRA] Created: (JBMICROCONT-183) ManifestDeployer has a TODO relating to VFS snapshot update

by Adrian Brock (JIRA)

ManifestDeployer has a TODO relating to VFS snapshot update ----------------------------------------------------------- Key: JBMICROCONT-183 URL: http://jira.jboss.com/jira/browse/JBMICROCONT-183 Project: JBoss MicroContainer Issue Type: Task Components: Deployment Reporter: Adrian Brock Assigned To: Ales Justin Fix For: JBossMC_2_0_0_CR1 Ales, you added this comment @Override protected T parse(VFSDeploymentUnit unit, VirtualFile file, T root) throws Exception { // todo - update once we have new vfs snapshot InputStream is = SecurityActions.openStream(file); Manifest manifest; try { manifest = new Manifest(is); } finally { try { is.close(); } catch (Exception ignored) { } } return createMetaData(manifest); } -- 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

18 years, 8 months

2
3
0 / 0

[JBoss JIRA] Created: (JBPM-1045) test suite has to trow a runtime exception on error so meaningful report is generated

by Aleksandar Kostadinov (JIRA)

test suite has to trow a runtime exception on error so meaningful report is generated ------------------------------------------------------------------------------------- Key: JBPM-1045 URL: http://jira.jboss.com/jira/browse/JBPM-1045 Project: JBoss jBPM Issue Type: Bug Affects Versions: jBPM jPDL 3.2.2 Reporter: Aleksandar Kostadinov Assigned To: Tom Baeyens When there are test suite initialization problems, test suite ignores exception (just prints it to the output) that causes junit to crash. I identified the issue in the following files: jpdl/jar/src/test/java/org/jbpm/AllDBTests.java jpdl/jar/src/test/java/org/jbpm/AllTests.java have to have "throw t;" after "t.printStackTrace();" As well the following test cases seem suspicious to me. I mean I'm not sure if an exception by these tests will cause a test suite crash. Please inspect if trowing an axception is desirable after printStackTrace method is used in these files: ./msg/command/AsyncExecutionDbTest.java ./perf/MemLeakTest.java -- 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

18 years, 8 months

3
8
0 / 0

[JBoss JIRA] Created: (JBREM-758) Associate remote socket address with the invocation

by Carlo de Wolf (JIRA)

Associate remote socket address with the invocation --------------------------------------------------- Key: JBREM-758 URL: http://jira.jboss.com/jira/browse/JBREM-758 Project: JBoss Remoting Issue Type: Feature Request Security Level: Public (Everyone can see) Reporter: Carlo de Wolf Add remote socket address to the InvocationRequest to allow it to be used for auditing and filtering. -- 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

18 years, 8 months

2
7
0 / 0

[JBoss JIRA] Created: (JBREM-792) Provide to the client local address of a TCP/IP connection, as seen from the server

by Ron Sigal (JIRA)

Provide to the client local address of a TCP/IP connection, as seen from the server ----------------------------------------------------------------------------------- Key: JBREM-792 URL: http://jira.jboss.com/jira/browse/JBREM-792 Project: JBoss Remoting Issue Type: Feature Request Security Level: Public (Everyone can see) Affects Versions: 2.4.0.Beta1 (Pinto) Reporter: Ron Sigal Assigned To: Ron Sigal Fix For: 2.4.0.Beta1 (Pinto) When org.jboss.remoting.Client.addListener() creates a callback org.jboss.remoting.transport.Connector, by default it calls InetAddress.getLocalHost().getHostAddress() to get a local address for the callback org.jboss.remoting.InvokerLocator. If the machine happens to have multiple addresses, getLocalHost() might return the wrong one. A solution, due to Ovidiu Feodorov, is to implement an internal invocation to which the server replies by returning the remote address of the connection over which the invocation was made. This solution has been implemented for the socket transport (and bisocket, by inheritance) in conjunction with JBREM-781. It should be implemented for the other transports. -- 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

18 years, 8 months

1
4
0 / 0

[JBoss JIRA] Created: (JBAS-3423) Fix org.jboss.test.cmp2.commerce.CompleteUnitTestCase in HEAD

by Anil Saldhana (JIRA)

Fix org.jboss.test.cmp2.commerce.CompleteUnitTestCase in HEAD ------------------------------------------------------------- Key: JBAS-3423 URL: http://jira.jboss.com/jira/browse/JBAS-3423 Project: JBoss Application Server Issue Type: Task Security Level: Public (Everyone can see) Components: CMP service Reporter: Anil Saldhana Assigned To: Alexey Loubyansky Fix For: JBossAS-5.0.0.Beta Could you please have a look at why the tests "testJBossQL, testEJBQL" are failing? ========================================================================================== Expected: SELECT t0_o1.ORDER_NUMBER FROM ORDER_DATA t0_o1, ORDER_DATA t3_o2, CUSTOMEREJB t1_o1_customer, CUSTOMEREJB t2_o2_customer WHERE (( NOT (t1_o1_customer.id=t2_o2_customer.id)) AND (t0_o1.CC_TYPE=t3_o2.CC_TYPE AND t0_o1.CC_FIRST_NAME=t3_o2.CC_FIRST_NAME AND t0_o1.CC_MI=t3_o2.CC_MI AND t0_o1.CC_LAST_NAME=t3_o2.CC_LAST_NAME AND t0_o1.CC_BILLING_ZIP=t3_o2.CC_BILLING_ZIP AND t0_o1.CC_CARD_NUMBER=t3_o2.CC_CARD_NUMBER) AND t0_o1.customer=t1_o1_customer.id AND t3_o2.customer=t2_o2_customer.id) but got: SELECT t0_o1.ORDER_NUMBER FROM ORDER_DATA t0_o1, ORDER_DATA t3_o2, CUSTOMEREJB t2_o2_customer, CUSTOMEREJB t1_o1_customer WHERE (( NOT (t1_o1_customer.id=t2_o2_customer.id)) AND (t0_o1.CC_TYPE=t3_o2.CC_TYPE AND t0_o1.CC_FIRST_NAME=t3_o2.CC_FIRST_NAME AND t0_o1.CC_MI=t3_o2.CC_MI AND t0_o1.CC_LAST_NAME=t3_o2.CC_LAST_NAME AND t0_o1.CC_BILLING_ZIP=t3_o2.CC_BILLING_ZIP AND t0_o1.CC_CARD_NUMBER=t3_o2.CC_CARD_NUMBER) AND t3_o2.customer=t2_o2_customer.id AND t0_o1.customer=t1_o1_customer.id) junit.framework.AssertionFailedError: Expected: SELECT t0_o1.ORDER_NUMBER FROM ORDER_DATA t0_o1, ORDER_DATA t3_o2, CUSTOMEREJB t1_o1_customer, CUSTOMEREJB t2_o2_customer WHERE (( NOT (t1_o1_customer.id=t2_o2_customer.id)) AND (t0_o1.CC_TYPE=t3_o2.CC_TYPE AND t0_o1.CC_FIRST_NAME=t3_o2.CC_FIRST_NAME AND t0_o1.CC_MI=t3_o2.CC_MI AND t0_o1.CC_LAST_NAME=t3_o2.CC_LAST_NAME AND t0_o1.CC_BILLING_ZIP=t3_o2.CC_BILLING_ZIP AND t0_o1.CC_CARD_NUMBER=t3_o2.CC_CARD_NUMBER) AND t0_o1.customer=t1_o1_customer.id AND t3_o2.customer=t2_o2_customer.id) but got: SELECT t0_o1.ORDER_NUMBER FROM ORDER_DATA t0_o1, ORDER_DATA t3_o2, CUSTOMEREJB t2_o2_customer, CUSTOMEREJB t1_o1_customer WHERE (( NOT (t1_o1_customer.id=t2_o2_customer.id)) AND (t0_o1.CC_TYPE=t3_o2.CC_TYPE AND t0_o1.CC_FIRST_NAME=t3_o2.CC_FIRST_NAME AND t0_o1.CC_MI=t3_o2.CC_MI AND t0_o1.CC_LAST_NAME=t3_o2.CC_LAST_NAME AND t0_o1.CC_BILLING_ZIP=t3_o2.CC_BILLING_ZIP AND t0_o1.CC_CARD_NUMBER=t3_o2.CC_CARD_NUMBER) AND t3_o2.customer=t2_o2_customer.id AND t0_o1.customer=t1_o1_customer.id) at org.jboss.test.cmp2.commerce.QueryTest.testJBossQL(QueryTest.java:173) at net.sourceforge.junitejb.EJBTestCase.runBare(EJBTestCase.java:133) at net.sourceforge.junitejb.EJBTestRunnerBean.runTestCase(EJBTestRunnerBean.java:102) at net.sourceforge.junitejb.EJBTestRunnerBean.run(EJBTestRunnerBean.java:44) at org.jboss.invocation.Invocation.performCall(Invocation.java:359) at org.jboss.ejb.StatelessSessionContainer$ContainerInterceptor.invoke(StatelessSessionContainer.java:228) at org.jboss.resource.connectionmanager.CachedConnectionInterceptor.invoke(CachedConnectionInterceptor.java:158) at org.jboss.ws.server.ServiceEndpointInterceptor.invoke(ServiceEndpointInterceptor.java:39) at org.jboss.ejb.plugins.CallValidationInterceptor.invoke(CallValidationInterceptor.java:63) at org.jboss.ejb.plugins.AbstractTxInterceptor.invokeNext(AbstractTxInterceptor.java:121) at org.jboss.ejb.plugins.AbstractTxInterceptorBMT.invokeNext(AbstractTxInterceptorBMT.java:173) at org.jboss.ejb.plugins.TxInterceptorBMT.invoke(TxInterceptorBMT.java:77) at org.jboss.ejb.plugins.StatelessSessionInstanceInterceptor.invoke(StatelessSessionInstanceInterceptor.java:168) at org.jboss.ejb.plugins.SecurityAuthorizationInterceptor.invoke(SecurityAuthorizationInterceptor.java:105) at org.jboss.ejb.plugins.JaasAuthenticationInterceptor.invoke(JaasAuthenticationInterceptor.java:146) at org.jboss.ejb.plugins.LogInterceptor.invoke(LogInterceptor.java:205) at org.jboss.ejb.plugins.ProxyFactoryFinderInterceptor.invoke(ProxyFactoryFinderInterceptor.java:136) at org.jboss.ejb.SessionContainer.internalInvoke(SessionContainer.java:646) at org.jboss.ejb.Container.invoke(Container.java:974) at org.jboss.mx.interceptor.ReflectedDispatcher.invoke(ReflectedDispatcher.java:157) ========================================================================================= -- 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

18 years, 8 months

3
2
0 / 0

[JBoss JIRA] Created: (JBPORTAL-1613) Refactor Content framework and Widget support

by Chris Laprun (JIRA)

Refactor Content framework and Widget support --------------------------------------------- Key: JBPORTAL-1613 URL: http://jira.jboss.com/jira/browse/JBPORTAL-1613 Project: JBoss Portal Issue Type: Task Security Level: Public (Everyone can see) Components: Portal Widget Affects Versions: 2.6.1 Final Reporter: Chris Laprun Fix For: 2.8 Final There are several interfaces that are either duplicated or not used (when they could be: WidgetProvider is not used, ContentPortlet is under-used...). Several definition of edit_content mode all over the place when the definition from ContentPortlet could be used. Overall clean-up seems required. -- 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

18 years, 8 months

4
4
0 / 0

[JBoss JIRA] Created: (JBPORTAL-1558) do not append default parameters values when rendering gadget

by Boleslaw Dawidowicz (JIRA)

do not append default parameters values when rendering gadget ------------------------------------------------------------- Key: JBPORTAL-1558 URL: http://jira.jboss.com/jira/browse/JBPORTAL-1558 Project: JBoss Portal Issue Type: Sub-task Security Level: Public (Everyone can see) Reporter: Boleslaw Dawidowicz Assigned To: Boleslaw Dawidowicz -- 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

18 years, 8 months

3
4
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 October 2007