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

[Design of JBoss internal QA (Test Suite)] - Testsuite broken in 4.2

by adrian＠jboss.org

The testsuite build for 4.2 is broken. | [ejort@warjort testsuite]$ ./build.sh | Searching for build.xml ... | Buildfile: /home/ejort/jboss-4.2/testsuite/build.xml | <snipped/> | _jars-classloader: | [jar] Building jar: /home/ejort/jboss-4.2/testsuite/output/lib/java-sql.jar | [unzip] Expanding: /home/ejort/jboss-4.2/testsuite/output/lib/loading.sar into /home/ejort/jboss-4.2/testsuite/output/lib/unpacked/loadingresource1.ear/loading.sar | [copy] Copying 1 file to /home/ejort/jboss-4.2/testsuite/output/lib/unpacked/loadingresource1.ear/loading.sar/META-INF | [mkdir] Created dir: /home/ejort/jboss-4.2/testsuite/output/lib/unpacked/loadingresource2.ear/loading.tmp/META-INF | [unzip] Expanding: /home/ejort/jboss-4.2/testsuite/output/lib/loading.sar into /home/ejort/jboss-4.2/testsuite/output/lib/unpacked/loadingresource2.ear/loading.tmp | [copy] Copying 1 file to /home/ejort/jboss-4.2/testsuite/output/lib/unpacked/loadingresource2.ear/loading.tmp/META-INF | [copy] Copying 2 files to /home/ejort/jboss-4.2/testsuite/output/lib/unpacked/loadingresource2.ear/loading.tmp/dtds | [copy] Copying 1 file to /home/ejort/jboss-4.2/testsuite/output/lib/unpacked/loadingresource2.ear/loading.tmp/dtds | [zip] Building zip: /home/ejort/jboss-4.2/testsuite/output/lib/unpacked/loadingresource2.ear/loading.sar | [delete] Deleting directory /home/ejort/jboss-4.2/testsuite/output/lib/unpacked/loadingresource2.ear/loading.tmp | [copy] Copying 1 file to /home/ejort/jboss-4.2/testsuite/output/gen-src/org/jboss/test/classloader/scoping/singleton | [echo] V1 MySingleton.java cksum: 4208e590356f488b8d8ab24a93c292a5 | [copy] Copying 1 file to /home/ejort/jboss-4.2/testsuite/output/classes/org/jboss/test/classloader/scoping/singleton | [javac] Compiling 1 source file to /home/ejort/jboss-4.2/testsuite/output/classes | | BUILD FAILED | /home/ejort/jboss-4.2/testsuite/imports/sections/classloader.xml:230: /home/ejort/jboss-4.2/testsuite/${jboss.dist}/client not found. | The following diff fixes it: | [ejort@warjort testsuite]$ svn diff | Index: build.xml | =================================================================== | --- build.xml (revision 61436) | +++ build.xml (working copy) | @@ -239,6 +239,9 @@ | <path refid="thirdparty.classpath"/> | </path> | | +  | + <import file="imports/server-config.xml"/> | + |  | <path id="tests.classpath"> | <fileset dir="${jboss.dist}/client"> | @@ -426,8 +429,6 @@ |  | <import file="imports/test-jars.xml"/> | | -  | - <import file="imports/server-config.xml"/> |  | <property name="jbosstest.dist" value="${jboss.dist}"/> | Not sure how this worked for whoever made the change? I thought we still used the buildmagic property implementation that did lazy property evaluation, or was that supposed to have been rolled into ant? View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=4029346#4029346 Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=4029346

19 years

1
0
0 / 0

[Design of JBoss internal QA (Test Suite)] - Re: Updating the server task to detect OutOfMemoryErrors

by mvecera＠redhat.com

As I see, there is only one method to get the thing working. I have to write my own Ant task and run it against the started server after every junit task is called... View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=4029339#4029339 Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=4029339

19 years

1
0
0 / 0

[Design of JBoss internal QA (Test Suite)] - Re: Updating the server task to detect OutOfMemoryErrors

by mvecera＠redhat.com

As I see, there is only one method to get the thing working. I have to write my own Ant task and run it against the started server after every junit task is called... View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=4029336#4029336 Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=4029336

19 years

1
0
0 / 0

[Design of Kosmos] - Re: Error: HessianServiceExporter only supports POST request

by mega

Thanks a lot for your reply. I tried to create SVN monitoring portlet instance and add it to the portal page. But the page was empty. :( I also tried to add a "flash.war" porlet (downloaded from the website) , create its instance and add it to the portal page. it worked O.K. What shall i do next? Thanks once again for your help. View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=4029304#4029304 Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=4029304

19 years

1
0
0 / 0

[Design of JBoss Build System] - Re: Mavenizing docbook project

by pgier

Yes, eventually we will migrate as much as possible to maven. I created this jira issue for mavenizing docbook: http://jira.jboss.com/jira/browse/JBBUILD-346 View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=4029289#4029289 Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=4029289

19 years

1
0
0 / 0

[Design of JBoss ESB] - Re: Big changes in deployment, distribution, and testing

by mark.little＠jboss.com

MP1 for 4.0 is due out at the end of this week. View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=4029270#4029270 Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=4029270

19 years

1
0
0 / 0

[Design of JBoss ESB] - Re: Testsuite for MP1

by mark.little＠jboss.com

The unit and integration tests are under product, but when I did a build yesterday they all ran fine. View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=4029265#4029265 Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=4029265

19 years

1
0
0 / 0

[Design of Kosmos] - Re: Error: HessianServiceExporter only supports POST request

by aron.gombas

Hello, That URL is not to drop to your browser, as that is the connection point for the web service. (BTW based on that message, the server component is properly set up in your env). What you need instead is simply adding the portlets to your portal pages in the Administration section of JBoss Portal. View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=4029255#4029255 Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=4029255

19 years

1
0
0 / 0

[Design of JBoss internal QA (Test Suite)] - Re: Updating the server task to detect OutOfMemoryErrors

by mvecera＠redhat.com

So I am supposed to override the JUnitTestRunner class and in the endTask() method call the ServerInfo mbean and check for free memory? Is it right? View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=4029250#4029250 Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=4029250

19 years

1
0
0 / 0

[Design of Kosmos] - Error: HessianServiceExporter only supports POST requests

by mega

Hi, there, I am trying to implement the kosmos on my machine. I am using JBoss4+jboss portal 2.4.1+JDK 1.5 I could see the "kosmos" in my portal page, but when i tried to open the "http://myserver:8080/kosmos-server/kosmos-services/sf-service" in my browser, i got an error. The Hessian-service seems does not work well. The error was: org.springframework.web.servlet.support.RequestMethodNotSupportedException: HessianServiceExporter only supports POST requests I used the default xml files (kosmos-services-servlet.xml and portlet.xml) Would you please give me any suggestions? Thanks in advance. View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=4029241#4029241 Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=4029241

19 years

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 2007