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

[Design of JBoss Wiki] - Re: Downloaded the source and wouldnt build from Maven

by tony.herstell＠gmail.com

anonymous wrote : | | C:\Documents and Settings\herstell\My Documents\Wiki\Source for wiki\jbosswiki-beta2-2.4>maven all | __ __ | | \/ |__ _Apache__ ___ | | |\/| / _` \ V / -_) ' \ ~ intelligent projects ~ | |_| |_\__,_|\_/\___|_||_| v. 1.0.2 | | build:start: | | all: | wiki:all: | prepare-repo: | [copy] Copying 15 files to C:\Documents and Settings\herstell\.maven\repository | Starting the reactor... | Our processing order: | Wiki common | +---------------------------------------- | | Making wiki-common for the repo Wiki common | | Memory: 2M/4M | +---------------------------------------- | Attempting to download junit-3.8.1.jar. | Error retrieving artifact from [http://www.ibiblio.org/maven/junit/jars/junit-3.8.1.jar]: java.io.IOException: Unknown error downloading; status code | WARNING: Failed to download junit-3.8.1.jar. | Attempting to download commons-fileupload-1.0.jar. | Error retrieving artifact from [http://www.ibiblio.org/maven/commons-fileupload/jars/commons-fileupload-1...]: java.io.IOException: Unknown error d | WARNING: Failed to download commons-fileupload-1.0.jar. | Attempting to download dom4j-1.6.jar. | Error retrieving artifact from [http://www.ibiblio.org/maven/dom4j/jars/dom4j-1.6.jar]: java.io.IOException: Unknown error downloading; status code wa | WARNING: Failed to download dom4j-1.6.jar. | Attempting to download portlet-api-1.0.jar. | Error retrieving artifact from [http://www.ibiblio.org/maven/portlet-api/jars/portlet-api-1.0.jar]: java.io.IOException: Unknown error downloading; st | WARNING: Failed to download portlet-api-1.0.jar. | Attempting to download jbossall-client-3.2.3.jar. | Error retrieving artifact from [http://www.ibiblio.org/maven/jboss/jars/jbossall-client-3.2.3.jar]: java.io.IOException: Unknown error downloading; st | WARNING: Failed to download jbossall-client-3.2.3.jar. | | BUILD FAILED | File...... C:\Documents and Settings\herstell\My Documents\Wiki\Source for wiki\jbosswiki-beta2-2.4\maven.xml | Element... maven:reactor | Line...... 58 | Column.... 56 | The build cannot continue because of the following unsatisfied dependencies: | | junit-3.8.1.jar | commons-fileupload-1.0.jar | dom4j-1.6.jar | portlet-api-1.0.jar | jbossall-client-3.2.3.jar | | Total time: 11 seconds | Finished at: Thu Mar 15 18:10:00 NZDT 2007 | | C:\Documents and Settings\herstell\My Documents\Wiki\Source for wiki\jbosswiki-beta2-2.4> | | Trying to build wiki... got really fed up hacking the .ear files. ;) I am new to maven .. how do I fix this? View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=4028235#4028235 Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=4028235

19 years

1
0
0 / 0

[Design of JBoss Web Services] - FEATURE_SECURE_PROCESSING and related dtd parsing config usa

by scott.stark＠jboss.org

A question has come up around the dtd entity parsing denial of service issue raised here: http://www-128.ibm.com/developerworks/xml/library/x-tipcfsx.html http://java.sun.com/j2se/1.5.0/docs/guide/xml/jaxp/JAXP-Compatibility_150... Are we allowing for the use of the parser.setFeature(XMLConstants.FEATURE_SECURE_PROCESSING, true) to limit the defaults? What about disabling doctypes via the http://apache.org/xml/features/disallow-doctype-decl feature: http://xerces.apache.org/xerces2-j/features.html View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=4028226#4028226 Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=4028226

19 years

1
0
0 / 0

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

by weston.price＠jboss.com

Nice. Good work all around guys. View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=4028220#4028220 Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=4028220

19 years

1
0
0 / 0

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

by kurt.stam＠jboss.com

Looks great Bill, just wanted to add that deployments to the standalone is kept inline with deploying to JBossAS, so it's easy to switch deployments between the two. So far only the helloworld sample has been converted to the new deployment. The work to convert one is to rename the jbossesb.xml to jboss-esb.xml, then add that to the custom-code-jar in META-INF, and make sure the extention of the archive is '.esb'. This is your deployable package. Cheers, --Kurt View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=4028217#4028217 Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=4028217

19 years

1
0
0 / 0

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

by bill.burke＠jboss.com

Kurt and I have been doing a number of things to leverage the JBoss kernel for ESB and to clean up the overall distribution of JBoss ESB. A lot of sweeping changes have been done for deployment and testing. We've also drastically changed the distribution. Here's what we've done so far: * ESB Deployer: real packaging and hotdeployment for ESB We've written a JBoss Deployer for ESB which allows you to create ESB jar archives or raw esb XML files and deploy them to a JBoss instance. In the old ESB jboss integration, you could only have one jbossesb.xml file. Now you can have multiple deployments. The two deployment options are: - a .esb jar archive. This is a regular JAR file with a .esb suffix that has any number of user classes in it. A META-INF/jboss-esb.xml file in the .esb jar archive is required and this defines your providers and services in the current and past XML file format. You may also add a META-INF/classloader.xml file if you want to have classloader scoping for this .esb deployment. The syntax is exactly the same as other classloading configuration of other JBoss components. - a xxx-esb.xml file. This is just a raw esb .xml file that defines * New .sar files. jbossesb.sar and jbossesb-registry.sar. In the old distribution, everything was in one scoped .sar file. This was not feasible as it required user classes, actions, services, etc. that use ESB to be in the same scoped classloader domain as the esb files. Now, only the jbossesb-registry.sar is scoped for the JAXR and Scout snapshots. * Everything is self contained in the .sar files now. There is no special installation step for installing into JBoss AS other than copying the .sar files into the deploy directory. All configuration files are now under jbossesb.sar. This includes juddi and esb property files, and datasource -ds.xml files for juddi and esb. * jbossesb.sar now will initialize the juddi and message store database at boot time if they haven't already been initialized. Look in jbossesb.sar/META-INF/jboss-service.xml to see how this is done with a generic DatabaseInitializer service that we wrote. * New distribution. JBoss ESB will now have a ESB Server distribution, and a SAR distribution. The ESB Server distribution is the raw JBoss 4.x Kernel configured with basic services that a full blown ESB needs like, database connection pooling, JNDI, juddi, JMS, transactions. FYI, this boots in 11 seconds. Most of the time is in initializing JMS and Tomcat. The SAR distribution is just the esb .sar files, without the server. The idea with the SAR distribution is if you want to deploy onto an existing JBoss AS distribution * To build the distribution, I created a new ant file under product/build-distr.xml. After you do ant dist, do a ant -f build-distr.xml This will create a full server distribution under product/build/jbossesb-server-4.0.1. * To run the distribution $ cd product/build/jbossesb-server-4.0.1/bin. run.bat or run.sh * TESTING. I've incorporated the JBoss Test junit integration that we use in the appserver project. It is really good because it allows you to specify archives/files you want to deploy to a running server for the duration of the tests of that test class. Look at qa/junit/src/org/jboss/soa/esb/server/unit/SimpleDeployUnitTestCase.java. * I added an ant target in qa/junit that allows you to run all the tests in a specific directory in the source tree. For example: ant -Dtest=server one-test will run the SimpleDeployUnitTestCase example I talk about above. This target creates junit output into qa/build/reports which another ant target "tests-report-html" can transform into a nice HTML report of all the tests you ran. Eventually we should really port all the tests to this framework so that you can build and run all tests within ESB just by checking out and building ESB. Well, I think that is about it. Hopefully I didn't miss anything. If I did, Kurt speak up!!! View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=4028214#4028214 Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=4028214

19 years

1
0
0 / 0

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

by ryan.campbell＠jboss.com

The JMX call could have a timeout of 10 seconds. We could just spawn a thread and sleep for 10 seconds, right? If you don't get an answer, the server is dead. I agree you couldn't check whether everything is alive, just whether there is any memory left. I think Dimitris created an MBean to do this? The problem with the log file approach is that the all log gets huge, and this would really slow down the runs, even when the server is fine. The JMX call should be performant if things are ok, which is the main case. View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=4028213#4028213 Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=4028213

19 years

1
0
0 / 0

[Design of JBoss jBPM] - Re: Problems with jBPM&gpd

by kukeltje

W R O N G forum, this forum is for the design OF jbpm, not desiging WITH jbpm View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=4028202#4028202 Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=4028202

19 years

1
0
0 / 0

[Design of Messaging on JBoss (Messaging/JBoss)] - JBAS-4204, BasicQueue.removeAllMessages cleanup

by scott.stark＠jboss.org

The BasicQueue.removeAllMessages is not handling removal of msgs that have events (timeouts for example) when they are also unacknowledged. The usage that produced this issue looks to be an invalid attempt to unsubscribe a durable subscription with active msgs, but the handling of the error is leaving the subscription in a broken state. Its seems that both the BasicQueue.removeAllMessages attempt to drop msgs that have already been dropped as well as the AbstractStateManager.setDurableSubscription handling of the unsubscribe need to be cleaned up. View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=4028190#4028190 Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=4028190

19 years

1
0
0 / 0

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

by wolfc

I don't think that is good enough. The OOM is preceeded by 1 hour of almost continious garbage collection and then something dies, but you can't predict what. I don't see how a service can check whether everything is alive. Even trying an uncaught on the ThreadGroup will probably get killed. The only thing I've found to be working is an external program monitoring the log file for OOM. View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=4028179#4028179 Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=4028179

19 years

1
0
0 / 0

[Design of JBoss ESB] - Re: Browser-based configuration editor

by kurt.stam＠jboss.com

Hi Derek, helloworld is checked in. The deploy task deploys a helloword.esb archive. If it makes it easier you can deploy it exploded. Email me if you want me to give you the archive. Cheers, --Kurt View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=4028171#4028171 Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=4028171

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