Hi Simon,

I checked out the code from EIDER branch, and made some changes.
Also I wrote some test cases for the message binding.

I've just uploaded a patch file patch.txt, which includes the changes
and test cases.

Thanks

Jack

On Jul 24, 9:33 am, [EMAIL PROTECTED] wrote:
> On 9 Jul, 14:57, Jack Zai <[EMAIL PROTECTED]> wrote:
>
>
>
>
>
> > My binding is not only a proxy to a JMS service, but also for exposing
> > a RPC-style message service. For example, assume we have a SCA file
> > MyService.php with soap binding. We can replace the annotation
> > @binding.soap with @binding.ms plus some config information about the
> > target queue.  Now, if we issue command >php MyService.php, the
> > service will be started by running a listener to the target queue.
> > then incoming JMS messages at the target queue will be processed by
> > the wrapper and pass on to appropriate operation of the service. So in
> > this case, the message sender could be a non-SCA JMS client.
>
> > In addition, I am sorry for the wrong link to the spec, which should
> > be as below :
> > [pdf]http://www.osoa.org/download/attachments/35/SCA_JMSBinding_V100.pdf?v...
>
> > On 6 Jul, 17:04, Caroline Maynard <[EMAIL PROTECTED]> wrote:
>
> > > Jack Zai wrote:
> > > > Unlike any of other bindings, where an http server is used for
> > > > listening to the ports, for the ms binding, a service is started from
> > > > a console (e.g. > php myservice.php). Once the service is started, it
> > > > will keep trying to get message from the queue, and it can be
> > > > terminated by pressing <Ctrl> + <C>.
>
> > > Can you explain a bit more? In an enterprise environment I would imagine
> > > the JMS service being started by some mechanism outside the scope of
> > > your binding. So your command-line service, is that just a way to
> > > bootstrap a JMS service locally?
>
> > > I'm assuming that your SCA binding is a client only, that is, it
> > > provides an SCA proxy to a remote JMS service, but not a wrapper for a
> > > local service to be exposed to non-SCA JMS clients. Is that right?
>
> Hi Jack
>
> Sorry this took such a long time for me to get to. I've just checked
> your code in. Thank you.
>
> I've changed the binding name from "ms" to "message". I think the
> latter is a little more meaningful.
> I've fixed up the class names etc but am unable to run/test it as
> there are no test cases included
>
> Based on the checked in code can you construct some test cases fur us?
>
> Also I've created a new link on the web site [1] for the documentation
> for this binding. If would be great if you could write a few words
> describing how to use the binding and what its various features are.
> We can then put that up there.
>
> Regards
>
> Simon
>
> [1]http://www.osoa.org/display/PHP/SCA+with+PHP- Hide quoted text -
>
> - Show quoted text -


--~--~---------~--~----~------------~-------~--~----~
You received this message because you are subscribed to the Google Groups 
"phpsoa" group.
To post to this group, send email to phpsoa@googlegroups.com
To unsubscribe from this group, send email to [EMAIL PROTECTED]
For more options, visit this group at 
http://groups.google.co.uk/group/phpsoa?hl=en
-~----------~----~----~----~------~----~------~--~---

Reply via email to