Links

  • 1. Sogeti
  • 2. JBoss
  • 3. IBM
  • 4. Oracle
  • 5. SpringSource
  • 6. NL-JUG
  • 7. Java

Archives

Syndication  RSS 2.0

RSS 1.0
RSS 2.0

Bookmark this site

Add 'JCN Blog' site to delicious  Add 'JCN Blog' site to technorati  Add 'JCN Blog' site to digg  Add 'JCN Blog' site to dzone

Posted by Jan-Hendrik Kuperus at 12:17 on Friday 5 December    Add 'Configure JBoss WS on multiple network interfaces' site to delicious  Add 'Configure JBoss WS on multiple network interfaces' site to technorati  Add 'Configure JBoss WS on multiple network interfaces' site to digg  Add 'Configure JBoss WS on multiple network interfaces' site to dzone

The JBoss WebServices package is a nice library to get your webservice kickstarted in no-time. One of its features is the automatic generation of a WSDL for your webservice endpoint. There is however a slight annoyance when you try to use this on a machine with two network interfaces.

On a single interface machine, JBoss automatically fills in the IP address or hostname of that interface in the <soap:address/> WSDL entry. No problems there. But, if you have a machine with two interfaces, for example one for internal and one for external access, then JBoss is likely to screw things up.

This is due to the following configuration directive in the jbossas/server/production/deploy/jbossws.sar/jbossws.beans/META-INF/jboss-beans.xml:


<property name="webServiceHost">${jboss.bind.address}</property>

This property causes JBoss to use the bind address in the WSDL rewriting/generation. Even if you start the server with -b 0.0.0.0, which binds it to all interfaces, JBoss still selects a single interface to use in this property.

The solution to this is luckily very simple: if this property is removed from the configuration file, JBoss will rewrite the WSDL with the address of the interface on which the request came in.

It does make me wonder, why is this not the default setting? Would it not be easier to drop in a server anywhere and it automatically exposes correct WSDL files on all interfaces? Then, if you want to restrict it to a single interface, add the property shown above.

–Jan-Hendrik Kuperus
http://blojsom.jhkuperus.nl/blog

Posted by Barend Garvelink at 14:17 on Tuesday 13 February    Add 'Artikel: Security Concepts, Challenges, and Design Considerations for Web Services Integration' site to delicious  Add 'Artikel: Security Concepts, Challenges, and Design Considerations for Web Services Integration' site to technorati  Add 'Artikel: Security Concepts, Challenges, and Design Considerations for Web Services Integration' site to digg  Add 'Artikel: Security Concepts, Challenges, and Design Considerations for Web Services Integration' site to dzone

Via het weblog van Gunnar Peterson kwam ik bij een artikel over het beveiligen van een webservices architectuur. Het behandelt een breed scala aan threats, tegenmaatregelen en standaards.

Security Concepts, Challenges, and Design Considerations for Web Services Integration

Posted by Barend Garvelink at 13:47 on Friday 9 February    Add 'SoapUI 1.6' site to delicious  Add 'SoapUI 1.6' site to technorati  Add 'SoapUI 1.6' site to digg  Add 'SoapUI 1.6' site to dzone

Op www.soapui.org is het tooltje SoapUI te downloaden. Prachttool. Werkt heel intuitief en doet vrijwel alles wat je ooit nodig hebt bij het testen van een webservice. Je kunt SOAP requests inschieten (uiteraard), je kunt ook automated tests maken waarbij je het teruggekomen SOAP response kan controleren met behulp van o.a. XPath. Ook load- en performancetesten zit in de featureset.

Versie 1.6 onderteunt het WS-Security UsernameToken gebeuren (zowel cleartext als digested passwords), en in het huidige development snapshot van 1.7 is inmiddels ook de Signing/Encryption support aanwezig (JKS keystores).

Warm aanbevolen.

Posted by Ruud Steeghs at 16:20 on Thursday 14 December    Add 'WS-Atomic Transactions & WS-Business Activity' site to delicious  Add 'WS-Atomic Transactions & WS-Business Activity' site to technorati  Add 'WS-Atomic Transactions & WS-Business Activity' site to digg  Add 'WS-Atomic Transactions & WS-Business Activity' site to dzone

Door Guy Pardon

Deze lezing gaat over transacties en hoe transacties in een SOA omgeving ondersteund kunnen worden.

Eerst legt Guy Pardon uit dat transactie ACID moeten zijn:
Atomic – een transactie slaagt als geheel of slaagt niet
Consistent – de database(s) moeten zowel voor als na de transacties in een consistente staat verkeren
Isolatable – transacties mogen elkaar niet be├»nvloeden
Durable – na een server crash moet de staat van een database (of meerdere databases) in een consistente staat verkeren

Transacties die betrekking hebben op een enkele database noemen we een local transaction.
Transacties waarbij meerdere databases of datasources (e.g. queues) bij betrokken zijn, heten global of distributed transactions.
JTA is de API die global transacties mogelijk maken. XA heeft betrekking op de connectoren voor de databases of de queues.
Read the rest of this entry »

Posted by Ruud Steeghs at 20:55 on Wednesday 13 December    Add 'WS-Reliable Messaging by Paul Fremantle' site to delicious  Add 'WS-Reliable Messaging by Paul Fremantle' site to technorati  Add 'WS-Reliable Messaging by Paul Fremantle' site to digg  Add 'WS-Reliable Messaging by Paul Fremantle' site to dzone

Het transport protocol JMS kent een garantie voor het afleveren van berichten. HTTP kent deze garantie niet. Voor berichten die middels Webservices over HTTP verzonden worden, is het daadwerkelijk afleveren niet gegarandeerd. WS-Reliable Messaging is een standaard die gebruikt kan worden om deze garantie van afleveren te implementeren voor Webservices.

WS-Reliable Messaging (WS-RM) is een initiatief van Microsoft en IBM. Helaas is er een ander initiatief van o.a. Sun en Oracle die hetzelfde beoogt: WS-Reliability (WS-R). Aan hoe WS-RM zich verhoudt tot WS-R wordt geen aandacht besteed in deze presentatie.

Het protocol werkt op de volgende wijze.
Read the rest of this entry »

Posted by Eric Gunnewegh at 9:24 on Friday 3 November    Add 'Introducing JAX-WS 2.0 With the Java SE 6 Platform, Part 2' site to delicious  Add 'Introducing JAX-WS 2.0 With the Java SE 6 Platform, Part 2' site to technorati  Add 'Introducing JAX-WS 2.0 With the Java SE 6 Platform, Part 2' site to digg  Add 'Introducing JAX-WS 2.0 With the Java SE 6 Platform, Part 2' site to dzone

Learn how to create a Java technology-based client for the eBay production server. You’ll use the Java API for XML Web Services (JAX-WS) tools in the Java SE 6 platform, as well as Web Services Definition Language (WSDL).

Read more on the SDN.

Posted by Eric Gunnewegh at 7:54 on Wednesday 13 September    Add 'Introducing JAX-WS 2.0 With the Java SE 6 Platform, Part 1' site to delicious  Add 'Introducing JAX-WS 2.0 With the Java SE 6 Platform, Part 1' site to technorati  Add 'Introducing JAX-WS 2.0 With the Java SE 6 Platform, Part 1' site to digg  Add 'Introducing JAX-WS 2.0 With the Java SE 6 Platform, Part 1' site to dzone

One of the most exciting new features of the Java Platform, Standard Edition 6 (Java SE 6) is support for the Java API for XML Web Services (JAX-WS), version 2.0. JAX-WS 2.0 is the center of a newly rearchitected API stack for web services, which also includes Java Architecture for XML Binding (JAXB) 2.0 and SOAP with Attachments API for Java (SAAJ) 1.3.

Read more about JAX-WS in Java SE 6 here.

Posted by Eric Gunnewegh at 11:28 on Friday 8 September    Add 'Axis2: The Next Generation of Apache Web Services' site to delicious  Add 'Axis2: The Next Generation of Apache Web Services' site to technorati  Add 'Axis2: The Next Generation of Apache Web Services' site to digg  Add 'Axis2: The Next Generation of Apache Web Services' site to dzone

Apache Axis2 is an effort to incorporate the latest changes in the Web services space and to improve performance and efficiency. During a face-to-face meeting in Colombo, Sri Lanka, in August 2003, some of the leading architects of Apache Axis 1.x got together and initiated Apache Axis2, the next generation of Apache Web services. A new architecture was introduced to fulfill the current demand, taking the best patterns and usage scenarios from Axis 1.x. Key improvements and new features included:

- A new XML processing model
- A messaging-based extensible core
- An improved deployment model
- Pluggable data binding support
- Asynchronous and synchronous Web services invocation

java.net

Posted by Eric Gunnewegh at 8:29 on Tuesday 18 July    Add 'Introducing Axiom' site to delicious  Add 'Introducing Axiom' site to technorati  Add 'Introducing Axiom' site to digg  Add 'Introducing Axiom' site to dzone

The Apache Web services community introduced AXIOM (Apache aXIs Object Model) as a fast-performing and memory-efficient object model for their Web service engine, Axis2. In this article, Eran Chinthaka describes the architecture of Axiom and explains how it works with StAX.

Posted by Eric Gunnewegh at 10:33 on Monday 3 July    Add 'Mustang: The fast track to Web services' site to delicious  Add 'Mustang: The fast track to Web services' site to technorati  Add 'Mustang: The fast track to Web services' site to digg  Add 'Mustang: The fast track to Web services' site to dzone

The upcoming release of Java Platform, Standard Edition (Java SE) version 6.0, also known as Mustang, makes development and consumption of Web services a breeze. It brings the power of metadata (just type @WebService and you are almost done) to simple Java classes, enabling them to be deployed as Web services. It also brings the Java API for XML Web Services to clients consuming those services. This article takes a hands-on approach to developing metadata-based Web services and thereafter consuming them using JAX-WS.


© 2019 Java Competence Network. All Rights Reserved.