Just my 2c. I think that an XML/HTTP integration of JBossMQ should be done by making a JAXM personality of JBossMQ. I had a quite lengty mail conversation with a guy a couple of month ago where we sort of tried to interpret the spec in a JMS way. He said he was going to implement the stuff, but then just disapeared.
If this is the way to go, what should actually be added as a message type is a SOAPMessage with attachement, I think. Unfortunately I do not have the time jsut not to implement JAXM on top of JBossMQ. But if anyone else is prepared to do it I might be able to help out (I have read the the fckn spec a number of times). //Peter On 13 Nov, Hiram Chirino wrote: >>From: Charles Chan <[EMAIL PROTECTED]> >>Reply-To: [EMAIL PROTECTED] >>To: Hiram Chirino <[EMAIL PROTECTED]> >>Subject: Re: JBossMQ PM XAResource interface >>Date: Tue, 13 Nov 2001 18:29:40 -0800 (PST) >> >>My initial idea with XML is simple... Just create an >>XMLMessage type (extended from TextMessage). Create a >>new Session interface that exposes the factory method >>to create this type of message. We could also provide >>a proprietary message selector based on XPath. That's >>what BEA WebLogic basically do. >> > > That would be cool. > >>However, after much thought, I think what you've >>suggested made more sense. HTTP is becoming important. >>We need a solid messaging framework over HTTP if we >>want reliable web services. >> > > I agree. > >>I am not sure if JBossSOAP uses JBossMQ as its >>transport but it can't unless JBossMQ supports HTTP >>and HTTPS. >> > > JBoss SOAP aka JBoss.Net will use the apache Axis server for HTTP and HTTPS. > What I want to do is be able either deploy a web service or a plain > servlet that would allow JBossMQ clients come in over HTTP/S > > So what I think we need is an IL that kinda goes like this: > HTTPServerIL -> (uses HTTP) -> MQHTTPServlet -> (JVM-IL) -> Server > > The hard part of this IL is going to be that the server can't directly > invoke methods on the client. The client is going to have to poll for > asynch message from the client by some thing like: > > 1. (Data structure accessible via the servlet) <- (JVM-IL) <- Server > 2. Client pool -> (uses HTTP) -> MQHTTPServlet -> (Data structure accessible > via the servlet) > > This approach would also let us run the web server in a different process as > the MQ server since the JVM-IL in my example could be replaced with any of > the other ILs. > > > What do you think?? > > Regards, > Hiram > >>Any discussion on this issue yet? I would like to look >>deeper into this. :) >> >>Thanks >>Charles >> >> >>--- Hiram Chirino <[EMAIL PROTECTED]> wrote: >> > >> > What were your ideas with XML?? >> > >> > A feature request that seemed interesting never had >> > been implemented was a >> > JMS over HTTP. Alot of companys only want to expose >> > port 80 at thier >> > firewall, and nothing else. >> > >> > Regards, >> > Hiram >> > >> > >From: Charles Chan <[EMAIL PROTECTED]> >> > >Reply-To: [EMAIL PROTECTED] >> > >To: Hiram Chirino <[EMAIL PROTECTED]> >> > >Subject: Re: JBossMQ PM XAResource interface >> > >Date: Tue, 13 Nov 2001 16:15:50 -0800 (PST) >> > > >> > > >> > >--- Hiram Chirino <[EMAIL PROTECTED]> wrote: >> > > >> > > > I don't think this a huge priority, since the >> > stuff >> > > > kinda works. But if >> > > > your intrested, go for it! >> > > >> > >I don't think it's a high priority either. The >> > >clustering work, however, is still rather unstable >> > at >> > >this point (I can't even run a JBoss cluster). I am >> > >now looking into using XML with JMS and hope to add >> > >something to our framework. Other suggestions? >> > > >> > >Charles >> > > >> > > >> > > >> > > > >> > > > Regards, >> > > > Hiram >> > > > >> > > > >Any thoughts? >> > > > > >> > > > >Charles >> > > > > >> > > > > >> > > > > >> > > > >--- David Jencks >> > <[EMAIL PROTECTED]> >> > > > >wrote: >> > > > > > On 2001.11.11 22:23:58 -0500 Charles Chan >> > wrote: >> > > > > > > HI, David, >> > > > > > > >> > > > > > > I replied your message on the list. To >> > tell >> > > > you >> > > > > > the >> > > > > > > truth, I found the JDBC PM stuffs a bit >> > > > > > convoluted... >> > > > > > >> > > > > > That's an understatement;-) >> > > > > > > (I admit I am totally new to this >> > framework) >> > > > > > > >> > > > > > > I was thinking of helping Hiram to get >> > some >> > > > > > clustering >> > > > > > > work done. Tell me some of your ideas, >> > maybe >> > > > they >> > > > > > will >> > > > > > > fit into the clustering work too. >> > > > > > >> > > > > > Mostly I was thinking it would be a good >> > idea to >> > > > > > change the pm interface to >> > > > > > expose an XAResource for transaction >> > management. >> > > > > > This would make using a >> > > > > > jca-wrapped xa datasource pretty easy for a >> > jdbc >> > > > pm. >> > > > > > The jca spec mentions >> > > > > > the possibility of a caching layer on top of >> > a >> > > > jca >> > > > > > connector: in this case >> > > > > > the caching layer registers a >> > synchronization >> > > > > > interface with the tm, and >> > > > > > flushes it's cached changes to the connector >> > on >> > > > the >> > > > > > before completion >> > > > > > notification. I'm wondering if it would be >> > > > possible >> > > > > > to treat the jms stuff >> > > > > > as such a caching layer, thus allowing us to >> > > > expose >> > > > > > the pm's XAResource as >> > > > > > the jms implementation's XAResource. This >> > would >> > > > > > allow 1phase optimization >> > > > > > if you are using the same db for jms and >> > regular >> > > > db >> > > > > > storage: I think this >> > > > > > would make jdbc based jms the clear speed >> > > > winner: >> > > > > > otherwise a more special >> > > > > > purpose method will be faster. >> > > > > > >> > > > > > So, I'm not sure this really fits in with >> > > > > > clustering... >> > > > > > >> > > > > > BTW the UIL layer seems broken- it doesn't >> > pass >> > > > many >> > > > > > tests. I can't figure >> > > > > > out why. >> > > > > > >> > > > > > Thanks >> > > > > > david jencks >> > > > > > >> > > > > > > >> > > > > > > Thanks! >> > > > > > > Charles >> > > > > > > >> > > > > > > --- David Jencks >> > > > <[EMAIL PROTECTED]> >> > > > > > > wrote: >> > > > > > > > This didn't show up on the list yet so >> > I'm >> > > > > > resending >> > > > > > > > it directly to you. >> > > > > > > > >> > > > > > > > BTW thanks for making the table names >> > > > > > configurable-- >> > > > > > > > excellent idea. >> > > > > > > > >> > > > > > > > Could I ask how much work you are >> > planning >> > > > to do >> > > > > > on >> > > > > > > > the PM's, especially >> > > > > > > > the jdbc one? I have several ideas that >> > I >> > > > won't >> > > > > > > > have time to implement for >> > > > > > > > quite a while - perhaps you would be >> > > > interested >> > > > > > in >> > > > > > > > discussing whether or >> > > > > > > > not they are good ideas ;-) >> > > > > > > > >> > > > > > > > Thanks! >> > > > > > > > David Jencks >> > > > > > > > >> > > > > > > > On 2001.11.11 15:28:39 -0500 David >> > Jencks >> > > > wrote: >> > > > > > > > Are you really sure this change is >> > correct? >> > > > I >> > > > > > have >> > > > > > > > been told that the jdbc >> > > > > > > > pm RELIES on unmanaged connections with >> > > > > > autocommit = >> > > > > > > > true. That is why I >> > > > > > > > created the NoTransDS and used it here. >> > > > There >> > > > > > is no >> > > > > > > > appropriate >> > > > > > > > transaction control from the container >> > that >> > > > I >> > > > > > can >> > > > > > > > discern. >> > > > > > > > >> > > > > > > > I believe with TM-managed transactions >> > on a >> > > > > > > > datasource used in jdbc - pm >> > > > > > > > there is an at least 50% chance that the >> > > > jdbc >> > > > > > > > DataSource XAResource (or >> > > > > > > > local transaction) will get commit >> > called >> > > > before >> > > > > > the >> > > > > > > > jms-xa XAResource gets >> > > > > > > > commit called - so the db transaction >> > will >> > > > be >> > > > > > > > comitted before all the >> > > > > > > > end-of-transaction work can be done. >> > > > > > > > >> > > > > > > > david jencks >> > > > > > > > >> > > > > > > > On 2001.11.11 14:43:33 -0500 Charles >> > Chan >> > > > wrote: >> > > > > > > > > User: charles_chan >> > > > > > > > > Date: 01/11/11 11:43:33 >> > > > > > > > > >> > > > > > > > > Modified: src/etc/conf/default >> > > > > > > > jbossmq-service.xml >> > > > > > > > > Log: >> > > > > > > > > - minor changes to JDBC PM >> > configuration >> > > > and >> > > > > > > > remove extraneous spaces. >> > > > > > > > > >> > > > > > > > > Revision Changes Path >> > > > > > > > > 1.10 +28 -21 >> > > > > > > > >> > > > jbossmq/src/etc/conf/default/jbossmq-service.xml >> > > > > > > > > >> > > > > > > > > Index: jbossmq-service.xml >> > > > > > > > > >> > > > > > > > >> > > > > > > >> > > > > > >> > > > >> > > >> > >> >=================================================================== >> > > > > > > > > RCS file: >> > > > > > > > >> > > > > > > >> > > > > > >> > > > >> > > >> > >> >/cvsroot/jboss/jbossmq/src/etc/conf/default/jbossmq-service.xml,v >> > > > > > > > > retrieving revision 1.9 >> > > > > > > > > retrieving revision 1.10 >> > > > > > > > > diff -u -r1.9 -r1.10 >> > > > > > > > > --- jbossmq-service.xml 2001/11/10 >> > > > 21:38:03 >> > > > > > 1.9 >> > > > > > > > > +++ jbossmq-service.xml 2001/11/11 >> > > > 19:43:33 >> > > > > > 1.10 >> > > > > > > > > @@ -7,9 +7,9 @@ >> > > > > > > > > <!-- >> > > > > > >> > > > > > > > >> > > > > > > > > --> >> > > > > > > > > <!-- >> > > > > > > > >> > > > > > > >> > > > > > >> > > > >> > > >> > >> >===================================================================== >> > > > > > > > > --> >> > > > > > > > > >> > > > > > > > > -<!-- $Id: jbossmq-service.xml,v 1.9 >> > > > > > 2001/11/10 >> > > > > > > > 21:38:03 d_jencks Exp $ >> > > > > > > > > --> >> > > > > > > > > +<!-- $Id: jbossmq-service.xml,v >> > 1.10 >> > > > > > 2001/11/11 >> > > > > > > > 19:43:33 charles_chan >> > > > > > > > > Exp $ --> >> > > > > > > > > >> > > > > > > > > -<!-- >> > > > > > > > > +<!-- >> > > > > > > > > | THis contains the default >> > > > > > configuration >> > > > > > > > of jbossmq >> > > > > > > > > | >> > > > > > > > > --> >> > > > > > > > > @@ -33,28 +33,28 @@ >> > > > > > > > > <mbean-ref >> > > > > > > > >> > > > > > > >> > > > > > >> > > > >> > > >> > >> >name="PersistenceManager">JBossMQ:service=PersistenceManager</mbean-ref> >> > > > > > > > > <mbean-ref >> > > > > > > > >> > > > > > > >> > > > > > >> > > > >> > > >> > >> >name="StateManager">JBossMQ:service=StateManager</mbean-ref> >> > > > > > > > > </mbean> >> > > > > > > > > - >> > > > > > > > > - <!-- >> > > > > > > > > + >> > > > > > > > > + <!-- >> > > > > > > > > | The MessageCache decides >> > where >> > > > to >> > > > > > put >> > > > > > > > JBossMQ message that >> > > > > > > > > | are sitting around waiting >> > to be >> > > > > > > > consumed by a client. >> > > > > > > > > | >> > > > > > > > > | The memory marks are in >> > > > Megabytes. >> > > > > > Once >> > > > > > > > the JVM memory usage >> > > > > > > > > hits >> > > > > > > > > | the high memory mark, the >> > old >> > > > > > messages >> > > > > > > > in the cache will start >> > > > > > > > > getting >> > > > > > > > > - | stored in the DataDirectory. >> > As >> > > > > > memory >> > > > > > > > usage gets closer to >> > > > > > > > > the >> > > > > > > > > + | stored in the DataDirectory. >> > As >> > > > > > memory >> > > > > > > > usage gets closer to >> > > > > > > > > the >> > > > > > > > > | Max memory mark, the amount >> > of >> > > > > > message >> > > > > > > > kept in the memory cache >> > > > > > > > > aproaches 0. >> > > > > > > > > --> >> > > > > > > > > - <mbean >> > > > > > > > code="org.jboss.mq.server.MessageCache" >> > > > > > > > > + <mbean >> > > > > > > > code="org.jboss.mq.server.MessageCache" >> > > > > > > > > >> > name="JBossMQ:service=MessageCache"> >> > > > > > > > > <attribute >> > > > > > > > name="HighMemoryMark">500</attribute> >> > > > > > > > > <attribute >> > > > > > > > name="MaxMemoryMark">600</attribute> >> > > > > > > > > <attribute >> > > > > > > > >> > name="DataDirectory">tmp/jbossmq</attribute> >> > > > > > > > > </mbean> >> > > > > > > > > >> > > > > > > > > - <!-- >> > > > > > > > > + <!-- >> > > > > > > > > | The StateManager is used to >> > keep >> > > > JMS >> > > > > > > > persistent state data. >> > > > > > > > > - | For example: what durable >> > > > > > subscriptions >> > > > > > > > are active. >> > > > > > > > > + | For example: what durable >> > > > > > subscriptions >> > > > > > > > are active. >> > > > > > > > > --> >> > > > > > > > > - <mbean >> > > > > > > > code="org.jboss.mq.server.StateManager" >> > > > > > > > > + <mbean >> > > > > > > > code="org.jboss.mq.server.StateManager" >> > > > > > > > > >> > name="JBossMQ:service=StateManager"> >> > > > > > > > > <attribute >> > > > > > > > >> > > > > > > >> > > > > > >> > > > >> > > >> > >> >name="StateFile">conf/default/jbossmq-state.xml</attribute> >> > > > > > > > > </mbean> >> > > > > > > > > @@ -65,15 +65,22 @@ >> > > > > > > > > <attribute >> > > > > > > > >> > > > > > >> > > > >> > name="DataDirectory">db/jbossmq/file/</attribute> >> > > > > > > > > <mbean-ref >> > > > > > > > >> > > > > > > >> > > > > > >> > > > >> > > >> > >> >name="MessageCache">JBossMQ:service=MessageCache</mbean-ref> >> > > > > > > > > </mbean> >> > > > > > > > > + >> > > > > > > > > + <!-- >> > > > > > > > > + >> > > > > > > > > + A JDBC PersistenceManager. >> > > > > > > > > + The "DataSource" reference should >> > > > refer >> > > > > > to >> > > > > > > > your datasource >> > > > > > > > > + configuration name. Check your >> > > > > > > > <datasource>-service.xml for the >> > > > > > > > > details >> > > > > > > > > >> > > > > > > > > - <!--mbean >> > > > > > > > >> > > > code="org.jboss.mq.pm.jdbc.PersistenceManager" >> > > > > > > > > + <mbean >> > > > > > > > >> > > > code="org.jboss.mq.pm.jdbc.PersistenceManager" >> > > > > > > > > >> > > > > > name="JBossMQ:service=PersistenceManager"> >> > > > > > > > > - <mbean-ref >> > > > > > > > >> > > > > > > >> > > > > > >> > > > >> > > >> > >> >>name="DataSource">JBossMQ:service=ConnectionFactoryLoader,name=NoTransDS</mbean-ref> >> > > > > > > > > + <mbean-ref >> > > > > > > > >> > > > > > > >> > > > > > >> > > > >> > > >> > >> >>name="DataSource">JBOSS-SYSTEM:service=ConnectionFactoryLoader,name=DefaultDS</mbean-ref> >> > > > > > > > > <mbean-ref >> > > > > > > > >> > > > > > > >> > > > > > >> > > > >> > > >> > >> >name="MessageCache">JBossMQ:service=MessageCache</mbean-ref> >> > > > > > > > > - </mbean--> >> > > > > > > > > + </mbean> >> > > > > > > > > + --> >> > > > > > > > > >> > > > > > > > > - <!-- >> > > > > > > > > - | InvocationLayers are the >> > > > different >> > > > > > > > transport methods that can >> > > > > > > > > + <!-- >> > > > > > > > > + | InvocationLayers are the >> > > > different >> > > > > > > > transport methods that can >> > > > > > > > > | be used to access the >> > server. >> > > > > > > > > --> >> > > > > > > > > <mbean >> > > > > > > > >> > > > code="org.jboss.mq.il.jvm.JVMServerILService" >> > > > > > > > > @@ -85,7 +92,7 @@ >> > > > > > > > > </mbean> >> > > > > > > > > >> > > > > > > > > <mbean >> > > > > > > > >> > > > code="org.jboss.mq.il.rmi.RMIServerILService" >> > > > > > > > > - >> > > > > > > > >> > > > name="JBossMQ:service=InvocationLayer,type=RMI"> >> > > > > > >> > > > > > > > > + >> > > > > > > > >> > > > name="JBossMQ:service=InvocationLayer,type=RMI"> >> > > > > > > > > <mbean-ref >> > > > > > > > >> > > > > > > >> > > > > > >> > > > >> > > >> > >> >name="JBossMQService">JBossMQ:service=Server</mbean-ref> >> > > > > > > > > <attribute >> > > > > > > > >> > > > > > > >> > > > > > >> > > > >> > > >> > >> >name="ConnectionFactoryJNDIRef">RMIConnectionFactory</attribute> >> > > > > > > > > <attribute >> > > > > > > > >> > > > > > > >> > > > > > >> > > > >> > > >> > >> >name="XAConnectionFactoryJNDIRef">RMIXAConnectionFactory</attribute> >> > > > > > > > > @@ -121,8 +128,8 @@ >> > > > > > > > > </mbean> >> > > > > > > > > --> >> > > > > > > > > >> > > > > > > > > - <!-- >> > > > > > > > > - | The following three line >> > create >> > > > 3 >> > > > > > topics >> > > > > > > > named: >> > > > > > > > > + <!-- >> > > > > > > > > + | The following three line >> > create >> > > > 3 >> > > > > > topics >> > > > > > > > named: >> > > > > > > > > | >> > > > > > > > > | testTopic, example, bob >> > > > > > > > > --> >> > > > > > > > > @@ -134,17 +141,17 @@ >> > > > > > > > > >> > > > > > name="JBossMQ:service=Topic,name=example"> >> > > > > > > > > <mbean-ref >> > > > > > > > >> > > > > > > >> > > > > > >> > > > >> > > >> > >> >name="JBossMQService">JBossMQ:service=Server</mbean-ref> >> > > > > > > > > </mbean> >> > > > > > > > > - <mbean >> > > > > > > > code="org.jboss.mq.server.TopicManager" >> > > > > > > > > + <mbean >> > > > > > > > code="org.jboss.mq.server.TopicManager" >> > > > > > > > > >> > > > name="JBossMQ:service=Topic,name=bob"> >> > > > > > > > > <mbean-ref >> > > > > > > > >> > > > > > > >> > > > > > >> > > > >> > > >> > >> >name="JBossMQService">JBossMQ:service=Server</mbean-ref> >> > > > > > > > > </mbean> >> > > > > > > > > >> > > > > > > > > - <!-- >> > > > > > > > > - | The following 9 line create >> > 9 >> > > > topics >> > > > > > > > named: >> > > > > > > > > + <!-- >> > > > > > > > > + | The following 9 line create >> > 9 >> > > > topics >> > > > > > > > named: >> > > > > > > > > | >> > > > > > > > > | testQueue, controlQueue, >> > A, B, >> > > > C, >> > > > > > D, >> > > > > > > > E, F, ex >> > > > > > > > > --> >> > > > > > > > > - <mbean >> > > > > > > > code="org.jboss.mq.server.QueueManager" >> > > > > > > > > + <mbean >> > > > > > > > code="org.jboss.mq.server.QueueManager" >> > > > > > > > > >> > > > > > name="JBossMQ:service=Queue,name=testQueue"> >> > > > > > > > > <mbean-ref >> > > > > > > > >> > > > > > > >> > > > > > >> > > > >> > > >> > >> >name="JBossMQService">JBossMQ:service=Server</mbean-ref> >> > > > > > > > > </mbean> >> > > > > > > > > >> > > > > > > > > >> > > > > > > > > >> > > > > > > > > >> > > > > > > > > >> > > > > > >> > _______________________________________________ >> > > > > > > > > Jboss-development mailing list >> > > > > > > > > >> > [EMAIL PROTECTED] >> > > > > > > > > >> > > > > > > > >> > > > > > > >> > > > > > >> > > > >> > > >> > >> >https://lists.sourceforge.net/lists/listinfo/jboss-development >> > > > > > > > > >> > > > > > > > > >> > > > > > > >> > > > > > > >> > > > > > > >> > > > >> > __________________________________________________ >> > > > > > > Do You Yahoo!? >> > > > > > > Find a job, post your resume. >> > > > > > > http://careers.yahoo.com >> > > > > > > >> > > > > > > >> > > > > >> > > > > >> > > > >> > >__________________________________________________ >> > > > >Do You Yahoo!? >> > > > >Find the one for you at Yahoo! Personals >> > > > >http://personals.yahoo.com >> > > > >> > > > >> > > > >> > >> >_________________________________________________________________ >> > > > Get your FREE download of MSN Explorer at >> > > > http://explorer.msn.com/intl.asp >> > > > >> > > >> > > >> > >__________________________________________________ >> > >Do You Yahoo!? >> > >Find the one for you at Yahoo! Personals >> > >http://personals.yahoo.com >> > >> > >> > >>_________________________________________________________________ >> > Get your FREE download of MSN Explorer at >> > http://explorer.msn.com/intl.asp >> > >> >> >>__________________________________________________ >>Do You Yahoo!? >>Find the one for you at Yahoo! Personals >>http://personals.yahoo.com > > > _________________________________________________________________ > Get your FREE download of MSN Explorer at http://explorer.msn.com/intl.asp > > > _______________________________________________ > Jboss-development mailing list > [EMAIL PROTECTED] > https://lists.sourceforge.net/lists/listinfo/jboss-development -- Jobba hos oss: http://www.tim.se/weblab ------------------------------------------------------------ Peter Antman Technology in Media, Box 34105 100 26 Stockholm Systems Architect WWW: http://www.tim.se Email: [EMAIL PROTECTED] WWW: http://www.backsource.org Phone: +46-(0)8-506 381 11 Mobile: 070-675 3942 ------------------------------------------------------------ _______________________________________________ Jboss-development mailing list [EMAIL PROTECTED] https://lists.sourceforge.net/lists/listinfo/jboss-development
