> use cases where the expression appears within curly braces, e.g. in a > function body, were particularly noticeable. That is a of course a question of taste, but I think I’d prefer such an explicit way of sequence construction
More:
Comma problem Re: ANSWERS to "What’s wrong with
XQuery" question
> * make your new version a clean break with the past (and change the names) – > that tends to mean you will end up with a large user community who don’t > move forward, because it’s too much work. There is a fourth choice, there are even people making incompatible changes all the time, but not caring about backwards compatibility or renaming (e.g. ObjectWeb ASM); but I think that is just bad engineering 
Martin
Read more from the original source:
module versioning
> It was somewhat surprising to me, coming from that background, that the precedence of “,” was so low, and from the other responses, it seems some others shared (or at least have been made aware of) the same confusion, although it is, as you say, easily remedied. The explanation of why the precedence is so low lies in the overloading of “,” to separate arguments in a function call, which was something where we really had no choice. This meant that we needed the concept of “ExprSingle” to mean “an expression not containing a top-level comma” to define what was allowed as a function argument, and this decision led to “,” having lower precedence than any other operator
See the original post here:
Comma problem Re: ANSWERS to "What’s wrong with
XQuery" question
On 28/07/2010 22:47, Pavel Minaev wrote: > An obvious alternative would be to provide some explicit top-level > construct that introduces (and clearly delineates) an XML fragment as > a sequence of direct element constructors, with no need for > interleaving commas. …… /*
Continue reading here:
Comma problem Re: ANSWERS to "What’s wrong with
XQuery" question
Daniela Florescu wrote: > On Jul 19, 2010, at 3:46 PM, Michael Kay wrote: Hi, I am sorry to respond to a quite old thread, I am still going through my unread emails, because I am back from holidays… > > I think if I were writing a library for a vocabulary where > > schema validation is the norm (like FpML , say), > What would you do for the EXPath’s HTTP module ?
Link:
Schema Typed Parameters and Return Values in
Library Modules
To be fair to my colleagues, the product’s documentation and the massive online tutorials we have published explain well what XQJ is and how to use DataDirect XQuery. http://web.datadirect.com/resources/dis/xqj-tutorial/index.html True, DataDirect XQuery is a commercial product, an enterprise -class implementation and an embeddable component. but that doesn’t mean that it cannot be easily used for querying plain XML.
With the recent (April 2010) SOA Suite 11g R1 Patch Set 2 (11.1.1.3.0), several new capabilities have been added to the SOA Suite.
Read the original here:
Publish SOA Composite application as EJB to be invoked from Java applications using EJB Binding
Donderdag as. is de AMIS Query van Doug Burns over SQL Tuning, gebruikmakend van de Oracle Enterprise Manager (Tuning en Diagnostics pack). Misschien verwachten velen een hoog “DBA” gehalte, maar niets is minder waar… Deze presentatie bevat bijna geen enkele slides en is echt een aanrader om bij te wonen.
Read the rest here:
Laatste “Plug” – Cuddly Toys Not Included – Een AMIS Query met Doug Burns
In a recent post I described how we can use the EJB Binding in SOA Suite 11g PS2 to invoke a SOA Composite application through RMI as a remote EJB. This interaction can be fully based on Java interfaces – no WSDL or XML required
See the original post here:
Invoke SOA Composite application through RMI as remote EJB (using binding.adf)
‘Oracle Team Productivity Center (TPC) is an Application Lifecycle Management (ALM) tool that enables software development teams to collaborate and work productively together when developing applications using JDeveloper.’ (OTN TPC page) TPC provides unified access to different ALM repositories from within JDeveloper and it allows to define relations between the so-called work-items in these (separate) repositories.
See more here:
Oracle Team Productivity Center
