----- Original Message -----
Sent: Tuesday, February 07, 2006 10:52
PM
Subject: Installing Synapse - feedback
2/2
Hi folks,
In continuation to my previous email (26/01/2006), here's another email
regarding the installation process with Maven, and my first go at
samples.
A. Using the Synapse snapshot (latest being the
M1)
(previous
email)
B. Using maven to build the binary (in WinXP
SP2)
I downloaded the whole project from the SVN repository,
opened a console, went to c:\synapse\trunk\java, and ran:
maven dist-bin.
This worked only with Maven 1.02, a fact that Paul later on confirmed.
This issue aside, the compiling and the battery of junit tests went just
fine.
I then decided to deploy Synapse in my Tomcat installation in lieu of
running the standalone server. (albeit I also ran the standalone server which
works just fine).
C. Running the samples
I've then tried running the samples using Synapse deployed in
Tomcat.
Secondly I tried running the first sample as stated in the
README.txt file which can be found in the samples folder of
the binary install. It states we should use Apache Ant 1.5 and above:
I
currently use ant 1.6.5.
Following step: type in ant of course which brings a series of messages
explaining how to run the samples.
Example: ant stockquote
Running this returns
org.apache.axis2.AxisFault:
com.ctc.wstx.exc.Wstx.UnexpectedCharException: Unexpected character d (code
100).
I've attached the full error the call causes.
Any ideas on this?
As far as
the online user guide is concerned (http://wiki.apache.org/ws/Synapse/UserGuide),
the Samples section is a bit unclear when it comes down to running the samples
themselves. The user guide doesn't mention the use of ant at
all...
When one tries to run java StockQuoteClient IBM http://www.webservicex.net/stockquote.asmx, he/she
gets the common java.lang.NoClassDefFoundError: StockQuoteClient
error. I've tried to work around it but I then get the following
error: java.lang.NoClassDefFoundError: StockQuoteClient (wrong name:
samples/userguide/StockQuoteClient)
Once again, this is a very basic error, and I'm probably forgetting
something very obvious.
Thanks again for your help.
David Brossard, MEng
Research Professional, Security Research
Centre
BT Group Chief Technology
Office
___________________________
pp2A
Rigel
House
Adastral Park
Martlesham Heath
Ipswich
Suffolk IP5
3RE
United Kingdom
Office: 01473 642930
Mobile: 07906 692612
Fax : 01473
649546
Email: [EMAIL PROTECTED]
British Telecommunications plc
Registered office: 81
Newgate Street London EC1A 7AJ
Registered in England no. 1800000
This electronic message contains
information from British Telecommunications plc which may be privileged or
confidential. The information is intended to be for the use of the
individual(s) or entity named above. If you are not the intended recipient be
aware that any disclosure, copying, distribution or use of the contents of
this information is prohibited. If you have received this electronic message
in error, please notify us by telephone or email (to the numbers or address
above) immediately.
Activity and use of the British
Telecommunications plc email system is monitored to secure its effective
operation and for other lawful business purposes. Communications using this
system will also be monitored and may be recorded to secure effective
operation and for other lawful business purposes.
Title: Improving the way we do references [task2 of M2 todo
list]
Current implementation of Synapse, we could have two types
of mediators.
1.IN-LINE
mediators
2.REFERENCE mediators
In-line
mediators have the following syntax
<foo name="fooMediator"
parm1="dosomething1" parm2="dosomething2"../>
In-line mediators have
always get executed and need NOT to have @name. So following syntax should
have been appropriate for in-line mediators.
<foo
parm1="dosomething1" parm2="dosomething2"../>
<never/> tag is
used to hold a set of mediators that is not going to execute directly.
Those mediators have to be referenced by a in-line mediator. As the
<never/> tags holds a list of mediators that can be referenced, lets
replace this by <define/>.
<define/> has the
following syntax
<define
name="name_of_define_mediator">
<mediator1/>
...
...
<mediatorN/>
</define>
So any
in-line mediator can call the <define/>'s @name to get it execute. So
there can be any number of <define/> tags exists in synapse.xml.
Lookup for the <define/> tag can be done with <ref/> tag
and these references will be stored in our good old SynapseEnvironment.
<define/> tags can be referenced either in IN or OUT path. We
need a clear distinction of IN and OUT.
Please be kind enough to
express your consensus on prior.
Thank you
Saminda
---------------------------------------------------------------------
To
unsubscribe, e-mail: [EMAIL PROTECTED]
For additional
commands, e-mail: [EMAIL PROTECTED]
