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

[Design of EJB 3.0] - Re: What Versions of AS5 Will EJB3 Plugin Support?

by adrian＠jboss.org

Why waste time on Beta4? Its gone. Once the GA is out nobody will use Beta4. Just don't forget that potentially RC1 == GA View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=4134985#4134985 Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=4134985

18 years, 1 month

1
0
0 / 0

[Design of POJO Server] - Re: JBAS-5259, JMS Destination Names is showing as QueueServ

by scott.stark＠jboss.org

Ok, I see. Yes, we don't deploy a bunch of default destinations in jboss5. All jms tests deploy what they need at the start. The JmsDestinationUnitTestCase creates destinations so its not depending on existing destinations. There are two queues in the deploy/messaging/destinations-service.xml deployment, DLQ, ExpiryQueue. I'll update the JmsDestinationUnitTestCase to query those. View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=4134984#4134984 Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=4134984

18 years, 1 month

1
0
0 / 0

[Design of POJO Server] - Re: JBAS-5259, JMS Destination Names is showing as QueueServ

by mark.spritzler

After stepping through both the console and the ManagementViewImpl class, I still am not getting the Topics/Queues. In the ManagementViewImpl class the compByCompType Map only had two keys in it, one LocalTX Datasource type and one for the JMS XA Connection Factory. There was no entries for JMSDestinations-Topics or Queues. So it got me thinking, in looking at the ManagedDeployment object that holds "vfsfile:/C:/JBossServers/jboss-5.0.0.CR1/server/default/deploy/messaging/" I found the destinations-service.xml Deployment, and it did not have any children. I am thinking this is the key. All the Topics and Queues that I am expecting to see are all defined in the destinations-service.xml file. I am thinking in the Hudson testsuite the JMS Unit Test, which adds a Topic/Queue through the profile service, is running before the ProfileService Unit Test, and that is why the test in the ProfileService Unit Test is passing the size() > 0 What do you think? Thanks Mark View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=4134983#4134983 Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=4134983

18 years, 1 month

1
0
0 / 0

[Design of EJB 3.0] - Re: What Versions of AS5 Will EJB3 Plugin Support?

by anil.saldhana＠jboss.com

Why not have a plugin that works all the way from Beta4 to GA? Seriously, all this discussion about ejb3 plugin/installation is making me giddy. Ok, hit me now with your justification. :) View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=4134981#4134981 Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=4134981

18 years, 1 month

1
0
0 / 0

[Design of EJB 3.0] - Re: What Versions of AS5 Will EJB3 Plugin Support?

by ALRubinger

I should mention that even though the EJB3 Codebase itself acts as a cumulative patch, because AS5 is a moving target there will have to be a separate Plugin Installer targeted at each AS5 Version we want to support. ie: * EJB3 Plugin RC13 AS5Beta4 * EJB3 Plugin RC13 AS5CR1 * EJB3 Plugin RC14 AS5Beta4 * EJB3 Plugin RC14 AS5CR1 * EJB3 Plugin RC14 AS5GA ...etc. Not a pretty solution (exponential releases over time == (EJB3 Version * Supported AS5 Versions)). S, ALR View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=4134979#4134979 Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=4134979

18 years, 1 month

1
0
0 / 0

[Design of EJB 3.0] - What Versions of AS5 Will EJB3 Plugin Support?

by ALRubinger

The AS Integration move of the deployers will lead Beta4 with the EJB3 Plugin to now fail with the following errors listed below. Worth fixing, or we push forward and Plugin will only be supported on AS5 CR1 and up? EJBStage2Deployer -> java.lang.ClassNotFoundException: org.jboss.ejb3.deployers.EJBStage2Deployer | | JBossClientParsingDeployer -> java.lang.ClassNotFoundException: org.jboss.ejb3.deployers.JBossClientParsingDeployer | | Ejb3ClientDeployer -> java.lang.ClassNotFoundException: org.jboss.ejb3.deployers.Ejb3ClientDeployer | | PersistenceUnitParsingDeployer -> java.lang.ClassNotFoundException: org.jboss.ejb3.deployers.PersistenceUnitParsingDeployer | | AppClientScanningDeployer -> java.lang.ClassNotFoundException: org.jboss.ejb3.deployers.AppClientScanningDeployer | | AppClientParsingDeployer -> java.lang.ClassNotFoundException: org.jboss.ejb3.deployers.AppClientParsingDeployer | | Ejb3Deployer -> java.lang.ClassNotFoundException: org.jboss.ejb3.deployers.Ejb3Deployer S, View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=4134976#4134976 Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=4134976

18 years, 1 month

1
0
0 / 0

[Design of JMX on JBoss (JBoss/JMX)] - Re: JBAS-5220 - Twiddle not displaying Platform MBean.

by Tobias

Hi Vicky, I updated to the trunk version yesterday and can not confirm this. Testing on Linux here. But I am glad you found that error as well. I am not sure if that error should be fixed like this. Right now a domain either can be in the JBoss or the platform MBean server. Is that intended or just a side effect of the implementation. My guess would be, that "combining" the two MBean servers should really behave like there would be only one MBean server. Does the spec say anything about that? Is that covered at all? Ciao, Tobias View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=4134975#4134975 Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=4134975

18 years, 1 month

1
0
0 / 0

[Design of JBossXB] - JBossXB Tests

by adrian＠jboss.org

I'm going to comment out the failing tests in the annotated xsd pojo tests. Its unlikely I'll ever complete these tests, and its the tests that are wrong not JBossXB. :-) That just leaves one failing test, which is the repeated element problem | <xsd:complexType> | <xsd:sequence> | <xsd:element name="child" type="xsd:string"/> | <xsd:element name="child" type="xsd:string"/> | </xsd:sequence> | </xsd:complexType> | | <top xmlns='http://www.jboss.org/test/xml/repeatedElements'> | <child>one</child> | <child>two</child> | </top> | This came from the EJB2.0 schema but I hacked around the problem there by pretending it was | <xsd:sequence minOccurs="2" maxOccurs="2"> | <xsd:element name="child" type="xsd:string"/> | <xsd:sequence/> | View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=4134969#4134969 Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=4134969

18 years, 1 month

1
0
0 / 0

[Design of JBossXB] - Re: JBossXB dependencies

by adrian＠jboss.org

e.g. you could have this | <dependency> | <groupId>wutka-dtdparser</groupId> | <artifactId>dtdparser121</artifactId> | <version>1.2.1</version> | <scope>compile</scope> | | <optional>true</optional> | | </dependency> | View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=4134967#4134967 Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=4134967

18 years, 1 month

1
0
0 / 0

[Design of JBossXB] - JBossXB dependencies

by adrian＠jboss.org

I've upgraded to the latest version of common-core and excluded some of the stupid transitive dependencies it causes http://jira.jboss.com/jira/browse/JBXB-131 You might also want to consider whether some of the dependencies are optional (the user should choose seperately whether to include them in their project), e.g. is javax.xml.steam really required to run JBossXB or is it only if you choose seperately to use stax parsing/marshalling? Same question for the dtd parser? | [ejort@warjort jbossxb]$ mvn dependency:list -DincludeScope=compile | [INFO] Scanning for projects... | [INFO] Searching repository for plugin with prefix: 'dependency'. | WAGON_VERSION: 1.0-beta-2 | [INFO] ------------------------------------------------------------------------ | [INFO] Building JBoss XML Binding | [INFO] task-segment: [dependency:list] | [INFO] ------------------------------------------------------------------------ | [INFO] [dependency:list] | [INFO] | [INFO] The following files have been resolved: | [INFO] apache-xerces:xercesImpl:jar:2.9.1:compile | [INFO] javax.activation:activation:jar:1.0.2:compile | [INFO] javax.xml.bind:jaxb-api:jar:2.1:compile | [INFO] javax.xml.stream:stax-api:jar:1.0-2:compile | [INFO] jboss:jboss-common-logging-spi:jar:2.0.4.GA:compile | [INFO] org.jboss:jboss-common-core:jar:2.2.3.GA:compile | [INFO] org.jboss:jboss-reflect:jar:2.0.0.Beta11:compile | [INFO] wutka-dtdparser:dtdparser121:jar:1.2.1:compile | [INFO] | View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=4134966#4134966 Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=4134966

18 years, 1 month

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-dev-forums March 2008