Guillaume,
Thank you for your help! It was due to a typo: the achive-wiretap-in
should have been archive-wiretap-in.
Another question: is the jbi.xml file in the SU archive really
necessary? The application seems to keep on working correctly, even if
the jbi.xml files are not updated...
Gert
Guillaume Nodet wrote:
These exceptions are thrown when a component sends a JBI exchange
to a service name, but there is no endpoint with the given service name.
Make sure the target endpoint of the Wire Tap exists and that namespaces
do match.
On 2/13/07, Gert Vanthienen <[EMAIL PROTECTED]> wrote:
L.S.,
I am trying to build an application which:
- polls several FTP servers for XML files
- transfers these files to a single (other) FTP server
- saves a copy of the files transferred in an archive directory
I had a working solution for the FTP transfers, using a simple xbean.xml
file in a single SU (containing only <ftp:sender/> and <ftp:poller/>
elements). To make the archiving work, I added two SUs to my SA:
- one SU, containing a <file:sender /> to save the file to the archive
directory
- one SU, containing an <eip:wiretap/> to enable saving the file while
sending it to the other FTP server
Now, the FTP poller does it's job, but when it encounters an XML file, I
get these messages:
ServiceName ({http://www.javafresh.eu/servicemix}achive-wiretap-in)
specified for routing, but can't find it registered
Failed to process file: /in/<name of file>.xml. Reason:
javax.jbi.messaging.MessagingException: Could not find route for
exchange: ...
I already added a META-INF/jbi.xml file to every SU zip file, containing
a <services/> element with <provides/> and <consumes/> elements for the
'services' contained in and required by every SU.
What am I missing here?
Gert
