View results here -> http://cruisecontrol.jboss.com/cc/buildresults/jboss-remoting-testsuite-1.4?log=log20060426044204
TESTS FAILEDAnt Error Message:/services/cruisecontrol/work/scripts/build-jboss-remoting.xml:96: The following error occurred while executing this line:
Use JBossXB :-)
On Tue, 2006-04-25 at 19:21 -0400, Emmanuel Bernard wrote:
I want to activate XML Schema validation in a portable way.
It doesn't seems to be possible.
For Xerces I have to do
saxReader = new SAXReader();
saxReader.setEntityResolver(entityResolver);
The issue is
'WARs don't deploy in JBoss HEAD built with 1.4'
http://jira.jboss.org/jira/browse/JBWS-799
Scott M Stark wrote:
This error showing up after updating my 4.0 workspace:
22:15:22,951 INFO [TomcatDeployer] deploy, ctxPath=/jmx-console,
warUrl=.../dep
loy/jmx-console.war/
I haven't tried it but maybe it'll help
http://xerces.apache.org/xerces2-j/faq-pcfp.html#faq-4
Emmanuel Bernard wrote:
I want to activate XML Schema validation in a portable way.
It doesn't seems to be possible.
For Xerces I have to do
saxReader = new SAXReader();
View results here -> http://cruisecontrol.jboss.com/cc/buildresults/jbossws-testsuite?log=log20060426074403Lbuild.1
BUILD COMPLETE-build.1Date of build:04/26/2006 07:44:03Time to build:10 minutes 15 seconds
Unit Tests: (745) Total
View results here -> http://cruisecontrol.jboss.com/cc/buildresults/jbpm-mysql-testsuite?log=log20060426052158
TESTS FAILEDAnt Error Message:/home/cruisecontrol/work/scripts/build-jbpm-db-matrix.xml:92: The following error occurred while executing this line:
A Seam use reported an isssue in the way Hibernate register a sync with
JBossTM (the old one at least).
I've described the issue in JIRA
http://jira.jboss.com/jira/browse/EJBTHREE-540
Please provide feedbacks on this one. We must fix that before JBoss AS
4.0.4 / JBoss EJB3 / Hibernate
View results here -> http://cruisecontrol.jboss.com/cc/buildresults/jbpm-oracle-testsuite?log=log20060426083130
TESTS FAILEDAnt Error Message:/home/cruisecontrol/work/scripts/build-jbpm-db-matrix.xml:100: The following error occurred while executing this line:
Replied on the forum.
Mark.
Emmanuel Bernard wrote:
A Seam use reported an isssue in the way Hibernate register a sync
with JBossTM (the old one at least).
I've described the issue in JIRA
http://jira.jboss.com/jira/browse/EJBTHREE-540
Please provide feedbacks on this one. We must fix that
View results here -> http://cruisecontrol.jboss.com/cc/buildresults/jbpm-hsqldb-testsuite?log=log20060426093028
TESTS FAILEDAnt Error Message:/home/cruisecontrol/work/scripts/build-jbpm-db-matrix.xml:85: The following error occurred while executing this line:
I've closed the JTA issue:
http://jira.jboss.com/jira/browse/JBAS-3155
AFAIK, this originally comes from the OTS spec.
I guess the only way an OTS backed JTA impl
could implement the new stuff:
View results here -> http://cruisecontrol.jboss.com/cc/buildresults/jbpm-mssql-testsuite?log=log20060426093936
TESTS FAILEDAnt Error Message:/home/cruisecontrol/work/scripts/build-jbpm-db-matrix.xml:123: The following error occurred while executing this line:
View results here -> http://cruisecontrol.jboss.com/cc/buildresults/jboss-remoting-testsuite-1.5?log=log20060426075446
TESTS FAILEDAnt Error Message:/services/cruisecontrol/work/scripts/build-jboss-remoting.xml:96: The following error occurred while executing this line:
Adrian Brock wrote:
I've closed the JTA issue:
http://jira.jboss.com/jira/browse/JBAS-3155
AFAIK, this originally comes from the OTS spec.
Synchronizations were standardised first in the OTS. Prior to that
everyone did it in a vendor-specific manner.
I guess the only way an OTS
On Wed, 2006-04-26 at 15:03 +0100, Mark Little wrote:
Adrian Brock wrote:
I've closed the JTA issue:
http://jira.jboss.com/jira/browse/JBAS-3155
AFAIK, this originally comes from the OTS spec.
Synchronizations were standardised first in the OTS. Prior to that
everyone did it
This does not apply to the 4.0 branch as the jbossws14.sar is used when
the dist is built using j2se1.4. What I am saying is that the
jbossws14.sar must always be what is installed as the default ws stack
regardless of what jdk is used to build the dist. There can be no java5
specific logic in the
Not sure what you mean. That reference is purely about registering a
subordinate synchronization with the original transaction coordinator.
JBossTS does this already because it's an optional part of the OTS
specification. You create and enlist the sub-synchronization with the
root
Quick question about this actually.
3.2.0.CR2 exists in the respository, specifying cglib, as a dependency
and has already been used in one of the 4.0.3 CR releases, correct?
So what is the policy on changing the component def of a component when
that particular release has already been used in
Normally you need to copy into a new hibernate release.
For this particular case, if you just add the javassist dependency,
without changing anything else, I suppose you could modify component.xml
with the effect being that older versions of component using this
version of hibernate will pickup
You would want to create a new version.The older version which uses
cglib should remain for historic reasons.
For example if 4.0.3.SP1 uses a hibernate version that is dependent upon
cglib, we may want to reproduce that build sometime in the future (doing
a service pack).
Modifying the
Right. It's a different issue. Sorry.
Scott M Stark wrote:
This does not apply to the 4.0 branch as the jbossws14.sar is used when
the dist is built using j2se1.4. What I am saying is that the
jbossws14.sar must always be what is installed as the default ws stack
regardless of what jdk is used
The binaries in the repository have to be treated as releases. As soon a
version is out there you have to consider that its being used and that
any change to it will break existing usage. If 3.2.0.CR2 is just
repacked with different configurations/dependencies I would call it
3.2.0.CR2-jboss or
SFSB has a similar issue. I'm just going to check to see if the tx is
marked, if so, just remove the SFSB.
Emmanuel Bernard wrote:
A Seam use reported an isssue in the way Hibernate register a sync with
JBossTM (the old one at least).
I've described the issue in JIRA
View results here -> http://cruisecontrol.jboss.com/cc/buildresults/jboss-cache-testsuite?log=log20060426104250
TESTS FAILEDAnt Error Message:/services/cruisecontrol/work/scripts/build-JBossCache.xml:86: The following error occurred while executing this line:
Right, that's the other part to this. I'd need to change the
hibernate-int module to depend on this new hibernate release. Then it
is a matter of specifying to use javassist over cglib as a config
parameter. The interesting thing here, though, is that this setting is
global to a classloader
I think we should be using something like the more flexible like the
java service provider notion used by jaxp and others as the env aware
factory bootstrap:
http://java.sun.com/j2se/1.5.0/docs/guide/jar/jar.html#Service Provider
A simple example test driver:
package util.jar;
import
If you install Fedora Core 5 on your laptop and install JBAS404RC2 from
the gui installer... things go off the screen and the screen isn't
resizable. I qualify this is bad. There does not appear to be a
forum for the installer (adrian) or if there is then it needs a better
more CTRL-Fable
View results here -> http://cruisecontrol.jboss.com/cc/buildresults/jbpm-sybase-testsuite?log=log20060426095746
BUILD TIMED OUTAnt Error Message:build timeoutDate of build:04/26/2006 09:57:46Time to build:Last changed:04/20/2006 03:10:08Last log entry:seam pageflow update. Changed type of
View results here -> http://cruisecontrol.jboss.com/cc/buildresults/jboss-head-jdk-matrix?log=log20060426173646
BUILD FAILEDAnt Error Message:/services/cruisecontrol/work/scripts/build-jboss-common.xml:220: The following error occurred while executing this line:
View results here -> http://cruisecontrol.jboss.com/cc/buildresults/jbpm-db2-testsuite?log=log20060426145802
TESTS FAILEDAnt Error Message:/home/cruisecontrol/work/scripts/build-jbpm-db-matrix.xml:116: The following error occurred while executing this line:
View results here -> http://cruisecontrol.jboss.com/cc/buildresults/jboss-4.0-jdk-matrix?log=log20060426203300
BUILD FAILEDAnt Error Message:/services/cruisecontrol/work/scripts/build-jboss-common.xml:220: The following error occurred while executing this line:
View results here -> http://cruisecontrol.jboss.com/cc/buildresults/jboss-head-jdk-matrix?log=log20060426205230
BUILD FAILEDAnt Error Message:/services/cruisecontrol/work/scripts/build-jboss-common.xml:220: The following error occurred while executing this line:
View results here -> http://cruisecontrol.jboss.com/cc/buildresults/jboss-4.0-jdk-matrix?log=log20060426210807Lbuild.1027
BUILD COMPLETE-build.1027Date of build:04/26/2006 21:08:07Time to build:18 minutes 6 secondsLast changed:04/26/2006 20:41:15Last log entry:Change the
View results here -> http://cruisecontrol.jboss.com/cc/buildresults/jbossweb?log=log20060426220020Lbuild.48
BUILD COMPLETE-build.48Date of build:04/26/2006 22:00:20Time to build:42 minutes 33 seconds
Unit Tests: (0) Total Errors and
View results here -> http://cruisecontrol.jboss.com/cc/buildresults/jboss-remoting-testsuite-1.5?log=log20060426233858
TESTS FAILEDAnt Error Message:/services/cruisecontrol/work/scripts/build-jboss-remoting.xml:96: The following error occurred while executing this line:
35 matches
Mail list logo
