Sorry about that, I edited the log text on Nabble straight after I
realised it was truncated replacing with the full text. I am accessing
this list on the Web (Nabble) not via email. So I guess you did not see
the correction. I am trying this now as an email test.

I am hoping to contribute to this list and to Synapse but unfortunately
I have not been able to resolve most of the issues posted. If I ever get
these working, I will contribute the solutions and help improve the
documentation.

I do not understand your response below and still cannot understand what
"context-name" does even after reading the
"Configuration guide" again ? 
Isn't the property name = "string" the literal name of the variable ?
It took me a few minutes to get my Class mediator working but I still
cannot get the POJOCommand to work.
I think the only solution is to look at the source for POJOCommand to
work out what "Context-name" is used for. 

You must understand that when people write software It is very clear to
them how it works. However outsiders have no idea. Encapsulation only
works when the contract (API) is well explained. So My dilemma (and many
other people trying to use synapse) is that I am trying to understand
Synapse, from the outside, but I do not have access to the knowledge
required. At the moment this knowledge only resides in the Synapse
Authors heads (and in the low level code). The Synapse world is steeped
with Jargon that the authors are familiar with but not us outsiders. I
am not sure how to overcome this dilemma.  Seems to be a Catch 22. 

So I am trying to construct the Use Cases for a POJOCommand, given
fragments of information, but my ones are obviously different to the
authors. The person that created POJOCommand has these use cases in
their head but no one else. I guess POJOCommand was created to solve a
real problem; a set of use case scenarios which are examples. However I
have no access to these.

Our development team uses many open source products here. I am not being
critical but Synapse stands out in that a number of developers here have
looked at Synapse and have given up; not being able to comprehend it.

So it is hard for people to make contributions when they can't get past
square one. Maybe a solution is a Synapse beginners email list; so
people new to Synapse can ask these "obvious" questions until they
become expert enough to contribute.






-----Original Message-----
From: Asankha Perera [mailto:[email protected]] On Behalf Of
Asankha C. Perera
Sent: Tuesday, 10 March 2009 8:23 PM
To: [email protected]
Subject: Re: POJOCommand Fails

> 2009-03-10 17:17:23,068 [192.168.0.204-icsws-kh] [HttpServerWorker-1]
ERROR
> POJOCommandMediator Error invoking setter method named : setUsernam
> t takes a single String, int, long, float, double or boolean parameter
> java.lang.NullPointerException
>   
This log is really difficult to read since its truncated along the 
width. Please "attach" log files etc into the email in future, and 
truncate any unnecessary parts out of them if they are large, before 
being attached.

http://www.catb.org/~esr/faqs/smart-questions.html
"/However, do /not/ wrap data (such as log file dumps or session 
transcripts) at any fixed column width. Data should be included as-is, 
so respondents can have confidence that they are seeing what you saw./"

Also keep the emails easy to read and reply to, since this is not the 
bug tracking JIRA; but a mailing list read by a people who are 
contributing time voluntarily, and we prefer emails with a courteous 
human touch :-)
>     <pojoCommand name="net.icsglobal.thelma.synapse.testPOJO">
>       <property name="username" context-name="literal"
> action="ReadAndUpdateContext">Fred</property>
>     </pojoCommand>
>   
The context name expects you to provide the literal name of a variable 
(e.g. property set before along the sequence) or an XPath over the 
message payload. So context-name="literal" is wrong.

You are free to provide us with a patch to improve the current 
documentation, and even add some more samples so that it will help 
another who encounters the same issue. Open source projects thrive when 
you give something back for what you get for free.

cheers
asankha

-- 
Asankha C. Perera
AdroitLogic, http://adroitlogic.org

http://esbmagic.blogspot.com




Reply via email to