The documentation says that camel-spring-ws(v2.7.1) officially supports spring-ws 1.5.9, but doesn't mention spring-ws 2.0.2.RELEASE. I'd like to stick with 2.0.2.RELEASE instead trying to retrofit 1.5.9 to work with Spring 3.0, but I'm hitting enough roadblocks to make me think that it's just not going to work.
Has anyone been successful with this?
Thanks,
Roy
There is a ticket to upgrade to use Spring 2.0.2. The was a bug in Spring WS 2.0.0 and 2.0.1 releases in terms of not working with OSGi. That should hopefully be fixed in Spring WS 2.0.2.
If you are not using OSGi you can most likely manually upgrade to Spring WS 2.0.x. But it requires a bit of work as some JARs have changed and whatnot.
Camel 2.8 should use the Spring WS 2.0.2 by default.
The ticket is here: https://issues.apache.org/jira/browse/CAMEL-3735
Related
I have a number of Grails apps running with 2.2.5. I've been considering upgrading them to Grails 3, but I'm worried about plugin compatibility, most notably to do with the Shiro plugin which I use. From the plugin page I'm not convinced that it has been updated yet to work with Grails 3. Is there anyone out there using Shiro with a Grails 3 app successfully?
The discussions regarding Shiro Grails 3 support is on going on Github Shiro Page. As per the thread, it is not fully ready and developers are looking for help. Some of the developers were successful on developing a Shiro Plugin for Grails 3. However it lacks proper documentation and a sample demo application support.
I too had a dilemma of this when upgrading Grails 2.x to 3.x. What, I did was use the Spring-Security-Shiro plugin. It uses a hybrid approach combining Spring Security and Shiro Security, and proved to be handy.
I've just recently started working with Grails, and I'd like to test out the Spring Security Plugin. I'm using Grails v3.0.0RC2, and I'm finding it difficult to come across accurate documentation for it with a lot of things.
I'm looking at the Grails page for the Spring Security Plugin, located at http://grails.org/plugin/spring-security-core, and it tells me to add the following to grails-app/conf/BuildConfig
plugins {
…
compile ':spring-security-core:2.0-RC4'
…
}
Now, Grails 3 has done away with the BuildConfig, and moved over to using Gradle. So I figured I could just that compile line to my "dependencies" section in build.gradle and it would work, like so:
dependencies{
...
compile:":spring-security-core:2.0-RC4"
}
However, that did not work. I get the error "Could not find :spring-security-core:2.0-RC4...".
Then I figured, 'Hey, it's a plugin, let me try prefacing it with "org.grails.plugins" like I see elsewhere in the build.gradle file:
dependencies{
...
compile:"org.grails.plugins:spring-security-core:2.0-RC4"
}
And still no go.
I have gotten it to compile by adding the dependency found on search.maven.org, like so:
dependencies{
...
compile 'org.springframework.security:spring-security-core:4.0.0.RELEASE'
}
But I don't think thats the proper way to do, because Grails documentation says I should have access to the command
grails s2-quickstart
once the plugin is installed, which I do not when I do it using the Maven repo.
I'm sure there's a simple configuration error I'm making, as I'm very new to both Grails, Spring, and Gradle, so I appreciate any help that can be provided.
The Spring Secuirty core plugin for Grails is not Grails 3 compatible. However, since Grails 3 is based on Spring Boot you can use the Spring Security Starter for Spring Boot instead.
This has been discussed on the Grails developers mailing list and going forward many Grails plugins will not be moved to Grails 3 and instead will be replaced by pure Spring solutions.
Update
Since this question was originally asked there has been a Spring Security plugin created for Grails 3.x. It can be found here: https://bintray.com/grails/plugins/spring-security-core/view
The "Spring Security Starter for Spring Boot" is a good starting point, but if you want to save yourself some time trying to figure out how to get it to work with Grails, check out this helpful blog post.
I wrote the blog post #Jamie referenced in his answer and I added a new blog post describing how to use the Gorm domain classes from Spring-Security-Core plugin from Grails 2.
dependencies {
...
compile 'org.grails.plugins:spring-security-core:3.0.4'
...
}
This is what I used and it worked for me
I need suggestions on cache clustering for Grails at the most recent version I can get.
I've been trying to set up Terracotta with Grails 2.4.4 but I can't manage to find a compatible version of its plugin (by the way, the Terracotta plugin page says it was last updated 6 years ago). Also I can't find any recent posts on cache clustering for grails.
I'm planning on using it also for session replication. I'm using Apache Shiro for authentication/authorization. But that shouldn't matter.
Ehcache has an embedded distributed solution based on RMI. I'm gonna give it a try but I'm not sure it'll work for web sessions in grails since the documentation says to use Terracotta.
On the Spring Security Core plugin GitHub repo, I see that Graeme on May 21st upped the required version of Grails from 2.0 to 2.3 before the RC4 version was released a couple of months later, but I don't see any explanation for why. Was it mismatched dependencies, bug reports, etc?
I run a 2.2.4 app, and I would prefer not to upgrade at this point just to get the latest RC of spring security core. I understand if the upgrade to 3.2.0.RELEASE of spring security caused mismatched dependencies with older versions of Grails since I've run into the same issues before.
This originally came up due to a pull request on the spring security OAuth2 provider plugin that I maintain. The pull request upped the required version to 2.3, and the requester pointed me to the RC4 release of core as the reason.
Thanks for the good works as always!
It's pure speculation on my part, but as far as I can tell, it has to do with the getNamespace() method introduced in the UrlMappingInfo interface in Grails 2.3.
The Spring Security Core plugin's class AnnotationFilterInvocationDefinition does check if it's dealing with Grails 2.3 or higher before it attempts to call getNamespace(), but in its current state it causes a compilation error (due to the missing method).
I suppose the class could resort to using the reflection API to get around this, making it possible to lower the requirement to Grails 2.2.0 (or keep it at 2.0.0)
String namespace = null;
try {
Method m = mapping.getClass().getDeclaredMethod("getNamespace", null);
namespace = (String)m.invoke();
} catch(NoSuchMethodException e) { ... }
I'm looking for a security plugin for a grails project.
Spring security core 1.2.7.3 looks awesome but it seems that it's not under development for almost a year. Does anyone knows if that is the case?
Also are there any other good plugins?
Also i'm using mongodb and wanted to know if spring security core is compatible with mongo
Thanks!
Roy
Take a look at the plugin again. It's supported by SpringSource. If no updates, no need in them. Don't think they just forget to update.