Posts tagged XML
In our current webservice project with JAX-WS in Â JDeveloper Â 188.8.131.52 we have a challenge with calling a webservice. This webservice from a remote organisation does not accept specific SOAP header elements our client application creates – although we followed the contract of the WSDL correctly. Of course this webservice must follow it as well as we have to, but for now we donâ€™t have a choice but to make a workaround. Â How can we remove unwanted elements from a SOAP header? In this blog I will show you how you can do that using a JAX-WS SOAPHandler that inspects the SOAP header and removes specific addressing elements. (more…)
For a couple of months I have been discovering the Android platform. As an original Oracle developer I was wondering how an Android app can be connected to an Oracle database. For this purpose I developed an Android app that stores speed traps that users may hit while driving, into an Oracle database. The app also retrieves these speed traps from the database and draws them onto a Google map:
Yesterday evening we had our annual Oracle Open World review at our office in Nieuwegein. Around eighty people attended and all were very involved with the session. Five AMIS employees were at Oracle Open World, and each one covered one area of interest.
Before dinner Lucas gave an overview of the trends and topics that were covered at Oracle Open World. Just to convey the sheer size of OOW, Peter illustrated this by facts (number of people attending, number of lunches served, etc) as well as by photos. I’m still very impressed that they covered a four lane street (Howard street) by a tent, just to serve lunch… amazing. Marco and myself gave an overview of what AMIS was doing at OOW, as well as the Oracle ACE Directors briefing right before OOW started.
There were a number of goodies that we took from Oracle Open World to give away this evening. We decided to do it a little different this year, we organized a BuzzWord Bingo. Each of the attendees was given a bingo sheet with some of the buzzwords that would be covered during our presentations. Before we went for dinner six people had bingo and got their goodies to take home.
This time we had a Mexican Style dinner, very lovely. More >
The Mediator component in SOA Suite 11g has a the option to specify a Java Callout, one for every WSDL operation. The Java Callout refers to a Java Class, either on the SOA Suite's classpath or deployed as part of the SOA Composite application. This class should implement interface oracle.tip.mediator.common.api.IJavaCallout and a convenient way of doing so is by extending AbstractJavaCalloutImpl in package oracle.tip.mediator.common.api.
The Java Callout is invoked by the Mediator on a number of times, prior to and after performing the Routing Rule and each of the cases in it. The Java Callout class can implement a number of methods, one for each specific event or stage in the Mediator process. These methods get access to the input message as well as the transformation result. That means that the callout class can inspect, validate, log, audit and even manipulate these messages, their payloads, headers and properties. Interestingly enough, the methods are not static what I thought might be the case. The first one to be called is an initialize() that has you initialize the callout class instance to prepare the object for further callout processing. This means that all stages More >
While looking into the XML functionality in JDeveloper 11g, I came across a feature that was added in the 184.108.40.206.0 release – July 2009: [Create] XML Schema from XML Document. Functionality previously found in commercial products such as XMLSpy, that enables us to make a head start with the development of XML Schema Definitions by using an existing XML Document as starting point.
In this article, I will very briefly demonstrate what this functionality allows us to do. And what its current limitations are.
In short: we can indicate an XML document and have an XSD created that derives its element, type and attribute definitions from the actual XML content in that document. Most XML documents do not represent the entire set of restrictions and freedom that the XSD will describe, so the generated XSD is only a starting point – but a very useful one all the same.
At this moment, the XML source document has to exist on the file system (we cannot feed the tool with a URL). The created XSD document does not work well with multiple namespaces – as well will see in this example. The tool does not create named (complexTypes) – only (nested) elements. It does create, when so requested, More >