This sounds like something I added for exploded deployments. (the url to
watch for redeployment is the app-specific xml: ejb-jar.xml for ejbs,
application.xml for ears, ...) It is an MBean operation in MainDeployer
that returns the corresponding DeploymentInfo's watch field.
-Larry
> Can someo
I set it up so non-numbered deployments deploy last. It seemed that someone
who required that kind of control over ordering would only need it for the
first deployments. Should I change it so that non-numbered deployments
deploy first?
-Larry
- Original Message -
From: "marc fleury" <[
The best solution I have found is to use the tag in your
default jboss-service.xml. Certainly putting it in your jboss-system.jar
seems a bit extreme.
-Larry
- Original Message -
From: "Per Nyfelt" <[EMAIL PROTECTED]>
To: <[EMAIL PROTECTED]>
Sent: Monday, June 03, 2002 12:30 AM
Subject
The jguru article is not accurate.
Given the code:
public class Test {
public int testInc(int x) {
x++;
return x;
}
public int testAdd(int x) {
x = x + 1;
return x;
}
}
This produces the following byte-code:
Method Test()
0 aload_0
1 invokes
Ah - you are correct. Here is the byte-code for the incrementor with a
member variable:
Method Test()
0 aload_0
1 invokespecial #1
4 return
Method int testInc()
0 aload_0
1 dup
2 getfield #2
5 iconst_1
6 iadd
7 putfield #2
10 aload_0
11 getfield #2
14 iretur
(JBoss Branch_3_0, though I've also verified this
on HEAD)
I think I've discovered a source of generic
XA_PROTO errors. When an XA connection is closed (see
org/jboss/resource/connectionmanager/XATxConnectionManager$XAConnectionEventListener.connectionClosed[306]),
it is first delisted fr
I think I may have tracked down the SwiftMQ bug... let me know if this
sounds right.
SwiftMQ doesn't support start(suspend), so they return false for all calls
to isSameRM(). This should cause all connections being enlisted to be given
a unique xid (with different branch qualifiers). I think th
I think I may have tracked down the SwiftMQ bug... let me know if this
sounds right.
SwiftMQ doesn't support start(suspend), so they return false for all calls
to isSameRM(). This should cause all connections being enlisted to be given
a unique xid (with different branch qualifiers). I think th
