[JBoss-dev] [Deployers on JBoss (Deployers/JBoss)] - Re: .ear deployment fails with: Failed to setup client ENC
Some additional information: If the deployment fails, I can re-try by touching the .ear file again and again. Eventually the deployment will then succeed. Best regards, Thomas View the original post : http://www.jboss.org/index.html?module=bb&op=viewtopic&p=3834017#3834017 Reply to the post : http://www.jboss.org/index.html?module=bb&op=posting&mode=reply&p=3834017 --- This SF.Net email is sponsored by Sleepycat Software Learn developer strategies Cisco, Motorola, Ericsson & Lucent use to deliver higher performing products faster, at low TCO. http://www.sleepycat.com/telcomwpreg.php?From=osdnemail3 ___ JBoss-Development mailing list [EMAIL PROTECTED] https://lists.sourceforge.net/lists/listinfo/jboss-development
[JBoss-dev] [Deployers on JBoss (Deployers/JBoss)] - .ear deployment fails with: Failed to setup client ENC
Hi! I'm trying to deploy an .ear file that contains several EJB modules, two web archives and a J2EE application client. The deployment, however, sometimes fails with an error message: | 07:53:03,933 DEBUG [URLDeploymentScanner] Failed to deploy: [EMAIL PROTECTED] url=file:/usr/java/jboss-3.2.3/server/default/deploy/x.ear, deployedLastModified=1083905425000 } | org.jboss.deployment.DeploymentException: Failed to setup client ENC; - nested throwable: (org.jboss.deployment.DeploymentException: Failed to resolve ejb-link: x make by ejb-name: ejb/x) | at org.jboss.deployment.ClientDeployer.create(ClientDeployer.java:120) | at org.jboss.deployment.MainDeployer.create(MainDeployer.java:786) | at org.jboss.deployment.MainDeployer.create(MainDeployer.java:778) | at org.jboss.deployment.MainDeployer.deploy(MainDeployer.java:641) | at org.jboss.deployment.MainDeployer.deploy(MainDeployer.java:605) | at sun.reflect.GeneratedMethodAccessor23.invoke(Unknown Source) | at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25) | at java.lang.reflect.Method.invoke(Method.java:324) | at org.jboss.mx.capability.ReflectedMBeanDispatcher.invoke(ReflectedMBeanDispatcher.java:284) | at org.jboss.mx.server.MBeanServerImpl.invoke(MBeanServerImpl.java:546) | at org.jboss.mx.util.MBeanProxyExt.invoke(MBeanProxyExt.java:177) | at $Proxy6.deploy(Unknown Source) | at org.jboss.deployment.scanner.URLDeploymentScanner.deploy(URLDeploymentScanner.java:302) | at org.jboss.deployment.scanner.URLDeploymentScanner.scan(URLDeploymentScanner.java:458) | at org.jboss.deployment.scanner.AbstractDeploymentScanner$ScannerThread.doScan(AbstractDeploymentScanner.java:201) | at org.jboss.deployment.scanner.AbstractDeploymentScanner$ScannerThread.loop(AbstractDeploymentScanner.java:212) | at org.jboss.deployment.scanner.AbstractDeploymentScanner$ScannerThread.run(AbstractDeploymentScanner.java:191) | Caused by: org.jboss.deployment.DeploymentException: Failed to resolve ejb-link: x make by ejb-name: ejb/x | at org.jboss.deployment.ClientDeployer.setupEnvironment(ClientDeployer.java:207) | at org.jboss.deployment.ClientDeployer.create(ClientDeployer.java:116) | ... 16 more | I have enabled PrefixDeploymentSorter in the jboss-service.xml and renamed the .jar files: 100-aa.jar = EJB module 200-aa.jar = EJB module 200-b.jar = EJB module 200-cc.jar = EJB module 300-aa.jar = EJB module aa.war = WAR module b.war = WAR mobule 400-aa.jar = J2EE application client The order is also maintained in the .ear's application.xml. According to the log files, I believe that the initial processing of .jar files happens in the above order (state: CONSTRUCTED). But the actual processing (create step?) of the .jar files seems to happen in more or less random order. Sometimes the deployment succeeds as the EJB modules are processed before the J2EE application client, but often it fails with the above error message. I have listed the ejb-links inside the J2EE application client's META-INF/application-client.xml. It shouldn't be the problem as the deployment sometimes is a success. The client also has a file META-INF/jboss-client.xml that specifies the client jndi-name. When the deployment succeeds, I can use all clients (stand-alone and web applications) normally. JBoss version is 3.2.3 running on a Linux box. Any ideas what could be wrong? Please let me know if you need more information. Thanks in advance! Best regards, Thomas View the original post : http://www.jboss.org/index.html?module=bb&op=viewtopic&p=3834013#3834013 Reply to the post : http://www.jboss.org/index.html?module=bb&op=posting&mode=reply&p=3834013 --- This SF.Net email is sponsored by Sleepycat Software Learn developer strategies Cisco, Motorola, Ericsson & Lucent use to deliver higher performing products faster, at low TCO. http://www.sleepycat.com/telcomwpreg.php?From=osdnemail3 ___ JBoss-Development mailing list [EMAIL PROTECTED] https://lists.sourceforge.net/lists/listinfo/jboss-development
[JBoss-dev] [ jboss-Bugs-891626 ] XML in jar prevents deployer from adding it to classpath
Bugs item #891626, was opened at 2004-02-06 13:32 Message generated for change (Comment added) made by raja05 You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=376685&aid=891626&group_id=22866 Category: None Group: v3.2 Status: Open Resolution: None Priority: 5 Submitted By: Antti Lehto (anajavi) Assigned to: Nobody/Anonymous (nobody) Summary: XML in jar prevents deployer from adding it to classpath Initial Comment: Deployer does not add classes from manifest if jar contains xml. This behavior violates the j2ee 1.3 and 1.4 specification. The 1.3 spec says that container should add all classes to classpath from jar. The 1.4 spec says that container should ignore any xml in jar's mentioned in manifest. Here's how I found the problem: I accidently jarred jboss.xml and ejb-jar.xml inside some.jar's META-INF. This some.jar was mentioned in MANIFEST.MF of a ejb-jar. When deploying ejb-jar the deployer failed to add some.jar to ejb-jar's classpath: 2004-01-30 15:36:14,814 DEBUG [org.jboss.deployment.MainDeployer] new manifest entry for sdi at some-ejb.jar entry is lib/some.jar 2004-01-30 15:36:14,822 DEBUG [org.jboss.deployment.MainDeployer] using deployer [EMAIL PROTECTED] 2004-01-30 15:36:14,823 DEBUG [org.jboss.deployment.MainDeployer] The manifest entry in file:/opt/jboss-3.2.3_jetty-4.2.14/server/default/deploy/some.ear/some-ejb.jar/ references URL file:/opt/jboss-3.2.3_jetty-4.2.14/server/default/deploy/some.ear/lib/some.jar which could not be opened, entry ignored It seems to me that deployer tried to deploy the some.jar because of these xml-files. Jar was not added to classpath after failing deployment. I also think, that these DEBUG messages are misleading. The jar-file could have been added to classpath, although of failing deployment. It took quite time to find the real problem. -- Comment By: Rajagopal Venkataraman (raja05) Date: 2004-05-07 10:22 Message: Logged In: YES user_id=206536 If this were to be delegated to the EJBDeployer which it would given that there was a jboss.xml and ejb-jar.xml in it, then the deployment shud have failed as the files mentioned in that xml would not be available in the package. Can you attach a small example to illustrate ur problem so i can reproduce it at my end? Thanks Raja -- Comment By: Rajagopal Venkataraman (raja05) Date: 2004-05-07 10:21 Message: Logged In: YES user_id=206536 If this were to be delegated to the EJBDeployer which it would given that there was a jboss.xml and ejb-jar.xml in it, then the deployment shud have failed as the files mentioned in that xml would not be available in the package. Can you attach a small example to illustrate ur problem so i can reproduce it at my end? Thanks Raja -- Comment By: Rajagopal Venkataraman (raja05) Date: 2004-05-07 10:20 Message: Logged In: YES user_id=206536 If this were to be delegated to the EJBDeployer which it would given that there was a jboss.xml and ejb-jar.xml in it, then the deployment shud have failed as the files mentioned in that xml would not be available in the package. Can you attach a small example to illustrate ur problem so i can reproduce it at my end? Thanks Raja -- You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=376685&aid=891626&group_id=22866 --- This SF.Net email is sponsored by Sleepycat Software Learn developer strategies Cisco, Motorola, Ericsson & Lucent use to deliver higher performing products faster, at low TCO. http://www.sleepycat.com/telcomwpreg.php?From=osdnemail3 ___ JBoss-Development mailing list [EMAIL PROTECTED] https://lists.sourceforge.net/lists/listinfo/jboss-development
[JBoss-dev] [ jboss-Bugs-891626 ] XML in jar prevents deployer from adding it to classpath
Bugs item #891626, was opened at 2004-02-06 13:32 Message generated for change (Comment added) made by raja05 You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=376685&aid=891626&group_id=22866 Category: None Group: v3.2 Status: Open Resolution: None Priority: 5 Submitted By: Antti Lehto (anajavi) Assigned to: Nobody/Anonymous (nobody) Summary: XML in jar prevents deployer from adding it to classpath Initial Comment: Deployer does not add classes from manifest if jar contains xml. This behavior violates the j2ee 1.3 and 1.4 specification. The 1.3 spec says that container should add all classes to classpath from jar. The 1.4 spec says that container should ignore any xml in jar's mentioned in manifest. Here's how I found the problem: I accidently jarred jboss.xml and ejb-jar.xml inside some.jar's META-INF. This some.jar was mentioned in MANIFEST.MF of a ejb-jar. When deploying ejb-jar the deployer failed to add some.jar to ejb-jar's classpath: 2004-01-30 15:36:14,814 DEBUG [org.jboss.deployment.MainDeployer] new manifest entry for sdi at some-ejb.jar entry is lib/some.jar 2004-01-30 15:36:14,822 DEBUG [org.jboss.deployment.MainDeployer] using deployer [EMAIL PROTECTED] 2004-01-30 15:36:14,823 DEBUG [org.jboss.deployment.MainDeployer] The manifest entry in file:/opt/jboss-3.2.3_jetty-4.2.14/server/default/deploy/some.ear/some-ejb.jar/ references URL file:/opt/jboss-3.2.3_jetty-4.2.14/server/default/deploy/some.ear/lib/some.jar which could not be opened, entry ignored It seems to me that deployer tried to deploy the some.jar because of these xml-files. Jar was not added to classpath after failing deployment. I also think, that these DEBUG messages are misleading. The jar-file could have been added to classpath, although of failing deployment. It took quite time to find the real problem. -- Comment By: Rajagopal Venkataraman (raja05) Date: 2004-05-07 10:21 Message: Logged In: YES user_id=206536 If this were to be delegated to the EJBDeployer which it would given that there was a jboss.xml and ejb-jar.xml in it, then the deployment shud have failed as the files mentioned in that xml would not be available in the package. Can you attach a small example to illustrate ur problem so i can reproduce it at my end? Thanks Raja -- Comment By: Rajagopal Venkataraman (raja05) Date: 2004-05-07 10:20 Message: Logged In: YES user_id=206536 If this were to be delegated to the EJBDeployer which it would given that there was a jboss.xml and ejb-jar.xml in it, then the deployment shud have failed as the files mentioned in that xml would not be available in the package. Can you attach a small example to illustrate ur problem so i can reproduce it at my end? Thanks Raja -- You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=376685&aid=891626&group_id=22866 --- This SF.Net email is sponsored by Sleepycat Software Learn developer strategies Cisco, Motorola, Ericsson & Lucent use to deliver higher performing products faster, at low TCO. http://www.sleepycat.com/telcomwpreg.php?From=osdnemail3 ___ JBoss-Development mailing list [EMAIL PROTECTED] https://lists.sourceforge.net/lists/listinfo/jboss-development
[JBoss-dev] [ jboss-Bugs-891626 ] XML in jar prevents deployer from adding it to classpath
Bugs item #891626, was opened at 2004-02-06 13:32 Message generated for change (Comment added) made by raja05 You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=376685&aid=891626&group_id=22866 Category: None Group: v3.2 Status: Open Resolution: None Priority: 5 Submitted By: Antti Lehto (anajavi) Assigned to: Nobody/Anonymous (nobody) Summary: XML in jar prevents deployer from adding it to classpath Initial Comment: Deployer does not add classes from manifest if jar contains xml. This behavior violates the j2ee 1.3 and 1.4 specification. The 1.3 spec says that container should add all classes to classpath from jar. The 1.4 spec says that container should ignore any xml in jar's mentioned in manifest. Here's how I found the problem: I accidently jarred jboss.xml and ejb-jar.xml inside some.jar's META-INF. This some.jar was mentioned in MANIFEST.MF of a ejb-jar. When deploying ejb-jar the deployer failed to add some.jar to ejb-jar's classpath: 2004-01-30 15:36:14,814 DEBUG [org.jboss.deployment.MainDeployer] new manifest entry for sdi at some-ejb.jar entry is lib/some.jar 2004-01-30 15:36:14,822 DEBUG [org.jboss.deployment.MainDeployer] using deployer [EMAIL PROTECTED] 2004-01-30 15:36:14,823 DEBUG [org.jboss.deployment.MainDeployer] The manifest entry in file:/opt/jboss-3.2.3_jetty-4.2.14/server/default/deploy/some.ear/some-ejb.jar/ references URL file:/opt/jboss-3.2.3_jetty-4.2.14/server/default/deploy/some.ear/lib/some.jar which could not be opened, entry ignored It seems to me that deployer tried to deploy the some.jar because of these xml-files. Jar was not added to classpath after failing deployment. I also think, that these DEBUG messages are misleading. The jar-file could have been added to classpath, although of failing deployment. It took quite time to find the real problem. -- Comment By: Rajagopal Venkataraman (raja05) Date: 2004-05-07 10:20 Message: Logged In: YES user_id=206536 If this were to be delegated to the EJBDeployer which it would given that there was a jboss.xml and ejb-jar.xml in it, then the deployment shud have failed as the files mentioned in that xml would not be available in the package. Can you attach a small example to illustrate ur problem so i can reproduce it at my end? Thanks Raja -- You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=376685&aid=891626&group_id=22866 --- This SF.Net email is sponsored by Sleepycat Software Learn developer strategies Cisco, Motorola, Ericsson & Lucent use to deliver higher performing products faster, at low TCO. http://www.sleepycat.com/telcomwpreg.php?From=osdnemail3 ___ JBoss-Development mailing list [EMAIL PROTECTED] https://lists.sourceforge.net/lists/listinfo/jboss-development
[JBoss-dev] JBoss Test Results: % ( / ) - . JBoss (HEAD/winxp/1.4.2_03) [AUTOMATED]
=== ==THIS IS AN AUTOMATED EMAIL - SEE http://jboss.kimptoc.net/ FOR DETAILS== === === Fri May 7 03:04:04 GMTDT 2004 === HERE ARE THE LAST 100 LINES OF THE LOG: === ==THIS IS AN AUTOMATED EMAIL - SEE http://jboss.kimptoc.net/ FOR DETAILS== === === === Fri May 7 03:04:05 GMTDT 2004 === CYGWIN_NT-5.1 quarks2 1.5.4(0.94/3/2) 2003-09-12 23:08 i686 unknown unknown Cygwin === java -version java version "1.4.2_03" Java(TM) 2 Runtime Environment, Standard Edition (build 1.4.2_03-b02) Java HotSpot(TM) Client VM (build 1.4.2_03-b02, mixed mode) --- This SF.Net email is sponsored by Sleepycat Software Learn developer strategies Cisco, Motorola, Ericsson & Lucent use to deliver higher performing products faster, at low TCO. http://www.sleepycat.com/telcomwpreg.php?From=osdnemail3 ___ JBoss-Development mailing list [EMAIL PROTECTED] https://lists.sourceforge.net/lists/listinfo/jboss-development
[JBoss-dev] Test Job Failed to Complete Successfully (or we gave up on it...)! JBoss (HEAD/winxp/1.4.2_03) [AUTOMATED]
=== ==THIS IS AN AUTOMATED EMAIL - SEE http://jboss.kimptoc.net/ FOR DETAILS== === === Fri May 7 02:51:13 GMTDT 2004 === HERE ARE THE LAST 100 LINES OF THE LOG: === ==THIS IS AN AUTOMATED EMAIL - SEE http://jboss.kimptoc.net/ FOR DETAILS== === === tests-jsr77-unit: [junit] Running org.jboss.test.management.test.JSR77SpecUnitTestCase [junit] Tests run: 16, Failures: 0, Errors: 0, Time elapsed: 11.953 sec tests-timer-unit: [junit] Running org.jboss.test.timer.test.BasicTimerUnitTestCase [junit] Tests run: 7, Failures: 0, Errors: 1, Time elapsed: 62.594 sec [junit] TEST org.jboss.test.timer.test.BasicTimerUnitTestCase FAILED tests-txtimer-unit: [junit] Running org.jboss.test.txtimer.test.CanceledTimerTestCase [junit] Tests run: 4, Failures: 2, Errors: 0, Time elapsed: 8.156 sec [junit] TEST org.jboss.test.txtimer.test.CanceledTimerTestCase FAILED [junit] Running org.jboss.test.txtimer.test.EntityBeanTestCase [junit] Tests run: 8, Failures: 0, Errors: 0, Time elapsed: 9.515 sec [junit] Running org.jboss.test.txtimer.test.SimpleTimerTestCase [junit] Tests run: 4, Failures: 0, Errors: 0, Time elapsed: 8.094 sec [junit] Running org.jboss.test.txtimer.test.TimerSerializationTestCase [junit] Tests run: 2, Failures: 0, Errors: 0, Time elapsed: 3.156 sec [junit] Running org.jboss.test.txtimer.test.TransactionalTimerTestCase [junit] Tests run: 3, Failures: 0, Errors: 0, Time elapsed: 4.266 sec tests-util-unit: [junit] Running org.jboss.test.util.test.PropertyEditorsUnitTestCase [junit] Tests run: 5, Failures: 0, Errors: 0, Time elapsed: 0.531 sec [junit] Running org.jboss.test.util.test.PropertyPatternUnitTestCase [junit] Tests run: 17, Failures: 0, Errors: 0, Time elapsed: 0.125 sec [junit] Running org.jboss.test.util.test.ProtocolHandlerUnitTestCase [junit] Tests run: 2, Failures: 0, Errors: 0, Time elapsed: 0.078 sec [junit] Running org.jboss.test.util.test.SchedulerUnitTestCase [junit] Tests run: 3, Failures: 0, Errors: 0, Time elapsed: 0.5 sec [junit] Running org.jboss.test.util.test.StringsUnitTestCase [junit] Tests run: 4, Failures: 0, Errors: 0, Time elapsed: 0.562 sec [junit] Running org.jboss.test.util.test.ThreadPoolRunnableUnitTestCase [junit] Tests run: 7, Failures: 0, Errors: 0, Time elapsed: 1.171 sec [junit] Running org.jboss.test.util.test.ThreadPoolTaskUnitTestCase [junit] Tests run: 7, Failures: 0, Errors: 0, Time elapsed: 1.25 sec tests-webservice-unit: [junit] Running org.jboss.test.webservice.basic.AxisUnitTestCase [junit] Tests run: 3, Failures: 0, Errors: 0, Time elapsed: 15.313 sec [junit] Running org.jboss.test.webservice.ejbcomplex.EJBComplexUnitTestCase [junit] org.jboss.test.webservice.ejbcomplex.EJBComplexUnitTestCase: This test involves some intense persistence actions and may require you to adjust your server -Xmx settings. [junit] Tests run: 4, Failures: 0, Errors: 0, Time elapsed: 27.672 sec [junit] Running org.jboss.test.webservice.ejbsimple.HelloUnitTestCase [junit] Tests run: 8, Failures: 0, Errors: 0, Time elapsed: 13.172 sec [junit] Running org.jboss.test.webservice.ejbsimple.RedeployUnitTestCase [junit] Tests run: 8, Failures: 0, Errors: 0, Time elapsed: 10.719 sec [junit] Running org.jboss.test.webservice.external.ExternalUnitTestCase [junit] org.jboss.test.webservice.external.ExternalUnitTestCase: This test requires a working http(s) connection to the internet. If you are running behind a firewall, you must start the server with the correct -Dhttp.proxy options. See the java documentation for that topic. [junit] Tests run: 2, Failures: 0, Errors: 0, Time elapsed: 17.14 sec [junit] Running org.jboss.test.webservice.external.RedeployUnitTestCase [junit] org.jboss.test.webservice.external.RedeployUnitTestCase: This test requires a working http(s) connection to the internet. If you are running behind a firewall, you must start the server with the correct -Dhttp.proxy options. See the java documentation for that topic. [junit] Tests run: 2, Failures: 0, Errors: 0, Time elapsed: 14.594 sec [junit] Running org.jboss.test.webservice.jmx.JmxUnitTestCase [junit] Tests run: 11, Failures: 0, Errors: 0, Time elapsed: 7.453 sec [junit] Running org.jboss.test.webservice.jmx.RedeployUnitTestCase [junit] Tests run: 11, Failures: 0, Errors: 0, Time elapsed: 7.531 sec [junit] Running org.jbo
[JBoss-dev] [AOP on JBoss (Aspects/JBoss)] - Re: Resolving class metadata
Hi I had the exact same question before. Take a look at the following thread: http://www.jboss.org/index.html?module=bb&op=viewtopic&t=47690 Miki View the original post : http://www.jboss.org/index.html?module=bb&op=viewtopic&p=3834002#3834002 Reply to the post : http://www.jboss.org/index.html?module=bb&op=posting&mode=reply&p=3834002 --- This SF.Net email is sponsored by Sleepycat Software Learn developer strategies Cisco, Motorola, Ericsson & Lucent use to deliver higher performing products faster, at low TCO. http://www.sleepycat.com/telcomwpreg.php?From=osdnemail3 ___ JBoss-Development mailing list [EMAIL PROTECTED] https://lists.sourceforge.net/lists/listinfo/jboss-development
[JBoss-dev] JBoss Test Results: 97 % ( 1676 / 1713 ) - nearly there - who is gonna get us to 100%!. JBoss (HEAD/winxp/1.4.1_06) [AUTOMATED]
=== ==THIS IS AN AUTOMATED EMAIL - SEE http://jboss.kimptoc.net/ FOR DETAILS== === === Fri May 7 01:38:37 GMTDT 2004 === HERE ARE THE LAST 100 LINES OF THE LOG: === ==THIS IS AN AUTOMATED EMAIL - SEE http://jboss.kimptoc.net/ FOR DETAILS== === === JBoss daily test results SUMMARY Number of tests run: 1713 Successful tests: 1676 Errors:29 Failures: 8 [time of test: 2004-05-06.23-37 GMT] [java.version: 1.4.1_06] [java.vendor: Sun Microsystems Inc.] [java.vm.version: 1.4.1_06-b01] [java.vm.name: Java HotSpot(TM) Client VM] [java.vm.info: mixed mode] [os.name: Windows XP] [os.arch: x86] [os.version: 5.1] Useful resources: - http://jboss.kimptoc.net/winxp/1.4.1_06/logtests/testresults/reports/html//2004-05-06.23-37 for the junit report of this test. NOTE: If there are any errors shown above - this mail is only highlighting them - it is NOT indicating that they are being looked at by anyone. It is assumed that whoever makes change(s) to jboss that break the test will be fixing the test or jboss, as appropriate! DETAILS OF ERRORS Suite: org.jboss.test.client.test.AppClientUnitTestCase Test:testENC Type:error Exception: javax.naming.NameNotFoundException Message: test-client not bound - Suite: org.jboss.test.client.test.AppClientUnitTestCase Test:testEjbs Type:error Exception: javax.naming.NameNotFoundException Message: test-client not bound - Suite: org.jboss.test.client.test.AppClientUnitTestCase Test:testServerFound Type:error Exception: java.lang.reflect.UndeclaredThrowableException Message: - Suite: org.jboss.test.exception.EntityExceptionUnitTestCase Test:testNotDiscardedApplicationExceptionInTxMarkRollback_remote Type:error Exception: net.sourceforge.junitejb.RemoteTestException Message: Error, bean instance was discarded! - Suite: org.jboss.test.exception.EntityExceptionUnitTestCase Test:testNotDiscardedApplicationExceptionNewTxMarkRollback_remote Type:error Exception: net.sourceforge.junitejb.RemoteTestException Message: Error, bean instance was discarded! - Suite: org.jboss.test.exception.EntityExceptionUnitTestCase Test:testNotDiscardedApplicationExceptionNoTx_remote Type:error Exception: net.sourceforge.junitejb.RemoteTestException Message: Error, bean instance was discarded! === Fri May 7 01:38:37 GMTDT 2004 === CYGWIN_NT-5.1 quarks2 1.5.4(0.94/3/2) 2003-09-12 23:08 i686 unknown unknown Cygwin === java -version java version "1.4.1_06" Java(TM) 2 Runtime Environment, Standard Edition (build 1.4.1_06-b01) Java HotSpot(TM) Client VM (build 1.4.1_06-b01, mixed mode) --- This SF.Net email is sponsored by Sleepycat Software Learn developer strategies Cisco, Motorola, Ericsson & Lucent use to deliver higher performing products faster, at low TCO. http://www.sleepycat.com/telcomwpreg.php?From=osdnemail3 ___ JBoss-Development mailing list [EMAIL PROTECTED] https://lists.sourceforge.net/lists/listinfo/jboss-development
[JBoss-dev] jboss-head build.128 Build Successful
View results here -> http://tck2.jboss.com/cc/buildresults/jboss-head?log=log20040506185734Lbuild.128 BUILD COMPLETE - build.128Date of build: 05/06/2004 18:57:34Time to build: 13 minutes 20 secondsLast changed: 05/06/2004 18:34:30Last log entry: first cut for port component handlers Unit Tests: (0)No Tests RunThis project doesn't have any tests Modifications since last build: (10)1.8modifiedtdieslerwebservice/src/main/org/jboss/webservice/metadata/WebservicesFactory.javafirst cut for port component handlers1.2modifiedtdieslerwebservice/src/main/org/jboss/webservice/server/InvokerProvider.javafirst cut for port component handlers1.2modifiedtdieslerwebservice/src/main/org/jboss/webservice/Constants.javafirst cut for port component handlers1.5modifiedtdieslerwebservice/samples/server-ejb/resources/META-INF/webservices.xmlfirst cut for port component handlers1.6modifiedtdieslerwebservice/samples/server-ejb/build.xmlfirst cut for port component handlers1.4modifiedtdieslerj2ee/src/main/javax/xml/rpc/handler/GenericHandler.java+ add javadoc+ fix a few implementation details1.4modifiedtdieslerj2ee/src/main/javax/xml/rpc/handler/Handler.java+ add javadoc+ fix a few implementation details1.4modifiedtdieslerj2ee/src/main/javax/xml/rpc/handler/HandlerChain.java+ add javadoc+ fix a few implementation details1.4modifiedtdieslerj2ee/src/main/javax/xml/rpc/handler/HandlerInfo.java+ add javadoc+ fix a few implementation details1.3modifiedtdieslerj2ee/src/main/javax/xml/rpc/handler/MessageContext.java+ add javadoc+ fix a few implementation details
[JBoss-dev] [Nukes Development] - Re: Ant Error when building Nukes
i don't have any problems running ant from inside eclipse (3.0 m8). have you tried building from the command line as a test? View the original post : http://www.jboss.org/index.html?module=bb&op=viewtopic&p=3833997#3833997 Reply to the post : http://www.jboss.org/index.html?module=bb&op=posting&mode=reply&p=3833997 --- This SF.Net email is sponsored by Sleepycat Software Learn developer strategies Cisco, Motorola, Ericsson & Lucent use to deliver higher performing products faster, at low TCO. http://www.sleepycat.com/telcomwpreg.php?From=osdnemail3 ___ JBoss-Development mailing list [EMAIL PROTECTED] https://lists.sourceforge.net/lists/listinfo/jboss-development
[JBoss-dev] [Nukes Development] - Re: Ant Error when building Nukes
Actually I was using the Ant script in Eclipse and the Run Ant command. That is when I got the error message. I don't have this problem with my other Ant scripts in Eclipse. View the original post : http://www.jboss.org/index.html?module=bb&op=viewtopic&p=3833995#3833995 Reply to the post : http://www.jboss.org/index.html?module=bb&op=posting&mode=reply&p=3833995 --- This SF.Net email is sponsored by Sleepycat Software Learn developer strategies Cisco, Motorola, Ericsson & Lucent use to deliver higher performing products faster, at low TCO. http://www.sleepycat.com/telcomwpreg.php?From=osdnemail3 ___ JBoss-Development mailing list [EMAIL PROTECTED] https://lists.sourceforge.net/lists/listinfo/jboss-development
[JBoss-dev] [Nukes Development] - Re: Ant Error when building Nukes
the build should compile using ant versions 1.5.x through 1.6.x (i just tested this). if you are building via the command line, you should be using one of the "wrapper" scripts (build.sh/bat) to do the build instead of invoking ant directly. ant is "packaged" w/ the nukes checkout so it can take advantage of custom taskdefs, etc that may not be installed on your local machine. did you pull the correct tools directory when you performed the checkout? View the original post : http://www.jboss.org/index.html?module=bb&op=viewtopic&p=3833994#3833994 Reply to the post : http://www.jboss.org/index.html?module=bb&op=posting&mode=reply&p=3833994 --- This SF.Net email is sponsored by Sleepycat Software Learn developer strategies Cisco, Motorola, Ericsson & Lucent use to deliver higher performing products faster, at low TCO. http://www.sleepycat.com/telcomwpreg.php?From=osdnemail3 ___ JBoss-Development mailing list [EMAIL PROTECTED] https://lists.sourceforge.net/lists/listinfo/jboss-development
[JBoss-dev] [Security on JBoss] - Re: Jboss caches credentials
There are two solutions for Authentication caching, that I was able to find: 1. Set Cached timeout (by default it is 30 minutes) This site explains how to do it: http://www.timfanelli.com/index.php?p=6 2. Flush authentication info. This site has solution: http://www.jboss.org/index.html?module=bb&op=viewtopic&t=45932 View the original post : http://www.jboss.org/index.html?module=bb&op=viewtopic&p=3833993#3833993 Reply to the post : http://www.jboss.org/index.html?module=bb&op=posting&mode=reply&p=3833993 --- This SF.Net email is sponsored by Sleepycat Software Learn developer strategies Cisco, Motorola, Ericsson & Lucent use to deliver higher performing products faster, at low TCO. http://www.sleepycat.com/telcomwpreg.php?From=osdnemail3 ___ JBoss-Development mailing list [EMAIL PROTECTED] https://lists.sourceforge.net/lists/listinfo/jboss-development
[JBoss-dev] [Nukes Development] - Ant Error when building Nukes
I just started getting this error. Here is the error message: Unsupported Ant version: Apache Ant version 1.6.1 compiled on February 12 2004 Please install a version which is compatible with Ant 1.5. All the rest of my project are OK. I have Ant 1.5 installed. Any ideas? View the original post : http://www.jboss.org/index.html?module=bb&op=viewtopic&p=3833991#3833991 Reply to the post : http://www.jboss.org/index.html?module=bb&op=posting&mode=reply&p=3833991 --- This SF.Net email is sponsored by Sleepycat Software Learn developer strategies Cisco, Motorola, Ericsson & Lucent use to deliver higher performing products faster, at low TCO. http://www.sleepycat.com/telcomwpreg.php?From=osdnemail3 ___ JBoss-Development mailing list [EMAIL PROTECTED] https://lists.sourceforge.net/lists/listinfo/jboss-development
[JBoss-dev] [Nukes Development] - Re: Can't compile nukes (Crimson related error)v
Does Nukes require Jboss source in order to compile? I am pointing JBOSS_HOME to a compiled installation of JBoss 3.2.3. The nukes code breaks the same way for both the latest CVS from head AND the source package located on the JBoss download page. View the original post : http://www.jboss.org/index.html?module=bb&op=viewtopic&p=3833988#3833988 Reply to the post : http://www.jboss.org/index.html?module=bb&op=posting&mode=reply&p=3833988 --- This SF.Net email is sponsored by Sleepycat Software Learn developer strategies Cisco, Motorola, Ericsson & Lucent use to deliver higher performing products faster, at low TCO. http://www.sleepycat.com/telcomwpreg.php?From=osdnemail3 ___ JBoss-Development mailing list [EMAIL PROTECTED] https://lists.sourceforge.net/lists/listinfo/jboss-development
[JBoss-dev] jboss-3.2 build.11 Build Fixed
View results here -> http://tck2.jboss.com/cc/buildresults/jboss-3.2?log=log20040506153804Lbuild.11 BUILD COMPLETE - build.11Date of build: 05/06/2004 15:38:04Time to build: 12 minutes 43 secondsLast changed: 05/06/2004 14:33:04Last log entry: switched back to mapping method objects to ejbSelect bridges, CMP/CMR bridges are still keyed by its method names. Unit Tests: (0)No Tests RunThis project doesn't have any tests Modifications since last build: (7)1.5.2.5modifiedloubyanskyserver/src/main/org/jboss/ejb/plugins/cmp/jdbc/JDBCCreateBeanClassInstanceCommand.javaswitched back to mapping method objects to ejbSelect bridges, CMP/CMR bridges are still keyed by its method names.1.15.4.4modifiedloubyanskyserver/src/main/org/jboss/ejb/plugins/cmp/bridge/EntityBridgeInvocationHandler.javaswitched back to mapping method objects to ejbSelect bridges, CMP/CMR bridges are still keyed by its method names.1.1.1.1.2.16modifiedbstansberrytomcat/src/resources/server-50.xmlAdd a commented out section explaining how to use the new clustered SSO.1.1.2.5modifiedbstansberrytomcat/.classpathAdd cache module and jgroups.jar; used by clustered SSO implementation.1.1.2.1modifiedbstansberrytomcat/src/resources/sso-channel-50.xmlAdd JGroups protocol stack config file used by clustered SSO.1.1.1.1.2.14modifiedbstansberrytomcat/build.xmlBuild changes needed for clustered SSO:1.160.2.152modifiedbstansberrybuild/build.xmlBuild cache module before tomcat integration, as TC integration's clustered SSO uses TreeCache
[JBoss-dev] [AOP on JBoss (Aspects/JBoss)] - Re: Interceptor not intercepting
I'm running outised the app server and my jboss-aop.xml is properly loaded from the META-INF directory but not the metadata-aop.xml. It seems that the metadata file only gets propery loaded using the jboss.aop.path, is that right ? View the original post : http://www.jboss.org/index.html?module=bb&op=viewtopic&p=3833987#3833987 Reply to the post : http://www.jboss.org/index.html?module=bb&op=posting&mode=reply&p=3833987 --- This SF.Net email is sponsored by Sleepycat Software Learn developer strategies Cisco, Motorola, Ericsson & Lucent use to deliver higher performing products faster, at low TCO. http://www.sleepycat.com/telcomwpreg.php?From=osdnemail3 ___ JBoss-Development mailing list [EMAIL PROTECTED] https://lists.sourceforge.net/lists/listinfo/jboss-development
[JBoss-dev] [AOP on JBoss (Aspects/JBoss)] - Re: Multiple metadata-aop.xml
My problem is I'm using JBossAOP in a standalone mode, note with the JBoss application server. But if I can find a (not too ugly) way to package everything, I'll be happy to explain it in a 'how to'. But if you have any other suggestion, I'd be happy to experiment. Moving to JDK 1.5 just for annotations doesn't really seduce me. View the original post : http://www.jboss.org/index.html?module=bb&op=viewtopic&p=3833981#3833981 Reply to the post : http://www.jboss.org/index.html?module=bb&op=posting&mode=reply&p=3833981 --- This SF.Net email is sponsored by Sleepycat Software Learn developer strategies Cisco, Motorola, Ericsson & Lucent use to deliver higher performing products faster, at low TCO. http://www.sleepycat.com/telcomwpreg.php?From=osdnemail3 ___ JBoss-Development mailing list [EMAIL PROTECTED] https://lists.sourceforge.net/lists/listinfo/jboss-development
[JBoss-dev] jboss-head build.127 Build Successful
View results here -> http://tck2.jboss.com/cc/buildresults/jboss-head?log=log20040506151440Lbuild.127 BUILD COMPLETE - build.127Date of build: 05/06/2004 15:14:40Time to build: 14 minutes 30 secondsLast changed: 05/06/2004 14:54:40Last log entry: use config mailserver Unit Tests: (0)No Tests RunThis project doesn't have any tests Modifications since last build: (7)1.6modifiedjboss-buildtools/etc/cruisecontrol/scripts/config.xml.templateuse config mailserver1.2modifiedtdieslertestsuite/src/resources/ws4ee/ws4eesimple-client/META-INF/HelloClient.wsdlfix classpath and packaging issue with ws4ee client test1.2modifiedtdieslertestsuite/src/resources/ws4ee/ws4eesimple-client/META-INF/application-client.xmlfix classpath and packaging issue with ws4ee client test1.364modifiedtdieslertestsuite/build.xmlfix classpath and packaging issue with ws4ee client test1.11modifiedtdieslertools/etc/buildmagic/modules.entadd webservice module1.10modifiedloubyanskyserver/src/main/org/jboss/ejb/plugins/cmp/jdbc/JDBCCreateBeanClassInstanceCommand.javaswitched back to mapping method objects to ejbSelect bridges, CMP/CMR bridges are still keyed by its method names.1.23modifiedloubyanskyserver/src/main/org/jboss/ejb/plugins/cmp/bridge/EntityBridgeInvocationHandler.javaswitched back to mapping method objects to ejbSelect bridges, CMP/CMR bridges are still keyed by its method names.
[JBoss-dev] jboss-head build.126 Build Successful
View results here -> http://tck2.jboss.com/cc/buildresults/jboss-head?log=log20040506143403Lbuild.126 BUILD COMPLETE - build.126Date of build: 05/06/2004 14:34:03Time to build: 15 minutes 51 secondsLast changed: 05/06/2004 14:22:50Last log entry: Add some context to the error messages. Unit Tests: (0)No Tests RunThis project doesn't have any tests Modifications since last build: (2)1.67modifiedejortjmx/src/main/org/jboss/mx/server/MBeanServerImpl.javaAdd some context to the error messages.1.5modifiedkimptoctools/etc/cruisecontrol/scripts/config.xml.templatechange cvs check period to 10mins with a 20min quiet period before doing a build
RE: [JBoss-dev] jboss-head Build Failed
Hi, --- Scott M Stark <[EMAIL PROTECTED]> wrote: > The window for waiting for updates before doing a compile seems a > bit > small. I have built > jboss-head from a clean checkout on seperate machines so it appears > this > failure is due to > building after incomplete checkins. > Ok - it was set to 5mins between checks for updates and then a wait for a 5mins quietperiod. I've now set this to 10mins between checks and a 20min quietperiod. Chris = __ Do you Yahoo!? Win a $20,000 Career Makeover at Yahoo! HotJobs http://hotjobs.sweepstakes.yahoo.com/careermakeover --- This SF.Net email is sponsored by Sleepycat Software Learn developer strategies Cisco, Motorola, Ericsson & Lucent use to deliver higher performing products faster, at low TCO. http://www.sleepycat.com/telcomwpreg.php?From=osdnemail3 ___ JBoss-Development mailing list [EMAIL PROTECTED] https://lists.sourceforge.net/lists/listinfo/jboss-development
[JBoss-dev] jboss-head build.125 Build Fixed
View results here -> http://tck2.jboss.com/cc/buildresults/jboss-head?log=log20040506141114Lbuild.125 BUILD COMPLETE - build.125Date of build: 05/06/2004 14:11:14Time to build: 13 minutes 6 secondsLast changed: 05/06/2004 13:56:25Last log entry: This is crazy. How can you be expected to implement something that is not properly specified.After much trial and error, gnashing of teeth and some analysis of Object serialization streamsJBoss/JMX is now serialization compatible with the underspecfied RI JMX query implementation.I have no intention to repeat this excercise for the legacy 1.0 serialization.MBeanPermission is still outstanding. Unit Tests: (0)No Tests RunThis project doesn't have any tests Modifications since last build: (106)1.2deletedejortjmx/src/main/org/jboss/mx/util/BinaryComparisonQueryExp.javaThis is crazy. How can you be expected to implement something that is not properly specified.After much trial and error, gnashing of teeth and some analysis of Object serialization streamsJBoss/JMX is now serialization compatible with the underspecfied RI JMX query implementation.I have no intention to repeat this excercise for the legacy 1.0 serialization.MBeanPermission is still outstanding.1.2deletedejortjmx/src/main/org/jboss/mx/util/OrQueryExp.javaThis is crazy. How can you be expected to implement something that is not properly specified.After much trial and error, gnashing of teeth and some analysis of Object serialization streamsJBoss/JMX is now serialization compatible with the underspecfied RI JMX query implementation.I have no intention to repeat this excercise for the legacy 1.0 serialization.MBeanPermission is still outstanding.1.2deletedejortjmx/src/main/org/jboss/mx/util/SingleValueExpSupport.javaThis is crazy. How can you be expected to implement something that is not properly specified.After much trial and error, gnashing of teeth and some analysis of Object serialization streamsJBoss/JMX is now serialization compatible with the underspecfied RI JMX query implementation.I have no intention to repeat this excercise for the legacy 1.0 serialization.MBeanPermission is still outstanding.1.2deletedejortjmx/src/main/org/jboss/mx/util/AndQueryExp.javaThis is crazy. How can you be expected to implement something that is not properly specified.After much trial and error, gnashing of teeth and some analysis of Object serialization streamsJBoss/JMX is now serialization compatible with the underspecfied RI JMX query implementation.I have no intention to repeat this excercise for the legacy 1.0 serialization.MBeanPermission is still outstanding.1.2deletedejortjmx/src/main/org/jboss/mx/util/AnySubStringQueryExp.javaThis is crazy. How can you be expected to implement something that is not properly specified.After much trial and error, gnashing of teeth and some analysis of Object serialization streamsJBoss/JMX is now serialization compatible with the underspecfied RI JMX query implementation.I have no intention to repeat this excercise for the legacy 1.0 serialization.MBeanPermission is still outstanding.1.2deletedejortjmx/src/main/org/jboss/mx/util/BetweenQueryExp.javaThis is crazy. How can you be expected to implement something that is not properly specified.After much trial and error, gnashing of teeth and some analysis of Object serialization streamsJBoss/JMX is now serialization compatible with the underspecfied RI JMX query implementation.I have no intention to repeat this excercise for the legacy 1.0 serialization.MBeanPermission is still outstanding.1.2deletedejortjmx/src/main/org/jboss/mx/util/BinaryOpValueExp.javaThis is crazy. How can you be expected to implement something that is not properly specified.After much trial and error, gnashing of teeth and some analysis of Object serialization streamsJBoss/JMX is now serialization compatible with the underspecfied RI JMX query implementation.I have no intention to repeat this excercise for the legacy 1.0 serialization.MBeanPermission is still outstanding.1.2deletedejortjmx/src/main/org/jboss/mx/util/BooleanValueExp.javaThis is crazy. How can you be expected to implement something that is not properly specified.After much trial and error, gnashing of teeth and some analysis of Object serialization streamsJBoss/JMX is now serialization compatible with the underspecfied RI JMX query implementation.I have no intention to repeat this excercise for the legacy 1.0 serialization.MBeanPermission is still outstanding.1.2deletedejortjmx/src/main/org/jboss/mx/util/ClassAttributeValueExp.javaThis is crazy. How can you be expected to implement something that is not properly specified.After much trial and error, gnashing of teeth and some analysis of Object serialization streamsJBoss/JMX is now serialization compatible with the underspecfied
[JBoss-dev] [AOP on JBoss (Aspects/JBoss)] - Re: Invoking session beans from Interceptors
Seems like some bug in weblogic PortableRemoteObject implementation or their JNDI. I could get it to work in JBoss 3.2.3 -rajiv View the original post : http://www.jboss.org/index.html?module=bb&op=viewtopic&p=3833970#3833970 Reply to the post : http://www.jboss.org/index.html?module=bb&op=posting&mode=reply&p=3833970 --- This SF.Net email is sponsored by Sleepycat Software Learn developer strategies Cisco, Motorola, Ericsson & Lucent use to deliver higher performing products faster, at low TCO. http://www.sleepycat.com/telcomwpreg.php?From=osdnemail3 ___ JBoss-Development mailing list [EMAIL PROTECTED] https://lists.sourceforge.net/lists/listinfo/jboss-development
[JBoss-dev] [AOP on JBoss (Aspects/JBoss)] - Resolving class metadata
Hi,
I am currently experimenting with JBoss-AOP and the annotation/metadata support. I
have noticed that for MethodInvocations the Class metadata is not part of path that is
used to resolved the metadata. See the code from MethodInvocation.java:
public Object getMetaData(Object group, Object attr) {
|Object val = super.getMetaData(group, attr);
|if (val != null) return val;
|
|if (getAdvisor() != null) {
| val = getAdvisor().getMethodMetaData().resolve(this, group, attr);
| if (val != null) return val;
|}
|
|if (getAdvisor() != null) {
| val = getAdvisor().getDefaultMetaData().resolve(this, group, attr);
| if (val != null) return val;
|}
|
|return null;
| }
I am wondering if there is a reason for this? If not, let me know and I will post a
patch to include it in the resolution path.
View the original post :
http://www.jboss.org/index.html?module=bb&op=viewtopic&p=3833968#3833968
Reply to the post :
http://www.jboss.org/index.html?module=bb&op=posting&mode=reply&p=3833968
---
This SF.Net email is sponsored by Sleepycat Software
Learn developer strategies Cisco, Motorola, Ericsson & Lucent use to
deliver higher performing products faster, at low TCO.
http://www.sleepycat.com/telcomwpreg.php?From=osdnemail3
___
JBoss-Development mailing list
[EMAIL PROTECTED]
https://lists.sourceforge.net/lists/listinfo/jboss-development
[JBoss-dev] [ jboss-Feature Requests-949365 ] message delivery algorithm config
Feature Requests item #949365, was opened at 2004-05-06 11:05 Message generated for change (Tracker Item Submitted) made by Item Submitter You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=376688&aid=949365&group_id=22866 Category: JBossMQ Group: v3.2 Status: Open Resolution: None Priority: 5 Submitted By: D. A. Rickard (drickard) Assigned to: Nobody/Anonymous (nobody) Summary: message delivery algorithm config Initial Comment: It would be great to have the option to be able to configure how messages are distributed to message consumers. I'm running 3.2.4RC2 in the HA configuration with MSSQL persistence on Windows 2000. Our messages are consumed by multi-threaded client apps running outside of JBoss. On each client, all threads share a connection, but each has its own session. I was seeing that all messages were being sent to one consumer when the queue depth was <= 1, but they would be sent to multiple consumers if there happened to be more than one message in the queue at once. This is not really a problem, but I was expecting the messages to be round-robin'd to all consumers. I read the thread specified here... http://www.jboss.org/index.html? module=bb&op=viewtopic&t=48400 ... and went ahead and modified BasicQueue.java to use an ArrayList for the receivers. That seems to have solved my "problem" by round-robining the messages to the various threads and their queue sessions. My request is to add the ability to configure message delivery algorithms from a configuration file rather than having ot modify the source. For example, perhaps in the jbossmq-destinations-service.xml file there could be a parameter to specify "round-robin", or "least active" or "random", etc. Please see the thread below for more discussion: http://www.jboss.org/index.html? module=bb&op=viewtopic&p=3833965#3833965 -- You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=376688&aid=949365&group_id=22866 --- This SF.Net email is sponsored by Sleepycat Software Learn developer strategies Cisco, Motorola, Ericsson & Lucent use to deliver higher performing products faster, at low TCO. http://www.sleepycat.com/telcomwpreg.php?From=osdnemail3 ___ JBoss-Development mailing list [EMAIL PROTECTED] https://lists.sourceforge.net/lists/listinfo/jboss-development
[JBoss-dev] [JBoss IDE] - Failed to install JBoss IDE 1.2.330 on Eclipse 2.1.3
Hi, When I try to install JBoss IDE 1.2.330 on Eclipse 2.1.3 with Install/Update manager, I have a message box saying: Requested operation cannot be performed because it would invalidate the current configuration. See details for more information. JBoss-IDE (1.2.330): Feature requires plug-in "org.eclipse.ui.console". JBoss-IDE (1.2.330): Feature requires plug-in "org.eclipse.ant.ui". So why this error ? Pascal View the original post : http://www.jboss.org/index.html?module=bb&op=viewtopic&p=3833955#3833955 Reply to the post : http://www.jboss.org/index.html?module=bb&op=posting&mode=reply&p=3833955 --- This SF.Net email is sponsored by Sleepycat Software Learn developer strategies Cisco, Motorola, Ericsson & Lucent use to deliver higher performing products faster, at low TCO. http://www.sleepycat.com/telcomwpreg.php?From=osdnemail3 ___ JBoss-Development mailing list [EMAIL PROTECTED] https://lists.sourceforge.net/lists/listinfo/jboss-development
[JBoss-dev] jboss-head Build Failed
View results here -> http://tck2.jboss.com/cc/buildresults/jboss-head?log=log20040506123323 BUILD FAILEDAnt Error Message: file:/home/build/cruisecontrol/work/scripts/build-jboss-head.xml:80: exec returned: -122Date of build: 05/06/2004 12:33:23Time to build: 12 minutes 5 secondsLast changed: 05/06/2004 12:24:20Last log entry: add ws4ee tests Unit Tests: (0)No Tests RunThis project doesn't have any tests Modifications since last build: (26)1.363modifiedtdieslertestsuite/build.xmladd ws4ee tests1.1addedtdieslerwebservice/src/resources/schema/j2ee_jaxrpc_mapping_1_1.xsd+ add support handlers in port-component+ verify corresponding SEI+ add schema files1.1addedtdieslerwebservice/src/resources/schema/j2ee_web_services_1_1.xsd+ add support handlers in port-component+ verify corresponding SEI+ add schema files1.1addedtdieslerwebservice/src/resources/schema/j2ee_web_services_client_1_1.xsd+ add support handlers in port-component+ verify corresponding SEI+ add schema files1.2modifiedtdieslerwebservice/src/main/org/jboss/webservice/server/InvokerProviderEJB.java+ add support handlers in port-component+ verify corresponding SEI+ add schema files1.1addedtdieslerwebservice/src/resources/schema/j2ee_1_4.xsd+ add support handlers in port-component+ verify corresponding SEI+ add schema files1.1addedtdieslerwebservice/src/main/org/jboss/webservice/metadata/PortComponentHandlerMetaData.java+ add support handlers in port-component+ verify corresponding SEI+ add schema files1.2modifiedtdieslerwebservice/src/main/org/jboss/webservice/metadata/PortComponentMetaData.java+ add support handlers in port-component+ verify corresponding SEI+ add schema files1.3modifiedtdieslerwebservice/src/main/org/jboss/webservice/metadata/WebserviceDescriptionMetaData.java+ add support handlers in port-component+ verify corresponding SEI+ add schema files1.7modifiedtdieslerwebservice/src/main/org/jboss/webservice/metadata/WebservicesFactory.java+ add support handlers in port-component+ verify corresponding SEI+ add schema files1.2modifiedtdieslerwebservice/src/main/org/jboss/webservice/metadata/WebservicesMetaData.java+ add support handlers in port-component+ verify corresponding SEI+ add schema files1.3modifiedtdieslerwebservice/samples/server-web/resources/WEB-INF/web.xml+ add support handlers in port-component+ verify corresponding SEI+ add schema files1.4modifiedtdieslerwebservice/samples/client-appl/resources/META-INF/application-client.xml+ add support handlers in port-component+ verify corresponding SEI+ add schema files1.322modifiedtdieslerbuild/build.xmlreactivate jboss-net.sar1.24modifiedtdieslerserver/src/etc/conf/default/log4j.xmladd org.jboss.webservice1.2deletedtdieslerserver/src/resources/schema/j2ee_jaxrpc_mapping_1_1.xsdsupport handler in service-ref1.2deletedtdieslerserver/src/resources/schema/j2ee_web_services_1_1.xsdsupport handler in service-ref1.2deletedtdieslerserver/src/resources/schema/j2ee_web_services_client_1_1.xsdsupport handler in service-ref1.25modifiedtdieslerserver/src/main/org/jboss/metadata/WebMetaData.javasupport handler in service-ref1.64modifiedtdieslerserver/src/main/org/jboss/metadata/BeanMetaData.javasupport handler in service-ref1.9modifiedtdieslerserver/src/main/org/jboss/metadata/ClientMetaData.javasupport handler in service-ref1.2deletedtdieslerserver/src/main/org/jboss/metadata/HandlerMetaData.javasupport handler in service-ref1.1addedtdieslerserver/src/main/org/jboss/metadata/InitParamMetaData.javasupport handler in service-ref1.1addedtdieslerserver/src/main/org/jboss/metadata/PortComponentRefMetaData.javasupport handler in service-ref1.1addedtdieslerserver/src/main/org/jboss/metadata/ServiceRefHandlerMetaData.javasupport handler in service-ref1.7modifiedtdieslerserver/src/main/org/jboss/metadata/ServiceRefMetaData.javasupport handler in service-ref
[JBoss-dev] jboss-head build.124 Build Fixed
View results here -> http://tck2.jboss.com/cc/buildresults/jboss-head?log=log20040506120408Lbuild.124 BUILD COMPLETE - build.124Date of build: 05/06/2004 12:04:08Time to build: 13 minutes 51 secondsLast changed: 05/06/2004 11:53:43Last log entry: fix endless loop, when currentNode.getParent() == currentNode Unit Tests: (0)No Tests RunThis project doesn't have any tests Modifications since last build: (103)1.2modifiedtdieslerserver/src/main/org/jboss/metadata/QNameBuilder.javafix endless loop, when currentNode.getParent() == currentNode1.18modifiedtdieslersystem/src/bin/run.shadd -Djava.endorsed.dirs to command line1.13modifiedtdieslersystem/src/bin/run.batadd -Djava.endorsed.dirs to command line1.5modifiedtdieslerj2ee/src/main/javax/xml/namespace/QName.javafix NPE in equals if other is null1.3deletedtdieslertestsuite/src/resources/webservice/ws4eesimple/META-INF/Hello.wsdlremove the ws4ee related tests, updated versions will be added soon1.2deletedtdieslertestsuite/src/resources/webservice/ws4eesimple/META-INF/HelloMapping.xmlremove the ws4ee related tests, updated versions will be added soon1.2deletedtdieslertestsuite/src/resources/webservice/ws4eesimple/META-INF/application-ejb.xmlremove the ws4ee related tests, updated versions will be added soon1.2deletedtdieslertestsuite/src/resources/webservice/ws4eesimple/META-INF/application-web.xmlremove the ws4ee related tests, updated versions will be added soon1.3deletedtdieslertestsuite/src/resources/webservice/ws4eesimple/META-INF/ejb-jar.xmlremove the ws4ee related tests, updated versions will be added soon1.3deletedtdieslertestsuite/src/resources/webservice/ws4eesimple/META-INF/webservices.xmlremove the ws4ee related tests, updated versions will be added soon1.2deletedtdieslertestsuite/src/resources/webservice/ws4eesimple/WEB-INF/web-secure.xmlremove the ws4ee related tests, updated versions will be added soon1.3deletedtdieslertestsuite/src/resources/webservice/ws4eesimple/WEB-INF/web.xmlremove the ws4ee related tests, updated versions will be added soon1.2deletedtdieslertestsuite/src/resources/webservice/ws4eesimple/WEB-INF/webservices.xmlremove the ws4ee related tests, updated versions will be added soon1.3deletedtdieslertestsuite/src/resources/webservice/ws4eesimple-client/WEB-INF/web.xmlremove the ws4ee related tests, updated versions will be added soon1.7deletedtdieslertestsuite/src/resources/webservice/ws4eecomplex/META-INF/Complex1.wsdlremove the ws4ee related tests, updated versions will be added soon1.7deletedtdieslertestsuite/src/resources/webservice/ws4eecomplex/META-INF/Complex1Mapping.xmlremove the ws4ee related tests, updated versions will be added soon1.4deletedtdieslertestsuite/src/resources/webservice/ws4eecomplex/META-INF/ejb-jar.xmlremove the ws4ee related tests, updated versions will be added soon1.3deletedtdieslertestsuite/src/resources/webservice/ws4eecomplex/META-INF/server-ejb-application.xmlremove the ws4ee related tests, updated versions will be added soon1.5deletedtdieslertestsuite/src/resources/webservice/ws4eecomplex/META-INF/server-web-application.xmlremove the ws4ee related tests, updated versions will be added soon1.5deletedtdieslertestsuite/src/resources/webservice/ws4eecomplex/META-INF/webservices.xmlremove the ws4ee related tests, updated versions will be added soon1.6deletedtdieslertestsuite/src/resources/webservice/ws4eecomplex/WEB-INF/web.xmlremove the ws4ee related tests, updated versions will be added soon1.2deletedtdieslertestsuite/src/resources/webservice/ws4eehandler/META-INF/Handler.wsdlremove the ws4ee related tests, updated versions will be added soon1.2deletedtdieslertestsuite/src/resources/webservice/ws4eehandler/META-INF/HandlerMapping.xmlremove the ws4ee related tests, updated versions will be added soon1.2deletedtdieslertestsuite/src/resources/webservice/ws4eehandler/META-INF/ejb-jar.xmlremove the ws4ee related tests, updated versions will be added soon1.3deletedtdieslertestsuite/src/resources/webservice/ws4eehandler/META-INF/webservices.xmlremove the ws4ee related tests, updated versions will be added soon1.2deletedtdieslertestsuite/src/resources/webservice/ws4eesimple-client/META-INF/HelloClient.wsdlremove the ws4ee related tests, updated versions will be added soon1.2deletedtdieslertestsuite/src/resources/webservice/ws4eesimple-client/META-INF/HelloMapping.xmlremove the ws4ee related tests, updated versions will be added soon1.2deletedtdieslertestsuite/src/resources/webservice/ws4eesimple-client/META-INF/application-client.xmlremove the ws4ee related tests, updated versions will be added soon1.2deletedtdieslertestsuite/src/resources/webservice/ws4eesimple-client/META-INF/application.xmlremove the ws4ee related tests, updated versions will be added soon1.5deletedtdieslertestsuite/src/re
[JBoss-dev] [JBoss IDE] - JMX and Xdoclets tutorial
Hello,
using : Eclipse 3M8, JBoss-Ide 1.2.330 nothing else...
I've spent a few days playing with MBeans and I would like to build them using
jboss-ide... And I've got a few problems using XDoclet...
The goal would be to have a small tutorial about jmx & Jboss-ide.
I explain how I do, and I ask a few question that I would like the answer for :o)
I would like to know for example about the @jboss.xmbean that I find nowhere in
xdoclet.. but it works !! Where does it come from ?
Consider a simple MBean like that, I put my comments/question in bold :
| package tutorial.jmx;
|
| import org.jboss.system.ServiceMBeanSupport;
|
|
| /**
| * @jmx.mbean description = "My Description" name =
"tutorial.jmx:service=MyService1" extends = "org.jboss.system.ServiceMBean"
| if my service uses JNDI, how do I inform about the dependancy ?
| *
| * @jboss.service servicefile="jboss"
| *
| @jboss.xmbean .. I've got no info about it in Xdoclet.. How to know I have to use
it ?? I found it in this forum
| * @jboss.xmbean
| *
| */
| public class MyFirstService extends ServiceMBeanSupport implements MyFirstService {
|
| private String myName = "nothing";
| private String yourName = "init";
|
| /**
| * @jmx.managed-attribute access = "read-write"
| */
| public String getMyName() {
| return myName;
| }
| /**
| * @jmx.managed-attribute access = "read-write" description = "pour mettre le
nom"
| */
| public void setMyName(String myName) {
| this.myName = myName;
| }
|
| /**
| * @jmx.managed-operation impact = "ACTION" description = "Something to do.."
| * @jmx.managed-parameter name="a" type="java.lang.String" description="well,
a"
| * @jmx.managed-parameter name="b" type="java.lang.String" description="well,
b"
| * @jmx.managed-parameter name="c" type="java.lang.String" description="well,
c"
| * @return
| */
| public int doSomething(String a, String b, String c) {
| this.myName = this.myName + "x" + a + "x" + b + "x" + c;
| return 3;
| }
|
|
| public void start() throws Exception {
| super.start();
| this.myName = "start";
| }
|
| public void stop() {
| super.stop();
| this.myName = "stop";
| }
| }
|
here is my ant script :
|
|
|
|
|
|
|
|
|
|
View the original post :
http://www.jboss.org/index.html?module=bb&op=viewtopic&p=3833949#3833949
Reply to the post :
http://www.jboss.org/index.html?module=bb&op=posting&mode=reply&p=3833949
---
This SF.Net email is sponsored by Sleepycat Software
Learn developer strategies Cisco, Motorola, Ericsson & Lucent use to
deliver higher performing products faster, at low TCO.
http://www.sleepycat.com/telcomwpreg.php?From=osdnemail3
___
JBoss-Development mailing list
[EMAIL PROTECTED]
https://lists.sourceforge.net/lists/listinfo/jboss-development
[JBoss-dev] [Caches on JBoss (Caches/JBoss)] - Re: Replication - JGroups or JBossCache problem.
Got it working Bela. Problem with my usage of transactions and locking properties. Taking the code forward for a large scale test. Raj View the original post : http://www.jboss.org/index.html?module=bb&op=viewtopic&p=3833945#3833945 Reply to the post : http://www.jboss.org/index.html?module=bb&op=posting&mode=reply&p=3833945 --- This SF.Net email is sponsored by Sleepycat Software Learn developer strategies Cisco, Motorola, Ericsson & Lucent use to deliver higher performing products faster, at low TCO. http://www.sleepycat.com/telcomwpreg.php?From=osdnemail3 ___ JBoss-Development mailing list [EMAIL PROTECTED] https://lists.sourceforge.net/lists/listinfo/jboss-development
[JBoss-dev] [Security on JBoss] - Re: Jboss caches credentials
Hi we run through the same problem. I found (http://www.javaworld.com/javaworld/jw-08-2001/jw-0831-jaas.html) this information regarding caching: "Note that you can configure the JaasSecurityManager to use a cache of authentication information so that a JAAS login is not performed on every method invocation. If no cache is specified in the JaasSecurityManager's configuration, a timed cache is used by default." >From our test JBoss refresh cached authentication information in 30 minutes range (30 >minutes after change was made actually). I still looking to configure caching mechanizm (change cached time, enforce refreshing...) If you get more information regarding caching, can you share it? View the original post : http://www.jboss.org/index.html?module=bb&op=viewtopic&p=3833941#3833941 Reply to the post : http://www.jboss.org/index.html?module=bb&op=posting&mode=reply&p=3833941 --- This SF.Net email is sponsored by Sleepycat Software Learn developer strategies Cisco, Motorola, Ericsson & Lucent use to deliver higher performing products faster, at low TCO. http://www.sleepycat.com/telcomwpreg.php?From=osdnemail3 ___ JBoss-Development mailing list [EMAIL PROTECTED] https://lists.sourceforge.net/lists/listinfo/jboss-development
[JBoss-dev] [Nukes Development] - Re: Can't compile nukes (Crimson related error)v
when is the last time you updated from cvs - from the output you are displaying above, you're missing a bunch of other classes that xdoclet should act upon even before you start the actual compile. the latest code in cvs compiles w/o issue for me. View the original post : http://www.jboss.org/index.html?module=bb&op=viewtopic&p=3833939#3833939 Reply to the post : http://www.jboss.org/index.html?module=bb&op=posting&mode=reply&p=3833939 --- This SF.Net email is sponsored by Sleepycat Software Learn developer strategies Cisco, Motorola, Ericsson & Lucent use to deliver higher performing products faster, at low TCO. http://www.sleepycat.com/telcomwpreg.php?From=osdnemail3 ___ JBoss-Development mailing list [EMAIL PROTECTED] https://lists.sourceforge.net/lists/listinfo/jboss-development
[JBoss-dev] [Nukes Development] - Can't compile nukes (Crimson related error)v
Everytime I try to compile nukes, I get the following error: build.sh: Executing: /home/tmccrary/workspace/nukes/tools/bin/ant -logger org.apache.tools.ant.NoBannerLogger | Buildfile: build.xml | | _buildmagic:init: | Trying to override old definition of task property | | configure-project: | [echo] groups: default | [echo] modules: common,nukes,adminmessages,bb,downloads,faq,jmx,journal,list,mp3player,news,permission,polls,quotes,sections,template | | _buildmagic:modules:most: | | == | == | == Executing 'most' in module 'common'... | == | == | | configure-defaults: | Overriding previous definition of reference to javac.classpath | | _default:compile-classes: |[depend] Deleted 0 out of date files in 0 seconds | | == | == | == Finished 'most' in module 'common'. | == | == | | | == | == | == Executing 'most' in module 'nukes'... | == | == | | generate-classes: | [execmodules] (XDocletMain.start 47 ) Running | [execmodules] (XDocletMain.start 47 ) Running | [execmodules] (XDocletMain.start 47 ) Running | [execmodules] (XDocletMain.start 47 ) Running | [execmodules] (XDocletMain.start 47 ) Running | [execmodules] INFO:Some classes refer to other classes that were not found among the sources or on the classpath. | [execmodules] (Perhaps the referred class doesn't exist? Hasn't been generated yet?) | [execmodules] The referring classes do not import any fully qualified classes matching these classes. | [execmodules] However, since no packages are imported, xjavadoc has assumed that the referred classes | [execmodules] belong to the same package as the referring class. The classes are: | [execmodules] /home/tmccrary/workspace/nukes/nukes/src/main/org/jboss/nukes/core/ejb/FileEJB.java --> Command qualified to org.jboss.nukes.core.ejb.Command | [execmodules] /home/tmccrary/workspace/nukes/nukes/src/main/org/jboss/nukes/core/ejb/FileEJB.java --> Action qualified to org.jboss.nukes.core.ejb.Action | [execmodules] /home/tmccrary/workspace/nukes/nukes/src/main/org/jboss/nukes/core/ejb/FileEJB.java --> FileCommand qualified to org.jboss.nukes.core.ejb.FileCommand | | _default:compile-classes: |[depend] Deleted 0 out of date files in 0 seconds | [javac] Compiling 188 source files to /home/tmccrary/workspace/nukes/nukes/output/classes | [execmodules] /home/tmccrary/workspace/nukes/nukes/src/main/org/jboss/nukes/flash/io/AMFSerializer.java:23: package org.apache.crimson.tree does not exist | [execmodules] import org.apache.crimson.tree.XmlDocument; | [execmodules]^ | [execmodules] /home/tmccrary/workspace/nukes/nukes/src/main/org/jboss/nukes/flash/io/AMFSerializer.java:227: cannot resolve symbol | [execmodules] symbol : class XmlDocument | [execmodules] location: class org.jboss.nukes.flash.io.AMFSerializer | [execmodules]private void writeXML(XmlDocument value) throws IOException | [execmodules] ^ | [execmodules] /home/tmccrary/workspace/nukes/nukes/src/main/org/jboss/nukes/core/modules/mail/MailModule.java:390: warning: Name(java.lang.String) in org.xbill.DNS.Name has been deprecated | [execmodules] Name _name = new Name(name); // Name _name = Name.fromString(name); does not work, why ? | [execmodules]^ | [execmodules] /home/tmccrary/workspace/nukes/nukes/src/main/org/jboss/nukes/flash/io/AMFSerializer.java:133: cannot resolve symbol | [execmodules] symbol : class XmlDocument | [execmodules] location: class org.jboss.nukes.flash.io.AMFSerializer | [execmodules] writeXML((XmlDocument) value); | [execmodules]^ | [execmodules] /home/tmccrary/workspace/nukes/nukes/src/main/org/jboss/nukes/handler/NukesImpl.java:226: warning: isRequestedSessionIdFromUrl() in javax.servlet.http.HttpServletRequest has been deprecated | [execmodules]public boolean isRequestedSessionIdFromUrl() | [execmodules] ^ | [execmodules] /home/tmccrary/workspace/nukes/nukes/src/main/org/jboss/nukes/handler/NukesImpl.java:353: warning: getRealPath(java.lang.String) in javax.servlet.ServletRequest has been deprecated | [execmodules]public String getRealPath(String s) | [execmodules] ^ | [execmodules] /home/tmccrary/workspace/nukes/nukes/src/main/org/jboss/nukes/handler/NukesImpl.java:451: warning: setStatus(int,java.lang.String) in javax.servlet.http.HttpServletResponse has been deprecated | [execmodules]public void setStatus(int
[JBoss-dev] [XDoclet on JBoss (XDoclet/JBoss)] - Re: how to create ejbSelect using Xdoclet
Hi, I'm having a hard time with ejbSelect / XDoclet too, but I did figure out how to generate the ejbSelect itself though. You should do something like this: | /** | * @ejb.select | * query="SELECT OBJECT(m.myField) FROM MyTable AS m WHERE ..." | */ | abstract public Integer ejbSelectMyField(...); | However, I want to use the ejbSelect to fetch the highest value of my primary key field in some table, so that I can calculate the next value for using in ejbCreate (which seems necessary because ejbCreate does not accept null for the primary key, although in the database I have an auto-incrementing int field). So I tried an EJB-QL query similar like this: | query="SELECT MAX(m.myPrimKey) FROM MyTable AS m" | However this goes wrong at deploy time, where JBoss reports an EJB-QL compile error since it does not understand the MAX() function. (apparently JBoss 3.2.3 is not CMP2.1 compliant where MAX() is defined). So I tried to use the jboss.query XDoclet tag, wich worked great for me with similar 'more advanced' queries on ejbFinder methods: | /** | * @ejb.select | * query="SELECT MAX(m.myPrimKey) FROM MyTable AS m" | * @jboss.query | * query="SELECT MAX(m.myPrimKey) FROM MyTable AS m" | */ | abstract public Integer ejbSelectMyPrimKey(); But this gives the same EJB-QL compile error; it seems the jboss.query tag is only applicable to ejbFinder and is ignored when used with ejbSelect methods. Possibly jboss.declared-sql must be used but I don't understand the XDoclet docs on this one. A working example indeed would be usefull. Anyone?? View the original post : http://www.jboss.org/index.html?module=bb&op=viewtopic&p=3833926#3833926 Reply to the post : http://www.jboss.org/index.html?module=bb&op=posting&mode=reply&p=3833926 --- This SF.Net email is sponsored by Sleepycat Software Learn developer strategies Cisco, Motorola, Ericsson & Lucent use to deliver higher performing products faster, at low TCO. http://www.sleepycat.com/telcomwpreg.php?From=osdnemail3 ___ JBoss-Development mailing list [EMAIL PROTECTED] https://lists.sourceforge.net/lists/listinfo/jboss-development
[JBoss-dev] [JBoss.net] - Re: tomcat/axis WS wars not deploying
you're in the wrong forum... use the user forums. you need jboss-net.sar in the deploy directory to enable web services. it's in the all config. look at the wiki for an example: View the original post : http://www.jboss.org/index.html?module=bb&op=viewtopic&p=3833923#3833923 Reply to the post : http://www.jboss.org/index.html?module=bb&op=posting&mode=reply&p=3833923 --- This SF.Net email is sponsored by Sleepycat Software Learn developer strategies Cisco, Motorola, Ericsson & Lucent use to deliver higher performing products faster, at low TCO. http://www.sleepycat.com/telcomwpreg.php?From=osdnemail3 ___ JBoss-Development mailing list [EMAIL PROTECTED] https://lists.sourceforge.net/lists/listinfo/jboss-development
[JBoss-dev] [ jboss-Patches-949196 ] package structure of JBoss microkernel
Patches item #949196, was opened at 2004-05-06 14:05 Message generated for change (Tracker Item Submitted) made by Item Submitter You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=376687&aid=949196&group_id=22866 Category: JBossMX Group: CVS HEAD Status: Open Resolution: None Priority: 5 Submitted By: nahk (aseem_bansal) Assigned to: Nobody/Anonymous (nobody) Summary: package structure of JBoss microkernel Initial Comment: Hi, We were evaluating Jboss microkernel for the last few days to host our manageable components and found that all our current requirements are getting fulfilled with it. So we are going ahead with its usage and are changing its package structure (from org.jboss.deployment.SARDeployer to com.fiorano.container.deployment.SARDeployer). After changing the package structure (and may be some code too), do we have to submit the updated JBoss code to the developers community? -A -- You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=376687&aid=949196&group_id=22866 --- This SF.Net email is sponsored by Sleepycat Software Learn developer strategies Cisco, Motorola, Ericsson & Lucent use to deliver higher performing products faster, at low TCO. http://www.sleepycat.com/telcomwpreg.php?From=osdnemail3 ___ JBoss-Development mailing list [EMAIL PROTECTED] https://lists.sourceforge.net/lists/listinfo/jboss-development
[JBoss-dev] jboss-head Build Failed
View results here -> http://tck2.jboss.com/cc/buildresults/jboss-head?log=log20040506091525 BUILD FAILEDAnt Error Message: file:/home/build/cruisecontrol/work/scripts/build-jboss-head.xml:80: exec returned: 1Date of build: 05/06/2004 09:15:25Time to build: 12 minutes 35 secondsLast changed: 05/06/2004 09:01:19Last log entry: fix NPE in equals if other is null Unit Tests: (0)No Tests RunThis project doesn't have any tests Modifications since last build: (100)1.5modifiedtdieslerj2ee/src/main/javax/xml/namespace/QName.javafix NPE in equals if other is null1.3deletedtdieslertestsuite/src/resources/webservice/ws4eesimple/META-INF/Hello.wsdlremove the ws4ee related tests, updated versions will be added soon1.2deletedtdieslertestsuite/src/resources/webservice/ws4eesimple/META-INF/HelloMapping.xmlremove the ws4ee related tests, updated versions will be added soon1.2deletedtdieslertestsuite/src/resources/webservice/ws4eesimple/META-INF/application-ejb.xmlremove the ws4ee related tests, updated versions will be added soon1.2deletedtdieslertestsuite/src/resources/webservice/ws4eesimple/META-INF/application-web.xmlremove the ws4ee related tests, updated versions will be added soon1.3deletedtdieslertestsuite/src/resources/webservice/ws4eesimple/META-INF/ejb-jar.xmlremove the ws4ee related tests, updated versions will be added soon1.3deletedtdieslertestsuite/src/resources/webservice/ws4eesimple/META-INF/webservices.xmlremove the ws4ee related tests, updated versions will be added soon1.2deletedtdieslertestsuite/src/resources/webservice/ws4eesimple/WEB-INF/web-secure.xmlremove the ws4ee related tests, updated versions will be added soon1.3deletedtdieslertestsuite/src/resources/webservice/ws4eesimple/WEB-INF/web.xmlremove the ws4ee related tests, updated versions will be added soon1.2deletedtdieslertestsuite/src/resources/webservice/ws4eesimple/WEB-INF/webservices.xmlremove the ws4ee related tests, updated versions will be added soon1.3deletedtdieslertestsuite/src/resources/webservice/ws4eesimple-client/WEB-INF/web.xmlremove the ws4ee related tests, updated versions will be added soon1.7deletedtdieslertestsuite/src/resources/webservice/ws4eecomplex/META-INF/Complex1.wsdlremove the ws4ee related tests, updated versions will be added soon1.7deletedtdieslertestsuite/src/resources/webservice/ws4eecomplex/META-INF/Complex1Mapping.xmlremove the ws4ee related tests, updated versions will be added soon1.4deletedtdieslertestsuite/src/resources/webservice/ws4eecomplex/META-INF/ejb-jar.xmlremove the ws4ee related tests, updated versions will be added soon1.3deletedtdieslertestsuite/src/resources/webservice/ws4eecomplex/META-INF/server-ejb-application.xmlremove the ws4ee related tests, updated versions will be added soon1.5deletedtdieslertestsuite/src/resources/webservice/ws4eecomplex/META-INF/server-web-application.xmlremove the ws4ee related tests, updated versions will be added soon1.5deletedtdieslertestsuite/src/resources/webservice/ws4eecomplex/META-INF/webservices.xmlremove the ws4ee related tests, updated versions will be added soon1.6deletedtdieslertestsuite/src/resources/webservice/ws4eecomplex/WEB-INF/web.xmlremove the ws4ee related tests, updated versions will be added soon1.2deletedtdieslertestsuite/src/resources/webservice/ws4eehandler/META-INF/Handler.wsdlremove the ws4ee related tests, updated versions will be added soon1.2deletedtdieslertestsuite/src/resources/webservice/ws4eehandler/META-INF/HandlerMapping.xmlremove the ws4ee related tests, updated versions will be added soon1.2deletedtdieslertestsuite/src/resources/webservice/ws4eehandler/META-INF/ejb-jar.xmlremove the ws4ee related tests, updated versions will be added soon1.3deletedtdieslertestsuite/src/resources/webservice/ws4eehandler/META-INF/webservices.xmlremove the ws4ee related tests, updated versions will be added soon1.2deletedtdieslertestsuite/src/resources/webservice/ws4eesimple-client/META-INF/HelloClient.wsdlremove the ws4ee related tests, updated versions will be added soon1.2deletedtdieslertestsuite/src/resources/webservice/ws4eesimple-client/META-INF/HelloMapping.xmlremove the ws4ee related tests, updated versions will be added soon1.2deletedtdieslertestsuite/src/resources/webservice/ws4eesimple-client/META-INF/application-client.xmlremove the ws4ee related tests, updated versions will be added soon1.2deletedtdieslertestsuite/src/resources/webservice/ws4eesimple-client/META-INF/application.xmlremove the ws4ee related tests, updated versions will be added soon1.5deletedtdieslertestsuite/src/resources/webservice/ws4eesimple-client/META-INF/ejb-jar.xmlremove the ws4ee related tests, updated versions will be added soon1.2deletedtdieslertestsuite/src/resources/webservice/ws4eesimple-client/META-INF/webservicesclient.xmlremove the ws4ee related tests, upd
[JBoss-dev] jboss-head Build Failed
View results here -> http://tck2.jboss.com/cc/buildresults/jboss-head?log=log20040506083359 BUILD FAILEDAnt Error Message: file:/home/build/cruisecontrol/work/scripts/build-jboss-head.xml:80: exec returned: -122Date of build: 05/06/2004 08:33:59Time to build: 13 minutes 13 secondsLast changed: 05/06/2004 08:26:25Last log entry: remove the ws4ee related tests, updated versions will be added soon Unit Tests: (0)No Tests RunThis project doesn't have any tests Modifications since last build: (99)1.3deletedtdieslertestsuite/src/resources/webservice/ws4eesimple/META-INF/Hello.wsdlremove the ws4ee related tests, updated versions will be added soon1.2deletedtdieslertestsuite/src/resources/webservice/ws4eesimple/META-INF/HelloMapping.xmlremove the ws4ee related tests, updated versions will be added soon1.2deletedtdieslertestsuite/src/resources/webservice/ws4eesimple/META-INF/application-ejb.xmlremove the ws4ee related tests, updated versions will be added soon1.2deletedtdieslertestsuite/src/resources/webservice/ws4eesimple/META-INF/application-web.xmlremove the ws4ee related tests, updated versions will be added soon1.3deletedtdieslertestsuite/src/resources/webservice/ws4eesimple/META-INF/ejb-jar.xmlremove the ws4ee related tests, updated versions will be added soon1.3deletedtdieslertestsuite/src/resources/webservice/ws4eesimple/META-INF/webservices.xmlremove the ws4ee related tests, updated versions will be added soon1.2deletedtdieslertestsuite/src/resources/webservice/ws4eesimple/WEB-INF/web-secure.xmlremove the ws4ee related tests, updated versions will be added soon1.3deletedtdieslertestsuite/src/resources/webservice/ws4eesimple/WEB-INF/web.xmlremove the ws4ee related tests, updated versions will be added soon1.2deletedtdieslertestsuite/src/resources/webservice/ws4eesimple/WEB-INF/webservices.xmlremove the ws4ee related tests, updated versions will be added soon1.3deletedtdieslertestsuite/src/resources/webservice/ws4eesimple-client/WEB-INF/web.xmlremove the ws4ee related tests, updated versions will be added soon1.7deletedtdieslertestsuite/src/resources/webservice/ws4eecomplex/META-INF/Complex1.wsdlremove the ws4ee related tests, updated versions will be added soon1.7deletedtdieslertestsuite/src/resources/webservice/ws4eecomplex/META-INF/Complex1Mapping.xmlremove the ws4ee related tests, updated versions will be added soon1.4deletedtdieslertestsuite/src/resources/webservice/ws4eecomplex/META-INF/ejb-jar.xmlremove the ws4ee related tests, updated versions will be added soon1.3deletedtdieslertestsuite/src/resources/webservice/ws4eecomplex/META-INF/server-ejb-application.xmlremove the ws4ee related tests, updated versions will be added soon1.5deletedtdieslertestsuite/src/resources/webservice/ws4eecomplex/META-INF/server-web-application.xmlremove the ws4ee related tests, updated versions will be added soon1.5deletedtdieslertestsuite/src/resources/webservice/ws4eecomplex/META-INF/webservices.xmlremove the ws4ee related tests, updated versions will be added soon1.6deletedtdieslertestsuite/src/resources/webservice/ws4eecomplex/WEB-INF/web.xmlremove the ws4ee related tests, updated versions will be added soon1.2deletedtdieslertestsuite/src/resources/webservice/ws4eehandler/META-INF/Handler.wsdlremove the ws4ee related tests, updated versions will be added soon1.2deletedtdieslertestsuite/src/resources/webservice/ws4eehandler/META-INF/HandlerMapping.xmlremove the ws4ee related tests, updated versions will be added soon1.2deletedtdieslertestsuite/src/resources/webservice/ws4eehandler/META-INF/ejb-jar.xmlremove the ws4ee related tests, updated versions will be added soon1.3deletedtdieslertestsuite/src/resources/webservice/ws4eehandler/META-INF/webservices.xmlremove the ws4ee related tests, updated versions will be added soon1.2deletedtdieslertestsuite/src/resources/webservice/ws4eesimple-client/META-INF/HelloClient.wsdlremove the ws4ee related tests, updated versions will be added soon1.2deletedtdieslertestsuite/src/resources/webservice/ws4eesimple-client/META-INF/HelloMapping.xmlremove the ws4ee related tests, updated versions will be added soon1.2deletedtdieslertestsuite/src/resources/webservice/ws4eesimple-client/META-INF/application-client.xmlremove the ws4ee related tests, updated versions will be added soon1.2deletedtdieslertestsuite/src/resources/webservice/ws4eesimple-client/META-INF/application.xmlremove the ws4ee related tests, updated versions will be added soon1.5deletedtdieslertestsuite/src/resources/webservice/ws4eesimple-client/META-INF/ejb-jar.xmlremove the ws4ee related tests, updated versions will be added soon1.2deletedtdieslertestsuite/src/resources/webservice/ws4eesimple-client/META-INF/webservicesclient.xmlremove the ws4ee related tests, updated versions will be added soon1.2deletedtdieslertestsuite/sr
[JBoss-dev] [JBoss IDE] - Re: Error At Start
Hi, I don't think the problem is coming from JBoss-IDE. I think the problem is that the Web application you are trying to deploy into JBoss is incomplete. You have forget to include some classes in your war and that's why the deployment failed. Laurent. View the original post : http://www.jboss.org/index.html?module=bb&op=viewtopic&p=3833906#3833906 Reply to the post : http://www.jboss.org/index.html?module=bb&op=posting&mode=reply&p=3833906 --- This SF.Net email is sponsored by Sleepycat Software Learn developer strategies Cisco, Motorola, Ericsson & Lucent use to deliver higher performing products faster, at low TCO. http://www.sleepycat.com/telcomwpreg.php?From=osdnemail3 ___ JBoss-Development mailing list [EMAIL PROTECTED] https://lists.sourceforge.net/lists/listinfo/jboss-development
[JBoss-dev] [JBoss IDE] - Re: Error At Start
Yes, I could tell from the error that I didn't have all the archives needed but the problem is that I loaded the jboss ide into eclipse through the Internet directly through the wizard and selected features to install as opposed to dowloading the plugin separately and then extracting it into the plugin directory. So, that is why I am confused on how to fix the problem. I don't think I can go through the wizard again to fix things. I am not sure how to unistall a plugin/featrue installed the way I did it. If I did I would start over or something. I thought if I posted the error that someone may be able to say go to the software update and do XYZ because this happen to me as well and I fixed it sort of thing. Also, can I install jboss ide by extracting it into the plugins dir and not just through the install wizard? If so where is the download page? Any suggestions? Thanks! Shane View the original post : http://www.jboss.org/index.html?module=bb&op=viewtopic&p=3833903#3833903 Reply to the post : http://www.jboss.org/index.html?module=bb&op=posting&mode=reply&p=3833903 --- This SF.Net email is sponsored by Sleepycat Software Learn developer strategies Cisco, Motorola, Ericsson & Lucent use to deliver higher performing products faster, at low TCO. http://www.sleepycat.com/telcomwpreg.php?From=osdnemail3 ___ JBoss-Development mailing list [EMAIL PROTECTED] https://lists.sourceforge.net/lists/listinfo/jboss-development
[JBoss-dev] [XDoclet on JBoss (XDoclet/JBoss)] - Re: auto-increment primarykey problem
Can you please post the generated jbosscmp-jdbc.xml? View the original post : http://www.jboss.org/index.html?module=bb&op=viewtopic&p=3833889#3833889 Reply to the post : http://www.jboss.org/index.html?module=bb&op=posting&mode=reply&p=3833889 --- This SF.Net email is sponsored by Sleepycat Software Learn developer strategies Cisco, Motorola, Ericsson & Lucent use to deliver higher performing products faster, at low TCO. http://www.sleepycat.com/telcomwpreg.php?From=osdnemail3 ___ JBoss-Development mailing list [EMAIL PROTECTED] https://lists.sourceforge.net/lists/listinfo/jboss-development
