quickstart shows you how to write a resource using the Java API. We use
the term resource because you can put any file in an application.
The xfa namespace does not resolve to an actual resource. It is a unique
URI that Adobe owns and we use to qualify the xfa prefix. Here is an
exerpt from the W3C recommendation for namespaces:As you can see, it is
not a goal that the URI be directly usable. It's main goal is to provide
a unique definition for a prefix - in our case xfa.
In your xml document, email is a node - not an attribute.The xPath
expression should be:/process_data/myXML/records/record/emailThe
location uses the @strEmail notation because as an LC process variable,
it's a simple value (String) and treated as an attribute of the process.
Looks like you have encountered a bug in the product .While the //Person
xPath query does in fact return the correct number of nodes found within
the XML source, it appears that there is some eroneous logic in
processing the xPath statement when nodes are childeren of a different
parent. For example, when I run some tests on the XML you sent me:I can
infact return node //Person and Person which are children of
. LC seems to not be able to locate the nodes
under and .I will log this on yo...
I was using the preview release of Flash Builder (Burrito) and the Flex
4.5 (Hero) SDK to build an application that runs on an Android device. I
created a simple view and included the SimpleChat component. As soon as
I try to run the application, I get an exception that states that
mx.controls.TextArea could not be found.Now, this makes sense since the
Flex 4.5 SDK does not support MX controls for mobile.Is there any work
being done to provide Spark implementations of the LCCS controls such as