4 Replies Latest reply on Jul 11, 2007 6:22 AM by Mark Little

    WSDL WS-AT missing policies?

    Guzman Llambi­as Novice

      Hello, we are testing the interoperability between WCF and JBossWS, now we are working with WS-AT. We have deployed the arjuna example (Bistro Service) on a jboss 4.2.0GA and we found something strange in the wsdl of the services. There aren't any policies that referred to WS-AT. Is this ok? If that's true, how can a client recognized that the service is using WS-AT?

      Thanks

        • 1. Re: WSDL WS-AT missing policies?
          Mark Little Master

          To have policy support for WS-AT or WS-BA, you need a SOAP stack that supports WS-Policy. We don't have that yet with JBossWS, but it'll come soon. Simply treat the absence of a policy as requiring a transaction context.

          • 2. Re: WSDL WS-AT missing policies?
            Mark Little Master

            BTW, I should also add that JBossTS WS-AT/WS-BA support is not using JBossWS at all at present. It uses its own SOAP stack, which has demonstrated interoperability with WS-TX 1.0 and 1.1 over the past few years (against IBM, MSFT and others) at the official interoperability events.

            • 3. Re: WSDL WS-AT missing policies?
              Guzman Llambi­as Novice

              Mark, thanks for the fast reply!


              To have policy support for WS-AT or WS-BA, you need a SOAP stack that supports WS-Policy. We don't have that yet with JBossWS, but it'll come soon

              I'm a bit confused here. You said that actually JBoss WS, doesn't support WS-Policy, but in the User Guide they say they do. I suppose here you meant that actually, you can't define WS-AT's policies with JBossWS. Is that correct?


              Simply treat the absence of a policy as requiring a transaction context.

              If I didn't understand wrong, it's enough to flow the transaction context according to the WS-AT specification to have interoperability between .Net and JBossTS. Do you recommend something to do so?


              I should also add that JBossTS WS-AT/WS-BA support is not using JBossWS at all at present

              Are there any plans in the near future to add JBoss WS-AT/WS-BA support to JBoss WS?

              Thanks a lot!

              Guzmán

              • 4. Re: WSDL WS-AT missing policies?
                Mark Little Master

                 

                "gllambi" wrote:
                Mark, thanks for the fast reply!


                To have policy support for WS-AT or WS-BA, you need a SOAP stack that supports WS-Policy. We don't have that yet with JBossWS, but it'll come soon

                I'm a bit confused here. You said that actually JBoss WS, doesn't support WS-Policy, but in the User Guide they say they do. I suppose here you meant that actually, you can't define WS-AT's policies with JBossWS. Is that correct?


                That support is relatively new. Our implementation of WS-TX support has been around for 4 years.



                Simply treat the absence of a policy as requiring a transaction context.

                If I didn't understand wrong, it's enough to flow the transaction context according to the WS-AT specification to have interoperability between .Net and JBossTS. Do you recommend something to do so?


                Check out the Theatre/Restaurant/Taxi example.



                I should also add that JBossTS WS-AT/WS-BA support is not using JBossWS at all at present

                Are there any plans in the near future to add JBoss WS-AT/WS-BA support to JBoss WS?


                http://jira.jboss.com/jira/browse/JBTM-16