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 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 :

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?

You received this message because you are subscribed to the Google Groups 
"phpsoa" group.
To post to this group, send email to
To unsubscribe from this group, send email to [EMAIL PROTECTED]
For more options, visit this group at

Reply via email to