Bug - xsl mapper

version 10.1.3.3.0.4157 Studio, doing ESB work.
trying to validate an XSD I need for work and using the Test XSL map
the inbound and outbound XML documents autogenerated by the mapper have errors.
Traced to
the XSL mapper not auto-generating correct data for the following XSD fragment
<xs:element name="upload-tag" minOccurs="0" maxOccurs="unbounded">
<xs:simpleType>
<xs:restriction base="xs:string">
<xs:pattern value="[a-zA-Z]{3}[0-9]{14}"/>
</xs:restriction>
</xs:simpleType>
</xs:element>
instead of abc12345678901234 a null string is returned causing both the source and target to have XML validation errors.
easy to get around, just fill in your own data abc12345678901234
BRGDS
Chris

Thanks Chris,
can you post this issue to SOA Suite forum?
SOA Suite
ESB is not a feature developed by the JDeveloper team
Frank

Similar Messages

How to use key() function in XSL Mapper file?

I would like to use the XSLT key() function in an XSL stylesheet in the XSL Mapper designer, but I can find no way to include the <xsl:key> element.
key() should be supported as it is available in the component palette, but I can't find a way to add <xsl:key> in the designer, and if I add it manually the designer tells me it is not supported.
This is with Jdeveloper JDEVADF_11.1.1.3.PS2_GENERIC_100408.2356.5660 on Linux.
Any help appreciated, thanks.

The usual practice is to leave the XSLT as such. A person skilled in XSLT would know to open the XSLT in source mode if the design view is not supported. Almost most of AIA XSLTs are such and one has to only open them in source view.
You might want to document this into some document/guide which the person might refer before actually making the changes!
Cheers,
- AR

XSL Mapper JDeveloper plugin fails to launch from App Engine

XSL Mapper JDeveloper plugin fails to launch from App Engine ONLY WHEN THE TARGET LOCATION OF THE SERVICE CONFIGURATION POINTS TO AN HTTPS URL.
If I make the target location field of the service configuration point to an HTTP url, the plugin launches fine.
The error message indicates that there is a missing certificate in the chain:
oracle.tip.tools.ide.common.xsdgrammar.SchemaGrammarException: sun.security.validator.ValidatorException: No trusted certificate found
A basic google search on this error leads me to believe that I need to add a key to the java clients keystore on my PC. Can anyone confirm or deny this? Has anyone else encountered this?

After digging pretty hard I believe I've found the cause and two possible solutions...and I quote...
"This seems to be a known conflict between versions of the Digi 001, the Audio Media III card, Panther OS, Pro Tools, and QuickTime 7 and above. This Mac is running...
OS Panther 10.3.9
Pro Tools LE 6.2.2
This is what I've found from http://sillydog.org/forum/sdt_8928.php (page three of this thread).
"testing has yielded that the Audio Media III card can be used with Pro Tools LE 6.2.3 on a platform as high as OSX Panther 10.3.9 as long as you do not (I repeat do not) install QuickTime 7ever. The QuickTime 6.5.2 re-installer will not remove problems created by installing QuickTime 7."
"Basically if you are running what Digidesign refers to as “Legacy” hardware. Audio Media III/ Toolbox or the Digi 001. You are running a version of Pro Tools LE that is incompatible with QuickTime 7. If at any point QuickTime 7 is installed you must re-install (the OS and all programs) to delete its effects, and are stalled on OSX 10.3.9 (w/o QuickTime 7)."
Knowing this, I was able to find a possible solution here... http://fox-gieg.com/tutorials/2005/undo-quicktime-7/
The other solution is to upgrade equipment, or re-install OS and other Apps to go backwards.
Hope this helps some people!

XSL mapper problem with namespace defined in the element

Hi.
Using XSL Mapper from JDeveloper, I have imported one xsl that now is working and it generates an error. The source for the mapper is:
<xsl:stylesheet xmlns:xsl="http://www.w3.org/1999/XSL/Transform" xmlns:ns4="http://sample.com" xmlns:ns3="http://sample2.com" version="1.0">
<xsl:template match="/">
<soapenv:Envelope xmlns:soapenv="http://schemas.xmlsoap.org/soap/envelope/">
And I get
Line Number:(25) : Error: "soapenv:Envelope" Element not Found in Target Schema
But, if I change a little bit the definition, I solve the error.
<xsl:stylesheet xmlns:xsl="http://www.w3.org/1999/XSL/Transform" xmlns:ns4="http://sample.com" xmlns:ns3="http://sample2.com" xmlns:soapenv="http://schemas.xmlsoap.org/soap/envelope/" version="1.0">
<xsl:template match="/">
<soapenv:Envelope >
Why is this happening? It will make a lot of work trying to change all the old transformations that are well formed according with w3 specifications.
Thanks in advance.
Regards

Hi,
Perhaps it would help if you post your XML file.

How to configure the Oracle XSL Mapper for schemaLocation attribute?

In the Transformation_1.xsl I need to have the schemaLocation attribute defined as such:
<inc:CaseIncidentReport xsi:schemaLocation="http://caseincidentreport.com/1.0.4 CaseIncidentReport.xsd">
This is fine as long as long as I dont switch to the Design tab. When I switch to the Design tab, Oracle XSL Mapper regenerates the XSL file and renders the root element as
<inc:CaseIncidentReport>
Can some one tell me how to configure Oracle XSL Mapper for schemaLocation attribute? I am using BPEL Designer/JDeveloper Version 10.1.2.1.0 (Build 1915)
Thanks,

What do you mean by normal import? Where can I include the 'schemaLocation' attribute in the Designer? I have no trouble adding the shemaLocation in the source tab but when I switch to the design tab it always stripe it off.
How do I file an enhancement request? I see the the XSL Mapper needs improvements.
Thanks,
Nathan

Question about XSL Mapper in BPEL designer

Hi,
I have a question regarding the XSL mapper within JDeveloper BPEL Designer.
Scenario:
Consider
1. Source xsd with 3 attributes
2. Target xsd with 5 attributes
An XSL mapping is defined for 3 source attributes to the corresponding target attributes.
The attributes remaining on the target side (2 attributes) are NOT mapped.
Now test the mapper using the in-built test tool
(by right clicking on the xsl editor screen).
The mapper generates a test-xml on the source side and its corresponding transformed xml on the target side.
Now,
If i click on "Validate" in the source side, it says "XML is Valid"
If i click on "Validate" in the target side, it says "XML is NOT Valid" (because the 2 un-mapped attributes are not apprearing the target xml)
My question is
Is it an expected behaviour that if an attribute is not mapped, an empty tag <attribute/> is not generated for this attribute in the target xml. If so, wouldn't the target xml be invalid with respect to the target xsd.
Thanks
Antony

I believe by default xml validation is set to false for a BPEL Domain. I am not sure whether setting this to true will cause your process to error out after the transformation or if it only validates inbound and outbound messages.

XSL mapper not working

When i try to open an XSL file in jDeveloper, it complains about the first line in the file is invalid, <?xml version="1.0" encoding="UTF-8" ?>, which is originally generated by the XSL mapper and perfectly valid.
because of this complaint, the mapper designer refused to open.
after a good few hours of investigation, i found that this only happens when i start jDev "directly" by starting jdeveloper.exe
if i go into JD Edwards OMW (object management workbench) and invoke jDev from there, the mapper works fine.
how weird is that!
anyone from Oracle can explain this? and maybe provide a work around?
Thanks!

We've been using JDeveloper/SOA Suite for almost 2 years now and this mapper issue happens now and then. No real explaination why other than it seems to be a memory issue and maybe something also with network speed. It seem to get worse when I try to work at home via VPN and I have Verizon Fios so speed shouldn't be an issue. All that seems to solve it is to close out and even log off for the memory resources to clear up.
I've opened a couple of tickets over this issue in the past but got nowhere.

Oracle-xsl-mapper-position

What is the exact use of oracle-xsl-mapper-position in xslt?
Can you please help with some example.
Thanks in advance

oracle-xsl-mapper-position in xslt to find out the position of a node in a loop.
For e.g.
<Array>
<String1></String1>
<String2></String2>
</Array>
Now if we want the position of each node in Array then we use the position() function.
Regards,
Anshul

XSL Mapper Extension

Hi
I am considering writing a Java extension functions for XSL Mapper in BPEL to do DB read. Is this possible? Also, How can I throw exceptions from this function?
Thank you.
Message was edited by:
user508086

consider using ora:dbLookup or follow the sample in
$BPEL_HOME/integration\orabpel\samples\references\CustomXPathFunction
or $BPEL_HOME\integration\orabpel\samples\demos\XSLMapper\ExtensionFunctions
hth clemens

JDeveloper extension with XSL mapper

We want to develop a JDeveloper custom extension (a wizard). In one of the wizard pages, we want to use the JDeveloper's XSL mapper for one of the function.
Can you please advise whether it is possible. If yes, any details would be highly appreciated.
Thanks.

chk this
http://docs.oracle.com/cd/E11036_01/doc.1013/e10295/xslt_mpr.htm
you should have SOA composite application extension for this..
if you dont want a visual transformation then you can use the jdeveloper project properties -> Run/Debug -> edit run configuration -> XSLT

Export of BPEL process : ?oracle-xsl-mapper? is missing from XSL file

Hi,
I am trying to export a BPEL process from Enterprise Manager 11g console (version:11.1.1.2.0). After exporting, i dont see the tag <?oracle-xsl-mapper?> inside xsl/*.xsl files.Because of this i couldnt open the transformation from Jdeveloper.Is any one faced this issue.Is there any workaround for this.
thanks,
ashok

Most of the deploy files are also BPEL Unix server. Login to BPEL Unix server and looking for deploy files /apps1/u10/BPEL/bpel/domains/default/tmp. Identify the .xsl file and replace in it your Jdevelper work folder.

JDeveloper performance with XSL Mapper

Hi All,
Not sure if this is the right place to ask this question since it has to do JDeveloper performance with SOA and not ADF.
In the XSL Transformation mapper tool, whenever I do an auto-map between two large schemas, my JDeveloper memory usage hikes up to about 1.3 GB and then both the JRE and JDeveloper hangs although the transformation finishes. The problem is that sometimes it hangs before you can save it. It almost seems like a memory leak.
NOTE: I am not getting any out-of-memory error since I increased already increased the memory.
Any help to optimize and solve this problem will be very helpful.
Thanks!

chk this
http://docs.oracle.com/cd/E11036_01/doc.1013/e10295/xslt_mpr.htm
you should have SOA composite application extension for this..
if you dont want a visual transformation then you can use the jdeveloper project properties -> Run/Debug -> edit run configuration -> XSLT

ESB RoutingService, routing rule, xsl mapper fails

Hi!
I've got the next situation.
I need to create a routingservice in ESB from the next wsdl (http://www.egem.nl/kennisbank/informatievoorziening/uitwisseling/stuf/stuf30stufsoa/stuf3familiepakket?searchterm=stuf) > bg030002.beantwoordVraag.wsdl
The wsdl imports some other wsdl's and those import some xsd's.
And ..i assume .. this is where is goes wrong.
When i create the routingservice, and use the wsdl from the url i just mention, everything is ok.
After this i want to routing from 1 operation in this wsdl to my testbpel, just to test if the routing from the whole process. I create in the routingservice the routingrule, and click the "create xsl mapping".
Next error pops up :
Failed to open the source schema:
The schema does not contain the global element
{http://www.egem.nl/StUF/sector/bg/0300}:adrLv01
i checked all the namespaces/imports/xsd/etc...element is there in the xsd and the imports should all be ok.
Any of you got an idea of what could be the problem of this ?
Possible solution would be to create 1 wsdl with just 1 import for the xsd, but in this case i need to refactor all the existing files, so i would rather hope one of you could help me into the good direction before i start on this.
Thanks for your time!

Hi,
Some things I've came across, maybe it helps:
* Are all the used namespaces declared in the XSL file? Maybe the mapper tool only declares the namespaces + prefixes from the top-level XSD's, not those of the underlying imported schema's.
* Do any of the imported XSD's have the same targetNamespace declared? Do all imported XSD's have a targetNamespace set?
* All WSDL's and XSD's are probably valid according to JDeveloper?
* If you create a routing service and do not use your WSDL but let JDeveloper generate it (Generate WSDL from Schemas) and then use the toplevel XSD, do you get the same error?
* Are some of the imported XSD's deployed more than once in the ESB; e.g. as part of more than one ESB flow?
Refactoring usually reveals the problem, but as you said not the nicest thing to so :-(
Regards, Ronald

Creating XSL Mapper extension

Is there an easy to understand tutorial with all the step to add a component to the "User Defined Extension Functions" pallet. I want to create a function that call a database stored procedure and be able to use it in an xsl map.

Try asking this on the SOA Suite forum.

Bug w/ xsl:attribute-set in java xdk

Hi - I found what seems to be a bug in the 9.0.0.2.0.0A xdk beta for java. In xsl, if you have an empty xsl:attribute-set (one that uses other attribute sets but does not define any of it's own), the XSL Processor gives an internal error. Adding an attribute to the set fixes the problem.
Example:
<xsl:attribute-set name="foo" use-attribute-sets="set1 set2"/>
Gives:
(Error) An internal error condition occurred. at oracle/xml/parser/v2/XSLProcessor.reportException (XSLProcessor.java:694) at oracle/xml/parser/v2/XSLProcessor.newXSLStylesheet (XSLProcessor.java:500) at oracle/xml/parser/v2/XSLStylesheet.<init>
Changing it to:
<xsl:attribute-set name="foo" use-attribute-sets="set1 set2">
<xsl:attribute name="bug"/>
</xsl:attribute-set>
Gives:
No error
Is this a bug or are you required to define at least one new attribute in every attribute set?
null

correct typos:
I can't reproduce the error you got by defining the following stylesheet. Please let me know if anything I misunderstand.
XSL:
<xsl:stylesheet xmlns:xsl="http://www.w3.org/1999/XSL/Transform"
version="1.0">
<xsl:attribute-set name="set1">
<xsl:attribute name="set1">good</xsl:attribute>
</xsl:attribute-set>
<xsl:attribute-set name="set2">
<xsl:attribute name="set2"/>
</xsl:attribute-set>
<xsl:attribute-set name="foo" use-attribute-sets="set1 set2">
</xsl:attribute-set>
<xsl:template match="/">
<out xsl:use-attribute-sets="foo">this is a try</out>
</xsl:template>
</xsl:stylesheet>
RESULT:
<?xml version = '1.0'?>
<out set1="good" set2="">this is a try</out>
null

Bug - xsl mapper

Similar Messages

Maybe you are looking for