jdotnetservices

Update on .NET Services SDK for Java Developers

admin — Thu, 01 Oct 2009 22:13:12 +0000

It has been a while since we posted an update on .NET Services SDK for Java Developers.

As we align the .NET Services SDK for Java Developers with the .NET Services features and programming style for the next milestone, there are a few changes in our approach.

In a nutshell, the .NET Services SDK for Java Developers will be adopting a REST based architecture for the next release planned for November 2009.

If you are using the .NET Services SDK for Java Developers today, what does this mean for you? Please see the updates on the Roadmap page for details of upcoming changes to the .NET Services SDK for Java Developers.

Announcing M3-CTP release of jdotnetservices

admin — Wed, 08 Jul 2009 17:18:36 +0000

We are pleased to announce the M3-CTP of jdotnetservices. This release is compatible with the .NET Services July 2009 CTP and contain few bug fixes.

Please feel free to download source code from here. Alternatively, you may also try out the Chat Application or SCM sample application that leverages the capabilities of jdotnetservices. Please give it a try and give us your feedback, and join the discussion on the mailing list.

–

jdotnetservices Team

Announcing M2-CTP release of jdotnetservices

admin — Tue, 14 Apr 2009 06:07:56 +0000

We are excited to announce the M2-CTP of jdotnetservices. It is compatible with .NET Services March 2009 CTP. Please feel free to download source code from here. Alternatively, you may also try out the Chat Application or SCM sample application that leverages the capabilities of jdotnetservices Please give it a try and give us your feedback at feedback, and join the discussion on the mailing list. Stay tuned for future releases!

This M2-CTP addresses following breaking changes in the .NET Services,

- The March 2009 CTP release uses solution names as part of the host name for all service end points. STS host reference location has changed from accesscontrol.windows.net to .accesscontrol.windows.net. Hence STS endpoint prefix has changed aswell.

- Solution name is now part of the DNS. All Service Bus applications must adopt this new naming convention of sb://.servicebus.windows.net/.

Stay tuned for future releases!

jdotnetservices Team

Announcing M1-CTP release of jdotnetservices

admin — Mon, 27 Oct 2008 08:49:16 +0000

The jdotnetservices team is very proud of launching the Milestone 1 - Technology Preview of JAVA SDK for Microsoft .NET Services.

The purpose of this project is to provide an interoperable open source Java software development kit(SDK) - set of libraries, tools, prescriptive patterns & guidance & real world sample applications that will enhance productivity for developers. Developers will be able to leverage the .NET Services to extend their Java applications by using the Azure™ Services Platform to build, deploy and manage reliable, internet-scale applications.

The project has been released as an open source project under BSD license.

The focus of this release is around Access Control and Service Bus Services. The detailed release notes are available here. We are thrilled about making this initial version available to you and look forward to your feedback. Following are the high level features we have implemented in this release.

• Custom transport (client and server) extension for Metro 1.3 to work with .NET Services
• Support for Soap 1.2 messages
• Support for Service Bus Service feature of .NET Services
• Support for Access Control Service feature of .NET Services
• Support for Relay one-way, two-way and multicast

Please feel free to download source code from our svn repository. Alternatively, you may also try out the “Supply Chain” sample application that leverages the capabilities of jdotnetservices.

Please give it a try and give us your feedback on the tracking system, and join the discussion on the SDK Forum.

Stay tuned for future releases!

jdotnetservices Team