Adds xml based Invocation Layer to Jbossmq
Please let me know if I can be of any help with
integrating the XIL into jboss-head.
Details on the structure of the XIL protocol, the current
C# client impl, and testsuite results are available at:
csil.sourceforge.net
- new packages in messaging module:
org.jboss.mq.il.xil
org.jboss.mq.il.xil.encoding
- new packages in testsuite module (primarily ports of
org.jboss.test.jbossmq, to run over xil):
org.jboss.test.tamale.*
For some reason, diff is corrupting the thirdparty jar
nanoxml.jar, so I have excluded it from the patch and
attached it seperately.
To apply patch from directory above jboss-head:
mkdir ./jboss-head/thirdparty/nanoxml-nanoxml
mkdir ./jboss-head/thirdparty/nanoxml-nanoxml/lib
(copy the attached nanoxml.jar into the above directory)
patch -u -p 4 -i xil.patch
affected files:
build/build.xml
messaging/build.xml
messaging/src/etc/server/default/deploy/jbossmq-
service.xml
messaging/src/etc/server/cluster/deploy/jbossmq-
service.xml
messaging/src/main/org/jboss/mq/AcknowledgementReq
uest.java
messaging/src/main/org/jboss/mq/AuthenticationReques
t.java
messaging/src/main/org/jboss/mq/BrowseRequest.java
messaging/src/main/org/jboss/mq/BrowseResponse.java
messaging/src/main/org/jboss/mq/ClientID.java
messaging/src/main/org/jboss/mq/ClientReceiveRequest.
java
messaging/src/main/org/jboss/mq/Connection.java
messaging/src/main/org/jboss/mq/ConnectionToken.java
messaging/src/main/org/jboss/mq/DurableSubscriptionID
.java
messaging/src/main/org/jboss/mq/GenericConnectionFa
ctory.java
messaging/src/main/org/jboss/mq/MessagePool.java
messaging/src/main/org/jboss/mq/Ping.java
messaging/src/main/org/jboss/mq/ReceiveRequest.java
messaging/src/main/org/jboss/mq/SessionID.java
messaging/src/main/org/jboss/mq/SpyBytesMessage.jav
a
messaging/src/main/org/jboss/mq/SpyConnectionMetaD
ata.java
messaging/src/main/org/jboss/mq/SpyConsumer.java
messaging/src/main/org/jboss/mq/SpyDestination.java
messaging/src/main/org/jboss/mq/SpyEncapsulatedMes
sage.java
messaging/src/main/org/jboss/mq/SpyJMSException.jav
a
messaging/src/main/org/jboss/mq/SpyMapMessage.java
messaging/src/main/org/jboss/mq/SpyMessage.java
messaging/src/main/org/jboss/mq/SpyMessageConsum
er.java
messaging/src/main/org/jboss/mq/SpyMessageProducer
.java
messaging/src/main/org/jboss/mq/SpyObjectMessage.ja
va
messaging/src/main/org/jboss/mq/SpyQueue.java
messaging/src/main/org/jboss/mq/SpyQueueBrowser.jav
a
messaging/src/main/org/jboss/mq/SpyQueueReceiver.jav
a
messaging/src/main/org/jboss/mq/SpyQueueSender.java
messaging/src/main/org/jboss/mq/SpySession.java
messaging/src/main/org/jboss/mq/SpyStreamMessage.j
ava
messaging/src/main/org/jboss/mq/SpyTemporaryQueue.j
ava
messaging/src/main/org/jboss/mq/SpyTemporaryTopic.ja
va
messaging/src/main/org/jboss/mq/SpyTextMessage.java
messaging/src/main/org/jboss/mq/SpyTopic.java
messaging/src/main/org/jboss/mq/SpyTopicPublisher.jav
a
messaging/src/main/org/jboss/mq/SpyTopicSubscriber.ja
va
messaging/src/main/org/jboss/mq/SpyXAConnection.java
messaging/src/main/org/jboss/mq/SpyXAConnectionFact
ory.java
messaging/src/main/org/jboss/mq/SpyXAResource.java
messaging/src/main/org/jboss/mq/SpyXAResourceMana
ger.java
messaging/src/main/org/jboss/mq/Subscription.java
messaging/src/main/org/jboss/mq/SubscriptionID.java
messaging/src/main/org/jboss/mq/TransactionRequest.ja
va
messaging/src/main/org/jboss/mq/il/xil/XILClientIL.java
messaging/src/main/org/jboss/mq/il/xil/XILClientILService
.java
messaging/src/main/org/jboss/mq/il/xil/XILReturnStatus.j
ava
messaging/src/main/org/jboss/mq/il/xil/XILServerIL.java
messaging/src/main/org/jboss/mq/il/xil/XILServerILFactor
y.java
messaging/src/main/org/jboss/mq/il/xil/XILServerILServic
e.java
messaging/src/main/org/jboss/mq/il/xil/encoding/Acknow
ledgementRequestXml.java
messaging/src/main/org/jboss/mq/il/xil/encoding/Authent
icationRequestXml.java
messaging/src/main/org/jboss/mq/il/xil/encoding/Browse
RequestXml.java
messaging/src/main/org/jboss/mq/il/xil/encoding/Browse
ResponseXml.java
messaging/src/main/org/jboss/mq/il/xil/encoding/ClientID
Xml.java
messaging/src/main/org/jboss/mq/il/xil/encoding/ClientR
eceiveRequestXml.java
messaging/src/main/org/jboss/mq/il/xil/encoding/Connec
tionTokenXml.java
messaging/src/main/org/jboss/mq/il/xil/encoding/Destina
tionXml.java
messaging/src/main/org/jboss/mq/il/xil/encoding/Durable
SubscriptionIDXml.java
messaging/src/main/org/jboss/mq/il/xil/encoding/Enabled
Xml.java
messaging/src/main/org/jboss/mq/il/xil/encoding/Encode
r.java
messaging/src/main/org/jboss/mq/il/xil/encoding/Excepti
onXml.java
messaging/src/main/org/jboss/mq/il/xil/encoding/HashX
ml.java
messaging/src/main/org/jboss/mq/il/xil/encoding/HexByt
eConverter.java
messaging/src/main/org/jboss/mq/il/xil/encoding/JavaObj
ectXml.java
messaging/src/main/org/jboss/mq/il/xil/encoding/ListXml.
java
messaging/src/main/org/jboss/mq/il/xil/encoding/Messag
eXml.java
messaging/src/main/org/jboss/mq/il/xil/encoding/PingXml
.java
messaging/src/main/org/jboss/mq/il/xil/encoding/Receive
RequestXml.java
messaging/src/main/org/jboss/mq/il/xil/encoding/Receive
ResponseXml.java
messaging/src/main/org/jboss/mq/il/xil/encoding/Session
IDXml.java
messaging/src/main/org/jboss/mq/il/xil/encoding/SimpleT
ypeXml.java
messaging/src/main/org/jboss/mq/il/xil/encoding/Subscri
ptionXml.java
messaging/src/main/org/jboss/mq/il/xil/encoding/Transac
tionRequestXml.java
messaging/src/main/org/jboss/mq/il/xil/encoding/UTFFra
gmenter.java
messaging/src/main/org/jboss/mq/il/xil/encoding/Unsubs
cribeRequestXml.java
messaging/src/main/org/jboss/mq/il/uil/multiplexor/Demu
xInputStream.java
messaging/src/main/org/jboss/mq/il/uil/multiplexor/Multip
lexorTest.java
messaging/src/main/org/jboss/mq/il/uil/multiplexor/MuxO
utputStream.java
messaging/src/main/org/jboss/mq/il/uil/multiplexor/Sock
etMultiplexor.java
messaging/src/main/org/jboss/mq/il/uil/multiplexor/Strea
mDemux.java
messaging/src/main/org/jboss/mq/il/uil/multiplexor/Strea
mMux.java
testsuite/build.xml
testsuite/src/main/org/jboss/test/tamale/encoding/HexCo
nversionTestCase.java
testsuite/src/main/org/jboss/test/tamale/mq/MQBase.jav
a
testsuite/src/main/org/jboss/test/tamale/mq_perf/Invocati
onLayerStressTestCase.java
testsuite/src/main/org/jboss/test/tamale/mq_perf/JBoss
MQPerfStressTestCase.java
testsuite/src/main/org/jboss/test/tamale/mq_test/Connec
tionUnitTestCase.java
testsuite/src/main/org/jboss/test/tamale/mq_test/JBoss
MQUnitTestCase.java
testsuite/src/main/org/jboss/test/tamale/mq_test/JBossS
essionRecoverUnitTestCase.java
testsuite/src/main/org/jboss/test/tamale/mq_test/Messa
geBodyUnitTestCase.java
testsuite/src/main/org/jboss/test/tamale/mq_test/RollBac
kUnitTestCase.java
testsuite/src/main/org/jboss/test/tamale/mq_test/Securit
yUnitTestCase.java
testsuite/src/main/org/jboss/test/tamale/mq_test/Unacke
dUnitTestCase.java
tools/etc/buildfragments/libraries.ent
compressed patch file.
thirdparty lib, nanoxml.jar
Logged In: YES
user_id=130188
This should be integrated into JBossMQ 3.2 but not HEAD
as JBossMQ 4 is being rebuilt from the ground up, and will
no longer use JBossMQ specific ILs per say. All invocation
layers are going to be factored out in favor of the JBoss
system-wide invokers.
Logged In: YES
user_id=370251
do I need to generate another patch? where can I find more
info about the system wide invokers? How would I integrate
the xml encoding into the new structure?
thanks,
fawce
Logged In: YES
user_id=370251
do I need to generate another patch? where can I find more
info about the system wide invokers? How would I integrate
the xml encoding into the new structure?
thanks,
fawce
Logged In: YES
user_id=130188
No, not now as JMS/JBoss 4 is still in the early stages of
development. When we get further along, we'll let you know
how XIL can fit in. Until then, I think this is a great addition to
JBossMQ 3. Having worked on Active JMS, I became
convinced that the best route to bring JMS to .NET and COM
was at the wire protocol level--or course you have to build one
for each JMS provider and you don't really know the wire
protocol for many JMS products... but since we're open
source, you can make it happen. This is exactly what you've
done with XIL.
Logged In: YES
user_id=370251
I am really excited to see this code included in jboss -- what
has to happen for XIL to be integrated into the 3.2 branch?
Also, I have a c# client in progress. It currently subscribes to
topics. Is there a way to include the client in jboss? It is of
course dependent on the XIL. Given your experience with
ActiveJMS, do you think the client should remain an
independent project?
I couldn't agree more about the OS nature of jboss making
this possible. We actually experimented with ActiveJMS
here, and reached the same conclusion. Our needs right now
are for a c# client, but we expect to connect a very diverse
client base to our JMS server and may need C/C++, VB, and
perl clients as well.
Is there any information available about the JBoss4 invoker
model? I'd like to learn more about it.
thanks,
fawce