[Design of EJB 3.0] - Re: Classloading problem in proxy factories
by ALRubinger
We're not going to be able to do that extra check like:
if (!businessInterfaceClass.equals(ourBusinessInterfaceClass))
|
..else we'll get the LinkageError elsewhere, where I can't catch it:
java.lang.LinkageError: Class somepackage/ThreeLocal1IF violates loader constraints
| 20:27:33,746 ERROR [STDERR] at java.lang.Class.getDeclaredMethods0(Native Method)
| 20:27:33,746 ERROR [STDERR] at java.lang.Class.privateGetDeclaredMethods(Class.java:2395)
| 20:27:33,747 ERROR [STDERR] at java.lang.Class.getDeclaredMethod(Class.java:1907)
| 20:27:33,747 ERROR [STDERR] at java.io.ObjectStreamClass.getPrivateMethod(ObjectStreamClass.java:1354)
| 20:27:33,747 ERROR [STDERR] at java.io.ObjectStreamClass.access$1700(ObjectStreamClass.java:52)
| 20:27:33,747 ERROR [STDERR] at java.io.ObjectStreamClass$2.run(ObjectStreamClass.java:421)
| 20:27:33,748 ERROR [STDERR] at java.security.AccessController.doPrivileged(Native Method)
| 20:27:33,748 ERROR [STDERR] at java.io.ObjectStreamClass.<init>(ObjectStreamClass.java:400)
| 20:27:33,748 ERROR [STDERR] at java.io.ObjectStreamClass.lookup(ObjectStreamClass.java:297)
| 20:27:33,748 ERROR [STDERR] at java.io.ObjectOutputStream.writeObject0(ObjectOutputStream.java:1035)
| 20:27:33,749 ERROR [STDERR] at java.io.ObjectOutputStream.writeObject(ObjectOutputStream.java:302)
| 20:27:33,749 ERROR [STDERR] at org.jboss.aop.joinpoint.InvocationResponse.writeExternal(InvocationResponse.java:100)
| 20:27:33,749 ERROR [STDERR] at java.io.ObjectOutputStream.writeExternalData(ObjectOutputStream.java:1310)
| 20:27:33,749 ERROR [STDERR] at java.io.ObjectOutputStream.writeOrdinaryObject(ObjectOutputStream.java:1288)
| 20:27:33,749 ERROR [STDERR] at java.io.ObjectOutputStream.writeObject0(ObjectOutputStream.java:1079)
| 20:27:33,750 ERROR [STDERR] at java.io.ObjectOutputStream.defaultWriteFields(ObjectOutputStream.java:1375)
| 20:27:33,750 ERROR [STDERR] at java.io.ObjectOutputStream.writeSerialData(ObjectOutputStream.java:1347)
| 20:27:33,750 ERROR [STDERR] at java.io.ObjectOutputStream.writeOrdinaryObject(ObjectOutputStream.java:1290)
| 20:27:33,750 ERROR [STDERR] at java.io.ObjectOutputStream.writeObject0(ObjectOutputStream.java:1079)
| 20:27:33,751 ERROR [STDERR] at java.io.ObjectOutputStream.writeObject(ObjectOutputStream.java:302)
| 20:27:33,751 ERROR [STDERR] at org.jboss.remoting.serialization.impl.java.JavaSerializationManager.sendObjectVersion2_2(JavaSerializationManager.java:120)
| 20:27:33,751 ERROR [STDERR] at org.jboss.remoting.serialization.impl.java.JavaSerializationManager.sendObject(JavaSerializationManager.java:95)
| 20:27:33,751 ERROR [STDERR] at org.jboss.remoting.marshal.serializable.SerializableMarshaller.write(SerializableMarshaller.java:120)
| 20:27:33,752 ERROR [STDERR] at org.jboss.remoting.transport.socket.ServerThread.versionedWrite(ServerThread.java:998)
| 20:27:33,752 ERROR [STDERR] at org.jboss.remoting.transport.socket.ServerThread.completeInvocation(ServerThread.java:781)
| 20:27:33,752 ERROR [STDERR] at org.jboss.remoting.transport.socket.ServerThread.processInvocation(ServerThread.java:695)
| 20:27:33,752 ERROR [STDERR] at org.jboss.remoting.transport.socket.ServerThread.dorun(ServerThread.java:522)
| 20:27:33,752 ERROR [STDERR] at org.jboss.remoting.transport.socket.ServerThread.run(ServerThread.java:230)
S,
ALR
View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=4172933#4172933
Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=4172933
16 years, 5 months
[Design of Clustering on JBoss] - Re: JBCLUSTER-206 - Extract HB/JBC integration layer from EJ
by bstansberry@jboss.com
Prabhat,
I can release this today as a CR1. Could even call it a GA if necessary, although I'd prefer to wait in do that in another 1.5 weeks after I come back from vacation next week. I'd like to blog about it and have no time this week.
One thing I'd like to change before cutting the release would be the name of the provider classes: from "org.jboss.hibernate.jbc.cacheprovider.(Optimistic)TreeCacheProvider" to "org.jboss.hibernate.jbc.cacheprovider.(Optimistic)JmxBoundTreeCacheProvider". Will that mess you guys up too much?
Reason for this is to conform to the naming pattern of the providers shipped (in a different package) in Hibernate:
TreeCacheProvider (which instantiates a JBC instance itself)
JndiBoundTreeCacheProvider (which looks for a JBC instance in JNDI)
JmxBoundTreeCacheProvider would then mean one that looks for a JBC instance in JMX. I could then easily enough create a TreeCacheProvider and a JndiBoundTreeCacheProvider that work like the standard hibernate equivalents.
View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=4172902#4172902
Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=4172902
16 years, 5 months