Apache camel

Apache camel is very cool in some sense that, it might be working like spring integration, or more as a enterprise integration pattern.

If with spring, it starts from camel context. Like spring application context. Within the camel context, the route builder should be specified. Key method within this route builder is the configure method.

Normal pattern is like from(one endpoint).bean ref(bean name, method).to(another endpoint) within the configure method.

The endpoint can be mq, timer, ejb etc.

The route builder will listen to the queue, for example, then upon any message comes, it will invoke the method of the bean, and possibly would send to another queue for example.

why annotated enity is not loaded in exploded jar?

why annotated enity is not loaded in exploded jar?

while the same works in non-exploded jar?? why ?


finally it’s solved.

LocalEntityManagerFatcoryBean, invokes its persistent provider (HibernatePersistence here), which in turn invokes EjB3Config, which invokes ZippedJarVisitor (dependent on the URL protocol, vzsfile). The ZippedJarVisistor would scan and add the Entity annotated entities. However, it would skip, if it’s a directory.

Solution is, within persistent.xml, specifiically tell persistent-unit, that to scan and add com.abc.UserClass which is the entity.

<persistent-unit ..> < include-class > com.abc.UserClass </include-class > </persistent-unit >

Another conclusion is, follow the exception, follow the trace, trace from top to bottom following stack trace.

Zk framework

I am currently studying Zk framework. Let’s see how fast and how well Ill grab it.

I still can’t appreciate the fancy of such framework. Instead of ZK’s new language, why not we ourselves pick up javascript, jquery ourselves. Why not we have our own say, instead of letting ZK control. Plus there is a performance impact using its translation mechanism.