blocks|key|4720061|text|就WS标准遵从性而言，Axis2是不完整的。|type|unstyled|depth|inlineStyleRanges|entityRanges|data|4720062|我最近(上个月)经历了一个POC阶段，Axis2没有通过我的WS-*兼容性测试(特别是WS-AT、WS-协调)。|4720063|看看"Project+Metro“吧。Sun和Microsoft合作使WCF和JAX-WS互操作“正确”。|4720064|https://metro.dev.java.net/|offset|length|4720065|entityMap|0|LINK|mutability|MUTABLE|url^0|0|0|0|0|R|0|0^^$0|@$1|2|3|4|5|6|7|Q|8|@]|9|@]|A|$]]|$1|B|3|C|5|6|7|R|8|@]|9|@]|A|$]]|$1|D|3|E|5|6|7|S|8|@]|9|@]|A|$]]|$1|F|3|G|5|6|7|T|8|@]|9|@$H|U|I|V|1|W]]|A|$]]|$1|J|3|-4|5|6|7|X|8|@]|9|@]|A|$]]]|K|$L|$5|M|N|O|A|$P|G]]]]

Axis2 is incomplete in terms of WS standards compliance. 

I recently (in the last month) went through a POC phase where Axis2 failed my WS-* compliance tests (specifically WS-AT, WS-Coordination). 

Have a look at "Project Metro". Sun and Microsoft collaborated on getting WCF and JAX-WS interop "right". 
<a href="https://metro.dev.java.net/" rel="nofollow noreferrer">https://metro.dev.java.net/</a>

blocks|key|4720111|text|如果可以的话，我也不推荐在Java端使用Axis2。使用Glassfish或JAX-WS显然会更容易，尽管我从未测试过它。|type|unstyled|depth|inlineStyleRanges|entityRanges|data|4720112|当我试图让WCF和Axis2合作时，我也遇到了这样的问题。检查WSDL文件中使用的标准的版本，在我们的示例中，这些标准不匹配。|4720113|entityMap^0|0|0^^$0|@$1|2|3|4|5|6|7|F|8|@]|9|@]|A|$]]|$1|B|3|C|5|6|7|G|8|@]|9|@]|A|$]]|$1|D|3|-4|5|6|7|H|8|@]|9|@]|A|$]]]|E|$]]

I would also not recommand going for Axis2 on the Java side, if you can. Would be easier with Glassfish or JAX-WS apparently, althoug I never tested it.

I ran into those kind of issues as well when trying to make WCF and Axis2 cooperate. Check the version of the standard used in the WSDL file, those were not matching in our case.

blocks|key|4719970|text|您是否正在处理文档文字与rpc编码的问题？(对不起，不得不问一下。)|type|unstyled|depth|inlineStyleRanges|entityRanges|data|4719971|http://www.ibm.com/developerworks/webservices/library/ws-whichwsdl/|offset|length|4719972|http://www.developerfusion.com/article/4694/web-services-interoperability-between-j2ee-and-net-part-1/3/|4719973|http://msdn.microsoft.com/en-us/library/ms996466.aspx|4719974|entityMap|0|LINK|mutability|MUTABLE|url|1|2^0|0|0|1V|0|0|0|2W|1|0|0|1H|2|0^^$0|@$1|2|3|4|5|6|7|S|8|@]|9|@]|A|$]]|$1|B|3|C|5|6|7|T|8|@]|9|@$D|U|E|V|1|W]]|A|$]]|$1|F|3|G|5|6|7|X|8|@]|9|@$D|Y|E|Z|1|10]]|A|$]]|$1|H|3|I|5|6|7|11|8|@]|9|@$D|12|E|13|1|14]]|A|$]]|$1|J|3|-4|5|6|7|15|8|@]|9|@]|A|$]]]|K|$L|$5|M|N|O|A|$P|C]]|Q|$5|M|N|O|A|$P|G]]|R|$5|M|N|O|A|$P|I]]]]

Are you handling the doc literal vs. rpc-encoded issue? (Sorry, have to ask.)

<a href="http://www.ibm.com/developerworks/webservices/library/ws-whichwsdl/" rel="nofollow noreferrer">http://www.ibm.com/developerworks/webservices/library/ws-whichwsdl/</a>

<a href="http://www.developerfusion.com/article/4694/web-services-interoperability-between-j2ee-and-net-part-1/3/" rel="nofollow noreferrer">http://www.developerfusion.com/article/4694/web-services-interoperability-between-j2ee-and-net-part-1/3/</a>

<a href="http://msdn.microsoft.com/en-us/library/ms996466.aspx" rel="nofollow noreferrer">http://msdn.microsoft.com/en-us/library/ms996466.aspx</a>

blocks|key|1187346|text|我假设服务器端是axis，这不是很清楚，但这更常见。|type|unstyled|depth|inlineStyleRanges|entityRanges|data|1187347|如果您正在使用Java语言编写可互操作的WS服务，则应该考虑切换到JAX-WS，这不仅是因为axis2编程模型有点奇怪，而且通常代码也是不完整的。我以前肯定遇到过部分实现的特性，而且我发现很难确定对Microsoft堆栈执行了哪些互操作性测试。|1187348|我想说，您将来使用JAX-WS堆栈的机会要大得多。一个主要原因是Sun工程师花了相当多的时间与微软工程师坐在一起，以确保他们的堆栈是可互操作的，并且他们以相同的方式解释了规范。除此之外，编程模型更容易，并且可以用注释驱动。它还在一定程度上简化了部署和维护。可以忽略用于服务.AAR文件的附加容器和从服务端点删除axis2的繁琐操作:可以将端点视为Servlet。|1187349|有关于让SAML与JAX-WS一起工作的文档：http://www.jroller.com/gmazza/entry/using_the_opensaml_library_in|offset|length|1187350|如果你不能离开axis2，我认为需要采用类似的策略。您将在其中拦截令牌，并在令牌调用服务端点之前进行身份验证。|1187351|请参阅：http://www.omg.org/news/meetings/workshops/Web_Services_USA_Manual/02-3_K_Smith.pdf|1187352|http://www.mail-archive.com/axis-user@xml.apache.org/msg10292.html|1187353|http://www2.sys-con.com/ITSG/virtualcd/WebServices/archives/0303/secrist/index.html|1187354|entityMap|0|LINK|mutability|MUTABLE|url|http://www.jroller.com/gmazza/entry/using_the_opensaml_library_in|1|http://www.omg.org/news/meetings/workshops/Web_Services_USA_Manual/02-3_K_Smith.pdf|2|3^0|0|0|0|N|1T|0|0|0|4|2B|1|0|0|1U|2|0|0|2B|3|0^^$0|@$1|2|3|4|5|6|7|13|8|@]|9|@]|A|$]]|$1|B|3|C|5|6|7|14|8|@]|9|@]|A|$]]|$1|D|3|E|5|6|7|15|8|@]|9|@]|A|$]]|$1|F|3|G|5|6|7|16|8|@]|9|@$H|17|I|18|1|19]]|A|$]]|$1|J|3|K|5|6|7|1A|8|@]|9|@]|A|$]]|$1|L|3|M|5|6|7|1B|8|@]|9|@$H|1C|I|1D|1|1E]]|A|$]]|$1|N|3|O|5|6|7|1F|8|@]|9|@$H|1G|I|1H|1|1I]]|A|$]]|$1|P|3|Q|5|6|7|1J|8|@]|9|@$H|1K|I|1L|1|1M]]|A|$]]|$1|R|3|-4|5|6|7|1N|8|@]|9|@]|A|$]]]|S|$T|$5|U|V|W|A|$X|Y]]|Z|$5|U|V|W|A|$X|10]]|11|$5|U|V|W|A|$X|O]]|12|$5|U|V|W|A|$X|Q]]]]

I'm assuming that the server side is axis, it's not clear but that is more common.

If you are programming interoperable webservices you in Java you should consider switching to JAX-WS, not only because the axis2 programing model is a little bizarre, but often the code is incomplete. I've certainly come across features partially implemented before, also it's I found it difficult to determine what testing for interoperability had been performed with the Microsoft stack.

I would say you have much better chances in the future using a JAX-WS stack. One major reason is Sun Engineers spend quite some time sitting with Microsoft engineers to make sure their stacks were interoperable and they'd interpreted the specs in the same way. Besides this the programming model is easier and can be driven with annotations. It also somewhat simplifies deployment and maintenance. The additional container for servicing .AAR files and the fiddling to remove axis2 from the service endpoint can just be ignored: the endpoint can just be treated as a Servlet.

There is documentation of people getting SAML to work with JAX-WS: <a href="http://www.jroller.com/gmazza/entry/using_the_opensaml_library_in" rel="nofollow noreferrer">http://www.jroller.com/gmazza/entry/using_the_opensaml_library_in</a>

If you cannot move away from axis2 I think a similar strategy needs to be employed. Where you would intercept the token and do the authentication before it gets to call the service endpoint.

See: <a href="http://www.omg.org/news/meetings/workshops/Web_Services_USA_Manual/02-3_K_Smith.pdf" rel="nofollow noreferrer">http://www.omg.org/news/meetings/workshops/Web_Services_USA_Manual/02-3_K_Smith.pdf</a>

<a href="http://www.mail-archive.com/axis-user@xml.apache.org/msg10292.html" rel="nofollow noreferrer">http://www.mail-archive.com/axis-user@xml.apache.org/msg10292.html</a>

<a href="http://www2.sys-con.com/ITSG/virtualcd/WebServices/archives/0303/secrist/index.html" rel="nofollow noreferrer">http://www2.sys-con.com/ITSG/virtualcd/WebServices/archives/0303/secrist/index.html</a>

blocks|key|1187438|text|我们已经成功地在客户端和服务器端使用WCF测试了Rampart+for+WS-Trust场景。|type|unstyled|depth|inlineStyleRanges|entityRanges|data|1187439|顺便说一句，Rampart还不支持WS-Federation场景，您的安全策略可能与此相关。FYI+-+WS-Federation将在明年年中随Rampart一起提供。|1187440|如果您能附上安全策略，我们可以仔细看看..|1187441|entityMap^0|0|0|0^^$0|@$1|2|3|4|5|6|7|H|8|@]|9|@]|A|$]]|$1|B|3|C|5|6|7|I|8|@]|9|@]|A|$]]|$1|D|3|E|5|6|7|J|8|@]|9|@]|A|$]]|$1|F|3|-4|5|6|7|K|8|@]|9|@]|A|$]]]|G|$]]

We have successfully tested Rampart for WS-Trust scenarios with WCF both at the client and server ends.

BTW Rampart doesn't have WS-Federation scenarios supported yet and your security policy could be related to it. [FYI - WS-Federation will be available with Rampart mid next year].

If you can please attach the security policies we can have a close look..

We are trying to get WCF and Java talking to each other using SAML tokens issued from an STS. Despite the fact that both sides are compliant with the standards, WS-Security, WS-Trust, WS-Policy, etc., they don't seem to talk to each other and one or the other will throw cryptic exceptions or ignore security headers.

We are using .NET 3.5, WCF Federation binding on the MS side, and Axis2/Rampart/Rahas on the java side.

Has anyone ever been able to make this work?

WCF Interop with Axis2 using WS-Trust

翻译质量差，导致语言生硬或混乱。

没有提供实际的解决方法或示例。

解答不清晰，无法理解或解决问题。

页面排版不美观，阅读体验差。

文章

问答

视频

教程

学习中心

腾讯云实验室

直播

竞赛

腾讯云代码分析专区

腾讯iOA零信任安全管理系统专区

腾讯云架构师技术同盟交流圈

腾讯云数据库专区

腾讯云智能顾问专区

腾讯云原生专区

腾讯混元专区

腾讯云TCE专区

腾讯云Lighthouse专区

腾讯云HAI专区

腾讯云Edgeone专区

腾讯云存储专区

腾讯云智能专区

腾讯轻联专区 

腾讯云开发专区

TAPD专区

腾讯轻量云游戏服专区

腾讯云最具价值专家

腾讯云架构师技术同盟

腾讯云创作之星

腾讯云开发者先锋

腾讯云AI代码助手

云原生构建

TAPD 敏捷项目管理

Cloud Studio

SDK中心

API中心

命令行工具

功能1上新10个字符

功能2描述100个字符功能2描述100个字符功能2描述100个字符功能2描述100个字符功能2描述100个字符功能2描述100个字符功能2描述100个字符功能2描述100个字符功能2描述100个字符。

功能2上新100个字符功能2上新100个字符功能2上新100个字符功能2上新100个字符功能2上新100个字符功能2上新100个字符功能2上新100个字符功能2上新100个字符功能2上新100个字符。

功能5描述100个字符功能5描述100个字符功能5描述100个字符功能5描述100个字符功能5描述100个字符功能5描述100个字符

功能5上新100个字符功能5上新100个字符功能5上新100个字符功能5上新100个字符功能5上新100个字符功能5上新100个字符功能5上新100个字符功能5上新100个字符功能5上新100个字符功能5上新100个字符

功能4上新

文章&问答评论现已支持表情

全新交互，全新视觉，新增快捷键、悬浮工具栏、高亮块等功能并同时优化现有功能，全面提升创作效率和体验

社区富文本编辑器全新改版！诚邀体验～ 

精选全网热门MCP server，让你的AI更好用 🚀

💥开发者 MCP广场重磅上线！

涵盖代码开发、场景应用、自动测试全流程，助你从零构建专属AI助手

一站式MCP教程库，解锁AI应用新玩法

聚焦“写作效率、视觉美观与运行性能”三方面进行全面升级，为您提供更高效、稳定的创作环境

社区富文本&Markdown编辑器全新改版上线，欢迎大家体验!

诚挚邀请您参与本次调研，分享您的真实使用感受与建议。您的反馈至关重要，感谢您的支持与参与！

社区新版编辑器体验调研

我们正在尝试使用从STS发出的SAML令牌来让WCF和Java相互通信。尽管双方都符合WS-Security、WS-Trust、WS-Policy等标准，但它们似乎并不相互通信，其中一方会抛出隐蔽的异常或忽略安全标头。我们在MS端使用WCF3.5，在MS端使用.NET联合绑定，在Java端使用Axis2/Rampart/Rahas。有没有人能够做到这一点？

问使用WS-Trust与Axis2进行WCF互操作
EN

回答 5

Stack Overflow用户

Stack Overflow用户

Stack Overflow用户

社区

活动

圈层

关于

腾讯云开发者

热门产品

热门推荐

更多推荐

问使用WS-Trust与Axis2进行WCF互操作EN

回答 5

Stack Overflow用户

Stack Overflow用户

Stack Overflow用户

社区

活动

圈层

关于

腾讯云开发者

热门产品

热门推荐

更多推荐

问使用WS-Trust与Axis2进行WCF互操作
EN