You need to have the spring-ws-samples project built and available in your local maven repository. Run mvn install from the top level samples/ directory.
For working with a milestone code...
Type: Posts; User: robododge; Keyword(s):
You need to have the spring-ws-samples project built and available in your local maven repository. Run mvn install from the top level samples/ directory.
For working with a milestone code...
Did you see the section on automatic WSDL exposure? http://static.springsource.org/spring-ws/sites/2.0/reference/html/server.html#server-automatic-wsdl-exposure ... Scroll down a few paragraphs...
Hey Rick,
Thanks for the contribution. I'm trying to run your example code, it seems you've left out a few java source files in your zip.
Missing Classes:
forums.scope.domain.Recipe...
Costin
Thanks for your efforts addressing these issues, it is greatly appreciated. I got your code updates from the main Spring CVS @ sourceforge. I'll be reporting back to the JIRA if...
Your're right, I need to re-work this using the BeanFactoryLocator as a delegate. I'd use the BeanFactoryRefrence to hold a reference to the ApplicationContext. I should be able to put that...
I'm using the current sping-jBPM module with jBPM 3.0. I think this version will suffice for the near future util jBPM 3.1 comes out. I posted to the jBPM developer forum regarding the...
Costin, I've tried contacting Rob about this, you're assumption is correct, he must be very busy. Therefore, I've moved along making my own changes in hopes Rob might be able to use them later.
...
I was wrong about the Toolbox.xml approach with VelocityTools, it only supports a Servlet environment. So the toolbox is not an option. I went ahead and implemented my own...
I want to use Spring's embedded Velocity template support to produce formatted e-mail messages. This is not a web app, so I loose all benefits of the extensive Velocity MVC. I can obtain a...
I think this is wrong. You should use url to specify the name of the content template. In your case, if the context template resides at /WEB-INF/views/content1.vm then you could simply type the...
Thanks Rob
First you have to fix the syntax error in JbpmTemplate line 170 missing semicolon.
Turns out you'll need at least Ant 1.6.2 to run the junit tests. I did the following using Ant 1.6.5 embedded...
On the topic of ApplicationContext, Matt already created a feature request, it's just in the wrong place.
http://opensource2.atlassian.com/projects/spring/browse/SPR-1320
I posted a bug regarding...
Costin,
I've been using spring-jbpm since Sep 15th and I haven't seen any new code checked in since then. I have a few suggestions for the current code. One suggestion is regarding access to the...
Hey,
You need to try the spring-jbpm module. Right now its in spring-projects/spring-jbpm in the main springframework CVS.
I've been using it with great results.
I agree that you want to group your service layer entry points in groupings of methods with like functionality. This keeps things logical. Also, you don't end up with that mega-service object or...
Julian,
I throughly tested the spring-jbpm module. Rob Harrop told me its still a work in progress, but everything including transaction management is working quite well for me. I've tested...
The concurrency issue goes away if I don't use JaxRpcPortProxyFactory and communicate with the web service via a standard dynamic proxy.
No concurrency issues arise using the javax.xml.rpc.Service...
I'm using the JaxRpcPortFactoryBean for calling a JAX RPC webservice. I've strayed from the basic usage scenario outlined in Chapter 17.5.2 of the Spring 1.2 Refrence Docs. I've used a Jboss...
This error is comming from the JK Coyote connector. It looks totally un-related to the ResourceBundleViewResolver. What servlet container are you using? Is it necesary that you run the Coyote...
It looks like you have things setup properly, except possibly the form's request type. The request type is usually of type POST or GET. You should explicitly set the request type on your form to...
Thanks Olivier, I now understand the reasoning.
I agree with you about older non-2.4 conmpiant containers being a good reason to stick with JSTL 1.0. But I don't agree with one statement.
JSTL 1.1 is backward compatible with servlet spec...
Greetings,
Moving into spring MVC over the past couple of days, I quickly found that Spring 1.1 and 1.1.1 both are packaged with the older jstl.jar and standard.jar for JSTL 1.0. This causes some...