[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
Re: ANN: XmlBlasterK2
pra at mint.se wrote:
Thanks a lot Peter, a little step for you, a big one for man kind ;-)
I have a little wish list remaining:
1. Could you please add a new requirement into
You can call it j2ee.connector.xml or something similar.
Please describe in simple words the motivation for the connector,
and what it is able to do for humans.
Please add a step by step example into the <example> section
how to install it.
Please add some little demo code into this example how to
use it (publish some data).
(Just similar to your README and README.jboss)
You can compile this xml file to html with 'make doc'
if you use a UNIX box (just to check how it looks like).
2. Add a short note into xmlBlaster/CHANGES about this new feature
3. How does this connector fit into our "Architecture and state of
image (see the link on our homepage).
4. It would be nice if you can draw a little image
showing how this connector fits into the 'big picture'
We could place this on our homepage or include it into
the requirements file from above.
5. Could you please add a README into
telling in a few words how to use the demo and what they do?
6. Is it possible to integrate a fully automated test to our
testsuite to assure that the connector is not broken on future
changes? (see our 'Guideline' link on the homepage).
> I have now added the new J2EE Connector resource adapter for XmlBlaster
> into the cvs tree.
> The main code is under src/java/org/xmlBlaster/j2ee/k2
> And there is some demo in demo/javaclients/j2ee/k2
> There is also two new targets in the build: k2 and jms-adapter.
> The J2EE Connector resource adapter will be produced in
> lib/xmlBlasterK2.rar and the demo bean in lib/JmsAdapter.jar
> Ok. I have seen the discussions on the list (I am not a member so I did
> not see it until now). What is a Connector resource adapter?
> The J2EE Connector is a specification of a way to integrate connectors
> to other datastorage than relational databases. It specifyes a contract
> beween an application server vendor and a storage vendor. The storage
> vendor provide a resource adapter that conforms to the Connector API and
> the application server vendor provides an implemention of the server API
> to support lifecykel management, pooling, security, transactions and so
> One nice thing about Connectors (compared to different non standard
> solutions) is that deployment (puting it into the application server
> runtime) and the API to get access to it from within a J2EE environment
> is standardized.
> For MOM stuff the connector API is interesting from two perspective:
> 1. It is for *publishing* only (not subscribing)
> 2. You get access to it in your bean the same way you get access to a
> JDBS database connection.
> The XmlBlasterK2.rar now works with JBoss (deploys fine in JBoss), but
> should work with any application server supporting J2EE Connector. This
> mean that in these environments, getting access to XmlBlaster will be an
> easy task.
> If you need to subscribe to XmlBlaster from within a J2EE runtime? This
> is not possible today, since EJB do not allow asynchronous handling.
> This is what Message Driven Beans are for. The may *recive* asynchronous
> My plan is to implement support for XmlBlaster based Message Driven
> Beans in JBoss (I have already done that for JMS). By this I mean: I
> will implement an MDB container that may subscribe to XmlBlaster and
> invoke beans with a XmlBlaster message. The beans them self will
> theoretically be able to use another application server, but the
> container (where the meat is) will be tightly coupled to JBoss.
mailto:ruff at swand.lake.de