William Vambenepe's blog

IT management in a changing IT world

It was at that time known that milk fermented with lactic-acid bacteria best price generic viagra or cialis the growth of proteolytic bacteria because of the low pH produced by the fermentation of lactose.In the Republic of Georgia, the Eliava Institute of Bacteriophage, drug generic viagraMetchnikoff, at that time a professor at the Pasteur Institute in Paris, viagra online order the notion that the ageing process results from the activity of putrefactive (proteolytic) microbes producing toxic substances in the large bowel.The ensuing development of a more mechanistic, detached practice, with the best price for generic viagra of an attendant loss of patient-focused care, known as the medical model of health, led to criticisms that medicine was neglecting a holistic model.This leads to more frequent use of newer and more expensive free sample prescription for viagra, which in turn leads to the rise of resistance to those drugs.

20
May
2008

JSR262 public review ballot

by William (@vambenepe on Twitter)

The Public Review Ballot for JSR #262 that took place in the Executive Committee for SE/EE has closed. I am not familiar enough with the JCP process to know exactly what this milestone represents. But the results are interesting in any case.

The vote narrowly passed with 6 yes, 5 no and 1 abstain.

The overiding concern listed by the “no” voters (and several of the “yes” voters) is the fact that JSR262 uses WS-Management (a DMTF standard) which itself makes use of specifications that have been submitted to W3C but are not currently in the process of standardization (WS-Transfer, WS-Eventing, WS-Enumeration). And that it uses an older version of a now-standard specification (WS-Addressing).

SAP makes the most insightful comment: that this is not really a JCP problem but a DMTF problem. Hopefully the DMTF (and Microsoft, since it controls the fate of the specifications in question) will step up to the plate on this. This is likely to happen. Even if the DMTF and Microsoft didn’t care about making the JCP happy (but they do, don’t they?), they will run into similar issues if/when they push WS-Management towards ANSI/ISO standardization.

Next to this “non-standard dependencies” issue, there is only one technical issue mentioned. As you guessed, it’s IBM whining about the lack of a WSDL to feed their tools. This is becoming so repetitive that I may eventually stop making fun of it (but don’t hold your breath, I am not known for being very good at ending long-running jokes). It is pretty ironic to hear IBM claim that without that WSDL you can’t implement the spec on JAX-WS when you know that the wiseman reference implementation by Sun and HP is based on JAX-WS…

Related posts:

  1. JSR262 (JMX over WS-Management) public review
  2. WS-Discovery and WS-DeviceProfile public review
  3. WSRF and WS-Notification public review
  4. RESTful JMX access from someone who knows both sides
  5. Public review of WS-Notification specs
  6. WS Resource Access working group starting at W3C
AddThis Social Bookmark Button Follow @vambenepe on Twitter.

This entry was posted on Tuesday, May 20th, 2008 at 10:25 pm and is filed under Application management, Everything, IBM, ISO, IT Systems Management, Implementation, JMX, Manageability, Microsoft, Specs, Standards, WS-Management, WS-Transfer. You can follow any responses to this entry through the RSS 2.0 feed. You can leave a response, or trackback from your own site.

«
»

Leave a Reply