New XSL processor release 2.2.0.8 ?

When can we expect the XSL processor release (2.2.0.8 ?) with the multi-thread bug fix?
Thanks,
null

Hi,
I replaced my previous ohw jar with ohw-2.0.6.jar: the issue regarding NPEs reported in the log when using the Tree Based TOC Navigator has been fixed. Thanks.
But now my branding logo has disappeared. In the ohwconfig.xml file, I wrote:
<brandings>
<branding imageSource="/helpsets/logo.gif" />
</brandings>
When I use the previous jar, the image location is interpreted as:
http://localhost:8080/ohw/help/webapp/2.0.0.0/helpsets/logo.gif
and the logo is displayed.
When I use the new jar, the image location is interpreted as:
http://localhost:8080/ohw/help/webapp/HELP_MAIN_NT_050310/helpsets/logo.gif
and the logo doesn't show. How come?
Thanks for your help,
Pierre

Similar Messages

Converting XML in WML using XSL Processor from XMLParser v2

When trying to concert an XML doc into WML, it seems like the XSL Processor is removing some WML tags. Below are the XML doc and XSL doc I am using :
The XML DOC
<?xml version="1.0"?>
<ROWSET>
<ROW id="1">
<NAME>RestaurantName</NAME>
<ADDRESS>RestaurantAddress</ADDRESS>
<PHONE_TYPE>Fixed</PHONE_TYPE>
<PHONE>0112345678</PHONE>
<PRICE>60</PRICE>
<MENU>Salad, Pizza</MENU>
<DESCRIPTION>Very good restaurant</DESCRIPTION>
</ROW>
<ROW id="2">
<NAME>SecondRestaurantName</NAME>
<ADDRESS>SecondRestaurantAddress</ADDRESS>
<PHONE_TYPE>Fixed</PHONE_TYPE>
<PHONE>0187654321</PHONE>
<PRICE>60</PRICE>
<MENU>Salad, Fish</MENU>
<DESCRIPTION>Godd restaurant</DESCRIPTION>
</ROW>
</ROWSET>
The XSL DOC
<?xml version="1.0"?>
<xsl:stylesheet xmlns:xsl="http://www.w3.org/1999/XSL/Transform">
<xsl:template match="/">
<WML>
<CARD>
<xsl:apply-templates/>
</CARD>
</WML>
</xsl:template>
<xsl:template match="ROWSET">
<xsl:for-each select="ROW">
<xsl:value-of select="NAME"/>
<xsl:value-of select="ADDRESS"/>
Phone : <xsl:value-of select="PHONE"/>
Price of the menu : <xsl:value-of select="PRICE"/>
You can order : <xsl:value-of select="MENU"/>
<xsl:value-of select="DESCRIPTION"/>
</xsl:for-each>
</xsl:template>
</xsl:stylesheet>
The
tag are removed by the XSL Processor ; In fact it seems that any tag contained within <xsl:template match="ROWSET"> and </template> is removed. This does not occurs with other XSL processor (such as lotusxsl).
Is there something I'm doing wrong ??

Your examples works correctly for me using the XSLT engine that comes with release 2.0.2.6 of the Oracle XML Parser "v2" for Java.
Are you working with this latest release?

XDK9.2.0.2, pb with JAXP and XSL Processor

Hello,
I'm using XDK 9.2.0.2 and I try to use JAXP.
I have a difference between using the Oracle XSL processor directly and through JAXP.
Through JAXP, the processor don't care about the xsl:outpout encoding attribute !
Why ?
It take care of method, indent, ... but not encoding !
I try to set the property with : transformer.setOutputProperty(OutputKeys.ENCODING, "iso-8859-1");
It works but I don't want to do that this way !
TIA
Didier
sample (from XSLSample2):
/* $Header: XSLSample2.java 07-jan-2002.02:24:56 sasriniv Exp $ */
/* Copyright (c) 2000, 2002, Oracle Corporation. All rights reserved. */
* DESCRIPTION
* This file gives a simple example of how to use the XSL processing
* capabilities of the Oracle XML Parser V2.0. An input XML document is
* transformed using a given input stylesheet
* This Sample streams the result of XSL transfromations directly to
* a stream, hence can support xsl:output features.
import java.net.URL;
import oracle.xml.parser.v2.DOMParser;
import oracle.xml.parser.v2.XMLDocument;
import oracle.xml.parser.v2.XMLDocumentFragment;
import oracle.xml.parser.v2.XSLStylesheet;
import oracle.xml.parser.v2.XSLProcessor;
// Import JAXP
import javax.xml.transform.*;
import javax.xml.transform.dom.*;
import javax.xml.transform.stream.*;
public class XSLSample2
* Transforms an xml document using a stylesheet
* @param args input xml and xml documents
public static void main (String args[]) throws Exception
DOMParser parser;
XMLDocument xml, xsldoc, out;
URL xslURL;
URL xmlURL;
try
if (args.length != 2)
// Must pass in the names of the XSL and XML files
System.err.println("Usage: java XSLSample2 xslfile xmlfile");
System.exit(1);
// Parse xsl and xml documents
parser = new DOMParser();
parser.setPreserveWhitespace(true);
// parser input XSL file
xslURL = DemoUtil.createURL(args[0]);
parser.parse(xslURL);
xsldoc = parser.getDocument();
// parser input XML file
xmlURL = DemoUtil.createURL(args[1]);
parser.parse(xmlURL);
xml = parser.getDocument();
// instantiate a stylesheet
XSLProcessor processor = new XSLProcessor();
processor.setBaseURL(xslURL);
XSLStylesheet xsl = processor.newXSLStylesheet(xsldoc);
// display any warnings that may occur
processor.showWarnings(true);
processor.setErrorStream(System.err);
// Process XSL
processor.processXSL(xsl, xml, System.out);
// With JAXP
System.out.println("");
System.out.println("With JAXP :");
TransformerFactory tfactory = TransformerFactory.newInstance();
String xslID = xslURL.toString();
Transformer transformer = tfactory.newTransformer(new StreamSource(xslID));
//transformer.setOutputProperty(OutputKeys.ENCODING, "iso-8859-1");
String xmlID = xmlURL.toString();
StreamSource source = new StreamSource(xmlID);
transformer.transform(source, new StreamResult(System.out));
catch (Exception e)
e.printStackTrace();
My XML file :
<?xml version="1.0" encoding="ISO-8859-1"?>
<ListePatients>
<Patient>
<Nom>Zeublouse</Nom>
<NomMarital/>
<Prinom>Agathe</Prinom>
</Patient>
<Patient>
<Nom>Stick</Nom>
<NomMarital>Laiboul</NomMarital>
<Prinom>Ella</Prinom>
</Patient>
<Patient>
<Nom>`ihnotvy</Nom>
<NomMarital/>
<Prinom>Jacques</Prinom>
</Patient>
</ListePatients>
my XSL file :
<?xml version="1.0" encoding="ISO-8859-1"?>
<xsl:stylesheet xmlns:xsl="http://www.w3.org/1999/XSL/Transform" version="1.0">
<xsl:output method="html" omit-xml-declaration="yes" indent="yes" encoding="ISO-8859-1"/>
<xsl:template match="*|/"><xsl:apply-templates/></xsl:template>
<xsl:template match="text()|@*"><xsl:value-of select="."/></xsl:template>
<xsl:template match="/">
<HTML>
<HEAD>
<TITLE>Liste de patients</TITLE>
</HEAD>
<BODY>
<xsl:apply-templates select='ListePatients'/>
</BODY>
</HTML>
</xsl:template>
<xsl:template match='ListePatients'>
<TABLE>
<xsl:for-each select='Patient'>
<xsl:sort select='Nom' order='ascending' data-type='text'/>
<TR TITLE='`ihnotvy'>
<TD><xsl:value-of select='Nom'/></TD>
<TD><xsl:value-of select='NomMarital'/></TD>
<TD><xsl:value-of select='Prinom'/></TD>
</TR>
</xsl:for-each>
</TABLE>
</xsl:template>
</xsl:stylesheet>
The result :
<HTML>
<HEAD>
<META http-equiv="Content-Type" content="text/html; charset=ISO-8859-1">
<TITLE>Liste de patients</TITLE>
</HEAD>
<BODY>
<TABLE>
<TR TITLE="`ihnotvy">
<TD>`ihnotvy</TD>
<TD></TD>
<TD>Jacques</TD>
</TR>
<TR TITLE="`ihnotvy">
<TD>Stick</TD>
<TD>Laiboul</TD>
<TD>Ella</TD>
</TR>
<TR TITLE="`ihnotvy">
<TD>Zeublouse</TD>
<TD></TD>
<TD>Agathe</TD>
</TR>
</TABLE>
</BODY>
</HTML>
With JAXP :
<HTML>
<HEAD>
<META http-equiv="Content-Type" content="text/html; charset=UTF-8">
<TITLE>Liste de patients</TITLE>
</HEAD>
<BODY>
<TABLE>
<TR TITLE="C C)C(C.C/C4C6C9">
<TD>C C)C(C.C/C4C6C9</TD>
<TD></TD>
<TD>Jacques</TD>
</TR>
<TR TITLE="C C)C(C.C/C4C6C9">
<TD>Stick</TD>
<TD>Laiboul</TD>
<TD>Ella</TD>
</TR>
<TR TITLE="C C)C(C.C/C4C6C9">
<TD>Zeublouse</TD>
<TD></TD>
<TD>Agathe</TD>
</TR>
</TABLE>
</BODY>
</HTML>

You can also use a PrintWriter to wrap a JspWriter
since PrintWriter has a constructor that takes any
Writer instance.I'm having the same problem, I've spent a lot of time
on it but I can't get it work.
Could you post some working code that shows how you
can do it?
Thanks.
It works now, I have used the code:
result = processor.processXSL(stylesheet, xml);
PrintWriter pw = new PrintWriter(out);
result.print(pw);
I had tried this before but there was an error in other place that prevented it to work.
Thank you anyway.

Spawning new entry processors from within an existing entry processor

Is it possible / legal to spawn a new entry processor (to operate within a different cache) from within an existing entry processor.
E.g we have a parent and a child cache, We will receive an update of the parent and start an entry processor to do this. Off the back of the parent update we will also need to update some child entries in another cache and need to start a new entry processor for the child entries. Is it legal to do this?

Hi Ghanshyam,
yes, in case of (a), you would be mixing different types in the same cache. There is nothing wrong with that from Coherence's point of view, as long as all code which is supposed to access such objects in their deserialized form is able to handle this situation.
This means that you need to use special extractors for creating indexes, and you need to write your filters, entry processors and aggregators appropriately to take this into account. But that's all it means.
The EntryProcessor on the child could be invoked, so long as there are more service
threads configured. This allows retaining partition affinity. I don't think this is technically
illegal.It is problematic, as invoking an entry-processor from another entry-processor in the same cache service can lead to deadlock/livelock situations. You won't find it out in a simple test as you get an exception or not.
But even if it is technically not guarded against, firing a second entry-processor consumes an additional thread from the thread-pool. Now if you get to a situation when all (or at least more than half of the thread-pool size) of your entry-processors try to fire an additional entry-processor, and there are no more threads in the thread-pool, then some or all would be waiting for a thread to be available, and of course none would be available, because there are not enough single-thread entry-processors to leave to get a thread to everyone.
However, none of them can back off as all are waiting for the fired entry-processor to complete. Poof, no processing is possible on your cache service.
Another problematic situation which can arise if entry processors are fired from entry processors is that your entry-processors may deadlock on entries (entry processors executing on some entries and trying to execute on another entry on which another entry processor executes and also tries to execute on the first entry). In this case the entry-processors would wait on each other to execute.
No code running in the cache server invoked by Coherence is supposed to access a cache service from code running in the threads of the same cache service, except for a couple of specifically named operations which only release resources but not consume additional new ones.
Best regards,
Robert

I purchased an iPad mini on October 10th. I want to return it and get the new ipad mini retina when it comes out. How do I do that if the new ipad mini release date isn't until "later in November", which is beyond the 14 days from my purchase date?

I purchased an iPad mini on October 10th. I want to return it and get the new ipad mini retina when it comes out. I am currently still within the 14 day return/exchange window but how can I exchange it if the new ipad mini release date isn't until "later in November", which would be beyond the 14 days from my purchase date? If apple announces a new version of a product you just purchased but won't actually release it for more than 14 days, how can you possibly exchange the one you just bought? Is my only option to return the one I bought on the 10th (so return by 10/24) and then not have an iPad until the new one is available for purchase? Or would it make any sense to return the one I bought, get a new one, which would presumably have another 14 day return window, and then exchange THAT one for the new ipad mini w/ retina when it comes out (hopefully within that second 14 day window)?

Call the apple store you got it from and ask them. Sometimes in the past they've extended the 'no questions asked return' but only Apple can tell you for sure.

I pre-ordered an iPhone 6 Plus and the delivery date now says October 14th. The point of the pre-order is to get it on release day (or shortly thereafter). Can I go to a Verizon store to pick up my new phone on release day?

I pre-ordered an iPhone 6 Plus and the delivery date now says October 14th. The point of the pre-order is to get it on release day (or shortly thereafter). Can I go to a Verizon store to pick up my new phone on release day?

I'm not sure that answers the question Candice.
I'm in the same situation. I was up trying to get on the Verizon page at 11:55, kept getting the ECPD error. When finally got through, the Silver Iphone Plus 64 showed arrival of 9-19. At every step of the process, it seemed that I was ordering a phone that would arrive on day1. At no point did it say this was an estimate. At no point did it say it might change. In a big yellow box, it said "9-19". Ordered it, then got confirmation email stating it should arrive at 9-19. Seems like all should be good, right? Order site said 9-19, I've got a confirmation email saying 9-19, done and done.
Then I check the website, and suddenly it changed to 10-14?!?!?!? I feel like this was a bait and switch. I was able to pickup an iphone5 in a local store on launch day, and would not have locked myself into a preorder through Verizon if I had known this would happen!
So, that leads back to the original questions. Lets assume I walk into a Verizon store on 9-19, and there is an available iphone6 plus just sitting there, can I either get that phone as fulfillment of my pre-order. Or, cancel my pre-order and buy that phone right then and there?
JJK
PS: It seems there are many people you misled this way. For every person who takes the time to post on this site, there are going to be many many more who are silently ****** off.

Can I get rid of Exchange with the new Server just released?

Hi, I saw the new 8 core machine and all the programs. I also recieved an email from Apple telling me about all the calendaring it has.
I want to get rid of Exchange. I have Outlook on 99.9% the clients, however, and they're not going to get rid of Windows or Office any time soon. Will the new server just released and the server software do Exchange server calendaring, scheduling, etc. just like (or better) than Exchange does?
Thanks.

iCalServer uses the new standard CalDAV protocol for calendaring. Exchange uses MS's own proprietary protocols - we do not have those implemented in iCalServer. As a result your existing Outlook users can't use iCalServer right now.
The good news is that there is at least one group working on a plugin for Outlook that will enable access to iCalServer. Whilst this is still alpha quality right now progress is being made, and hopefully in the near future thee will be something usable. See <http://openconnector.org>.

Xsl:output function fully implemented in XSL-processor?

I'm using XSL-processor as contained in the XML-parser version 2.0.2 in C.
When changing the referring DTD of an incoming XML-message with following XSL-stylesheet
<xsl:output method="xml"/>
<xsl:output ommit-xml-declaration="no"/>
<xsl:output standalone="no"/>
<xsl:output doctype-system="someOther.dtd"/>
nothing seems to happen.
Is <xsl:output> already fully implemented in this C-version of the XSL-processor?
Erwin

Hi,
The xsl:output is not yet implemented. This was specified in the README file.
Thanks,
Oracle XML Team
null

Oracle XSL Processor Bug

Description
We are currently using the XMLData class (oracle.jbo.html.databeans.XmlData)
We submit an XML document having some empty XML elements. We apply an XSL Transformation but we receive a non-conform XML Document in output!!
The problem happens when one of the XML elements is empty. Oracle XSL Processor doesn't close my open tag <textarea> with a </textarea>
XSL template:
<xsl:template name="LigneAvecDetail">
<xsl:param name="value"/>
<xsl:param name="name"/>
<xsl:param name="checkboxtag"/>
<xsl:param name="detail"/>
<tr>
<td xsl:use-attribute-sets='LigneDetailStyle'>
<xsl:choose>
<xsl:when test="string-length($value) < 1">
<input type="checkbox" value="ON" onclick="compute(this)">
<xsl:attribute name="name"><xsl:value-of select="concat('C_', $name)"/></xsl:attribute>
<xsl:attribute name="id"><xsl:value-of select="$name"/></xsl:attribute>
</input>
</xsl:when>
<xsl:otherwise>
<input type="checkbox" value="ON" onclick="compute(this)">
<xsl:attribute name="name"><xsl:value-of select="concat('C_', $name)"/></xsl:attribute>
<xsl:attribute name="id"><xsl:value-of select="$name"/></xsl:attribute>
<xsl:attribute name="checked">TRUE</xsl:attribute>
</input>
</xsl:otherwise>
</xsl:choose>
<xsl:value-of select="$checkboxtag"/>
<textarea rows="2" name="S1" cols="20"><xsl:value-of select="$detail"/></textarea>
</td>
<xsl:call-template name="GroupeRadioBouton">
<xsl:with-param name="value" select="$value"/>
<xsl:with-param name="name" select="$name"/>
</xsl:call-template>
</tr>
</xsl:template>
Here my XML document:
<Results>
<DRIOQ_BilanMe_view>
<NoSommaire>1</NoSommaire>
<AutreInfo>Autre information pertinente au dossier</AutreInfo>
<IdIntervenant>1</IdIntervenant>
<PoumonsRx></PoumonsRx>
<PoumonsTdm></PoumonsTdm>
<PoumonsAutre>B</PoumonsAutre>
<PoumonsAutreDetail>Le commentaire de l'autre detail du poumon</PoumonsAutreDetail>
<OsScint></OsScint>
<OsRx>I</OsRx>
<OsRxDetail>Le commentaire du detail RX de l'os</OsRxDetail>
<OsTdm></OsTdm>
<OsTdmDetail></OsTdmDetail>
<OsAutre></OsAutre>
<OsAutreDetail></OsAutreDetail>
<FoieEnzymes>B</FoieEnzymes>
<FoieEchographie>M</FoieEchographie>
<FoieTdm>I</FoieTdm>
<FoieAutre>B</FoieAutre>
<FoieAutreDetail>Le commentaire de l'autre detail du foie</FoieAutreDetail>
</DRIOQ_BilanMe_view>
</Results>
Thanks!

This is a known bug in the HTML Output method of 2.0.2.6 which is incorrectly
outputting elements like:
<script/>
and
<textarea/>
as
<script> instead of <script></script>
and
<textarea> instead of <textarea></textarea>
This will be fixed in 2.0.2.7. The workaround
is to have some content defaulted into the <textarea> so that it's not an empty element.

Backward Compatibility of New Intel Processor Mac Mini

Will the data files and applications like Quicken 2006 on my old Power Processor Mac Mini transfer to the new Intel Processor Mac Mini?
Mac mini Mac OS X (10.3.9)

Data files will certainly transfer, though applications are not always a matter of such certainty. Most will, but a few non-Intel native ones may not - or may run but not run perfectly if they were not written to conform to the programming guidelines and thus not be fully compatible with Rosetta.
It would do no hard to try, though if you plan to be reliant on PPC applications from your G4 system, be aware that running under Rosetta, they are not likely to give you notable performance gains, even if you max out the RAM in the Intel model. If you plan to update software to Intel-native versions or have those already, a move to the Intel platform will give you significant performance advantages.

New ACR RC released... Looking forward to seeing new features in LR

Adobe just announced ACR 8.5 RC: Camera Raw 8.5 RC and DNG Converter 8.5 RC Now Available
Some very useful new features are included along with the usual support for new camera models, such as the ability to modify gradients with a new brush tool and being able to display a mask overlay for gradients... Nice! Looking forward to seeing LR 5.5 (or perhaps even 6?). No news on a release candidate for LR; perhaps there won't be one as per 5.4.
M

I note this paragraph heading in the notes for the release's new features:
"Camera Raw 8.5 introduces the following new features for Photoshop CC customers"
Could this mean that although the Beta update is stated to be for both CS6 and CC that the new features (outside the camera additions) would not be implemented with a CS6 install?

New Spry Widgets Released

Hi All,
I know that we have been remiss in keeping up with our
ambitious release schedule.
As I mentioned earlier, we were shooting for a full new
release this month but didn't have the time.
Well, we decided to do a 'light launch' for our new Spry
widgets.
We have posted our new Spry widgets and 2 new beta docs here:
http://labs.adobe.com/technologies/spry/samples/preview.html
As you can see we have:
- Menu Bar
-Collapsible Panel
-Tabbed Panel
- Form Text Field
- Form Text Area
- Form Select
- Form Checkbox
- Tabbed Panel doc
- Collapsible Panel doc
As I say there, we are releasing these in this manner because
they are mostly done, but we don't have complete docs for
everything. Once we have full docs and some updates for data, we
will make a new zip and release Spry 1.4.
For now, you can check out these samples and play around with
them.
Let us know what you think.
We also added a new demo here:
http://labs.adobe.com/technologies/spry/demos/formsvalidation/
Hope you like the new stuff.
Thanks,
The Adobe Spry Team

Hi John,
So the thinking on that is this:
They are widgets because they are pieces of markup that
encapsulate advanced functionality. The actual validation is the
major part of the funtionality, but the actual widget is the span
tag container, the input itself, and then additional markup for the
messages. Basic mark-up, style with CSS and a constructor
script=Spry Widget.
As for structure, the 'widgets' folder is where we keep the
latest versions of the real thing. All required widgets resources,
like CSS and JS, plus the basic example file, go in the 'widgets'
folder.
The 'samples' directory is where we put samples that explain
or add onto the basic widget. This is more of a playing around
area.
But we reference the dependent files in the 'widgets'
directory so that we only need to have one copy of the files on the
site and in the zip. This helps ensure that every sample is working
off the same files.
But for you guys, it makes it a pain to get all the required
source files, I know. I was thinking of zipping the new samples and
putting them up so it's easier to download the new stuff.
Make sense?
Thanks,
Don

Will the new iPad be released at 5pm on March 16th or when stores open?

Will the new iPad be released at 5pm on March 16th or when stores open?

We're all just fellow users here and know no more than you do. Call your local Apple Store and ask.
Regards.

Xsl processor and xml parser?

Hello,
Can someone tell me wich is the xsl processor and the xml parser used by Livecycle ES? And their versions?
Thank you

XML Parser parses the text representation of an XML 1.0-compliant document to make the document's information set -- elements, attributes, text, comments, processing instructions, namespace declarations -- available for access to a comptuter program.
Without a parser, a program cannot make heads or tails of the tree of information contained in your tags.
An XSL Processor is a program that takes an XML Document as input, along with an XSLT transformation definition (also known as a stylesheet), and effects the transformation of the source document as instructed by the stylesheet. This might mean transforming:
<ROWSET>
<ROW>
<ENAME>Steve</ENAME>
</ROW>
</ROWSET>
into
<human-resources>
<employee name="Steve"/>
</human-resources>
or alternatively into:
<html>
<body>
<b>Steve</b>
</body>
</html>
In both cases, the source XML document
is the same, but when transformed by
one stylesheet, it might become
the <human-resources> XML document.
When transformed by another stylesheet,
it can become pretty HTML.
To put the two terms in context, an XSL processor uses an XML parser to read the source XML document and to read the XSL transformation definition (aka stylesheet) -- since it, too, is an XML document -- and then it proceeds to transform the source into the target.

XSL processor adding white space

Hi,
Is it possible to prevent the XSL processor from inserting
white space as this can affect HTML table layout & other
things.
For example.
XSL contains the following: (On one line)
<td colspan="2" bgcolor="#000066"><img
src="/images/global_spacer01.gif"/ width="1" height="1"/></td>
is converted to (Three lines)
<td colspan="2" bgcolor="#000066">
<img rc="/images/global_spacer01.gif"/ width="1" height="1">
</td>
~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
null

Dougall Squair (guest) wrote:
: Hi,
: Is it possible to prevent the XSL processor from inserting
: white space as this can affect HTML table layout & other
: things.
: For example.
: XSL contains the following: (On one line)
: <td colspan="2" bgcolor="#000066"><img
: src="/images/global_spacer01.gif"/ width="1" height="1"/></td>
: is converted to (Three lines)
: <td colspan="2" bgcolor="#000066">
: <img rc="/images/global_spacer01.gif"/ width="1"
height="1">
: </td>
: ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
null

New XSL processor release 2.2.0.8 ?

Similar Messages

Maybe you are looking for