Peter Antman wrote:
> > What is ASF? Is this a public API?
>
> It's a JMS Application Server API, defined and explained in chapter 8 of
> the jms 1.0.2 specification.
>
> The basic reason behind it is - as far as I understand - the following:
>
> A JMS Session may not be threaded. If you want cocurrency you will have
> to create one session per thread. Say you have 10 messages send per
> second, but that every message takes 1 second. Then you would generally
> like to have more sessions to be able to serve the messages somwhat
> faster. This is what MessageDriven beans should handle. Problem is: how
> is the client to know how many messages that are waiting? You could try
> to figure out some slick algoritm. But there already exists an API in
> JMS for this: ASF. The application server must define a ServerSession
> and a ServerSessionPool. For JMS-services that support AFS it will have
> the imlementation to use this via its ConnectionConsumer and Session.
>
> If I have understod it correctly, not all JMS providers have done this.
> Bea has, openjms have, but not SpyderMQ for example ( I have realy
> tried to do my homework in this ;-)).
I see. Makes sense. I looked for that, but my JMS spec was too old.
> The way I have think about it is that you will have to have a special
> CI for every type of MOM-system, since the setup will be done in the CI
> (connection, creation of listeners ...), but when it invokes the
> Interceptor chain it will do this via the standard MethodInvokation.
Exactly.
> > Yup. I am working on a metadata rewrite, and am currently looking at EJB
> > 2.0 extensions.
>
> We will probably do some interlapping work then. I have already written
> a MesageDrivenMetaData, and changed the ConfigurationMetaData and
> ApplicationMetaData classes. I have not done the jboss specific stuff
> yet though.
Alright, I see. Don't overdo the metadata stuff, as I will be covering
that base from here.
> I have also rewritten the ContainerFactory, added a
> MesageDrivenContainer, MesageDrivenEnterpriseContext,
> MessageDrivenContainerInterceptor, MessageDrivenInstancePool (taken from
> memory - the implementation is on my home computer).
Sounds good. What does the MDCI do?
> Whats basically left in the ContainerInvoker - and testing ofcource
> ;-)
Oh, that little detail.. ;-)
> >> Well, more will probably pop up. Give me a week or to and we will see (I
> >> only have time to spend one hour or two each evening when my kids have
> >> gone to sleep).
> >
> > If you have any further questions, let me know. Eventually you will have
> > access to the proper metadata from the XML, but for now just use some
> > hardcoded values or similar.
> >
> > And good luck! :-)
>
> Thank you. Hope it will work in the end! (I will probably also write an
> MBean for openjms - but this will come later).
Alright, sounds good.
Keep me/us posted about your progress!
regards,
Rickard
--
Rickard �berg
Email: [EMAIL PROTECTED]
http://www.telkel.com
http://www.jboss.org
http://www.dreambean.com
--
--------------------------------------------------------------
To subscribe: [EMAIL PROTECTED]
To unsubscribe: [EMAIL PROTECTED]
Problems?: [EMAIL PROTECTED]
