This is now available on jboss labs:
http://labs.jboss.com/portal/jbossmessaging/downloads
This recommend contains several important fixes, so I highly recommend
that any users upgrade to this version if you are using an earlier version.
Release notes are available here:
This is still occurring for me ..
Is anyone else seeing this??
Ovidiu Feodorov wrote:
The 796th reason to switch to a separated build ...
Tim Fox wrote:
I'm getting the following after doing a cvs update -C in HEAD and then a
build clean:
BUILD FAILED
C:\dev\jboss-head\build
often to avoid all the build breakages. :-)
On Mon, 2006-06-26 at 08:55 +0100, Tim Fox wrote:
This is still occurring for me ..
Is anyone else seeing this??
Ovidiu Feodorov wrote:
The 796th reason to switch to a separated build ...
Tim Fox wrote:
I'm getting the following after doing a cvs
be
out of action for days
Tim Fox wrote:
Thx, that worked.
Adrian Brock wrote:
Maybe you changed the local filesystem date?
Try deleting the directory from thirdparty.
On Mon, 2006-06-26 at 10:34 +0200, Adrian Brock wrote:
My jbossxb is currently at snapshot not 1.0.0.CR4
but then I'm
1.5 is a pain for us, since we need to build and test our (jboss
messaging) releases using 1.4
Stan Silvert wrote:
So, head should only be compilable with a 1.5 jdk.
However, some modules will still enforce source target at 1.4, so
that
we can back merge fixes to the jboss4 tree.
Message-
From: Tim Fox
Sent: Monday, June 26, 2006 8:09 AM
To: Stan Silvert
Cc: Ryan Campbell; JBoss.org development list; Scott M Stark; The Core;
Bill Burke
Subject: Re: [JBoss-dev] Tomcat 6 integrated
1.5 is a pain for us, since we need to build and test our (jboss
messaging
I'm getting the following after doing a cvs update -C in HEAD and then a
build clean:
BUILD FAILED
C:\dev\jboss-head\build\build.xml:999: The following error occurred
while execut
ing this line:
C:\dev\jboss-head\build\build-thirdparty.xml:140: A versioning problem
exists:
Component:
I've noticed that some (most?) of the library entries on the Java build
path (Eclipse) for many of the projects start with a leading slash:
/thirdparty/jboss/profiler/jvmti/lib.
This means on my system that the libraries cannot be found since I do
not checkout jboss head into the root of the
.
Do you create a simple project called thirdparty in the workspace
based on what the build/build-thirdparty.xml creates?
On Sat, 2006-06-24 at 15:10 +0100, Tim Fox wrote:
I've noticed that some (most?) of the library entries on the Java build
path (Eclipse) for many of the projects start
(to guarantee
ordering). So JTA or JTS won't help you here. However, if you want to
look at JBossTransactions specifics, then that can help you: we give you
full control over the ordering of participants.
Mark.
Tim Fox wrote:
One of you transaction gurus may know the answer:
If I enlist 2
One of you transaction gurus may know the answer:
If I enlist 2 (or more) XAResources into a JTA transaction.
Transaction tx = tm.getTransaction();
tx.enlistResource(res1);
tx.enlistResource(res2);
Then I rollback the transaction, which causes rollback() to be called on
each of the
ok, hacked it to make it build.
lucky we're not using web services
Tim Fox wrote:
It's 5am, we're going through the release procedure for JBossMessaging
1.0, updated from CVS to build the release bundle, and HEAD is broken!
If any one from web services is listening please *fix this* we
It's 5am, we're going through the release procedure for JBossMessaging
1.0, updated from CVS to build the release bundle, and HEAD is broken!
If any one from web services is listening please *fix this* we are NOT
very happy bunnies right now
[EMAIL PROTECTED] wrote:
View results here -
I've been seeing this too for some time.
Alexey Loubyansky wrote:
HEAD
Kabir Khan wrote:
Which version/branch?
-Original Message-
From: [EMAIL PROTECTED]
[mailto:[EMAIL PROTECTED] On Behalf Of
Alexey Loubyansky
Sent: 13 March 2006 14:52
To:
Environment: Windows XP
Reporter: Tim Fox
The component JNDI environment for a Stateless session bean does not appear to
be read-only.
I have a SLSB running in 3.2.6.
It attempts to modify it's ENC (java:comp/env environment) and succeeds. I.e.
the following succeeds:
InitialContext ic
[ http://jira.jboss.com/jira/browse/JBAS-1490?page=history ]
Tim Fox updated JBAS-1490:
--
Description:
The component JNDI environment for a Stateless session bean does not appear to
be read-only.
I have a SLSB running in 3.2.6.
It attempts to modify it's ENC
Have you thought of profiling the code to determine what's taking so long?
-Original Message-
From: [EMAIL PROTECTED]
[mailto:[EMAIL PROTECTED]]On Behalf
Of Dain Sundstrom
Sent: 13 November 2001 15:49
To: 'Peter Levart'; [EMAIL PROTECTED]
Subject: RE: [JBoss-dev] loading 10 EBs
Anyone know of any timescales for the release of JBoss 3.0?
TIA
___
Jboss-development mailing list
[EMAIL PROTECTED]
https://lists.sourceforge.net/lists/listinfo/jboss-development
I have a simple message driven bean, listening on a queue.
When I send a message to the queue, the send happens ok (ok meaning no error
messages/exceptions), but the message seems to be disappear into the void.
I guess the bean isn't registered on this queue somehow, even though I'm
pretty damned
I need to use a scheduler to hit some ejbs - apparently jboss has one,
although I can find no examples/documentation on how to use this.
Anyone know of any pointers?
Cheers
___
Jboss-development mailing list
[EMAIL PROTECTED]
20 matches
Mail list logo
