On 25 Jul, 17:02, Jack Zai <za... hotmail.com> wrote:
> 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, simonsl...googlemail.com wrote:
>
> > On 9 Jul, 14:57, Jack Zai <za...hotmail.com> 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
<c...php.net> 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]htt
p://www.osoa.org/display/PHP/SCA+with+PHP-Hide quoted
text -
>
> > - Show quoted text -
Jack, sorry this took me a month to get to. Heads down doing
Java
releases. Anyhow I have applied the patch locally and am
seeing
notices when I run the tests which I assume are because I
haven't yet
configure SAM in my PHP installation..
...I...........I.......PHP Notice: Use of undefined
constant SAM_HOST
- assumed
'SAM_HOST' in
C:simonProjectsTuscanyphpbranch-buildpeclsdo
testsSCAphp
unitMessageBindingMSTest.php on line 46
PHP Notice: Use of undefined constant SAM_PORT - assumed
'SAM_PORT'
in C:simon
ProjectsTuscanyphpbranch-buildpeclsdotestsSCAphpuni
t
MessageBindingMST
est.php on line 46
PHP Notice: Use of undefined constant SAM_BROKER - assumed
'SAM_BROKER' in C:s
imonProjectsTuscanyphpbranch-buildpeclsdotestsSCAph
punit
MessageBinding
MSTest.php on line 46
PHP Notice: Use of undefined constant SAM_ENDPOINTS -
assumed
'SAM_ENDPOINTS' i
n
C:simonProjectsTuscanyphpbranch-buildpeclsdotestsSC
Aphpunit
MessageB
indingMSTest.php on line 46
PHP Notice: Use of undefined constant SAM_TARGETCHAIN -
assumed
'SAM_TARGETCHAI
N' in
C:simonProjectsTuscanyphpbranch-buildpeclsdotestsSC
A
phpunitMess
ageBindingMSTest.php on line 46
PHP Notice: Use of undefined constant SAM_BUS - assumed
'SAM_BUS' in
C:simonP
rojectsTuscanyphpbranch-buildpeclsdotestsSCAphpunit
MessageBindingMSTes
t.php on line 46
PHP Notice: Use of undefined constant SAM_USERID - assumed
'SAM_USERID' in C:s
imonProjectsTuscanyphpbranch-buildpeclsdotestsSCAph
punit
MessageBinding
MSTest.php on line 46
PHP Notice: Use of undefined constant SAM_PASSWORD -
assumed
'SAM_PASSWORD' in
C:simonProjectsTuscanyphpbranch-buildpeclsdotestsSC
Aphpunit
MessageBin
dingMSTest.php on line 46
PHP Notice: Use of undefined constant SAM_CORRELID -
assumed
'SAM_CORRELID' in
C:simonProjectsTuscanyphpbranch-buildpeclsdotestsSC
Aphpunit
MessageBin
dingMSTest.php on line 46
PHP Notice: Use of undefined constant SAM_DELIVERYMODE -
assumed
'SAM_DELIVERYM
ODE' in
C:simonProjectsTuscanyphpbranch-buildpeclsdotestsSC
A
phpunitMe
ssageBindingMSTest.php on line 46
PHP Notice: Use of undefined constant SAM_TIMETOLIVE -
assumed
'SAM_TIMETOLIVE'
in
C:simonProjectsTuscanyphpbranch-buildpeclsdotestsSC
A
phpunitMessag
eBindingMSTest.php on line 46
PHP Notice: Use of undefined constant SAM_PRIORITY -
assumed
'SAM_PRIORITY' in
C:simonProjectsTuscanyphpbranch-buildpeclsdotestsSC
Aphpunit
MessageBin
dingMSTest.php on line 46
PHP Fatal error: Class 'SAMMessage' not found in
C:simonProjects
Tuscanyphp
branch-buildpeclsdotestsSCAphpunitMessageBindingMSTes
t.php on
line 52
Before I go and do that I need to ask the question about
whether we
want to make SAM a mandatory dependency. It maybe more
appropriate to
have the tests raise a warning it SAM is not configured and
skip onto
the next tests so that people without SAM are able to see
the full
picture.
Also I note that some of the test files don't have
copyright
headers.
As it's a month since you posted this do you have more
changes to
submit and if so do you want me to apply these changes and
then some
more or do you want to submit a new patch against FULMER
with all of
the changes. Happy to do whichever is easier for you.
Thanks
Simon
--~--~---------~--~----~------------~-------~--~----~
You received this message because you are subscribed to the
Google Groups "phpsoa" group.
To post to this group, send email to phpsoagooglegroups.com
To unsubscribe from this group, send email to
phpsoa-unsubscribegooglegroups.com
For more options, visit this group at http://
groups.google.co.uk/group/phpsoa?hl=en
-~----------~----~----~----~------~----~------~--~---
|
