March 2007 - jboss-dev-forums - Jboss List Archives

[Design of POJO Server] - how to build/test VFS

by bill.burke＠jboss.com

I was able to build VFS by deleting the parent entry in the pom.xml file. What I"m finding though is that I"m getting a lot of errors (hundreds) when running the testsuite with $ mvn test But, when running inside an IDE, I get only a handeful(like 5). Thanks Bill View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=4032224#4032224 Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=4032224

17 years, 3 months

1
0
0 / 0

[Design of JBoss Web Services] - JBoss WS 1.0.3 and JDK 1.6 not working

by c_eric_ray

Do these two place nice together. They don't for me. What used to work with JDK 1.5 now doesn't with JDK 1.6. On every web service request I get the following exception. Any suggestions on a work around or solution or do I just need to go back to JDK 1.5 in order to use JBoss WS 1.0.3? | 16:25:39,638 ERROR [SOAPFaultExceptionHelper] SOAP request exception | java.lang.UnsupportedOperationException: setProperty must be overridden by all subclasses of SOAPMessage | at javax.xml.soap.SOAPMessage.setProperty(SOAPMessage.java:424) | at org.jboss.ws.soap.SOAPMessageImpl.<init>(SOAPMessageImpl.java:65) | at org.jboss.ws.soap.MessageFactoryImpl.createMessageInternal(MessageFactoryImpl.java:209) | at org.jboss.ws.soap.MessageFactoryImpl.createMessage(MessageFactoryImpl.java:142) | at org.jboss.ws.server.ServiceEndpoint.handleRequest(ServiceEndpoint.java:190) | at org.jboss.ws.server.ServiceEndpointManager.processSOAPRequest(ServiceEndpointManager.java:355) | at org.jboss.ws.server.StandardEndpointServlet.doPost(StandardEndpointServlet.java:115) | at javax.servlet.http.HttpServlet.service(HttpServlet.java:717) | at org.jboss.ws.server.StandardEndpointServlet.service(StandardEndpointServlet.java:76) | at javax.servlet.http.HttpServlet.service(HttpServlet.java:810) | at org.apache.catalina.core.ApplicationFilterChain.internalDoFilter(ApplicationFilterChain.java:252) | at org.apache.catalina.core.ApplicationFilterChain.doFilter(ApplicationFilterChain.java:173) | at org.jboss.web.tomcat.filters.ReplyHeaderFilter.doFilter(ReplyHeaderFilter.java:96) | at org.apache.catalina.core.ApplicationFilterChain.internalDoFilter(ApplicationFilterChain.java:202) | at org.apache.catalina.core.ApplicationFilterChain.doFilter(ApplicationFilterChain.java:173) | at org.apache.catalina.core.StandardWrapperValve.invoke(StandardWrapperValve.java:213) | at org.apache.catalina.core.StandardContextValve.invoke(StandardContextValve.java:178) | at org.jboss.web.tomcat.security.SecurityAssociationValve.invoke(SecurityAssociationValve.java:175) | at org.apache.catalina.authenticator.AuthenticatorBase.invoke(AuthenticatorBase.java:432) | at org.jboss.web.tomcat.security.JaccContextValve.invoke(JaccContextValve.java:74) | at org.apache.catalina.core.StandardHostValve.invoke(StandardHostValve.java:126) | at org.apache.catalina.valves.ErrorReportValve.invoke(ErrorReportValve.java:105) | at org.apache.catalina.core.StandardEngineValve.invoke(StandardEngineValve.java:107) | at org.apache.catalina.connector.CoyoteAdapter.service(CoyoteAdapter.java:148) | at org.apache.coyote.http11.Http11Processor.process(Http11Processor.java:869) | at org.apache.coyote.http11.Http11BaseProtocol$Http11ConnectionHandler.processConnection(Http11BaseProtocol.java:664) | at org.apache.tomcat.util.net.PoolTcpEndpoint.processSocket(PoolTcpEndpoint.java:527) | at org.apache.tomcat.util.net.MasterSlaveWorkerThread.run(MasterSlaveWorkerThread.java:112) | at java.lang.Thread.run(Thread.java:619) | 16:25:39,638 ERROR [SOAPFaultExceptionHelper] Error creating SOAPFault message | java.lang.UnsupportedOperationException: setProperty must be overridden by all subclasses of SOAPMessage | at javax.xml.soap.SOAPMessage.setProperty(SOAPMessage.java:424) | at org.jboss.ws.soap.SOAPMessageImpl.<init>(SOAPMessageImpl.java:65) | at org.jboss.ws.soap.MessageFactoryImpl.createMessage(MessageFactoryImpl.java:115) | at org.jboss.ws.jaxrpc.SOAPFaultExceptionHelper.toSOAPMessage(SOAPFaultExceptionHelper.java:203) | at org.jboss.ws.jaxrpc.SOAPFaultExceptionHelper.exceptionToFaultMessage(SOAPFaultExceptionHelper.java:188) | at org.jboss.ws.server.ServiceEndpoint.handleRequest(ServiceEndpoint.java:223) | at org.jboss.ws.server.ServiceEndpointManager.processSOAPRequest(ServiceEndpointManager.java:355) | at org.jboss.ws.server.StandardEndpointServlet.doPost(StandardEndpointServlet.java:115) | at javax.servlet.http.HttpServlet.service(HttpServlet.java:717) | at org.jboss.ws.server.StandardEndpointServlet.service(StandardEndpointServlet.java:76) | at javax.servlet.http.HttpServlet.service(HttpServlet.java:810) | at org.apache.catalina.core.ApplicationFilterChain.internalDoFilter(ApplicationFilterChain.java:252) | at org.apache.catalina.core.ApplicationFilterChain.doFilter(ApplicationFilterChain.java:173) | at org.jboss.web.tomcat.filters.ReplyHeaderFilter.doFilter(ReplyHeaderFilter.java:96) | at org.apache.catalina.core.ApplicationFilterChain.internalDoFilter(ApplicationFilterChain.java:202) | at org.apache.catalina.core.ApplicationFilterChain.doFilter(ApplicationFilterChain.java:173) | at org.apache.catalina.core.StandardWrapperValve.invoke(StandardWrapperValve.java:213) | at org.apache.catalina.core.StandardContextValve.invoke(StandardContextValve.java:178) | at org.jboss.web.tomcat.security.SecurityAssociationValve.invoke(SecurityAssociationValve.java:175) | at org.apache.catalina.authenticator.AuthenticatorBase.invoke(AuthenticatorBase.java:432) | at org.jboss.web.tomcat.security.JaccContextValve.invoke(JaccContextValve.java:74) | at org.apache.catalina.core.StandardHostValve.invoke(StandardHostValve.java:126) | at org.apache.catalina.valves.ErrorReportValve.invoke(ErrorReportValve.java:105) | at org.apache.catalina.core.StandardEngineValve.invoke(StandardEngineValve.java:107) | at org.apache.catalina.connector.CoyoteAdapter.service(CoyoteAdapter.java:148) | at org.apache.coyote.http11.Http11Processor.process(Http11Processor.java:869) | at org.apache.coyote.http11.Http11BaseProtocol$Http11ConnectionHandler.processConnection(Http11BaseProtocol.java:664) | at org.apache.tomcat.util.net.PoolTcpEndpoint.processSocket(PoolTcpEndpoint.java:527) | at org.apache.tomcat.util.net.MasterSlaveWorkerThread.run(MasterSlaveWorkerThread.java:112) | at java.lang.Thread.run(Thread.java:619) | 16:25:39,655 ERROR [StandardEndpointServlet] Error processing web service request | javax.xml.rpc.JAXRPCException: Cannot create SOAPFault message for: javax.xml.rpc.soap.SOAPFaultException: setProperty must be overridden by all subclasses of SOAPMessage | at org.jboss.ws.jaxrpc.SOAPFaultExceptionHelper.exceptionToFaultMessage(SOAPFaultExceptionHelper.java:194) | at org.jboss.ws.server.ServiceEndpoint.handleRequest(ServiceEndpoint.java:223) | at org.jboss.ws.server.ServiceEndpointManager.processSOAPRequest(ServiceEndpointManager.java:355) | at org.jboss.ws.server.StandardEndpointServlet.doPost(StandardEndpointServlet.java:115) | at javax.servlet.http.HttpServlet.service(HttpServlet.java:717) | at org.jboss.ws.server.StandardEndpointServlet.service(StandardEndpointServlet.java:76) | at javax.servlet.http.HttpServlet.service(HttpServlet.java:810) | at org.apache.catalina.core.ApplicationFilterChain.internalDoFilter(ApplicationFilterChain.java:252) | at org.apache.catalina.core.ApplicationFilterChain.doFilter(ApplicationFilterChain.java:173) | at org.jboss.web.tomcat.filters.ReplyHeaderFilter.doFilter(ReplyHeaderFilter.java:96) | at org.apache.catalina.core.ApplicationFilterChain.internalDoFilter(ApplicationFilterChain.java:202) | at org.apache.catalina.core.ApplicationFilterChain.doFilter(ApplicationFilterChain.java:173) | at org.apache.catalina.core.StandardWrapperValve.invoke(StandardWrapperValve.java:213) | at org.apache.catalina.core.StandardContextValve.invoke(StandardContextValve.java:178) | at org.jboss.web.tomcat.security.SecurityAssociationValve.invoke(SecurityAssociationValve.java:175) | at org.apache.catalina.authenticator.AuthenticatorBase.invoke(AuthenticatorBase.java:432) | at org.jboss.web.tomcat.security.JaccContextValve.invoke(JaccContextValve.java:74) | at org.apache.catalina.core.StandardHostValve.invoke(StandardHostValve.java:126) | at org.apache.catalina.valves.ErrorReportValve.invoke(ErrorReportValve.java:105) | at org.apache.catalina.core.StandardEngineValve.invoke(StandardEngineValve.java:107) | at org.apache.catalina.connector.CoyoteAdapter.service(CoyoteAdapter.java:148) | at org.apache.coyote.http11.Http11Processor.process(Http11Processor.java:869) | at org.apache.coyote.http11.Http11BaseProtocol$Http11ConnectionHandler.processConnection(Http11BaseProtocol.java:664) | at org.apache.tomcat.util.net.PoolTcpEndpoint.processSocket(PoolTcpEndpoint.java:527) | at org.apache.tomcat.util.net.MasterSlaveWorkerThread.run(MasterSlaveWorkerThread.java:112) | at java.lang.Thread.run(Thread.java:619) | 16:25:39,655 ERROR [[ListBags]] Servlet.service() for servlet ListBags threw exception | javax.xml.rpc.JAXRPCException: Cannot create SOAPFault message for: javax.xml.rpc.soap.SOAPFaultException: setProperty must be overridden by all subclasses of SOAPMessage | at org.jboss.ws.jaxrpc.SOAPFaultExceptionHelper.exceptionToFaultMessage(SOAPFaultExceptionHelper.java:194) | at org.jboss.ws.server.ServiceEndpoint.handleRequest(ServiceEndpoint.java:223) | at org.jboss.ws.server.ServiceEndpointManager.processSOAPRequest(ServiceEndpointManager.java:355) | at org.jboss.ws.server.StandardEndpointServlet.doPost(StandardEndpointServlet.java:115) | at javax.servlet.http.HttpServlet.service(HttpServlet.java:717) | at org.jboss.ws.server.StandardEndpointServlet.service(StandardEndpointServlet.java:76) | at javax.servlet.http.HttpServlet.service(HttpServlet.java:810) | at org.apache.catalina.core.ApplicationFilterChain.internalDoFilter(ApplicationFilterChain.java:252) | at org.apache.catalina.core.ApplicationFilterChain.doFilter(ApplicationFilterChain.java:173) | at org.jboss.web.tomcat.filters.ReplyHeaderFilter.doFilter(ReplyHeaderFilter.java:96) | at org.apache.catalina.core.ApplicationFilterChain.internalDoFilter(ApplicationFilterChain.java:202) | at org.apache.catalina.core.ApplicationFilterChain.doFilter(ApplicationFilterChain.java:173) | at org.apache.catalina.core.StandardWrapperValve.invoke(StandardWrapperValve.java:213) | at org.apache.catalina.core.StandardContextValve.invoke(StandardContextValve.java:178) | at org.jboss.web.tomcat.security.SecurityAssociationValve.invoke(SecurityAssociationValve.java:175) | at org.apache.catalina.authenticator.AuthenticatorBase.invoke(AuthenticatorBase.java:432) | at org.jboss.web.tomcat.security.JaccContextValve.invoke(JaccContextValve.java:74) | at org.apache.catalina.core.StandardHostValve.invoke(StandardHostValve.java:126) | at org.apache.catalina.valves.ErrorReportValve.invoke(ErrorReportValve.java:105) | at org.apache.catalina.core.StandardEngineValve.invoke(StandardEngineValve.java:107) | at org.apache.catalina.connector.CoyoteAdapter.service(CoyoteAdapter.java:148) | at org.apache.coyote.http11.Http11Processor.process(Http11Processor.java:869) | at org.apache.coyote.http11.Http11BaseProtocol$Http11ConnectionHandler.processConnection(Http11BaseProtocol.java:664) | at org.apache.tomcat.util.net.PoolTcpEndpoint.processSocket(PoolTcpEndpoint.java:527) | at org.apache.tomcat.util.net.MasterSlaveWorkerThread.run(MasterSlaveWorkerThread.java:112) | at java.lang.Thread.run(Thread.java:619) | View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=4032223#4032223 Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=4032223

17 years, 3 months

1
0
0 / 0

[Design of AOP on JBoss (Aspects/JBoss)] - Re: Woven class compatibility

by clebert.suconic＠jboss.com

I think my other failures with AOP were something that happened on my environment that time.. I can't replicate it any more... and also as JbossMessaging is running fine.. I would say we don't have any other compatibility problems besides the array list size vs null argument. View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=4032219#4032219 Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=4032219

17 years, 3 months

1
0
0 / 0

[Design of Messaging on JBoss (Messaging/JBoss)] - Re: org.jboss.test.cts.test.MDBUnitTestCase

by scott.stark＠jboss.org

I have the latest update from Clebert, and with that 9/10 tests in the MDBUnitTestCase pass. The failing one looks to simply be a missing testObjectMessage queue. I'm doing a full jboss-all-config-tests to see what the mdb, existing jms test status is currently. the tests-jbossmessaging-unit itself still has some major failures (joram config looks completely broken, security tests have issues): | tests-jbossmessaging-unit: | [junit] Running org.jboss.test.jbossmessaging.perf.JMSPerfStressTestCase | [starksm@succubus testsuite]$ ant tests-jbossmessaging | Buildfile: build.xml | Overriding previous definition of reference to jboss.test.classpath | | tests-jbossmessaging: | [unzip] Expanding: /home/svn/JBossHead/jboss-head/thirdparty/jboss/jms-integration-tests/lib/jms-integration-tests.jar into /home/svn/JBossHead/jboss-head/testsuite/output/classes | Overriding previous definition of reference to jboss.test.classpath | | tests-jbossmessaging-unit: | [junit] Running org.jboss.test.jbossmessaging.perf.JMSPerfStressTestCase | [junit] Tests run: 4, Failures: 0, Errors: 0, Time elapsed: 5.557 sec | [junit] Running org.jboss.test.jbossmessaging.perf.JMSReconnectStressTestCase | [junit] Tests run: 1, Failures: 0, Errors: 0, Time elapsed: 2.659 sec | [junit] Running org.jboss.test.jbossmessaging.perf.ReceiveNackClientStressTestCase | [junit] Tests run: 1, Failures: 0, Errors: 1, Time elapsed: 0.71 sec | [junit] Test org.jboss.test.jbossmessaging.perf.ReceiveNackClientStressTestCase FAILED | [junit] Running org.jboss.test.jbossmessaging.perf.SendReplyPerfStressTestCase | [junit] Tests run: 2, Failures: 0, Errors: 0, Time elapsed: 2.229 sec | [junit] Running org.jboss.test.jbossmessaging.ra.RaJMSSessionUnitTestCase | [junit] Tests run: 1, Failures: 0, Errors: 0, Time elapsed: 6.781 sec | [junit] Running org.jboss.test.jbossmessaging.ra.RaQueueUnitTestCase | [junit] Tests run: 4, Failures: 0, Errors: 0, Time elapsed: 5.784 sec | [junit] Running org.jboss.test.jbossmessaging.ra.RaSyncRecUnitTestCase | [junit] Tests run: 1, Failures: 0, Errors: 0, Time elapsed: 2.551 sec | [junit] Running org.jboss.test.jbossmessaging.ra.RaTopicUnitTestCase | [junit] Tests run: 4, Failures: 0, Errors: 0, Time elapsed: 5.607 sec | [junit] Running org.jboss.test.jbossmessaging.test.ConcurrentDeliveryUnitTestCase | [junit] Tests run: 1, Failures: 0, Errors: 0, Time elapsed: 22.011 sec | [junit] Running org.jboss.test.jbossmessaging.test.ConnectionConsumerUnitTestCase | [junit] Tests run: 3, Failures: 0, Errors: 0, Time elapsed: 1.95 sec | [junit] Running org.jboss.test.jbossmessaging.test.DuplicateClientIDUnitTestCase | [junit] Tests run: 3, Failures: 0, Errors: 1, Time elapsed: 1.697 sec | [junit] Test org.jboss.test.jbossmessaging.test.DuplicateClientIDUnitTestCase FAILED | [junit] Running org.jboss.test.jbossmessaging.test.JBossSessionRecoverUnitTestCase | [junit] Tests run: 5, Failures: 0, Errors: 0, Time elapsed: 13.897 sec | [junit] Running org.jboss.test.jbossmessaging.test.JoramUnitTestCase | [junit] Tests run: 199, Failures: 0, Errors: 197, Time elapsed: 3.367 sec | [junit] Test org.jboss.test.jbossmessaging.test.JoramUnitTestCase FAILED | [junit] Running org.jboss.test.jbossmessaging.test.MessageBodyUnitTestCase | [junit] Tests run: 5, Failures: 1, Errors: 0, Time elapsed: 13.537 sec | [junit] Test org.jboss.test.jbossmessaging.test.MessageBodyUnitTestCase FAILED | [junit] Running org.jboss.test.jbossmessaging.test.MessageTypesUnitTestCase [junit] Tests run: 6, Failures: 0, Errors: 0, Time elapsed: 2.369 sec | [junit] Running org.jboss.test.jbossmessaging.test.RollBackUnitTestCase | [junit] Tests run: 5, Failures: 0, Errors: 5, Time elapsed: 1.919 sec | [junit] Test org.jboss.test.jbossmessaging.test.RollBackUnitTestCase FAILED [junit] Running org.jboss.test.jbossmessaging.test.SecurityUnitTestCase | [junit] Tests run: 32, Failures: 11, Errors: 12, Time elapsed: 16.974 sec | [junit] Test org.jboss.test.jbossmessaging.test.SecurityUnitTestCase FAILED [junit] Running org.jboss.test.jbossmessaging.test.TemporarySessionConnectionUnitTestCase | [junit] Tests run: 2, Failures: 0, Errors: 0, Time elapsed: 1.833 sec | [junit] Running org.jboss.test.jbossmessaging.test.UnackedUnitTestCase | [junit] Tests run: 6, Failures: 3, Errors: 3, Time elapsed: 12.219 sec | [junit] Test org.jboss.test.jbossmessaging.test.UnackedUnitTestCase FAILED | [junit] Running org.jboss.test.jbossmessaging.test.XAResourceUnitTestCase | [junit] Tests run: 2, Failures: 0, Errors: 2, Time elapsed: 2.085 sec | [junit] Test org.jboss.test.jbossmessaging.test.XAResourceUnitTestCase FAILED | [junit] Running org.jboss.test.jbossmessaging.test.XAResourceWrapperSmokeUnitTestCase | [junit] Tests run: 1, Failures: 0, Errors: 0, Time elapsed: 0.799 sec | [junit] Running org.jboss.test.jms.integration.mdb.SimpleMDBDurableTest | [junit] Tests run: 1, Failures: 0, Errors: 0, Time elapsed: 10.835 sec | [junit] Running org.jboss.test.jms.integration.mdb.SimpleMDBTest | [junit] Tests run: 2, Failures: 2, Errors: 0, Time elapsed: 14.899 sec | [junit] Test org.jboss.test.jms.integration.mdb.SimpleMDBTest FAILED | [junit] Running org.jboss.test.jms.integration.mdb.SimpleMDBUserTransactionDupsOKTest | [junit] Tests run: 1, Failures: 0, Errors: 0, Time elapsed: 13.33 sec | [junit] Running org.jboss.test.jms.integration.mdb.SimpleMDBUserTransactionTest | [junit] Tests run: 1, Failures: 0, Errors: 0, Time elapsed: 13.182 sec | [junit] Running org.jboss.test.jms.integration.mdb.SimpleMDBWithSelectorTest | [junit] Tests run: 1, Failures: 0, Errors: 0, Time elapsed: 10.421 sec | | BUILD SUCCESSFUL | Total time: 3 minutes 27 seconds | View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=4032173#4032173 Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=4032173

17 years, 3 months

1
0
0 / 0

[Design of JBoss internal QA (Test Suite)] - Where to find support for AWT - needed for webservice tests

by ldimaggi＠redhat.com

I'm trying to resolve the following problem running the 4.0.5 and 4.2.0 test suites with 1.4.2 JVMs on RHEL5 - the webservice tests (for example: org.jboss.test.webservice.admindevel.ExampleTestCase.testHelloString(ExampleTestCase) fail with an exception caused by: Caused by: java.lang.UnsatisfiedLinkError: no awt in java.library.path I've gotten around this problem on RHEL4 by installing the xorg-x11-deprecated-libs package and failures with Java 1.5 on RHEL5 by installing the libXp package, but there are still about ~200 web service testcase failures with the 1.4.2 JVMs (Sun and BEA). Has anyone tried the test suites on RHEL5 yet? Thanks... testHelloString Error Call invocation failed: Could not transmit message; nested exception is: javax.xml.soap.SOAPException: Could not transmit message java.rmi.RemoteException: Call invocation failed: Could not transmit message; nested exception is: javax.xml.soap.SOAPException: Could not transmit message at org.jboss.ws.jaxrpc.CallImpl.invokeInternal(CallImpl.java:718) at org.jboss.ws.jaxrpc.CallImpl.invoke(CallImpl.java:404) at org.jboss.ws.jaxrpc.CallProxy.invoke(CallProxy.java:148) at $Proxy3.helloString(Unknown Source) at org.jboss.test.webservice.admindevel.ExampleTestCase.testHelloString(ExampleTestCase.java:64) at junit.extensions.TestDecorator.basicRun(TestDecorator.java:22) at junit.extensions.TestSetup$1.protect(TestSetup.java:19) at junit.extensions.TestSetup.run(TestSetup.java:23) Caused by: javax.xml.soap.SOAPException: Could not transmit message at org.jboss.ws.soap.SOAPConnectionImpl.call(SOAPConnectionImpl.java:204) at org.jboss.ws.jaxrpc.CallImpl.invokeInternal(CallImpl.java:687) ... 25 more Caused by: java.lang.UnsatisfiedLinkError: no awt in java.library.path at java.lang.ClassLoader.loadLibrary(ClassLoader.java:1517) at java.lang.Runtime.loadLibrary0(Runtime.java:788) at java.lang.System.loadLibrary(System.java:834) at sun.security.action.LoadLibraryAction.run(LoadLibraryAction.java:50) at sun.awt.NativeLibLoader.loadLibraries(NativeLibLoader.java:38) at sun.awt.DebugHelper.(DebugHelper.java:29) at java.awt.Component.(Component.java:506) at java.lang.Class.forName0(Native Method) at java.lang.Class.forName(Class.java:141) at org.jboss.ws.soap.attachment.ContentHandlerRegistry.(ContentHandlerRegistry.java:51) at org.jboss.ws.xop.XOPMarshallerImpl.(XOPMarshallerImpl.java:57) at org.jboss.ws.jaxrpc.encoding.SimpleSerializer.serialize(SimpleSerializer.java:60) at org.jboss.ws.soap.SOAPContentElement.getXMLFragment(SOAPContentElement.java:157) at org.jboss.ws.soap.SOAPContentElement.expandToDOM(SOAPContentElement.java:817) at org.jboss.ws.soap.SOAPContentElement.handleMTOMTransitions(SOAPContentElement.java:1015) at org.jboss.ws.soap.SOAPContentElement.write(SOAPContentElement.java:968) at org.jboss.ws.soap.SAAJElementWriter.writeElement(SAAJElementWriter.java:171) at org.jboss.ws.soap.SAAJElementWriter.writeElement(SAAJElementWriter.java:184) at org.jboss.ws.soap.SAAJElementWriter.writeElement(SAAJElementWriter.java:184) at org.jboss.ws.soap.SAAJElementWriter.writeElement(SAAJElementWriter.java:184) View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=4032170#4032170 Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=4032170

17 years, 3 months

1
0
0 / 0

[Design of AOP on JBoss (Aspects/JBoss)] - Re: MethodInvocation.getArguments return value for 0 argumen

by clebert.suconic＠jboss.com

For JBossMessaging, we have adapted our code to test also the size of the array... but I just think changing semantics on the API is kind of dangerous. I don't know if other users will have problems with that. As you guys know your user base, take the decision thinking how other users would accept this change. Anyway I would clearly document this change on the release notes and documentation if you go that path. View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=4032157#4032157 Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=4032157

17 years, 3 months

1
0
0 / 0

[Design of AOP on JBoss (Aspects/JBoss)] - Re: MethodInvocation.getArguments return value for 0 argumen

by kabir.khan＠jboss.com

Despite what I have said previously on this thread, I prefer the empty array, and think we should go with that. View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=4032151#4032151 Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=4032151

17 years, 3 months

1
0
0 / 0

[Design of AOP on JBoss (Aspects/JBoss)] - Re: MethodInvocation.getArguments return value for 0 argumen

by flavia.rainone＠jboss.com

While I was working on JBAOP-379, I found out that call arguments array have never been null for empty arguments list. This means that CallInvocation.getArguments returns an empty array in that case. So, changing this would be equivalent to changing method and constructor execution arguments to being empty instead of null. We would be changing the semantics of the getArguments method anyway. On the other hand, we would prefer to be more consistent and stick with only one of the possibilities: - null arguments array when there are no arguments - empty arguments array when there are no arguments Given that, I want to know how do you find the idea of keeping 2.0 as is (i.e., all arguments array are non-null). View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=4032145#4032145 Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=4032145

17 years, 3 months

1
0
0 / 0

[Design of JBoss Build System] - Re: New Release Process

by scott.stark＠jboss.org

For any reasonably stable project I already expect there to be a branch. The issue with incrementing either the branch or trunk to the next version exists for either strategy as both end up with a codebase that does not match the tag as soon as another change is made. The http://maven.apache.org/plugins/maven-release-plugin/examples/prepare-rel... docs say that existing poms are updated though: Bump the version in the POMs to a new value y-SNAPSHOT (these values will also be prompted for) If that is the case whether or not a branch is used is just a function of the project maturity/policy. If there is not already a branch its not helping much to create one. View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=4032136#4032136 Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=4032136

17 years, 3 months

1
0
0 / 0

[Design of JBoss Build System] - Re: New Release Process

by pgier

Some questions for discussion: Instead of creating a tag directly off the trunk, maybe we should first create a branch for the release and increment the trunk to the next version? Then the tag would be created from the branch, and if problems are found in the tag, the tag is deleted, and the bugs are fixed in the branch. The maven release plugin is not currently set up to do branches, but this is something that could probably be added pretty easily. Instead of having QA test the actual release, maybe they can test the release candidate version, and if everything is fine, then we just rename the release candidate and do some verification that the bits are the same. View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=4032119#4032119 Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=4032119

17 years, 3 months

1
0
0 / 0

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

2009

2008

2007

2006

jboss-dev-forums March 2007