July 2007 - jboss-jira - Jboss List Archives

[JBoss JIRA] Created: (JBAOP-422) Document advice matching involving generics

by Flavia Rainone (JIRA)

Document advice matching involving generics ------------------------------------------- Key: JBAOP-422 URL: http://jira.jboss.com/jira/browse/JBAOP-422 Project: JBoss AOP Issue Type: Feature Request Security Level: Public (Everyone can see) Affects Versions: 2.0.0.alpha5 Reporter: Flavia Rainone Assigned To: Flavia Rainone Fix For: 2.1.0.GA We should add text explainingg in details how advice matching on genadvisor mode when dealing with generics. We have three major scenarios: - there is generics only on the joinpoint being intercepted - there is generics only on the advice/aspect class making the interception - there is generics on both the joinpoint and advice/aspect All three scenarios have to be explained in the documentation. -- 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

15 years, 10 months

2
1
0 / 0

[JBoss JIRA] Created: (EJBTHREE-750) support xml overides/augmentations for WS annotations

by William DeCoste (JIRA)

support xml overides/augmentations for WS annotations ----------------------------------------------------- Key: EJBTHREE-750 URL: http://jira.jboss.com/jira/browse/EJBTHREE-750 Project: EJB 3.0 Issue Type: Feature Request Affects Versions: EJB 3.0 RC9 - FD Reporter: William DeCoste Assigned To: William DeCoste For example, @PortComponent. See the org.jboss.test.ws.jaxws.samples.jsr181ejb test. -- 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

15 years, 10 months

3
2
0 / 0

[JBoss JIRA] Created: (JBAS-3952) Problem with SerializableProxy when de-serializing in a remote client

by Frank Ulbricht (JIRA)

Problem with SerializableProxy when de-serializing in a remote client --------------------------------------------------------------------- Key: JBAS-3952 URL: http://jira.jboss.com/jira/browse/JBAS-3952 Project: JBoss Application Server Issue Type: Bug Security Level: Public (Everyone can see) Components: EJB3, Hibernate service Affects Versions: JBossAS-4.0.5.GA Environment: Windows Vista and Windows XP, Java 1.5.0 Update 10 and Java 1.6.0 Reporter: Frank Ulbricht Assigned To: Bill Burke After calling a SessionBean method that returns an entity with a lazy relation there is an problem with de-serialization on the client side. The lazy field cannot not be assigned because of a ClassCastException. In other projects the same happens after a method returns the result of a query where lazy fields are involved. The problem occurs only with lazy fields. The is a simple test case attached with the problem code line marked. Here is the complete stacktrace: java.lang.reflect.UndeclaredThrowableException at $Proxy6.updateAddress(Unknown Source) at com.qualitype.testcase.client.RemoteClientTestCase.test(RemoteClientTestCase.java:48) at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method) at sun.reflect.NativeMethodAccessorImpl.invoke(Unknown Source) at sun.reflect.DelegatingMethodAccessorImpl.invoke(Unknown Source) at java.lang.reflect.Method.invoke(Unknown Source) at org.junit.internal.runners.TestMethodRunner.executeMethodBody(TestMethodRunner.java:99) at org.junit.internal.runners.TestMethodRunner.runUnprotected(TestMethodRunner.java:81) at org.junit.internal.runners.BeforeAndAfterRunner.runProtected(BeforeAndAfterRunner.java:34) at org.junit.internal.runners.TestMethodRunner.runMethod(TestMethodRunner.java:75) at org.junit.internal.runners.TestMethodRunner.run(TestMethodRunner.java:45) at org.junit.internal.runners.TestClassMethodsRunner.invokeTestMethod(TestClassMethodsRunner.java:71) at org.junit.internal.runners.TestClassMethodsRunner.run(TestClassMethodsRunner.java:35) at org.junit.internal.runners.TestClassRunner$1.runUnprotected(TestClassRunner.java:42) at org.junit.internal.runners.BeforeAndAfterRunner.runProtected(BeforeAndAfterRunner.java:34) at org.junit.internal.runners.TestClassRunner.run(TestClassRunner.java:52) at org.eclipse.jdt.internal.junit4.runner.JUnit4TestReference.run(JUnit4TestReference.java:38) at org.eclipse.jdt.internal.junit.runner.TestExecution.run(TestExecution.java:38) at org.eclipse.jdt.internal.junit.runner.RemoteTestRunner.runTests(RemoteTestRunner.java:460) at org.eclipse.jdt.internal.junit.runner.RemoteTestRunner.runTests(RemoteTestRunner.java:673) at org.eclipse.jdt.internal.junit.runner.RemoteTestRunner.run(RemoteTestRunner.java:386) at org.eclipse.jdt.internal.junit.runner.RemoteTestRunner.main(RemoteTestRunner.java:196) Caused by: java.rmi.MarshalException: Failed to communicate. Problem during marshalling/unmarshalling; nested exception is: java.lang.ClassCastException: cannot assign instance of org.hibernate.proxy.pojo.javassist.SerializableProxy to field com.qualitype.testcase.entity.Address.person of type com.qualitype.testcase.entity.Person in instance of com.qualitype.testcase.entity.Address at org.jboss.remoting.transport.socket.SocketClientInvoker.transport(SocketClientInvoker.java:306) at org.jboss.remoting.RemoteClientInvoker.invoke(RemoteClientInvoker.java:143) at org.jboss.remoting.Client.invoke(Client.java:525) at org.jboss.remoting.Client.invoke(Client.java:488) at org.jboss.aspects.remoting.InvokeRemoteInterceptor.invoke(InvokeRemoteInterceptor.java:55) at org.jboss.aop.joinpoint.MethodInvocation.invokeNext(MethodInvocation.java:101) at org.jboss.aspects.tx.ClientTxPropagationInterceptor.invoke(ClientTxPropagationInterceptor.java:61) at org.jboss.aop.joinpoint.MethodInvocation.invokeNext(MethodInvocation.java:101) at org.jboss.aspects.security.SecurityClientInterceptor.invoke(SecurityClientInterceptor.java:53) at org.jboss.aop.joinpoint.MethodInvocation.invokeNext(MethodInvocation.java:101) at org.jboss.ejb3.remoting.IsLocalInterceptor.invoke(IsLocalInterceptor.java:77) at org.jboss.aop.joinpoint.MethodInvocation.invokeNext(MethodInvocation.java:101) at org.jboss.ejb3.stateless.StatelessRemoteProxy.invoke(StatelessRemoteProxy.java:102) ... 22 more Caused by: java.lang.ClassCastException: cannot assign instance of org.hibernate.proxy.pojo.javassist.SerializableProxy to field com.qualitype.testcase.entity.Address.person of type com.qualitype.testcase.entity.Person in instance of com.qualitype.testcase.entity.Address at java.io.ObjectStreamClass$FieldReflector.setObjFieldValues(Unknown Source) at java.io.ObjectStreamClass.setObjFieldValues(Unknown Source) at java.io.ObjectInputStream.defaultReadFields(Unknown Source) at java.io.ObjectInputStream.readSerialData(Unknown Source) at java.io.ObjectInputStream.readOrdinaryObject(Unknown Source) at java.io.ObjectInputStream.readObject0(Unknown Source) at java.io.ObjectInputStream.readObject(Unknown Source) at org.jboss.aop.joinpoint.InvocationResponse.readExternal(InvocationResponse.java:122) at java.io.ObjectInputStream.readExternalData(Unknown Source) at java.io.ObjectInputStream.readOrdinaryObject(Unknown Source) at java.io.ObjectInputStream.readObject0(Unknown Source) at java.io.ObjectInputStream.defaultReadFields(Unknown Source) at java.io.ObjectInputStream.readSerialData(Unknown Source) at java.io.ObjectInputStream.readOrdinaryObject(Unknown Source) at java.io.ObjectInputStream.readObject0(Unknown Source) at java.io.ObjectInputStream.readObject(Unknown Source) at org.jboss.remoting.serialization.impl.java.JavaSerializationManager.receiveObject(JavaSerializationManager.java:128) at org.jboss.remoting.marshal.serializable.SerializableUnMarshaller.read(SerializableUnMarshaller.java:66) at org.jboss.remoting.transport.socket.SocketClientInvoker.transport(SocketClientInvoker.java:279) ... 34 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

15 years, 10 months

5
6
0 / 0

[JBoss JIRA] Created: (JBBUILD-346) Mavenize Docbook support

by Paul Gier (JIRA)

Mavenize Docbook support ------------------------ Key: JBBUILD-346 URL: http://jira.jboss.com/jira/browse/JBBUILD-346 Project: JBoss Build System Issue Type: Feature Request Components: Maven Reporter: Paul Gier Fix For: MavenBuild 2.0 Migrate docbook-support from ant to maven. https://svn.jboss.org/repos/jbossas/trunk/docbook-support/ -- 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

15 years, 10 months

1
2
0 / 0

[JBoss JIRA] Created: (JBAS-3828) spelling mistake in xml tag

by Goran Oberg (JIRA)

spelling mistake in xml tag --------------------------- Key: JBAS-3828 URL: http://jira.jboss.com/jira/browse/JBAS-3828 Project: JBoss Application Server Issue Type: Bug Affects Versions: JBossAS-4.0.4.GA Environment: All Reporter: Goran Oberg Priority: Trivial Just a spelling mistake... Should be <url-delimiter> instead of <url-delimeter> in <ha-local-tx-datasource> -- 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

15 years, 10 months

5
7
0 / 0

[JBoss JIRA] Created: (JBPORTAL-953) wiki not visible

by Sacha Labourey (JIRA)

wiki not visible ---------------- Key: JBPORTAL-953 URL: http://jira.jboss.com/jira/browse/JBPORTAL-953 Project: JBoss Portal Issue Type: Bug Security Level: Public (Everyone can see) Affects Versions: 2.4 Final Reporter: Sacha Labourey deploying wiki.war from portletswap in JBP deploy's folder doesn't make it visible in the list of creatable portlet (admin interface) -- 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

15 years, 10 months

3
2
0 / 0

[JBoss JIRA] Created: (JBMESSAGING-983) Messages can be delivered after connection is stopped

by Tim Fox (JIRA)

Messages can be delivered after connection is stopped ----------------------------------------------------- Key: JBMESSAGING-983 URL: http://jira.jboss.com/jira/browse/JBMESSAGING-983 Project: JBoss Messaging Issue Type: Bug Reporter: Tim Fox Assigned To: Tim Fox Fix For: 1.4.0.CR1 Stopping a connection does not currently block until all current onMessage invocations are complete, as per JMS spec. We need to make sure it does. -- 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

15 years, 10 months

2
7
0 / 0

[JBoss JIRA] Created: (JBMESSAGING-806) JBM is assuming it can look up system properties on the client side

by Tim Fox (JIRA)

JBM is assuming it can look up system properties on the client side ------------------------------------------------------------------- Key: JBMESSAGING-806 URL: http://jira.jboss.com/jira/browse/JBMESSAGING-806 Project: JBoss Messaging Issue Type: Bug Affects Versions: 1.0.1.SP3, 1.2.0.Beta1 Reporter: Tim Fox Assigned To: Tim Fox Fix For: 1.2.0.Beta2, 1.0.1.SP4 JBM (JMSRemotingConnection) does several System.getProperties() to get the override bind address and port. However in a security restricted environment e.g. jnlp or applet this may not work. This causes an exception to be thrown and the connection is not created. Need to catch the exception and set to null. -- 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

15 years, 10 months

5
15
0 / 0

[JBoss JIRA] Created: (JBAS-4569) ClusterPatrition.stopService( ) fails when server is shut down

by Jerry Gauthier (JIRA)

ClusterPatrition.stopService( ) fails when server is shut down -------------------------------------------------------------- Key: JBAS-4569 URL: http://jira.jboss.com/jira/browse/JBAS-4569 Project: JBoss Application Server Issue Type: Bug Security Level: Public (Everyone can see) Components: Clustering Affects Versions: JBossAS-5.0.0.Beta2 Reporter: Jerry Gauthier Assigned To: Jerry Gauthier Priority: Minor Fix For: JBossAS-5.0.0.Beta3 When the server is shut down, the stopService( ) method of ClusterPartition fails with a lengthy stack trace when attempting to unbind the partition from JNDI. The error occurs because InitialContext can't be instantiated due to the following exception. javax.naming.NoInitialContextException: Cannot instantiate class: org.jboss.iiop.naming.ORBInitialContextFactory[Root exception is java.lang.ClassNotFoundException: org.jboss.iiop.naming.ORBInitialContextFactory] This error only occurs when the server is being shut down; it doesn't occur if the HAPArtition service is stopped while the server is running. -- 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

15 years, 10 months

4
9
0 / 0

[JBoss JIRA] Created: (HIBERNATE-43) SQL native Request who respond only the first letter

by Alexandre PETRILLO (JIRA)

SQL native Request who respond only the first letter ---------------------------------------------------- Key: HIBERNATE-43 URL: http://jira.jboss.com/jira/browse/HIBERNATE-43 Project: Hibernate Issue Type: Bug Environment: Jboss 4.0.4 G.A. patch 1 Reporter: Alexandre PETRILLO Assigned To: Steve Ebersole I need to do some sql native query (to a data base Oracle 9i) from an EJB session Bean. I use Jboss in version 4.0.4 G.A. patch 1 My simple code : public List doNativeQueryMultiple(String sqlQuery) { List list = manager.createNativeQuery(sqlQuery).getResultList(); return list; } This is some exemple for understand the probleme. SELECT 'OUI' val FROM dual union SELECT 'NON' FROM dual Order BY 1 asc Response is : O,N SELECT 'TOTO' val FROM dual union SELECT 'NON' FROM dual Order BY 1 asc Response is : TOTO,NON SELECT 'TOT' val FROM dual union SELECT 'NON' FROM dual Order BY 1 asc Response is : T,N SELECT 'OUI' val FROM dual union SELECT 'abc' FROM dual Order BY 1 asc Response is : O,a SELECT 'OUI' val FROM dual union SELECT 'abcd' FROM dual Order BY 1 asc Response is : OUI,abcd SELECT 'OUI' val FROM dual union SELECT 'NON' FROM dual union SELECT 'TOT' FROM dual Order BY 1 asc Response is : O,N,T SELECT 'OUI' val FROM dual union SELECT 'NON' FROM dual union SELECT 'TOTO' FROM dual Order BY 1 asc Response is : OUI,NON,TOTO When the response of the request is correct, the return class type is java.lang.String And when is incorrect , the return class type is java.lang.Charactere, and the response contain the first letter. The bug is when the size of all of the selected string have the same length. The test done by Jboss for determine the class return type maybe is wrong. -- 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

15 years, 10 months

3
4
0 / 0

2025

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

2009

2008

2007

2006

jboss-jira July 2007