[JBoss-dev] [ jboss-Bugs-706213 ] EARDeployer deploying EJBs not listed in application.xml

Bugs item #706213, was opened at 2003-03-19 11:10 You can respond by visiting: https://sourceforge.net/tracker/?func=detailatid=376685aid=706213group_id=22866 Category: JBossServer Group: v3.2 Status: Open Resolution: None Priority: 5 Submitted By: Andrew May (amayingenta) Assigned to:

[JBoss-dev] [PROPOSAL]: clean conf/jboss-service.xml deploy

Hello, Currently, the content of conf/jboss-service.xml and deploy is not very clean. 1°) Some services defined in conf/jboss-service.xml require services later deployed in deploy Exemples: - the EJBDeployer depends on the JMS Pool - some invokers (3.2+) require jboss-jca.jar

Re: [JBoss-dev] [PROPOSAL]: clean conf/jboss-service.xml deploy

Hi Sacha! I think this sounds very good, because it is as you said a bit confusing with all these files in deploy and conf. To group them together in JMS/JMX/... subdiroctories i think would be a good solution and also having them apart from users application deployments - like deploy/system

RE: [JBoss-dev] [PROPOSAL]: clean conf/jboss-service.xml deploy

Sacha, The thing I care about most is ease of configurability (which, for the most part, I think we already have). I like the idea that I can add or remove functionality by adding or removing modules from /deploy. Much of the functionality of the server works this way (jmx-console, for

RE: [JBoss-dev] [PROPOSAL]: clean conf/jboss-service.xml deploy

The thing I care about most is ease of configurability (which, for the most part, I think we already have). I like the idea that I can add or remove functionality by adding or removing modules from /deploy. Much of the functionality of the server works this way (jmx-console, for

RE: [JBoss-dev] jboss_3_0.dtd vs jboss_3_2.dtd

-Original Message- From: Scott M Stark [mailto:[EMAIL PROTECTED] Subject: Re: [JBoss-dev] jboss_3_0.dtd vs jboss_3_2.dtd ... the enterprise-beans element model would have to be: !ELEMENT enterprise-beans (session | entity | message-driven)* content model for backward compability

Re: [JBoss-dev] jboss_3_0.dtd vs jboss_3_2.dtd

Fine. Scott Stark Chief Technology Officer JBoss Group, LLC - Original Message - From: [EMAIL PROTECTED] To: [EMAIL PROTECTED] Sent: Wednesday, March 19, 2003 6:29 AM Subject: RE: [JBoss-dev] jboss_3_0.dtd vs jboss_3_2.dtd How

[JBoss-dev] [ jboss-Bugs-706494 ] InitialContext missing jndi.properties entries

Bugs item #706494, was opened at 2003-03-19 12:07 You can respond by visiting: https://sourceforge.net/tracker/?func=detailatid=376685aid=706494group_id=22866 Category: None Group: v3.0 Rabbit Hole Status: Open Resolution: None Priority: 5 Submitted By: Dan Ciarniello (dciarnie) Assigned to:

[JBoss-dev] Automated JBoss(Branch_3_2 WonderLand) Testsuite Results: 19-March-2003

JBoss daily test results SUMMARY Number of tests run: 1145 Successful tests: 1135 Errors:10 Failures: 0 [time of test: 2003-03-19.18-30 GMT] [java.version:

[JBoss-dev] Automated JBoss(Branch_3_0) Testsuite Results: 19-March-2003

JBoss daily test results SUMMARY Number of tests run: 1096 Successful tests: 1092 Errors:1 Failures: 3 [time of test: 2003-03-19.12-04 GMT] [java.version:

[JBoss-dev] [ jboss-Bugs-625277 ] Servlet classloader static classes

Bugs item #625277, was opened at 2002-10-18 08:17 You can respond by visiting: https://sourceforge.net/tracker/?func=detailatid=376685aid=625277group_id=22866 Category: None Group: v3.0 Rabbit Hole Status: Closed Resolution: Wont Fix Priority: 5 Submitted By: Dani G. (danig) Assigned to: Scott M

[JBoss-dev] [ jboss-Bugs-706494 ] InitialContext missing jndi.properties entries

Bugs item #706494, was opened at 2003-03-19 12:07 You can respond by visiting: https://sourceforge.net/tracker/?func=detailatid=376685aid=706494group_id=22866 Category: JBossServer Group: v3.0 Rabbit Hole Status: Closed Resolution: Invalid Priority: 5 Submitted By: Dan Ciarniello (dciarnie)

[JBoss-dev] [ jboss-Bugs-706494 ] InitialContext missing jndi.properties entries

Bugs item #706494, was opened at 2003-03-19 12:07 You can respond by visiting: https://sourceforge.net/tracker/?func=detailatid=376685aid=706494group_id=22866 Category: JBossServer Group: v3.0 Rabbit Hole Status: Closed Resolution: Invalid Priority: 5 Submitted By: Dan Ciarniello (dciarnie)

[JBoss-dev] [ jboss-Bugs-701553 ] Incorrect behaviour from Session.recover()

Bugs item #701553, was opened at 2003-03-11 14:04 You can respond by visiting: https://sourceforge.net/tracker/?func=detailatid=376685aid=701553group_id=22866 Category: JBossMQ Group: v3.2 Status: Closed Resolution: Fixed Priority: 5 Submitted By: Frédéric Donckels (lubdub) Assigned to: Adrian

[JBoss-dev] [ jboss-Bugs-672551 ] javax.jms.InvalidDestinationException not being thrown.

Bugs item #672551, was opened at 2003-01-22 16:47 You can respond by visiting: https://sourceforge.net/tracker/?func=detailatid=376685aid=672551group_id=22866 Category: JBossMQ Group: v3.0 Rabbit Hole Status: Closed Resolution: Fixed Priority: 5 Submitted By: E.Sriram (esriram) Assigned to:

[JBoss-dev] [ jboss-Bugs-639064 ] MDB Bean Stops Delivering messages

Bugs item #639064, was opened at 2002-11-15 19:47 You can respond by visiting: https://sourceforge.net/tracker/?func=detailatid=376685aid=639064group_id=22866 Category: JBossMQ Group: v3.0 Rabbit Hole Status: Open Resolution: None Priority: 5 Submitted By: Yossarian Nosscire (yosarian1) Assigned

[JBoss-dev] [ jboss-Bugs-633868 ] Expired message blocks queue

Bugs item #633868, was opened at 2002-11-05 15:56 You can respond by visiting: https://sourceforge.net/tracker/?func=detailatid=376685aid=633868group_id=22866 Category: JBossMQ Group: v3.0 Rabbit Hole Status: Closed Resolution: None Priority: 5 Submitted By: Kevin Wood (kwood) Assigned to:

[JBoss-dev] [ jboss-Bugs-639064 ] MDB Bean Stops Delivering messages

Bugs item #639064, was opened at 2002-11-15 19:47 You can respond by visiting: https://sourceforge.net/tracker/?func=detailatid=376685aid=639064group_id=22866 Category: JBossMQ Group: v3.0 Rabbit Hole Status: Open Resolution: None Priority: 5 Submitted By: Yossarian Nosscire (yosarian1) Assigned

[JBoss-dev] [ jboss-Bugs-706494 ] InitialContext missing jndi.properties entries

Bugs item #706494, was opened at 2003-03-19 12:07 You can respond by visiting: https://sourceforge.net/tracker/?func=detailatid=376685aid=706494group_id=22866 Category: JBossServer Group: v3.0 Rabbit Hole Status: Closed Resolution: Works For Me Priority: 5 Submitted By: Dan Ciarniello (dciarnie)

[JBoss-dev] JBoss 3.2 CORBA deployment

Anybody got this to work? I am at the point where all beans get successfully deployed, and show up in the iiop context. However, I get ClassCastExceptions as soon as I try to PRO.narrow() the reference. It looks like the stub class loading is not or can not be done on the client side. The

[JBoss-dev] JDK 1.3.1_07 and -classic bug

I updated my JDK to 1.3.1_07 and ran across a strange bug with -classic. JBoss won't even startup when -classic is enabled because the File.getCanonicalPath method is returning the wrong value: -- BEGIN SOURCE -- import java.io.File; class tstPath2 { public static void

RE: [JBoss-dev] [PROPOSAL]: clean conf/jboss-service.xml deploy

Rather than a specialized SubDirSubDeployer, how about having the SAR report multiple watch-urls? It may also be possible to have the SAR start its own URLDeploymentScanner for its content rather than explicitly sub-deploy it. This would support automatic redeployment of unpacked sar content over

[JBoss-dev] [ jboss-Bugs-699938 ] Unnecessary UPDATE calls for CMR fields

Bugs item #699938, was opened at 2003-03-08 12:44 You can respond by visiting: https://sourceforge.net/tracker/?func=detailatid=376685aid=699938group_id=22866 Category: JBossCMP Group: v3.2 Status: Open Resolution: None Priority: 5 Submitted By: Christopher G. Stach II (cstach) Assigned to: