Hi Bill,
JBossWS will not contain the JAXWS api in
the forseeable future. We plan to have a JAXWS implemenation by the end of Q3.
I suggest you resolve the dependency on JAXWS in the EJB3 project without
relying on functionality provided by JBossWS.
Cheers
View results here -> http://cruisecontrol.jboss.com/cc/buildresults/jboss-4.0-testsuite-1.5?log=log20060518010456
BUILD FAILEDAnt Error Message: /services/cruisecontrol/work/scripts/build-jboss-common.xml:268: The following error occurred while executing this line: /services/cruisecontrol/work/scr
View results here -> http://cruisecontrol.jboss.com/cc/buildresults/jbossweb?log=log2006051722Lbuild.66
BUILD COMPLETE - build.66Date of build: 05/17/2006 22:00:00Time to build: 35 minutes 13 secondsLast changed: 05/17/2006 13:09:34Last log entry: Build on dev13 (Solaris 10
View results here -> http://cruisecontrol.jboss.com/cc/buildresults/jboss-head-jdk-matrix?log=log20060517220034
BUILD FAILEDAnt Error Message: /services/cruisecontrol/work/scripts/build-jboss-common.xml:272: The following error occurred while executing this line: /services/cruisecontrol/work/scrip
View results here -> http://cruisecontrol.jboss.com/cc/buildresults/jboss-head-jdk-matrix?log=log20060517192826
BUILD FAILEDAnt Error Message: /services/cruisecontrol/work/scripts/build-jboss-common.xml:272: The following error occurred while executing this line: /services/cruisecontrol/work/scrip
View results here -> http://cruisecontrol.jboss.com/cc/buildresults/jboss-head-jdk-matrix?log=log20060517180836
BUILD FAILEDAnt Error Message: /services/cruisecontrol/work/scripts/build-jboss-common.xml:272: The following error occurred while executing this line: /services/cruisecontrol/work/scrip
View results here -> http://cruisecontrol.jboss.com/cc/buildresults/jboss-4.0-testsuite-1.6?log=log20060517153412
BUILD FAILEDAnt Error Message: /services/cruisecontrol/work/scripts/build-jboss-common.xml:268: The following error occurred while executing this line: /services/cruisecontrol/work/scr
View results here -> http://cruisecontrol.jboss.com/cc/buildresults/jboss-4.0-testsuite-1.5?log=log20060517152756
BUILD FAILEDAnt Error Message: /services/cruisecontrol/work/scripts/build-jboss-common.xml:268: The following error occurred while executing this line: /services/cruisecontrol/work/scr
1/ JBoss Cache sucks with hibernate and ehcache works better (so far)
2/ If I use JBoss Cache X with Portal Y and I run in AS version Z in
config ALL that use JBoss Cache X', then I have an integration issue.
Steve Ebersole wrote:
If I recall correctly, they tried that setup initially but ran
View results here -> http://cruisecontrol.jboss.com/cc/buildresults/jboss-4.0-compatibility-matrix?log=log20060517111347
TESTS FAILEDAnt Error Message: /services/cruisecontrol/work/scripts/build-jboss-common.xml:236: The following error occurred while executing this line: /services/cruisecontrol/w
For an example look in "our"
javax.management.modelmbean.DescriptorSupport
private void readObject(ObjectInputStream ois)
throws IOException, ClassNotFoundException
{
ObjectInputStream.GetField getField = ois.readFields();
HashMap serMap = (HashMap) getField.get("descriptor
Dimitris Andreadis wrote:
We certainly need to maintain compatibility between the 4.x (and 3.2.x)
versions, so the serialVersionUID must be the same, although I don't
know why this Mbean needs to be serializable in the first place.
It should be serializable because an instance is bound to the J
We certainly need to maintain compatibility between the 4.x (and 3.2.x)
versions, so the serialVersionUID must be the same, although I don't
know why this Mbean needs to be serializable in the first place.
And since you are just adding fields, implementing Externalizable should
not really be neede
I added a couple of managed attributes to the class in HEAD. I want to
backport this to Branch_4_0 but the class there has serialVersionUID.
Should I make it implement java.io.Externalizable in Branch_4_0 and
preserve the value of serialVersionUID?
Thanks!
Original Message
If I recall correctly, they tried that setup initially but ran into the
locking issues that plagued the earlier Hibernate/JBossCache
integrations.
Conceivably they could try with the new optimistic-locking-based
provider, but we really need some performance numbers here to see how a
local, optim
View results here -> http://cruisecontrol.jboss.com/cc/buildresults/jbossweb?log=log20060517082113Lbuild.65
BUILD COMPLETE - build.65Date of build: 05/17/2006 08:21:13Time to build: 34 minutes 44 secondsLast changed: 05/17/2006 03:13:17Last log entry: Add patch logic. Make sure
FYI, I have updated from jboss-cache.jar to jboss-cache-jdk50.jar in jboss-head
since AS5.0 will use JDK5.0 anyway:
http://jira.jboss.com/jira/browse/JBAS-3224
The other purpose is to fully support JDK50 annotation (used in PojoCache).
It has passed the clustering tests. But if you see a proble
View results here -> http://cruisecontrol.jboss.com/cc/buildresults/jboss-remoting-testsuite-1.4?log=log20060517070309
TESTS FAILEDAnt Error Message: /services/cruisecontrol/work/scripts/build-jboss-remoting.xml:96: The following error occurred while executing this line: /services/cruisecontrol/wo
BTW, Congratulations to Dimitris and the QA team for
getting there, that's great.
Cheers,
sacha
From:
[EMAIL PROTECTED]
[mailto:[EMAIL PROTECTED] On Behalf Of
Ruel LoehrSent: lundi, 15. mai 2006 18:43To:
jboss-development@lists.sourceforge.netSubject: [JBoss-dev]
Same for me
> -Original Message-
> From: [EMAIL PROTECTED]
> [mailto:[EMAIL PROTECTED] On
> Behalf Of Mladen Turk
> Sent: mercredi, 17. mai 2006 10:09
> To: jboss-development@lists.sourceforge.net
> Subject: Fwd: Undeliverable:[JBoss-dev] *
>
> Hi,
>
> Can someone kick out this user (
View results here -> http://cruisecontrol.jboss.com/cc/buildresults/jbossweb?log=log20060517075106
BUILD FAILEDAnt Error Message: /home/cruisecontrol/work/scripts/build-jbossweb.xml:28: Exit code: 1 See compile.log in Build Artifacts for details.Date of build: 05/17/2006 07:51:06Time to
Break up the jars into more reusable pieces then.
-Original Message-
From: Ben Wang
Sent: Wednesday, May 17, 2006 4:46 AM
To: jboss-development@lists.sourceforge.net; Manik Surtani
Cc: Ryan Campbell; Steve Ebersole; Julien Viet; Roy Russo; QA
Subject: RE: [JBoss-dev] Re: FW: jboss-4.0.4 p
Currently JBossCache has direct dependecy on Jgroups and JBossAop. The
"default" already has aop but not jgroups. So that means an extra jgroups there
with the idea that "default" should be non-clustering related.
-Original Message-
From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED] On
Already been done yesterday but sf seems backlogged on mail delivery.
-Original Message-
From: [EMAIL PROTECTED]
[mailto:[EMAIL PROTECTED] On Behalf Of
Mladen Turk
Sent: Wednesday, May 17, 2006 1:09 AM
To: jboss-development@lists.sourceforge.net
Subject: Fwd: Undeliverable:[JBoss-dev] *
H
View results here -> http://cruisecontrol.jboss.com/cc/buildresults/jboss-cache-testsuite?log=log20060517054529
TESTS FAILEDAnt Error Message: /services/cruisecontrol/work/scripts/build-JBossCache.xml:86: The following error occurred while executing this line: /services/cruisecontrol/work/scripts/
Hi,
Can someone kick out this user ([EMAIL PROTECTED])?
I'm constantly getting this bounce message for couple
of days.
Regards,
Mladen.
Original Message
Subject: Undeliverable:[JBoss-dev] jbossws-testsuite Build Failed
Date: Wed, 17 May 2006 02:28:19 -0500
From: System Admini
View results here -> http://cruisecontrol.jboss.com/cc/buildresults/jboss-head-testsuite-1.6?log=log20060517035742
BUILD FAILEDAnt Error Message: /services/cruisecontrol/work/scripts/build-jboss-common.xml:268: The following error occurred while executing this line: /services/cruisecontrol/work/sc
View results here -> http://cruisecontrol.jboss.com/cc/buildresults/jbossws-testsuite?log=log20060517035042
TESTS FAILEDAnt Error Message: /services/cruisecontrol/work/scripts/build-jbossws-testsuite.xml:95: The following error occurred while executing this line: /services/cruisecontrol/work/scrip
28 matches
Mail list logo
