RE: [JBoss-dev] client libraries on EJB3
But here we are talking about what exists after the object in question has been serialized outside of the jvm. Does what your talking about still apply in that situation? Regardless, I think this discussion just further pushes for a unified javassist based proxy framework sometime before ejb3 is finalized. -Original Message- From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED] On Behalf Of Max Rydahl Andersen Sent: Wednesday, February 15, 2006 11:56 PM To: jboss-development@lists.sourceforge.net Cc: Steve Ebersole Subject: Re: [JBoss-dev] client libraries on EJB3 Hi guys, Just bumping in here to tell the whole story about the needed dependencies. Here are the reasons for ever neededing any hibernate specific stuff on a client side: 1. Managing persistent collections To track how a collection mutates so when the object comes back to the server hibernate can be more efficient when detecting and executing changes. 2. Handle lazy loaded objects If lazy=true on a class (it is by default) the object can be a simple proxied shell only containing the id. This allows us to use the object in associations without loading it (e.g. child.setParent(proxiedParent);) and to throw an exception if it is accessed without being previously loaded or in a session (e.g. proxiedParent.getName() goes boom) #1 does not require proxy libraries AFAIK but I have not tested it. #2 requires the proxy libraries (in 3.2 either javaassist or cglib), I don't know if it is feasible to generate something that is not dependent on the proxy library and still be able to reassociate it when it comes back to the server. These are important issues that should be handled in Hibernate 3.2 if at all possible. (cc'ed steve) /max --- This SF.net email is sponsored by: Splunk Inc. Do you grep through log files for problems? Stop! Download the new AJAX search engine that makes searching your log files as easy as surfing the web. DOWNLOAD SPLUNK! http://sel.as-us.falkag.net/sel?cmd=lnkkid3432bid#0486dat1642 ___ JBoss-Development mailing list JBoss-Development@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/jboss-development
Re: [JBoss-dev] client libraries on EJB3
On Thu, 16 Feb 2006 10:29:46 +0100, Adrian Brock [EMAIL PROTECTED] wrote: On Thu, 2006-02-16 at 03:26, Max Rydahl Andersen wrote: Regardless, I think this discussion just further pushes for a unified javassist based proxy framework sometime before ejb3 is finalized. Hibernate 3.2 is fully working on javaassist now so that is good ;) Doesn't jboss have client side aop based interceptors running ? Do they work without the proxy framework (javaassist.jar) ? The way AOP Remoting solves this issue (no proxy framework on the client) is to use remote classloading on the client to download the generated classes. JBoss Remoting has a notion of remote classloading that does not require all the baggage of the RMI solution, like opening an http port to make the class downloadable. It simply requests the class over the transport you are already using. Can this remote classloading be done transaparently for ejb3/hibernate related classes when running in ejb3-clientmode ? -- -- Max Rydahl Andersen callto://max.rydahl.andersen Hibernate [EMAIL PROTECTED] http://hibernate.org JBoss Inc [EMAIL PROTECTED] --- This SF.net email is sponsored by: Splunk Inc. Do you grep through log files for problems? Stop! Download the new AJAX search engine that makes searching your log files as easy as surfing the web. DOWNLOAD SPLUNK! http://sel.as-us.falkag.net/sel?cmd=lnkkid=103432bid=230486dat=121642 ___ JBoss-Development mailing list JBoss-Development@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/jboss-development
Re: [JBoss-dev] client libraries on EJB3
On Thu, 2006-02-16 at 04:37, Max Rydahl Andersen wrote: JBoss Remoting has a notion of remote classloading that does not require all the baggage of the RMI solution, like opening an http port to make the class downloadable. It simply requests the class over the transport you are already using. Can this remote classloading be done transaparently for ejb3/hibernate related classes when running in ejb3-clientmode ? You'd have to ask Bill/Tom. JBoss Remoting has two layers where you can plugin your own processing. 1) The low level marshalling 2) Component specific behaviour in the subsystem handling. -- Adrian Brock Chief Scientist JBoss Inc. --- This SF.net email is sponsored by: Splunk Inc. Do you grep through log files for problems? Stop! Download the new AJAX search engine that makes searching your log files as easy as surfing the web. DOWNLOAD SPLUNK! http://sel.as-us.falkag.net/sel?cmd=lnkkid=103432bid=230486dat=121642 ___ JBoss-Development mailing list JBoss-Development@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/jboss-development
Re: [JBoss-dev] client libraries on EJB3
On Thu, 2006-02-16 at 03:26, Max Rydahl Andersen wrote: Regardless, I think this discussion just further pushes for a unified javassist based proxy framework sometime before ejb3 is finalized. Hibernate 3.2 is fully working on javaassist now so that is good ;) Doesn't jboss have client side aop based interceptors running ? Do they work without the proxy framework (javaassist.jar) ? The way AOP Remoting solves this issue (no proxy framework on the client) is to use remote classloading on the client to download the generated classes. JBoss Remoting has a notion of remote classloading that does not require all the baggage of the RMI solution, like opening an http port to make the class downloadable. It simply requests the class over the transport you are already using. -- Adrian Brock Chief Scientist JBoss Inc. --- This SF.net email is sponsored by: Splunk Inc. Do you grep through log files for problems? Stop! Download the new AJAX search engine that makes searching your log files as easy as surfing the web. DOWNLOAD SPLUNK! http://sel.as-us.falkag.net/sel?cmd=lnkkid=103432bid=230486dat=121642 ___ JBoss-Development mailing list JBoss-Development@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/jboss-development
[JBoss-dev] jboss-remoting-testsuite-1.4 Build Completed With Testsuite Errors
View results here -> http://cruisecontrol.jboss.com/cc/buildresults/jboss-remoting-testsuite-1.4?log=log20060216041239 TESTS FAILEDAnt Error Message:/services/cruisecontrol/work/scripts/build-jboss-remoting.xml:96: The following error occurred while executing this line: /services/cruisecontrol/work/scripts/build-common-targets.xml:11: Build Successful - Tests completed with errors or failures.Date of build:02/16/2006 04:12:39Time to build:16 minutes 46 secondsLast changed:02/14/2006 11:24:00Last log entry:JBREM-317 - adding ability to by-pass setting up lease on the client side. Unit Tests: (146) Total Errors and Failures: (8)unknownorg.jboss.test.remoting.stream.StreamingTestCase(java_serialization)testMultipleClientsDifferentLocatorsDontWaitOnServerorg.jboss.test.remoting.transport.multiplex.InvokerGroupTestCase(java_serialization)testMultipleClientsDifferentLocatorsWaitOnServerorg.jboss.test.remoting.transport.multiplex.InvokerGroupTestCase(java_serialization)testMultipleClientsMixedLocatorsorg.jboss.test.remoting.transport.multiplex.InvokerGroupTestCase(java_serialization)unknownorg.jboss.test.remoting.transport.multiplex.MultiplexInvokerConfigTestCase(java_serialization)unknownorg.jboss.test.remoting.transport.multiplex.MultiplexInvokerConfigTestCase(java_serialization)unknownorg.jboss.test.remoting.transport.multiplex.MultiplexInvokerTestCase(java_serialization)unknownorg.jboss.test.remoting.transport.multiplex.MultiplexInvokerTestCase(java_serialization) Modifications since last build:(first 50 of 22)1.23modifiedtelrodsrc/main/org/jboss/remoting/Client.javaJBREM-317 - adding ability to by-pass setting up lease on the client side.1.3modifiedtelrodsrc/main/org/jboss/remoting/transport/socket/ssl/SSLSocketClientInvoker.javaJBREM-317 - adding ability to by-pass setting up lease on the client side.1.7modifiedtelrodsrc/main/org/jboss/remoting/transporter/TransporterClient.javaJBREM-317 - adding ability to by-pass setting up lease on the client side.1.8modifiedtelrodsrc/tests/org/jboss/test/remoting/transport/http/HTTPInvokerClientTestCase.javaJBREM-317 - adding ability to by-pass setting up lease on the client side.1.17modifiedtelrodsrc/main/org/jboss/remoting/transport/http/HTTPClientInvoker.javaJBREM-317 - adding ability to by-pass setting up lease on the client side.1.5modifiedtelrodsrc/main/org/jboss/remoting/transport/http/ssl/HTTPSClientInvoker.javaJBREM-317 - adding ability to by-pass setting up lease on the client side.1.8modifiedtelrodsrc/main/org/jboss/remoting/transport/rmi/RMIClientInvoker.javaJBREM-317 - adding ability to by-pass setting up lease on the client side.1.2modifiedtelrodsrc/tests/org/jboss/test/remoting/transport/socket/connection/SocketTestClient.javaJBREM-310 - added flag for turning off socket connection check (needed to fix config flag for test case)1.2modifiedtelrodsrc/tests/org/jboss/test/remoting/transport/socket/connection/SocketTestServer.javaJBREM-310 - added flag for turning off socket connection check (needed to fix config flag for test case)1.1addedtelrodsrc/tests/org/jboss/test/remoting/transport/socket/connection/SocketConnectionTestCase.javaJBREM-310 - added flag for turning off socket connection check.1.1addedtelrodsrc/tests/org/jboss/test/remoting/transport/socket/connection/SocketTestClient.javaJBREM-310 - added flag for turning off socket connection check.1.1addedtelrodsrc/tests/org/jboss/test/remoting/transport/socket/connection/SocketTestServer.javaJBREM-310 - added flag for turning off socket connection check.1.19modifiedtelrodsrc/main/org/jboss/remoting/transport/socket/ServerThread.javaJBREM-310 - added flag for turning off socket connection check.1.29modifiedtelrodsrc/main/org/jboss/remoting/transport/socket/SocketClientInvoker.javaJBREM-310 - added flag for turning off socket connection check.1.16modifiedtelrodsrc/main/org/jboss/remoting/transport/socket/SocketServerInvoker.javaJBREM-310 - added flag for turning off socket connection check.1.3modifiedtelrodsrc/main/org/jboss/remoting/transport/coyote/ClientAbortException.javaJBREM-316 - changed header apache license where appropriate.1.4modifiedtelrodsrc/main/org/jboss/remoting/transport/coyote/CoyoteInputStream.javaJBREM-316 - changed header apache license where appropriate.1.10modifiedtelrodsrc/main/org/jboss/remoting/transport/coyote/CoyoteInvoker.javaJBREM-316 - changed header apache license where appropriate.1.5modifiedtelrodsrc/main/org/jboss/remoting/transport/coyote/CoyoteOutputStream.javaJBREM-316 - changed header apache license where appropriate.1.3modifiedtelrodsrc/main/org/jboss/remoting/transport/coyote/InputBuffer.javaJBREM-316 - changed header apache license where appropriate.1.4modifiedtelrodsrc/main/org/jboss/remoting/transport/coyote/OutputBuffer.javaJBREM-316 - changed header apache license where
Re: [JBoss-dev] client libraries on EJB3
On Thu, 16 Feb 2006 09:07:49 +0100, Scott M Stark [EMAIL PROTECTED] wrote: But here we are talking about what exists after the object in question has been serialized outside of the jvm. Does what your talking about still apply in that situation? If I understand your question correctly, then yes and maybe no ;) yes, in the case of hibernate because the serialized object is detached and thus can be sent back to the client for the purpose of being reattached/made persistent again, here the PersistentCollection and proxied objects with its internal id is relevant. maybe no, because EJB3 does not seem to have the possibility to reattach, it only supports merge. But that still makes it required/needed that a lazy object can be represented as something that looks and feels like an object (e.g. for child.setParent(proxiedParent) and to get an exception for proxiedParent.getName()) Regardless, I think this discussion just further pushes for a unified javassist based proxy framework sometime before ejb3 is finalized. Hibernate 3.2 is fully working on javaassist now so that is good ;) Doesn't jboss have client side aop based interceptors running ? Do they work without the proxy framework (javaassist.jar) ? /max -Original Message- From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED] On Behalf Of Max Rydahl Andersen Sent: Wednesday, February 15, 2006 11:56 PM To: jboss-development@lists.sourceforge.net Cc: Steve Ebersole Subject: Re: [JBoss-dev] client libraries on EJB3 Hi guys, Just bumping in here to tell the whole story about the needed dependencies. Here are the reasons for ever neededing any hibernate specific stuff on a client side: 1. Managing persistent collections To track how a collection mutates so when the object comes back to the server hibernate can be more efficient when detecting and executing changes. 2. Handle lazy loaded objects If lazy=true on a class (it is by default) the object can be a simple proxied shell only containing the id. This allows us to use the object in associations without loading it (e.g. child.setParent(proxiedParent);) and to throw an exception if it is accessed without being previously loaded or in a session (e.g. proxiedParent.getName() goes boom) #1 does not require proxy libraries AFAIK but I have not tested it. #2 requires the proxy libraries (in 3.2 either javaassist or cglib), I don't know if it is feasible to generate something that is not dependent on the proxy library and still be able to reassociate it when it comes back to the server. These are important issues that should be handled in Hibernate 3.2 if at all possible. (cc'ed steve) /max --- This SF.net email is sponsored by: Splunk Inc. Do you grep through log files for problems? Stop! Download the new AJAX search engine that makes searching your log files as easy as surfing the web. DOWNLOAD SPLUNK! http://sel.as-us.falkag.net/sel?cmd=lnkkid3432bid#0486dat1642 ___ JBoss-Development mailing list JBoss-Development@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/jboss-development -- -- Max Rydahl Andersen callto://max.rydahl.andersen Hibernate [EMAIL PROTECTED] http://hibernate.org JBoss Inc [EMAIL PROTECTED] --- This SF.net email is sponsored by: Splunk Inc. Do you grep through log files for problems? Stop! Download the new AJAX search engine that makes searching your log files as easy as surfing the web. DOWNLOAD SPLUNK! http://sel.as-us.falkag.net/sel?cmd=lnkkid=103432bid=230486dat=121642 ___ JBoss-Development mailing list JBoss-Development@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/jboss-development
[JBoss-dev] jboss-remoting-testsuite-1.5 Build Completed With Testsuite Errors
View results here -> http://cruisecontrol.jboss.com/cc/buildresults/jboss-remoting-testsuite-1.5?log=log20060216043114 TESTS FAILEDAnt Error Message:/services/cruisecontrol/work/scripts/build-jboss-remoting.xml:96: The following error occurred while executing this line: /services/cruisecontrol/work/scripts/build-common-targets.xml:11: Build Successful - Tests completed with errors or failures.Date of build:02/16/2006 04:31:14Time to build:71 minutes 46 secondsLast changed:12/31/2005 20:37:24Last log entry:JBREM-272:Added tests for (clientPool != null) and (threadPool != null) in cleanup. Unit Tests: (295) Total Errors and Failures: (12)testStartorg.jboss.test.remoting.callback.pull.memory.callbackstore.CallbackStoreCallbackTestCase(java_serialization)testStartorg.jboss.test.remoting.callback.pull.memory.callbackstore.CallbackStoreCallbackTestCase(jboss_serialization)unknownorg.jboss.test.remoting.stream.StreamingTestCase(java_serialization)unknownorg.jboss.test.remoting.stream.StreamingTestCase(jboss_serialization)unknownorg.jboss.test.remoting.transport.multiplex.MultiplexInvokerConfigTestCase(java_serialization)unknownorg.jboss.test.remoting.transport.multiplex.MultiplexInvokerConfigTestCase(java_serialization)unknownorg.jboss.test.remoting.transport.multiplex.MultiplexInvokerConfigTestCase(jboss_serialization)unknownorg.jboss.test.remoting.transport.multiplex.MultiplexInvokerConfigTestCase(jboss_serialization)unknownorg.jboss.test.remoting.transport.multiplex.MultiplexInvokerTestCase(java_serialization)unknownorg.jboss.test.remoting.transport.multiplex.MultiplexInvokerTestCase(java_serialization)unknownorg.jboss.test.remoting.transport.multiplex.MultiplexInvokerTestCase(jboss_serialization)unknownorg.jboss.test.remoting.transport.multiplex.MultiplexInvokerTestCase(jboss_serialization) Modifications since last build:(first 50 of 2053)1.3modifiedtelrodsrc/tests/org/jboss/test/remoting/transport/socket/timeout/TimeoutClientTest.javaJBREM-235 - added new lgpl headers.1.3modifiedtelrodsrc/tests/org/jboss/test/remoting/transport/socket/timeout/TimeoutServerTest.javaJBREM-235 - added new lgpl headers.1.2modifiedtelrodsrc/tests/org/jboss/test/remoting/transport/socket/timeout/TimeoutTestCase.javaJBREM-235 - added new lgpl headers.1.3modifiedtelrodsrc/tests/org/jboss/test/remoting/transport/web/ComplexObject.javaJBREM-235 - added new lgpl headers.1.4modifiedtelrodsrc/tests/org/jboss/test/remoting/transport/web/WebInvocationHandler.javaJBREM-235 - added new lgpl headers.1.6modifiedtelrodsrc/tests/org/jboss/test/remoting/transport/web/WebInvokerTestClient.javaJBREM-235 - added new lgpl headers.1.2modifiedtelrodsrc/tests/org/jboss/test/remoting/transporter/TestClient.javaJBREM-235 - added new lgpl headers.1.2modifiedtelrodsrc/tests/org/jboss/test/remoting/transporter/TestServer.javaJBREM-235 - added new lgpl headers.1.2modifiedtelrodsrc/tests/org/jboss/test/remoting/transporter/TestServerImpl.javaJBREM-235 - added new lgpl headers.1.2modifiedtelrodsrc/tests/org/jboss/test/remoting/transporter/TransporterTestCase.javaJBREM-235 - added new lgpl headers.1.2modifiedtelrodsrc/tests/org/jboss/test/remoting/transport/socket/ssl/SSLInvokerConstants.javaJBREM-235 - added new lgpl headers.1.4modifiedtelrodsrc/tests/org/jboss/test/remoting/transport/socket/ssl/basic/InvokerClientTest.javaJBREM-235 - added new lgpl headers.1.8modifiedtelrodsrc/tests/org/jboss/test/remoting/transport/socket/ssl/basic/InvokerServerTest.javaJBREM-235 - added new lgpl headers.1.4modifiedtelrodsrc/tests/org/jboss/test/remoting/transport/socket/ssl/basic/InvokerTestCase.javaJBREM-235 - added new lgpl headers.1.4modifiedtelrodsrc/tests/org/jboss/test/remoting/transport/socket/ssl/custom/InvokerClientTest.javaJBREM-235 - added new lgpl headers.1.7modifiedtelrodsrc/tests/org/jboss/test/remoting/transport/socket/ssl/custom/InvokerServerTest.javaJBREM-235 - added new lgpl headers.1.5modifiedtelrodsrc/tests/org/jboss/test/remoting/transport/socket/ssl/custom/InvokerTestCase.javaJBREM-235 - added new lgpl headers.1.2modifiedtelrodsrc/tests/org/jboss/test/remoting/transport/socket/ssl/test/SSLSimpleClient.javaJBREM-235 - added new lgpl headers.1.3modifiedtelrodsrc/tests/org/jboss/test/remoting/transport/socket/ssl/test/SSLSimpleServer.javaJBREM-235 - added new lgpl headers.1.6modifiedtelrodsrc/tests/org/jboss/test/remoting/transport/socket/timeout/keepalive/TimeoutClientTest.javaJBREM-235 - added new lgpl headers.1.6modifiedtelrodsrc/tests/org/jboss/test/remoting/transport/socket/timeout/keepalive/TimeoutServerTest.javaJBREM-235 - added new lgpl headers.1.7modifiedrsigalsrc/tests/org/jboss/test/remoting/transport/socket/ssl/basic/InvokerServerTest.javaJBREM-270:Replaced "," with ""1.6modifiedrsigalsrc/tests/org/jboss/test/remoting/transport/socket/ssl/custom/InvokerServerTest.javaJBREM-270:Replaced "," with
[JBoss-dev] concurrent-testsuite Build Completed With Testsuite Errors
View results here -> http://cruisecontrol.jboss.com/cc/buildresults/concurrent-testsuite?log=log20060216085359 TESTS FAILEDAnt Error Message:/services/cruisecontrol/work/scripts/build-concurrent-testsuite.xml:73: The following error occurred while executing this line: /services/cruisecontrol/work/scripts/build-common-targets.xml:11: Build Successful - Tests completed with errors or failures.Date of build:02/16/2006 08:53:59Time to build:7 minutes 20 seconds Unit Tests: (1707) Total Errors and Failures: (1)testPrivilegedThreadFactory.ExecutorsTest Modifications since last build:(first 50 of 0)
[JBoss-dev] ejb3-4.0-testsuite Build Failed
View results here -> http://cruisecontrol.jboss.com/cc/buildresults/ejb3-4.0-testsuite?log=log20060216112903 BUILD FAILEDAnt Error Message:/services/cruisecontrol/work/scripts/build-ejb3-4.0-testsuite.xml:83: Exit code: 1 See tests.log in Build Artifacts for details.Date of build:02/16/2006 11:29:03Time to build:35 minutes 32 secondsLast changed:12/31/2005 16:46:08Last log entry:call isOpen() when obtaining session so that HEM registers with EM with TXset cglib_use_reflection flag to false Unit Tests: (0) Total Errors and Failures: (0) Modifications since last build:(first 50 of 3664)1.3modifiedbillsrc/test/org/jboss/ejb3/test/tableperinheritance/unit/EntityUnitTestCase.javaEJBs and Persistence can now be within a .jar file1.7modifiedbillsrc/test/org/jboss/ejb3/test/timer/unit/RemoteUnitTestCase.javaEJBs and Persistence can now be within a .jar file1.6modifiedbillsrc/test/org/jboss/ejb3/test/txexceptions/unit/TxExceptionsTestCase.javaEJBs and Persistence can now be within a .jar file1.3modifiedbillsrc/test/org/jboss/ejb3/test/xmlcfg/unit/EntityUnitTestCase.javaEJBs and Persistence can now be within a .jar file1.4modifiedbdecostesrc/test/org/jboss/ejb3/test/txexceptions/Dao.javaapplication-exception support1.7modifiedbdecostesrc/test/org/jboss/ejb3/test/txexceptions/DaoBean.javaapplication-exception support1.1addedbdecostesrc/test/org/jboss/ejb3/test/txexceptions/DeploymentDescriptorAppException.javabranches: 1.1.2;application-exception support1.1addedbdecostesrc/test/org/jboss/ejb3/test/txexceptions/DeploymentDescriptorCheckedRollbackException.javabranches: 1.1.2;application-exception support1.5modifiedbdecostesrc/test/org/jboss/ejb3/test/txexceptions/unit/TxExceptionsTestCase.javaapplication-exception support1.2modifiedbdecostesrc/test/org/jboss/ejb3/test/wls/embeddedwar/QueueTestMDB.javabranches: 1.2.2;activateConfig to activationConfig1.2modifiedbdecostesrc/test/org/jboss/ejb3/test/wls/embeddedwar/TopicTestMDB.javabranches: 1.2.2;activateConfig to activationConfig1.1addedbdecostesrc/test/org/jboss/ejb3/test/wls/embeddedwar/unit/EmbeddedEjb3TestCase.javatest for embedded EJB3 in WLS1.1addedbdecostesrc/test/org/jboss/ejb3/test/wls/embeddedwar/Customer.javatest for embedded EJB3 in WLS1.1addedbdecostesrc/test/org/jboss/ejb3/test/wls/embeddedwar/CustomerDAOBean.javabranches: 1.1.2;test for embedded EJB3 in WLS1.1addedbdecostesrc/test/org/jboss/ejb3/test/wls/embeddedwar/CustomerDAOLocal.javabranches: 1.1.2;test for embedded EJB3 in WLS1.1addedbdecostesrc/test/org/jboss/ejb3/test/wls/embeddedwar/CustomerDAORemote.javabranches: 1.1.2;test for embedded EJB3 in WLS1.1addedbdecostesrc/test/org/jboss/ejb3/test/wls/embeddedwar/EmbeddedEJB3.jsptest for embedded EJB3 in WLS1.1addedbdecostesrc/test/org/jboss/ejb3/test/wls/embeddedwar/JndiTest.jsptest for embedded EJB3 in WLS1.1addedbdecostesrc/test/org/jboss/ejb3/test/wls/embeddedwar/QueueTestMDB.javatest for embedded EJB3 in WLS1.1addedbdecostesrc/test/org/jboss/ejb3/test/wls/embeddedwar/TopicTestMDB.javatest for embedded EJB3 in WLS1.3modifiedstarksmsrc/test/org/jboss/ejb3/test/xmlcfg/Customer.javaUpdate the jboss LGPL headers1.3modifiedstarksmsrc/test/org/jboss/ejb3/test/xmlcfg/EntityTest.javaUpdate the jboss LGPL headers1.6modifiedstarksmsrc/test/org/jboss/ejb3/test/xmlcfg/EntityTestBean.javaUpdate the jboss LGPL headers1.4modifiedstarksmsrc/test/org/jboss/ejb3/test/timer/TimerTester.javaUpdate the jboss LGPL headers1.9modifiedstarksmsrc/test/org/jboss/ejb3/test/timer/TimerTesterBean.javaUpdate the jboss LGPL headers1.2modifiedstarksmsrc/test/org/jboss/ejb3/test/timer/TimerTesterBean21.javaUpdate the jboss LGPL headers1.6modifiedstarksmsrc/test/org/jboss/ejb3/test/timer/unit/RemoteUnitTestCase.javaUpdate the jboss LGPL headers1.2modifiedstarksmsrc/test/org/jboss/ejb3/test/txexceptions/AnnotatedAppException.javaUpdate the jboss LGPL headers1.2modifiedstarksmsrc/test/org/jboss/ejb3/test/txexceptions/AppException.javaUpdate the jboss LGPL headers1.2modifiedstarksmsrc/test/org/jboss/ejb3/test/txexceptions/CheckedRollbackException.javaUpdate the jboss LGPL headers1.3modifiedstarksmsrc/test/org/jboss/ejb3/test/txexceptions/Dao.javaUpdate the jboss LGPL headers1.6modifiedstarksmsrc/test/org/jboss/ejb3/test/txexceptions/DaoBean.javaUpdate the jboss LGPL headers1.2modifiedstarksmsrc/test/org/jboss/ejb3/test/txexceptions/NoRollbackRemoteException.javaUpdate the jboss LGPL headers1.2modifiedstarksmsrc/test/org/jboss/ejb3/test/txexceptions/NoRollbackRuntimeException.javaUpdate the jboss LGPL headers1.2modifiedstarksmsrc/test/org/jboss/ejb3/test/txexceptions/RollbackRemoteException.javaUpdate the jboss LGPL headers1.2modifiedstarksmsrc/test/org/jboss/ejb3/test/txexceptions/RollbackRuntimeException.javaUpdate the jboss LGPL headers1.3modifiedstarksmsrc/test/org/jboss/ejb3/test/txexceptions/SimpleEntity.javaUpdate the jboss LGPL
RE: [JBoss-dev] client libraries on EJB3
Well unfortunately serialization is used in two distinct scenarios that have vastly different de-serialization needs. The current code is written to handle both scenarios. The first scenario is serialization of the Hibernate Session itself such that when that Session is then de-serialized all the proxies are properly re-attached and usable. The other scenario is serialization specifically to send across a class-loader boundary. Theoretically we could just replace the proxy with some stand-in object that just always throws a LazyInitializationException. But this thing still needs to be typed correctly upon de-serialization in order to fulfill this role, so not sure how to do that without the library being used for lazy proxy generation being available on the client-side anyway. Hibernate 3.2 does have the ability to use Javassist as the bytecode library instead of CGLIB. Hibernate 3.2 is the version I am expecting to be used in EJB3 moving forward, so there is no problem if you are fine with requiring Javassist on the client-side... BTW, even with collections there is a possibility to still need access to the proxy generation library on de-serialization. This is because it is *possible* to have a collection containing proxies in the case of many-to-many associations. -Original Message- From: Scott M Stark Sent: Thursday, February 16, 2006 2:08 AM To: jboss-development@lists.sourceforge.net Cc: Steve Ebersole Subject: RE: [JBoss-dev] client libraries on EJB3 But here we are talking about what exists after the object in question has been serialized outside of the jvm. Does what your talking about still apply in that situation? Regardless, I think this discussion just further pushes for a unified javassist based proxy framework sometime before ejb3 is finalized. -Original Message- From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED] On Behalf Of Max Rydahl Andersen Sent: Wednesday, February 15, 2006 11:56 PM To: jboss-development@lists.sourceforge.net Cc: Steve Ebersole Subject: Re: [JBoss-dev] client libraries on EJB3 Hi guys, Just bumping in here to tell the whole story about the needed dependencies. Here are the reasons for ever neededing any hibernate specific stuff on a client side: 1. Managing persistent collections To track how a collection mutates so when the object comes back to the server hibernate can be more efficient when detecting and executing changes. 2. Handle lazy loaded objects If lazy=true on a class (it is by default) the object can be a simple proxied shell only containing the id. This allows us to use the object in associations without loading it (e.g. child.setParent(proxiedParent);) and to throw an exception if it is accessed without being previously loaded or in a session (e.g. proxiedParent.getName() goes boom) #1 does not require proxy libraries AFAIK but I have not tested it. #2 requires the proxy libraries (in 3.2 either javaassist or cglib), I don't know if it is feasible to generate something that is not dependent on the proxy library and still be able to reassociate it when it comes back to the server. These are important issues that should be handled in Hibernate 3.2 if at all possible. (cc'ed steve) /max --- This SF.net email is sponsored by: Splunk Inc. Do you grep through log files for problems? Stop! Download the new AJAX search engine that makes searching your log files as easy as surfing the web. DOWNLOAD SPLUNK! http://sel.as-us.falkag.net/sel?cmd=lnkkid3432bid#0486dat1642 ___ JBoss-Development mailing list JBoss-Development@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/jboss-development
[JBoss-dev] An ESB bomb just went off
If your not subscribed to the [EMAIL PROTECTED] (see how to subscribe here http://wiki.jboss.org/wiki/Wiki.jsp?page=JBossDeveloperChannels) then you missed the explosion of JBossESB threads Mark Little has started. See the following forum for the threads: http://www.jboss.com/index.html?module=bbop=viewforumf=220 Scott Stark VP Architecture Technology JBoss Inc. --- This SF.net email is sponsored by: Splunk Inc. Do you grep through log files for problems? Stop! Download the new AJAX search engine that makes searching your log files as easy as surfing the web. DOWNLOAD SPLUNK! http://sel.as-us.falkag.net/sel?cmd=lnkkid3432bid#0486dat1642 ___ JBoss-Development mailing list JBoss-Development@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/jboss-development
RE: [JBoss-dev] client libraries on EJB3
So I guess we need a discussion on aop proxies in general such that when hibernate is combined with jboss ejb3/remoting/aop we know what the behavior is and how it relates to any aop configuration that might exist in the deserialization context. -Original Message- From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED] On Behalf Of Steve Ebersole Sent: Thursday, February 16, 2006 10:10 AM To: jboss-development@lists.sourceforge.net Subject: RE: [JBoss-dev] client libraries on EJB3 Well unfortunately serialization is used in two distinct scenarios that have vastly different de-serialization needs. The current code is written to handle both scenarios. The first scenario is serialization of the Hibernate Session itself such that when that Session is then de-serialized all the proxies are properly re-attached and usable. The other scenario is serialization specifically to send across a class-loader boundary. Theoretically we could just replace the proxy with some stand-in object that just always throws a LazyInitializationException. But this thing still needs to be typed correctly upon de-serialization in order to fulfill this role, so not sure how to do that without the library being used for lazy proxy generation being available on the client-side anyway. Hibernate 3.2 does have the ability to use Javassist as the bytecode library instead of CGLIB. Hibernate 3.2 is the version I am expecting to be used in EJB3 moving forward, so there is no problem if you are fine with requiring Javassist on the client-side... BTW, even with collections there is a possibility to still need access to the proxy generation library on de-serialization. This is because it is *possible* to have a collection containing proxies in the case of many-to-many associations. -Original Message- From: Scott M Stark Sent: Thursday, February 16, 2006 2:08 AM To: jboss-development@lists.sourceforge.net Cc: Steve Ebersole Subject: RE: [JBoss-dev] client libraries on EJB3 But here we are talking about what exists after the object in question has been serialized outside of the jvm. Does what your talking about still apply in that situation? Regardless, I think this discussion just further pushes for a unified javassist based proxy framework sometime before ejb3 is finalized. -Original Message- From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED] On Behalf Of Max Rydahl Andersen Sent: Wednesday, February 15, 2006 11:56 PM To: jboss-development@lists.sourceforge.net Cc: Steve Ebersole Subject: Re: [JBoss-dev] client libraries on EJB3 Hi guys, Just bumping in here to tell the whole story about the needed dependencies. Here are the reasons for ever neededing any hibernate specific stuff on a client side: 1. Managing persistent collections To track how a collection mutates so when the object comes back to the server hibernate can be more efficient when detecting and executing changes. 2. Handle lazy loaded objects If lazy=true on a class (it is by default) the object can be a simple proxied shell only containing the id. This allows us to use the object in associations without loading it (e.g. child.setParent(proxiedParent);) and to throw an exception if it is accessed without being previously loaded or in a session (e.g. proxiedParent.getName() goes boom) #1 does not require proxy libraries AFAIK but I have not tested it. #2 requires the proxy libraries (in 3.2 either javaassist or cglib), I don't know if it is feasible to generate something that is not dependent on the proxy library and still be able to reassociate it when it comes back to the server. These are important issues that should be handled in Hibernate 3.2 if at all possible. (cc'ed steve) /max --- This SF.net email is sponsored by: Splunk Inc. Do you grep through log files for problems? Stop! Download the new AJAX search engine that makes searching your log files as easy as surfing the web. DOWNLOAD SPLUNK! http://sel.as-us.falkag.net/sel?cmd=kkid3432bid#0486dat1642 ___ JBoss-Development mailing list JBoss-Development@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/jboss-development --- This SF.net email is sponsored by: Splunk Inc. Do you grep through log files for problems? Stop! Download the new AJAX search engine that makes searching your log files as easy as surfing the web. DOWNLOAD SPLUNK! http://sel.as-us.falkag.net/sel?cmd=lnkkid3432bid#0486dat1642 ___ JBoss-Development mailing list JBoss-Development@lists.sourceforge.net
[JBoss-dev] jboss-3.2-testsuite Build Completed With Testsuite Errors
View results here -> http://cruisecontrol.jboss.com/cc/buildresults/jboss-3.2-testsuite?log=log20060216150727 TESTS FAILEDAnt Error Message:/services/cruisecontrol/work/scripts/build-jboss-common.xml:235: The following error occurred while executing this line: /services/cruisecontrol/work/scripts/build-common-targets.xml:26: Build Successful - Tests completed with errors or failures.Date of build:02/16/2006 15:07:27Time to build:50 minutes 4 seconds Unit Tests: (1848) Total Errors and Failures: (1)testAsynchTopicReceiveRollBackorg.jboss.test.jbossmq.test.RollBackUnitTestCase Modifications since last build:(first 50 of 0)
[JBoss-dev] jboss-cache-testsuite Build Completed With Testsuite Errors
View results here -> http://cruisecontrol.jboss.com/cc/buildresults/jboss-cache-testsuite?log=log20060216165830 TESTS FAILEDAnt Error Message:/services/cruisecontrol/work/scripts/build-JBossCache.xml:96: The following error occurred while executing this line: /services/cruisecontrol/work/scripts/build-common-targets.xml:11: Build Successful - Tests completed with errors or failures.Date of build:02/16/2006 16:58:30Time to build:37 minutes 47 secondsLast changed:12/28/2005 10:48:11Last log entry:Add the 1.2.4SP1 changelog notes. Unit Tests: (1399) Total Errors and Failures: (43)testSimplifiedorg.jboss.cache.aop.integrated.PropagationManagerlAopTesttestPropagationorg.jboss.cache.aop.integrated.PropagationManagerlAopTesttestSimplifiedorg.jboss.cache.aop.integrated.ReplicatedPropagationManagerlAopTesttestPropagationorg.jboss.cache.aop.integrated.ReplicatedPropagationManagerlAopTesttestCheckReplInstanceorg.jboss.cache.aop.ReplicatedObjectGraphAopTesttestCollectionWithCacheLoaderorg.jboss.cache.aop.loader.FileCacheLoaderAopTesttestConcurrentUseSyncorg.jboss.cache.aop.statetransfer.StateTransfer1241AopTesttestConcurrentUseSyncorg.jboss.cache.aop.statetransfer.StateTransfer124AopTesttestConcurrentUseSyncorg.jboss.cache.aop.statetransfer.StateTransfer130AopTestwarningorg.jboss.cache.benchmark.support.BaseTestwarningorg.jboss.cache.benchmark.support.Read50PercentTestwarningorg.jboss.cache.benchmark.support.Read75PercentTestwarningorg.jboss.cache.benchmark.support.Read90PercentTestwarningorg.jboss.cache.benchmark.tests.HashMapRead50JRunitTestwarningorg.jboss.cache.benchmark.tests.HashMapRead75JRunitTestwarningorg.jboss.cache.benchmark.tests.HashMapRead90JRunitTestwarningorg.jboss.cache.benchmark.tests.LocalPessIsoNoneRead50JRunitTestwarningorg.jboss.cache.benchmark.tests.LocalPessIsoNoneRead75JRunitTestwarningorg.jboss.cache.benchmark.tests.LocalPessIsoNoneRead90JRunitTestwarningorg.jboss.cache.benchmark.tests.LocalPessIsoRRRead50JRunitTestwarningorg.jboss.cache.benchmark.tests.LocalPessIsoRRRead75JRunitTestwarningorg.jboss.cache.benchmark.tests.LocalPessIsoRRRead90JRunitTestwarningorg.jboss.cache.benchmark.tests.ReplAsyncPessRead50JRunitTestwarningorg.jboss.cache.benchmark.tests.ReplAsyncPessRead75JRunitTestwarningorg.jboss.cache.benchmark.tests.ReplAsyncPessRead90JRunitTestwarningorg.jboss.cache.benchmark.tests.ReplSyncPessRead50JRunitTestwarningorg.jboss.cache.benchmark.tests.ReplSyncPessRead75JRunitTestwarningorg.jboss.cache.benchmark.tests.ReplSyncPessRead90JRunitTesttestUpdateEvictionorg.jboss.cache.eviction.AopLRUPolicyTesttestOptSyncReplorg.jboss.cache.loader.CacheLoaderWithReplicationTesttest2ReadersAnd1Writerorg.jboss.cache.lock.ReentrantWriterPreferenceReadWriteLockTestwarningorg.jboss.cache.optimistic.LocalCLTestwarningorg.jboss.cache.optimistic.LocalPessimisticCLTestwarningorg.jboss.cache.optimistic.LocalPessimisticTestwarningorg.jboss.cache.optimistic.LocalTesttestGetChildren9Passivationorg.jboss.cache.passivation.PassivationToBdbjeCacheLoaderTesttestGetChildren10Passivationorg.jboss.cache.passivation.PassivationToBdbjeCacheLoaderTesttestGetChildren9Passivationorg.jboss.cache.passivation.PassivationToFileCacheLoaderTesttestGetChildren10Passivationorg.jboss.cache.passivation.PassivationToFileCacheLoaderTesttestGetChildren9Passivationorg.jboss.cache.passivation.PassivationToLocalDelegatingCacheLoaderTesttestGetChildren10Passivationorg.jboss.cache.passivation.PassivationToLocalDelegatingCacheLoaderTesttestConcurrentAccessWithRWLockorg.jboss.cache.transaction.ConcurrentTransactionalTesttestNodeCreationRollbackorg.jboss.cache.transaction.IsolationLevelReadCommittedTest Modifications since last build:(first 50 of 1653)1.3modifiedmsurtanitests/perf/org/jboss/cache/loader/CacheLoaderPerfTest.javaFixes rating to JBCACHE-118 - optimising cache loader functionality.1.2modifiedmsurtanitests/perf/org/jboss/cache/loader/CacheLoaderPerfTest.javaAdded a perf test to measure performance on basic operations with a cache loader1.1addedmsurtanitests/perf/org/jboss/cache/loader/CacheLoaderPerfTest.javaAdded a perf test to measure performance on basic operations with a cache loader1.2modifieddhuangtests/stress/org/jboss/cache/EvictionLocalStressTest.javaEviction policy refactoring to support 1 Policy per Region.Refactoring of Eviction Policies to allow for easier user extension.Introduce EvictionQueue and EvictionConfiguration interfaces.New Eviction Policies for MRU and LFU.Allow configuration of EvictionPolicies at runtime.References JIRA tasks:JBCACHE-314JBCACHE-313JBCACHE-312JBCACHE-286JBCACHE-225JBCACHE-2131.2modifieddhuangtests/stress/org/jboss/cache/LocalStressTest.javaEviction policy refactoring to support 1 Policy per Region.Refactoring of Eviction Policies to allow for easier user extension.Introduce EvictionQueue and EvictionConfiguration interfaces.New Eviction Policies for MRU and LFU.Allow
[JBoss-dev] jbossretro-testsuite Build Completed With Testsuite Errors
View results here -> http://cruisecontrol.jboss.com/cc/buildresults/jbossretro-testsuite?log=log20060216173629 TESTS FAILEDAnt Error Message:/services/cruisecontrol/work/scripts/build-jbossretro-testsuite.xml:75: The following error occurred while executing this line: /services/cruisecontrol/work/scripts/build-common-targets.xml:11: Build Successful - Tests completed with errors or failures.Date of build:02/16/2006 17:36:29Time to build:17 secondsLast changed:02/15/2006 17:31:12Last log entry:[JBAS-2809] - Add JDK1.5 String methods needed by webservices. Unit Tests: (27) Total Errors and Failures: (1)testWebServiceorg.jboss.test.annotations.AnnotationsTestCase Modifications since last build:(first 50 of 9)1.5modifiedadriansrc/main/org/jboss/ant/tasks/retro/ClassRedirectEditor.java[JBAS-2809] - Add JDK1.5 String methods needed by webservices.1.3modifiedadriansrc/main/org/jboss/lang/ClassRedirects.java[JBAS-2809] - Add JDK1.5 String methods needed by webservices.1.2modifiedadriansrc/test/org/jboss/test/other/AutoboxTestCase.javaAdd missing license header.1.4modifiedadriansrc/main/org/jboss/ant/tasks/retro/ClassRedirectEditor.java[JBAS-2810] - Add support for parameter annotations.1.3modifiedadriansrc/main/org/jboss/lang/AnnotationHelper.java[JBAS-2810] - Add support for parameter annotations.1.3modifiedadriansrc/test/org/jboss/test/annotations/AnnotationsTestCase.java[JBAS-2810] - Add support for parameter annotations.1.2modifiedadriansrc/test/org/jboss/test/annotations/TestWebService.java[JBAS-2810] - Add support for parameter annotations.1.2modifiedadriansrc/test/org/jboss/test/annotations/j2ee/jws/TestAnnotation.java[JBAS-2810] - Add support for parameter annotations.1.5modifiedadrianthirdparty/javassist/lib/javassist.jar[JBAS-2810] - Add support for parameter annotations.
