December 2006 - jboss-jira - Jboss List Archives

[JBoss JIRA] Created: (JBAS-3509) org.jboss.test.cache.bean.MBeanUnitTestCase because "ejb" is not bound

by Jaroslaw Kijanowski (JIRA)

org.jboss.test.cache.bean.MBeanUnitTestCase because "ejb" is not bound ---------------------------------------------------------------------- Key: JBAS-3509 URL: http://jira.jboss.com/jira/browse/JBAS-3509 Project: JBoss Application Server Issue Type: Bug Security Level: Public (Everyone can see) Components: Test Suite Affects Versions: JBossAS-5.0.0.Beta Environment: win xp Reporter: Jaroslaw Kijanowski org.jboss.test.cache.bean.MBeanUnitTestCase because "ejb" is not bound because of missing xml files. Resolve: Copy following xml files to testsuite\src\resources\cache\META-INF ************ ejb-jar.xml: ************ <?xml version="1.0" encoding="UTF-8"?> <!DOCTYPE ejb-jar PUBLIC "-//Sun Microsystems, Inc.//DTD Enterprise JavaBeans 2.0//EN" "http://java.sun.com/dtd/ejb-jar_2_0.dtd"> <ejb-jar > <description><![CDATA[No Description.]]></description> <display-name>Generated by XDoclet</display-name> <enterprise-beans>  <session > <description><![CDATA[]]></description> <ejb-name>CacheObjectMeanTester</ejb-name> <home>org.jboss.test.cache.bean.CacheObjectMeanTesterHome</home> <remote>org.jboss.test.cache.bean.CacheObjectMeanTester</remote> <ejb-class>org.jboss.test.cache.bean.CacheObjectMeanTesterBean</ejb-class> <session-type>Stateless</session-type> <transaction-type>Container</transaction-type> </session> <session > <description><![CDATA[Proxy to the TreeCache MBean.]]></description> <ejb-name>test/TreeCacheTester</ejb-name> <home>org.jboss.test.cache.bean.TreeCacheTesterHome</home> <remote>org.jboss.test.cache.bean.TreeCacheTester</remote> <ejb-class>org.jboss.test.cache.bean.TreeCacheTesterBean</ejb-class> <session-type>Stateful</session-type> <transaction-type>Container</transaction-type> </session> <session > <description><![CDATA[Proxy to the TreeCacheAop MBean.]]></description> <ejb-name>test/TreeCacheAopTester</ejb-name> <home>org.jboss.test.cache.bean.TreeCacheAopTesterHome</home> <remote>org.jboss.test.cache.bean.TreeCacheAopTester</remote> <ejb-class>org.jboss.test.cache.bean.TreeCacheAopTesterBean</ejb-class> <session-type>Stateful</session-type> <transaction-type>Container</transaction-type> </session> <session > <description><![CDATA[EJB proxy to the TreeCache MBean service.]]></description> <ejb-name>test/TreeCacheMBeanTester</ejb-name> <home>org.jboss.test.cache.bean.TreeCacheMBeanTesterHome</home> <remote>org.jboss.test.cache.bean.TreeCacheMBeanTester</remote> <ejb-class>org.jboss.test.cache.bean.TreeCacheMBeanTesterBean</ejb-class> <session-type>Stateful</session-type> <transaction-type>Container</transaction-type> </session> <session > <description><![CDATA[Proxy to the TreeCacheAop MBean.]]></description> <ejb-name>test/TreeCacheAopMBeanTester</ejb-name> <home>org.jboss.test.cache.bean.TreeCacheAopMBeanTesterHome</home> <remote>org.jboss.test.cache.bean.TreeCacheAopMBeanTester</remote> <ejb-class>org.jboss.test.cache.bean.TreeCacheAopMBeanTesterBean</ejb-class> <session-type>Stateful</session-type> <transaction-type>Container</transaction-type> </session>      </enterprise-beans>   <assembly-descriptor >        <container-transaction > <method > <ejb-name>test/TreeCacheTester</ejb-name> <method-name>*</method-name> </method> <trans-attribute>Supports</trans-attribute> </container-transaction> <container-transaction > <method > <ejb-name>test/TreeCacheAopTester</ejb-name> <method-name>*</method-name> </method> <trans-attribute>Supports</trans-attribute> </container-transaction> <container-transaction > <method > <ejb-name>test/TreeCacheMBeanTester</ejb-name> <method-name>*</method-name> </method> <trans-attribute>Supports</trans-attribute> </container-transaction> <container-transaction > <method > <ejb-name>test/TreeCacheAopMBeanTester</ejb-name> <method-name>*</method-name> </method> <trans-attribute>Supports</trans-attribute> </container-transaction>  </assembly-descriptor> </ejb-jar> ************ ************ jboss.xml ************ <?xml version="1.0" encoding="UTF-8"?> <!DOCTYPE jboss PUBLIC "-//JBoss//DTD JBOSS 3.0//EN" "http://www.jboss.org/j2ee/dtd/jboss_3_0.dtd"> <jboss> <enterprise-beans>  <session> <ejb-name>CacheObjectMeanTester</ejb-name> <jndi-name>test/CacheObjectMeanTester</jndi-name> </session> <session> <ejb-name>test/TreeCacheTester</ejb-name> <jndi-name>ejb/test/TreeCacheTester</jndi-name> </session> <session> <ejb-name>test/TreeCacheAopTester</ejb-name> <jndi-name>test/TreeCacheAopTester</jndi-name> </session> <session> <ejb-name>test/TreeCacheMBeanTester</ejb-name> <jndi-name>ejb/test/TreeCacheMBeanTester</jndi-name> </session> <session> <ejb-name>test/TreeCacheAopMBeanTester</ejb-name> <jndi-name>ejb/test/TreeCacheAopMBeanTester</jndi-name> </session> </enterprise-beans> <resource-managers> </resource-managers> </jboss> *************** -- 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, 7 months

2
2
0 / 0

[JBoss JIRA] Created: (JBCACHE-802) NonManagedConnectionFactory does not place new connections in ThreadLocal (JDBCCacheLoader)

by Manik Surtani (JIRA)

NonManagedConnectionFactory does not place new connections in ThreadLocal (JDBCCacheLoader) ------------------------------------------------------------------------------------------- Key: JBCACHE-802 URL: http://jira.jboss.com/jira/browse/JBCACHE-802 Project: JBoss Cache Issue Type: Bug Security Level: Public (Everyone can see) Components: Cache loaders Affects Versions: 1.4.0.SP1 Reporter: Manik Surtani Assigned To: Manik Surtani Fix For: 1.4.0.SP2, 2.0.0 In NonManagedConnectionFactory.getConnection(): public Connection getConnection() { Connection con = (Connection) connection.get(); if(con == null) { try { con = DriverManager.getConnection(url, usr, pwd); // CODE ADDED HERE connection.set(con); // END CODE MODIFICATION } catch(SQLException e) ... -- 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: (JBWEB-64) JBoss Web integration improvements

by Remy Maucherat (JIRA)

JBoss Web integration improvements ---------------------------------- Key: JBWEB-64 URL: http://jira.jboss.com/jira/browse/JBWEB-64 Project: JBoss Web Issue Type: Feature Request Security Level: Public (Everyone can see) Reporter: Remy Maucherat Assigned To: Remy Maucherat Priority: Critical Many things can be done in this area, including migration off raw JMX, etc. -- 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: (JBAS-3954) Cannot compile jsp on Windows with reference to a class in WEB-INF/classes of the same name but difference case as a package name

by Jim Moran (JIRA)

Cannot compile jsp on Windows with reference to a class in WEB-INF/classes of the same name but difference case as a package name --------------------------------------------------------------------------------------------------------------------------------- Key: JBAS-3954 URL: http://jira.jboss.com/jira/browse/JBAS-3954 Project: JBoss Application Server Issue Type: Bug Security Level: Public (Everyone can see) Components: Web (Tomcat) service Affects Versions: JBossAS-4.0.4.GA Reporter: Jim Moran Assigned To: Remy Maucherat If UseJBossWebLoader is true in jbossweb-tomca55.sar/META-INF/jboss-service.xml And there is a class in a war's WEB-INF/classes that has a classname identical to a package name except that the cases are different And there is a jsp which references this class And this war is deployed on Windows Then the jsp causes error on Compile such as: 2006-11-22 12:04:40,414 ERROR [org.apache.catalina.core.ContainerBase.[jboss.web].[localhost].[/jdt].[jsp]] Servlet.service() for servlet jsp threw exception org.apache.jasper.JasperException: Unable to compile class for JSP An error occurred at line: 5 in the jsp file: /index.jsp Generated servlet error: test.mypackage.name cannot be resolved to a type at org.apache.jasper.compiler.DefaultErrorHandler.javacError(DefaultErrorHandler.java:84) at org.apache.jasper.compiler.ErrorDispatcher.javacError(ErrorDispatcher.java:328) at org.apache.jasper.compiler.JDTCompiler.generateClass(JDTCompiler.java:414) -- 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: (JBAS-3812) TomcatDeployment should use modified WebMetaData

by Thomas Diesler (JIRA)

TomcatDeployment should use modified WebMetaData ------------------------------------------------ Key: JBAS-3812 URL: http://jira.jboss.com/jira/browse/JBAS-3812 Project: JBoss Application Server Issue Type: Task Security Level: Public (Everyone can see) Reporter: Thomas Diesler Fix For: JBossAS-5.0.0.Beta The Web Service Deployers modify the WebMetaData. This should then be used to deploy to Tomcat. Rewrite of the war should not be necessary. -- 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

6
11
0 / 0

[JBoss JIRA] Created: (EJBTHREE-765) EJB3 documentation on website is out of date

by Jeff Schnitzer (JIRA)

EJB3 documentation on website is out of date -------------------------------------------- Key: EJBTHREE-765 URL: http://jira.jboss.com/jira/browse/EJBTHREE-765 Project: EJB 3.0 Issue Type: Task Components: Documentation Reporter: Jeff Schnitzer Two things: The docs at http://docs.jboss.org/ejb3/ are for EJB3 RC6 The "Notes" link on http://labs.jboss.com/portal/jbossejb3/download/index.html points at the release notes for RC4. -- 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: (JBFORUMS-125) BBCode URL Tag improvement

by Ryszard Kozmik (JIRA)

BBCode URL Tag improvement -------------------------- Key: JBFORUMS-125 URL: http://jira.jboss.com/jira/browse/JBFORUMS-125 Project: JBoss Forums Issue Type: Feature Request Components: Forum Enhancements Reporter: Ryszard Kozmik Fix For: 1.1.0 Alpha BBCode's URL tag could work similar to html "a href" style like : [url=http://www.example.com]My Example[/url] -- 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
3
0 / 0

[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: (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: (JBPM-791) make email port in test suite configurable

by Tom Baeyens (JIRA)

make email port in test suite configurable ------------------------------------------ Key: JBPM-791 URL: http://jira.jboss.com/jira/browse/JBPM-791 Project: JBoss jBPM Issue Type: Feature Request Components: Core Engine Reporter: Tom Baeyens Assigned To: Tom Baeyens we're using dumpster in the test suite for testing emails. but our continuous integration server doesn't allow for ports to be opened under 1024. so we need to find a way to tell dumpster to open up the fake mailserver on a different port. also we need to figure out how to tell the JavaMail API that mails should be sent using this different port... -- 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

2026

2025

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

2009

2008

2007

2006

jboss-jira December 2006