August 2006 - jboss-dev-forums - Jboss List Archives

[Design of JBoss internal QA (Test Suite)] - Re: Testsuite failures for MalformedTestCase testMalformed t

by scott.stark＠jboss.org

It would be better categorized as a known failure that can be ignored. View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=3967128#3967128 Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=3967128

18 years, 1 month

1
0
0 / 0

[Design of JBoss Eclipse IDE (dev)] - Re: xdoclet eclipse The currently displayed page contains in

by billsommers

Hello, I'm getting the same error message with 1.6.0. Does anyone know if there are plans to fix this in 1.6? I'd hate to jump to an alpha release. View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=3967117#3967117 Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=3967117

18 years, 1 month

1
0
0 / 0

[Design of JBoss internal QA (Test Suite)] - Re: Testsuite failures for MalformedTestCase testMalformed t

by mwringe

Since this test is only meaningful is the JVM version is less than 1.5, shouldn't this test be disabled if a 1.5 jvm is present? View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=3967108#3967108 Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=3967108

18 years, 1 month

1
0
0 / 0

[Design of JBoss jBPM] - Web Console unit test adventures

by david.lloyd＠jboss.com

I've been working on getting the unit tests working for the web console, and I've run across a couple of snags. First, there is a bug in httpunit 1.6, still present in 1.6.2 (which is the newest version), which causes it to fail to parse valid XHTML properly. I've got a patch in with the maintainer and with any luck he'll put out a new version shortly. In the meantime, I've been using a patched 1.6.2 locally. Second, and perhaps more seriously, there's a bug in jwebunit 1.2 (also XHTML-related) that prevents the tests from passing. Basically it has to do with not being namespace-aware. It's a simple fix, so I thought I'd see if it was corrected in 1.3. Unfortunately, 1.3 is a fairly substantial rewrite involving a very large number of dependancies. Here's the full list: avalon-framework-4.1.3.jar - New to jBPM, but exists in the repository commons-codec-1.3.jar - New to jBPM, but exists in the repository commons-collections-3.2.jar - We're using 3.1, so we'd have to test this commons-httpclient-3.0.1.jar - We've got this one commons-io-1.2.jar - New to jBPM, not in repository commons-lang-2.1.jar - New to jBPM, but exists in the repository commons-logging-1.1.jar - We're using 1.0.4; it shouldn't hurt to upgrade but we'd still have to test htmlunit-1.9.jar - This is a new dependency; I'm not sure where it comes from or what the license is yet icu4j-2.6.1.jar - This is a new dependency; I'm not sure where it comes from or what the license is yet jaxen-1.1-beta-9.jar - We're using 1.1-beta-6 currently, repository does not have beta-9 yet jdom-1.0.jar - New dependency, not in repository js-1.6R2.jar - New dependency, not in repository; comes from Mozilla so license is probably OK (?) junit-3.8.2.jar - We're using 3.8.1, upgrade is probably fine log4j-1.2.12.jar - We're using 1.2.8, upgrade is probably fine logkit-1.0.1.jar - This is a new dependency; I'm not sure where it comes from or what the license is yet nekohtml-0.9.5.jar - Repository has 0.9.1, so we'd have to update that regexp-1.3.jar - This is Jakarta regexp. Exists in repository, new to jBPM servlet-api-2.4.jar - Got it already tagsoup-0.9.7.jar - This is a new dependency; I'm not sure where it comes from or what the license is yet xalan-2.6.0.jar - In repository xercesImpl-2.6.2.jar - We're using 2.7.1, but it should work fine; we're only using it for unit tests anyway xml-apis-1.0.b2.jar - I don't think this is needed xmlParserAPIs-2.6.2.jar - I don't think this is needed xom-1.0b3.jar - Not sure if this is needed, but if so, it's not in the repository Incidentally, applying the fix to 1.2 is pretty simple. The question becomes, do we want to continue to work from a modified old version, or should we go through the work of getting all these extra dependencies for the purpose of unit testing? View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=3967106#3967106 Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=3967106

18 years, 1 month

1
0
0 / 0

[Design of JBoss internal QA (Test Suite)] - Re: Testsuite failures for MalformedTestCase testMalformed t

by scott.stark＠jboss.org

-Could you please explain this issue a little bit more? A jmx object name string of "domain:=,foo=bar" violates the jmx spec ObjectName syntax of: [domainName]:property=value[,property=value]* and ObjectName javadoc which states that http://java.sun.com/j2se/1.5.0/docs/api/index.html anonymous wrote : | The key properties are an unordered set of keys and associated values. | | Each key is a nonempty string of characters which may not contain any of the characters comma (,), equals (=), colon, asterisk, or question mark. The same key may not occur twice in a given ObjectName. | | Each value associated with a key is a string of characters that is either unquoted or quoted. | | An unquoted value is a possibly empty string of characters which may not contain any of the characters comma, equals, colon, quote, asterisk, or question mark. | I have submitted a bug report to sun on this. -Why does JBoss have separate versions of Sun's classes? We have had our own implementation of JMX since it was an extension package to jdk1.3. -This test usually passes on the 1.4.2 JVM, is this test only meant to be run on a 1.4.2 JVM? This test is only meaningful for jdk < 5 to test our implementation. View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=3967087#3967087 Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=3967087

18 years, 1 month

1
0
0 / 0

[Design of POJO Server] - Re: Behavior with AbstractKernelController

by anil.saldhana＠jboss.com

I have updated the testcase to use the ServiceController to create/start/stop/destroy a service (and look into its ServiceContext to give me the state of the service at any time). The test in question is: | ant -Dtest=org.jboss.test.security.test.DynamicLoginConfigServiceUnitTestCase one-test Currently I see three issues: a) I am unable to set an attribute on a service that has been created but failed to start (in FAILED state). b) I cannot destroy a service that is in FAILED state but has been created. b) Against a running JBoss instance, if you run the same test a second time, you will see issues because the previous run did not destroy the service. View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=3967079#3967079 Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=3967079

18 years, 1 month

1
0
0 / 0

[Design of POJO Server] - Re: What's the status of HEAD?

by bill.burke＠jboss.com

I just wanted to know if the kernel changes went in because my guys were having problems... View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=3967060#3967060 Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=3967060

18 years, 1 month

1
0
0 / 0

[Design of Clustering on JBoss (Clusters/JBoss)] - Re: Convert HA-JNDI Proxies to Remoting (JBAS-3151)

by bstansberry＠jboss.com

See http://www.jboss.com/index.html?module=bb&op=viewtopic&t=87198 for a problem created by the use of RMI for this service (or any clustered service.) Basically, if separate networks are used for client and internal cluster traffic, a node cannot start and join the cluster if the client network is down. The RMI stubs that the DRM distributes around the cluster try to contact their origin server upon deserilization; this fails because the client network is down. Not a huge problem, but it prevents the server starting properly and then becoming automagically usable when the client network is restored. View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=3967058#3967058 Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=3967058

18 years, 1 month

1
0
0 / 0

[Design of JBoss Collaboration Server] - Re: MessageData Bug (only in special case)

by acoliver＠jboss.org

great. I should be done sometime next week with my rewrite of this code (to use mime4j). I'll merge it in then. View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=3967057#3967057 Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=3967057

18 years, 1 month

1
0
0 / 0

[Design of JBoss internal QA (Test Suite)] - Re: Testsuite failures for MalformedTestCase testMalformed t

by ryan.campbell＠jboss.com

Perhaps we should just ignore this if running under jdk5? View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=3967044#3967044 Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=3967044

18 years, 1 month

1
0
0 / 0

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

2009

2008

2007

2006

jboss-dev-forums August 2006