August 2006 - jboss-jira - Jboss List Archives

[JBoss JIRA] Commented: (JBIDE-331) Support for ejb3.0 archives, xml, generic jar, and .sar archives

by Robert Stryker (JIRA)

[ http://jira.jboss.com/jira/browse/JBIDE-331?page=comments#action_12341271 ] Robert Stryker commented on JBIDE-331: -------------------------------------- Refactored to allow all jar files. XML's not yet accepted. > Support for ejb3.0 archives, xml, generic jar, and .sar archives > ---------------------------------------------------------------- > > Key: JBIDE-331 > URL: http://jira.jboss.com/jira/browse/JBIDE-331 > Project: JBoss IDE > Issue Type: Feature Request > Components: JBossAS Adapter > Affects Versions: 2.0.0.Alpha > Reporter: Robert Stryker > Assigned To: Robert Stryker > Fix For: 2.0.0.Beta2 > > Original Estimate: 2 days > Remaining Estimate: 2 days > > Ensure that factories for all archive types ( ejb3.0 archives, xml, generic jar, and .sar archives) exist and create publishable modules. -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: http://jira.jboss.com/jira/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira

19 years, 11 months

1
0
0 / 0

[JBoss JIRA] Created: (JBIDE-340) secondary IPs failing to be recognized as localhost

by Robert Stryker (JIRA)

secondary IPs failing to be recognized as localhost ---------------------------------------------------- Key: JBIDE-340 URL: http://jira.jboss.com/jira/browse/JBIDE-340 Project: JBoss IDE Issue Type: Bug Components: JBossAS Adapter Affects Versions: 2.0.0.Alpha, 1.6 Reporter: Robert Stryker Assigned To: Robert Stryker User trying to create a jboss server with a localhost IP is having it fail on their second IP address (eth 0:0) This bug is dependent on: https://bugs.eclipse.org/bugs/show_bug.cgi?id=150531 Reported by user at: http://www.jboss.com/index.html?module=bb&op=viewtopic&p=3957679#3957679 -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: http://jira.jboss.com/jira/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira

19 years, 11 months

1
2
0 / 0

[JBoss JIRA] Resolved: (JBIDE-301) JBossAS Adapter configuration page

by Robert Stryker (JIRA)

[ http://jira.jboss.com/jira/browse/JBIDE-301?page=all ] Robert Stryker resolved JBIDE-301. ---------------------------------- Fix Version/s: 2.0.0.Beta1 (was: 2.0.0.GA) Resolution: Done Port editing implemented in descriptor section of the view (and in properties view). Allows for modification of any xpath as well. Changing of jboss install directory deemed not allowed. Answer: Create a new server. > JBossAS Adapter configuration page > ---------------------------------- > > Key: JBIDE-301 > URL: http://jira.jboss.com/jira/browse/JBIDE-301 > Project: JBoss IDE > Issue Type: Feature Request > Components: JBossAS Adapter > Reporter: Marshall Culpepper > Assigned To: Robert Stryker > Fix For: 2.0.0.Beta1 > > Original Estimate: 2 weeks > Remaining Estimate: 2 weeks > > The configuration page should be form based and include the following: > - commonly used port numbers (JNDI, HTTP, etc) > - currently published apps (maybe with a mapping of app->web context ?) > - jboss installation directory -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: http://jira.jboss.com/jira/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira

19 years, 11 months

1
0
0 / 0

[JBoss JIRA] Resolved: (JBIDE-329) RunOnServer/DebugOnServer Dialog doesn't come up anymore after removing module from server. (Nightly Build)

by Robert Stryker (JIRA)

[ http://jira.jboss.com/jira/browse/JBIDE-329?page=all ] Robert Stryker resolved JBIDE-329. ---------------------------------- Fix Version/s: 2.0.0.GA Resolution: Done Bug fixed in eclipse. Not entirely sure when it'll be integrated with us. > RunOnServer/DebugOnServer Dialog doesn't come up anymore after removing module from server. (Nightly Build) > ----------------------------------------------------------------------------------------------------------- > > Key: JBIDE-329 > URL: http://jira.jboss.com/jira/browse/JBIDE-329 > Project: JBoss IDE > Issue Type: Bug > Components: JBossAS Adapter > Environment: Debian Linux, Kernel 2.6.16, jdk 1.5.0_6-b05, eclipse-SDK-3.2RC7-linux-gtk > Reporter: Florian Beckmann > Assigned To: Robert Stryker > Fix For: 2.0.0.GA > > > That happens to any module for which you click on the "Set server as project default (do not ask again)"-checkbox in the "Run On Server" dialog. First the module can be deployed , but after removing it (selecting "Remove" in Server view), and selecting "RunAs->RunOnServer" again, nothing happens (no Dialog appears). > That happens with all files which are listed in the > .metadata/.plugins/org.eclipse.wst.server.core/modules.xml file and are then removed from server. If you remove the entry for the module the Dialog appaers again. > No Exception in the error log. -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: http://jira.jboss.com/jira/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira

19 years, 11 months

1
0
0 / 0

[JBoss JIRA] Assigned: (JBCACHE-8) Handling of (state) merging --> emission of callbacks/notifications

by Bela Ban (JIRA)

[ http://jira.jboss.com/jira/browse/JBCACHE-8?page=all ] Bela Ban reassigned JBCACHE-8: ------------------------------ Assignee: Manik Surtani (was: Brian Stansberry) > Handling of (state) merging --> emission of callbacks/notifications > ------------------------------------------------------------------- > > Key: JBCACHE-8 > URL: http://jira.jboss.com/jira/browse/JBCACHE-8 > Project: JBoss Cache > Issue Type: Feature Request > Affects Versions: 1.2.4SP1, 1.2.4, 1.2.4beta, 1.2.3, 1.2.2, 1.2.1, 1.2, 1.3.0.SP2, 1.3.0.SP1, 1.3.0 > Reporter: Bela Ban > Assigned To: Manik Surtani > Fix For: 2.1.0 > > Original Estimate: 1 week > Remaining Estimate: 1 week > > We need to look into handling the merge for JBossCache. Merging occurs after a network partition, or as result of 2 members starting concurrently, or as a result of a PING.timeout set too low -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: http://jira.jboss.com/jira/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira

19 years, 11 months

1
0
0 / 0

[JBoss JIRA] Assigned: (JBCLUSTER-78) Handling of merge (currently only done in DistributedReplicantManager)

by Bela Ban (JIRA)

[ http://jira.jboss.com/jira/browse/JBCLUSTER-78?page=all ] Bela Ban reassigned JBCLUSTER-78: --------------------------------- Assignee: Brian Stansberry (was: Ben Wang) > Handling of merge (currently only done in DistributedReplicantManager) > ---------------------------------------------------------------------- > > Key: JBCLUSTER-78 > URL: http://jira.jboss.com/jira/browse/JBCLUSTER-78 > Project: JBoss Clustering > Issue Type: Feature Request > Security Level: Public(Everyone can see) > Reporter: Bela Ban > Assigned To: Brian Stansberry > > All building blocks which involve state do *not* implement handling of merging. E.g. DRM.mergeMembers() should invoke a callback so that each subscribed listener can handle the merge. > This needs to be done for the existing building blocks for backward compatibility, the new mechanism used is JBossCache (see link) which will handle state merging -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: http://jira.jboss.com/jira/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira

19 years, 11 months

1
0
0 / 0

[JBoss JIRA] Created: (EJBTHREE-688) Deployment Descriptor for Message Driven POJOs requires all elements.

by fred chen (JIRA)

Deployment Descriptor for Message Driven POJOs requires all elements. --------------------------------------------------------------------- Key: EJBTHREE-688 URL: http://jira.jboss.com/jira/browse/EJBTHREE-688 Project: EJB 3.0 Issue Type: Bug Components: EJB3 Extensions Affects Versions: EJB 3.0 RC8 - FD Environment: Windows XP Professional, JDK 1.5.0_07 EJB 3.0 RC8 Reporter: fred chen Priority: Minor The deployment descriptor used for deploying an Message Driven POJO currently requires all elements to be configured. Specifically, when creating a deployment descriptor for a Message Driven POJO, a producer, local-producer, current message, message-properties element must all be specified. Current message,message-properties should be optional configurations. Furthermore it should be possible to specify either a producer or local-producer individually (currently, both are required). -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: http://jira.jboss.com/jira/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira

19 years, 11 months

1
0
0 / 0

[JBoss JIRA] Created: (JBSER-87) dataOutput.close being called twice on JBossObjectOutputStream

by Clebert Suconic (JIRA)

dataOutput.close being called twice on JBossObjectOutputStream -------------------------------------------------------------- Key: JBSER-87 URL: http://jira.jboss.com/jira/browse/JBSER-87 Project: JBoss Serialization Issue Type: Bug Reporter: Clebert Suconic Assigned To: Clebert Suconic I don't know why we didn't find this bug before... But.... JbossObjectOutputStream.close is this following: public void close() throws IOException { flush(); dataOutput.close(); dataOutput.close(); } -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: http://jira.jboss.com/jira/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira

19 years, 11 months

2
6
0 / 0

[JBoss JIRA] Created: (JBMICROCONT-102) Still a problem with recursive installs

by Adrian Brock (JIRA)

Still a problem with recursive installs --------------------------------------- Key: JBMICROCONT-102 URL: http://jira.jboss.com/jira/browse/JBMICROCONT-102 Project: JBoss MicroContainer Issue Type: Sub-task Components: Dependency Reporter: Adrian Brock Fix For: JBossMC_2_0_0M1 Further to the parent problem. There is still a problem with recursive installs where a component (not party to recursion) will be attempted to be installed twice. The fix for the parent was incomplete. We also need to check that a context is still in the state we expect before incrementing the state. This is because the recursive invocation may have already done the increment for us. Here's an example failure: java.lang.IndexOutOfBoundsException: Index: 7, Size: 7 at EDU.oswego.cs.dl.util.concurrent.CopyOnWriteArrayList.rangeCheck(CopyOnWriteArrayList.java:752) at EDU.oswego.cs.dl.util.concurrent.CopyOnWriteArrayList.get(CopyOnWriteArrayList.java:372) at org.jboss.dependency.plugins.AbstractController.incrementState(AbstractController.java:422) at org.jboss.dependency.plugins.AbstractController.resolveContexts(AbstractController.java:533) at org.jboss.dependency.plugins.AbstractController.resolveContexts(AbstractController.java:472) at org.jboss.dependency.plugins.AbstractController.install(AbstractController.java:274) at org.jboss.dependency.plugins.AbstractController.install(AbstractController.java:177) at org.jboss.test.dependency.controller.test.AbstractDependencyTest.assertInstall(AbstractDependencyTest.java:85) at org.jboss.test.dependency.controller.test.RecursiveControllerActionTestCase.testInstall(RecursiveControllerActionTestCase.java:62) at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method) at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:39) at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25) at java.lang.reflect.Method.invoke(Method.java:585) at junit.framework.TestCase.runTest(TestCase.java:154) at junit.framework.TestCase.runBare(TestCase.java:127) at junit.framework.TestResult$1.protect(TestResult.java:106) at junit.framework.TestResult.runProtected(TestResult.java:124) at junit.framework.TestResult.run(TestResult.java:109) at junit.framework.TestCase.run(TestCase.java:118) at junit.framework.TestSuite.runTest(TestSuite.java:208) at junit.framework.TestSuite.run(TestSuite.java:203) at junit.extensions.TestDecorator.basicRun(TestDecorator.java:22) at junit.extensions.TestSetup$1.protect(TestSetup.java:19) at junit.framework.TestResult.runProtected(TestResult.java:124) at junit.extensions.TestSetup.run(TestSetup.java:23) at org.eclipse.jdt.internal.junit.runner.junit3.JUnit3TestReference.run(JUnit3TestReference.java:128) at org.eclipse.jdt.internal.junit.runner.TestExecution.run(TestExecution.java:38) at org.eclipse.jdt.internal.junit.runner.RemoteTestRunner.runTests(RemoteTestRunner.java:460) at org.eclipse.jdt.internal.junit.runner.RemoteTestRunner.runTests(RemoteTestRunner.java:673) at org.eclipse.jdt.internal.junit.runner.RemoteTestRunner.run(RemoteTestRunner.java:386) at org.eclipse.jdt.internal.junit.runner.RemoteTestRunner.main(RemoteTestRunner.java:196) -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: http://jira.jboss.com/jira/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira

19 years, 11 months

1
1
0 / 0

[JBoss JIRA] Commented: (JBAS-2904) Allow for ear modules to be deployed in the order that they are declared in application.xml

by Kabir Khan (JIRA)

[ http://jira.jboss.com/jira/browse/JBAS-2904?page=comments#action_12341250 ] Kabir Khan commented on JBAS-2904: ---------------------------------- This also caused JBAS-3489, which I have fixed > Allow for ear modules to be deployed in the order that they are declared in application.xml > ------------------------------------------------------------------------------------------- > > Key: JBAS-2904 > URL: http://jira.jboss.com/jira/browse/JBAS-2904 > Project: JBoss Application Server > Issue Type: Feature Request > Security Level: Public(Everyone can see) > Components: Deployment services > Affects Versions: JBossAS-4.0.3 SP1, JBossAS-3.2.8.SP1 > Reporter: Jim Moran > Assigned To: Vicky Kak > Fix For: JBossAS-5.0.0.Beta, JBossAS-4.0.5.CR1 > > -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: http://jira.jboss.com/jira/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira

19 years, 11 months

1
0
0 / 0

2026

2025

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

2009

2008

2007

2006

jboss-jira August 2006