|
Updated: 9/1/2002; 7:03:30 PM.
 |
Wednesday, January 30, 2002 |
Update: fireball in the sky story moved here.
8:54:26 PM 
|
|
Update: Discussion of the recent update to the Apache Jakarta site can be found here.
7:41:01 PM
|
|
This is sure to get some attention. In case it is taken down, the original can likely be found here. The relevant quote from the original: "The J2EE Compatible brand has achieved significant momentum over the past two years, and we want to make sure that any open source efforts don't impact the viability of that effort.". This follows statements that describe the Sun Community Source License and the value of open standards.
5:39:09 PM
|
|
I love it when our "competitors" submit patches to Apache to improve interoperability with their SOAP stack. In this case, the fix was to a sample, but the point remains the same: being able to interoperate with Apache apparently means enough to some people to track down the issues and address them - without regard to where the "fault" lies.
3:36:23 PM
|
|
Tony Hong writes: XMethods has a policy that all services have WSDL descriptions, which we validate on submission with some integrity checks. Having that WSDL ensures that the listings are as useful as possible - those that have toolkits that require WSDL have it without exception, those that don't still benefit because they can derive the technical details in a consistent, standardized manner.
3:28:42 PM
|
|
Anne Thomas Manes writes: You are never required to provide a WSDL file. But if you want to "offer" this service (and by "offer" I assume that you intend to make it avilable to a variety of clients) then you need to provide technical information to these clients about how to use the service.
9:55:31 AM
|
|
|
