Search:

I'm encountering a problem with Axiom 1.2.5 on the server side which I don't get with SAAJ. I want to return a SOAP fault from my endpoint which I consume with WebServiceTemplate.

With Axiom I get...

Hi all,

I wrote a TaskExecutor for GridGain. GridGain is the easiest way to set up a grid computer for Java applications.

With this implementation you can send Runnable objects over the network...

After I call the refresh() method on FlowDefinitionRegistryImpl I get an exception on Flow:328, namely IllegalArgumentException, when the current state of the current FlowExecution is no longer...

There's a new Spring Web Flow article on Javalobby.

The Persistent Object Life-cycle Event Validation (POLEV) pattern is an implementation currently residing in the Spring Modules sandbox. This pattern offers validation of persistent objects when ORM...

You need a transaction manager to manage XA transactions. Take a look at JOTM.

If you use a XA capable transaction manager and your JMS provider and database both support XA transactions you should configure JtaTransactionManager in your Spring setup.

You need to use HibernateTransactionManager in conjunction with HibernateTemplate to enable declarative transaction management. Take a look at this section of the Spring reference for more...

You cannot achieve the same with Struts with so little effort. A page flow in SWF operates under one URI, including sub page flows and their sub page flows and their sub page flows and so on. SWF...

Say you build a page flow to select a customer that allows you to search you existing customer base in a number of ways, allows you to create new customers, etc.

You can reuse this page flow...

Try using DriverManagerDataSource.

I've added support for OGNL expressions and created a convenience class TouchingNameMethodMatchAdvisor. If collections are returned you can use the #returned variable in OGNL expressions:


...

TouchingAfterReturningAdvice offers an alternative to the open session in view pattern in that it touches configurable properties on the return value of method invocations. This advice is available...

That's a valid point. Standard Java deserialization uses the thread context loader. Spring could solve this issue but this hasn't happened so far. I've created a JIRA issue.

You may want to take a look at Spring Web Flow. It solves issues related to state elegantly.

The code below works in an Eclipse plug-in.



ApplicationContext appCtx = new ClassPathXmlApplicationContext("applicationContext.xml") {
public ClassLoader getClassLoader() {
return...

You cannot prevent interceptor invocation on every method of the exposed interface. You can however control the invocation:



public Object invoke(MethodInvocation invocation) throws...

Take a look at org.springframework.aop.framework.AopContext and org.springframework.aop.framework.ProxyConfig#setExposeProxy(boolean).

Scott,

Rod Johnson thinks Spring should only encapsulate the ugly details of persistence but certainly not all of it. I do agree with him this would not be one of Spring's core tasks.

Myself...

There's an article on the Spring Modules wiki on Valang validator. It discusses usage, features and syntax.

Maybe this will work for you:



<bean name="CA_dataSource" class="...">
properties ...
</bean>

<bean name="dataSourceMap" class="java.util.HashMap">
<constructor-arg>

If I change this so that onMessage() calls a processMessage() method on another bean, the proxy should then see exceptions thrown from the latter, right? So the proxy doesn't affect the inner...

If I change this so that onMessage() calls a processMessage() method on another bean, the proxy should then see exceptions thrown from the latter, right? So the proxy doesn't affect the inner...

You may want to take a look at Spring WebFlow which by default stores command objects in the request scope.

The checked exception is never thrown by the onMessage method, as illustrated in the code example.