On Tue, Oct 5, 2010 at 8:46 PM, lexsoto wrote:
>
> Problem solved. Adding
> class="org.apache.camel.jboss.JBossPackageScanClassResolver"/>Fixes the
> problem for running inside JBoss container, but it breaks the unit test.
> Separated this bean definition to its own separate file so it does not
Problem solved. Adding
Fixes the
problem for running inside JBoss container, but it breaks the unit test.
Separated this bean definition to its own separate file so it does not get
used during unit test.
--
View this message in context:
http://camel.465427.n5.nabble.com/Split-XPath-JBoss-tp3198
Hi Claus,
I think I am getting close. With the jbossResolver resolver I get:
13:09:47,659 DEBUG [DefaultTypeConverter:379] Loading type converters ...
13:09:48,107 DEBUG [DefaultTypeConverter:390] Loading type converters done
13:09:48,109 INFO [DefaultTypeConverter:394] Loaded 0 type converters
Don't assume you XML is gone. Its just that the DOM in Java has a way
of not showing the XML content but just the NodeList or something like
that.
On Tue, Oct 5, 2010 at 6:20 PM, lexsoto wrote:
>
> I am sorry I still need help with this.
>
> I have enabled logging and tracing during unit test.
I am sorry I still need help with this.
I have enabled logging and tracing during unit test.
I can see my XML message as is routed. The last time I see the XML body is
when it is sent to the split component:
[Tracer:88] 77fdf366-9dfc-414c-a7d7-6a687f24d078 >>> choice --> split[XPath:
/message/b
I did not see this FAQ before.
Funny thing is now that I added this dependency, the unit test fails exactly
the same way as my integration test was. I suppose it is a good thing
because at least I get consistent results. Hopefully now I will be able to
troubleshoot better.
Thank you very much f
And you have seen this FAQ?
http://camel.apache.org/how-do-i-run-activemq-and-camel-in-jboss.html
You must use the camel-jboss component when running in JBoss.
On Mon, Oct 4, 2010 at 9:44 PM, lexs...@gmail.com wrote:
>
> Hi,
>
> I have this split route that works well during unit testing, but no
More findings. I've Modified my bean method to this:
public void processImprint(Node node) throws TransformerException
{
TransformerFactory transfac = TransformerFactory.newInstance();
Transformer trans = transfac.newTransformer();
trans.setOutputProperty(OutputKeys.INDENT, "yes");
