Enunciate

support for spring 3

Details

  • Type: Improvement Improvement
  • Status: Closed Closed
  • Priority: Major Major
  • Resolution: Fixed
  • Affects Version/s: 1.18
  • Fix Version/s: 1.20
  • Component/s: None
  • Labels:
    None
  • Number of attachments :
    0

Activity

Hide
Ryan Heaton added a comment -

fixed for 1.20

Show
Ryan Heaton added a comment - fixed for 1.20
Hide
Ryan Heaton added a comment -

There's a new artifact enunciate-spring3-app-rt. Depend on that artifact instead of enunciate-spring-app-rt and you should be good to go.

Try it out with the release candidate. It worked with the tests I ran against it. If there are any issues, let me know before 1.20 final is released.

Show
Ryan Heaton added a comment - There's a new artifact enunciate-spring3-app-rt. Depend on that artifact instead of enunciate-spring-app-rt and you should be good to go. Try it out with the release candidate. It worked with the tests I ran against it. If there are any issues, let me know before 1.20 final is released.
Hide
Lilians Auvigne added a comment -

Hi,

I've tried the 1.20-RC1 playing with the wannabecool sample.
after adding the new enunciate-spring3-app-rt

Here are the problems I encountered :

1. from the generated artifact :

  • enunciate.xml defines 1.19.xsd instead of 1.20.xsd

2. add custom stuff in the enunciate.xml :
<spring-app enableSecurity="true"/>

  • refs to spring-2..xsd in generated jaxws--servlet.xml files
  • 2 different versions of activation in the final war file WEB-INF/lib
  • no spring-security jars in the final war
Show
Lilians Auvigne added a comment - Hi, I've tried the 1.20-RC1 playing with the wannabecool sample. after adding the new enunciate-spring3-app-rt Here are the problems I encountered : 1. from the generated artifact :
  • enunciate.xml defines 1.19.xsd instead of 1.20.xsd
2. add custom stuff in the enunciate.xml : <spring-app enableSecurity="true"/>
  • refs to spring-2..xsd in generated jaxws--servlet.xml files
  • 2 different versions of activation in the final war file WEB-INF/lib
  • no spring-security jars in the final war
Hide
Ryan Heaton added a comment -

Thanks for the report.

enunciate.xml defines 1.19.xsd instead of 1.20.xsd

That will be changed with the final release.

refs to spring-2..xsd in generated jaxws--servlet.xml files

Thanks. We got that fixed.

2 different versions of activation in the final war file WEB-INF/lib

I couldn't reproduce that. When I do a dependency:tree, for example, I see only one activation jar.

no spring-security jars in the final war

As designed. Security is optional, and if you enable it, you also have to be responsible for referencing the jars you need. This is because we didn't want to make all users download the security jars if they didn't need security.

Show
Ryan Heaton added a comment - Thanks for the report.
enunciate.xml defines 1.19.xsd instead of 1.20.xsd
That will be changed with the final release.
refs to spring-2..xsd in generated jaxws--servlet.xml files
Thanks. We got that fixed.
2 different versions of activation in the final war file WEB-INF/lib
I couldn't reproduce that. When I do a dependency:tree, for example, I see only one activation jar.
no spring-security jars in the final war
As designed. Security is optional, and if you enable it, you also have to be responsible for referencing the jars you need. This is because we didn't want to make all users download the security jars if they didn't need security.
Hide
Lilians Auvigne added a comment -

Hi Ryan

Thanks for your answer!

Here the next step of security configuration I ran in

The security-context.xml generated for spring3-security contains obsolete tag :
<authentication-manager>
http://forum.springsource.org/showthread.php?t=76292

I've changed it by (in the generated file):

<beans:bean id="enunciate-auth-provider" class="org.codehaus.enunciate.modules.spring_app.DefaultEnunciateAuthenticationProvider">
  <beans:property name="userDetailsService" ref="userDetailsService" />
</beans:bean>

<!-- service method interceptor (used to lock down the service methods.)-->
<authentication-manager alias="authenticationManager">
  <authentication-provider ref="enunciate-auth-provider"/>
</authentication-manager>

(I've defined bean userDetailsService in the other-beans.xml included in the enunciate.xml)

jetty is running.

thank you

Show
Lilians Auvigne added a comment - Hi Ryan Thanks for your answer! Here the next step of security configuration I ran in The security-context.xml generated for spring3-security contains obsolete tag : <authentication-manager> http://forum.springsource.org/showthread.php?t=76292 I've changed it by (in the generated file):
<beans:bean id="enunciate-auth-provider" class="org.codehaus.enunciate.modules.spring_app.DefaultEnunciateAuthenticationProvider">
  <beans:property name="userDetailsService" ref="userDetailsService" />
</beans:bean>

<!-- service method interceptor (used to lock down the service methods.)-->
<authentication-manager alias="authenticationManager">
  <authentication-provider ref="enunciate-auth-provider"/>
</authentication-manager>
(I've defined bean userDetailsService in the other-beans.xml included in the enunciate.xml) jetty is running. thank you
Hide
Ryan Heaton added a comment -

Thanks again. Will you do me a favor and try out RC2 and let me know if there are any more issues?

Show
Ryan Heaton added a comment - Thanks again. Will you do me a favor and try out RC2 and let me know if there are any more issues?
Hide
Fred Do Couto added a comment -

Hi Ryan,

I'm working with Lilians on the 1.20 RC tests.

The RC2 looks great for us.

Thanks

Show
Fred Do Couto added a comment - Hi Ryan, I'm working with Lilians on the 1.20 RC tests. The RC2 looks great for us. Thanks
Hide
Ryan Heaton added a comment -

closed for 1.20 release

Show
Ryan Heaton added a comment - closed for 1.20 release

People

Vote (3)
Watch (2)

Dates

  • Created:
    Updated:
    Resolved: