XSLT Mapper: a lot of unused import namespaces

Hi.
The only way I have found to substitute an "any" element with a particular one from other schema in the XSLT mapper is to import the schemas in the main one. The problem is when you import a lot of schemas, the result mapper defines all these namespaces at the root level of the xslt (just in case), whether they are used or not. That produces an unnecessary overhead in the xslt file size.
Is there any way to clean up the result mapper, so only the needed namespaces will be defined?
It could seem it is not very important, but now I have 150 namespaces defined, when only 7 are used.
Thanks.
Ramon
Edited by: Ramon Gordillo on Jun 6, 2011 5:19 PM

Hi.
I have been watching for some solutions, like for example the wtp for eclipse, which allows you to select the namespaces and clean them manually (without further checks than a valid XML), but all of the solutions falls in the "select" expressions with xpaths referring namespaces (and some of them, also with QNames elements).
Any help? Oracle masters?

Similar Messages

XSLT Mapper file does not open in design view

XSLT mapper file in the composites exported from weblogic EM as a jar and imported in JDeveloper 11.1.14 does not open in design view. There is no option of design view itself in the tab structure. It is viewable only in source view.
Please suggest, how do I view the desgn view of the xslt mapper?
Thanks,
Promiit

When you export composites from Weblogic EM in jar format, the resulting files are differently formatted from what was used for deployment.
So, basically, the XSLT file, you are trying to open in Jdeveloper has lost the "mapSources" and "mapTargets" sections, which are generally present in the header section of the jdeveloper-generated XSLT file. Try to manually hand-crack those sections and you should be good to go.
Hope it helps !

How to do closing tag: tag /tag instead of tag/ in jdev xslt mapper

Hi!
We have commercial systems, which cannot work with short closing tags for empty nodes.
Xslt mapper for oracle mediator optimize everytime to short closing tag, when node content is empty.
Is there a property or technique to achieve long closing tags?
Kind regards
Torsten

http://www.biglist.com/lists/xsl-list/archives/200610/msg00342.html
not really a pretty solution, but you could try adding the comments

Generating CDATA containing XML-like text using XSLT Mapper in OFM 11g

Hi,
One of our partners requires XML to be sent as XML string inside a CDATA section. The use of "real" XML is not an option at the moment. We try to generate something like the following using XSLT/XSLT Mapper in SOA Suite 11g:
<element>
<![CDATA[
<supplierElement1>
<supplierElement2>
etcetera
<supplierElement2>
</supplierElement1>
]]>
</element>
We've tried the following two approaches, so far unsuccessful:
<xsl:template match="/">
<inp1:singleString>
<inp1:input>
<xsl:text disable-output-escaping="yes"><![CDATA[test]]></xsl:text>
</inp1:input
</inp1:singleString>
</xsl:template>
resulting in:
<inp1:singleString xmlns:inp1="http://xmlns.oracle.com/singleString">
<inp1:input><![CDATA[test]]></inp1:input>
</inp1:singleString>
and:
<xsl:output method="xml" indent="yes" cdata-section-elements="input"/>
<xsl:template match="/">
<inp1:singleString>
<input>test</input>
</inp1:singleString>
</xsl:template>
resulting in:
<inp1:singleString xmlns:inp1="http://xmlns.oracle.com/singleString" xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance">
<input>test</input>
</inp1:singleString>
Does anyone know how to generate the CDATA section declaratively (within XSLT/XSLT Mapper), without resorting to custom code and parsing as we have to do now?
Thanks!
Ronald

The exact error message I'm getting is :
ABAP XML formatting error in XML node of type "element", name: "abap"

How to use xslt mapper with sequence occurences

I'm using Bpel process manager.
I'm trying to use multiple partname fields in my xsd. I'have defined a sequence occurence in my xsd.
In the xslt mapper I see just one partname. How can I map initials, nickname, fullname etc to the 'different' partnames while I just see one.
I'hope somebody can help me?
Jasper Goede

I use the following xsd (just part of the whole xsd):
<xsd:complexType name="nameType">
<xsd:sequence>
     <xsd:element name="partname" type="partnameType" minOccurs="3" maxOccurs="5"/>
     </xsd:sequence>
     </xsd:complexType>
     <xsd:complexType name="partnameType">
     <xsd:sequence>
     <xsd:element name="typename" type="typenamenameType"/>
     <xsd:element name="text" type="nametextType"/>
     </xsd:sequence>
     </xsd:complexType>
In the xslt mapper I just see one text field. So I can connect only nickname to the text field. I suspect more text fields.

Disabling validation in xslt mapper

My xslt source code is valid as per xslt 1.0 and runs correctly when deployed. But the design view of the xslt mapper throws errors. How can I disable the error-checking of the xslt mapper?
Thanks,
Bipin Raj
PS:
Below is the xslt code that I added to my map, followed by the errors I am getting.
<ns0:NOTES>
<xsl:attribute name="index">
<xsl:value-of select='string("1")'/>
</xsl:attribute>
<xsl:for-each select="ns1:Loop-N9_1/ns1:Segment-N9">
<xsl:value-of select="ns1:Element-369"/>
<xsl:text>|</xsl:text>
</xsl:for-each>
<xsl:for-each select="ns1:Loop-N9_1/ns1:Segment-MSG">
<xsl:value-of select="ns1:Element-933"/>
<xsl:if test="position() != last()">
<xsl:text>|</xsl:text>
</xsl:if>
</xsl:for-each>
</ns0:NOTES>
Errors:
Error: Invalid Usage of <for-each> Element
Error: xsl:for-each does not Support Mixed Content
Error: xsl:for-each does not Support Mixed Content
Error: Invalid Usage of <for-each> Element
Error: Invalid Usage of <if> Element
Error: xsl:for-each does not Support Mixed Content
Error: xsl:for-each does not Support Mixed Content
Error: This Node is Already Mapped : "/ns0:PROCESS_PO_007/ns0:DATAAREA/ns0:PROCESS_PO/for-each"
Invalid Source Node Path (//ns1:Transaction-850/ns1:Loop-PO1/ns1:Element-933)
Invalid Source Node Path (//ns1:Transaction-850/ns1:Loop-PO1/ns1:Element-369)

Can you explain a bit more what you want to do. It's very vague right now. Probably will be able to help you out.
Thanks

How to use xslt mapper

I'have created a xsd with sequence occurences. In the xslt mapper I try to connect nickname, initials and full name to the same field, because I just see one field.
Can somebody help me?
Thanks
Jasper

I use the following xsd (just part of the whole xsd):
<xsd:complexType name="nameType">
<xsd:sequence>
     <xsd:element name="partname" type="partnameType" minOccurs="3" maxOccurs="5"/>
     </xsd:sequence>
     </xsd:complexType>
     <xsd:complexType name="partnameType">
     <xsd:sequence>
     <xsd:element name="typename" type="typenamenameType"/>
     <xsd:element name="text" type="nametextType"/>
     </xsd:sequence>
     </xsd:complexType>
In the xslt mapper I just see one text field. So I can connect only nickname to the text field. I suspect more text fields.

Can not find xslt mapper

Hi ,
I need to use the xslt mapper to transform the xml from site A to the xml structure that site B can accept. The documents mention that the xslt mapper is the new featrue for JDeveloper. I download the 11GR2 from Oracle and can not find the tool in it. Some posts said that it is the feature in 10G and then i continue to download the 10G JDV but i can not find this tool also.
Does anyone use this feature and can give me some suggestions?
Thanks in advance.

goto the project properties.. Run/ Debugs Profile -> Default - Edit -> Launch Settngs [XSLT]
here provide input and output xml file..
if you want a visual transformation then you have to use.. SOA Suite.. BPEL
http://download.oracle.com/docs/cd/E12483_01/integrate.1013/b28981/xslt_mpr.htm

XSLT Mapper - Transform - Error when using remote WSDL/XSD

Whenever I attempt to use JDeveloper built in XSLT Mapper on a remote WSDL service the mapper either gives me a blank mapper screen or throws a error.
But when I pull the WSDLS and the XSDs into JDeveloper and use those for my Partner links the mapper does not have any issues.
The WSDLS and XSDs are being generated by Weblogic 10.3 and the SOA version I'm using is 11g. Everything is the newest download of 11g as of about 3 days ago.
Is there a known issue with the XSLT mapper or am I doing something wrong?
If you need any other information just ask thank you.

The XSLT service is configurable.
http://help.adobe.com/en_US/LiveCycle/9.5/WorkbenchHelp/WS92d06802c76abadb-1cc35bda128261a 20dd-6750.html
1) Stop LiveCycle.
2) Add the .jars of your XSLT processor of choice to the LiveCycle server lib folder.
3) Restart LiveCycle.
4) Go to Workbench and stop the XSLT service. Right-click on XSLTService:1.0 and Edit Service Configuration.
5) Enter the factory name for the given XSLT processor. I think for Xalan 2.7.1 it is org.apache.xalan.processor.TransformerFactoryImpl (but I could be wrong).
6) Restart the service.
Steve

XSLT Mapper doesn't support xsi:type

I'm starting to think that XSLT Mapper supports only the basic features of XML Schema ...
It (XSLT Mapper in JDeveloper) does not seem to support mapping to generate this kind of element (cannot do it in Design view, when added to the Source view, cannot go back to Design view):
<HighLevel:ParentEntity xsi:type="HighLevel:AChildEntity" xmlns:HighLevel="someNamespace">
<A>ABC</A>
<B>1</B>
<FromAChildEntity>ABCDE</FromAChildEntity>
</HighLevel:ParentEntity>
If we leave this in Source view and run the xsl, the resulting XML has a validation error, the last element (FromAChildEntity is not known). The XML is valid in XML Spy.
This problem combines with not being able to map two source elements to one target element, makes XSLT Mapper not able to deal with XML Schema inheritance at all.... ?

I just want to reformat the XML from the original message (didn't realize I had to escape some of the characters). This is the XML that cannot be validated by JDeveloper):
<HighLevel:ParentEntity xsi:type="HighLevel:AChildEntity" xmlns:HighLevel="someNamespace">
<A>ABC</A>
<B>1</B>
<FromAChildEntity>ABCDE</FromAChildEntity>
</HighLevel:ParentEntity>

Where is XSLT mapper?

I was advised by PeopleSoft Tech Support (who now work for Oracle!) that JDeveloper contained a utility for creating XSLT. There directions were to right-click the project, expand General, select XML, then select XSLT mapper in the Items list. Problem: XSLT mapper is NOT in that list, and I did not leave anything out when installing (Studio 10.1.3.0.3.3412)
Essentially I have an XML interface file that I generate out of PeopleSoft Financials - and I have an XML file that my non-PS client wants to receive. There is a gap between - ok, a chasm - and apparently this XSLT mapper enables you to drag a field from one file into the other & it will generate the XSLT code for you.
Can anyone shed some light on where this tool is? Thanks!

Paul, this is not in the EA1 realese of JDeveloper 10.1.3.
Something like this is suppose to be part of the BPEL extension to JDeveloper 10.1.3 production.
There are other "more manual" XSLT capabilities in JDeveloper right now.
See here:
http://www.oracle.com/technology/products/jdev/101/viewlets/101/xsltdebug_viewlet_swf.html

What is the "Imported Namespaces" window in Visual Studio Project Properties (VB)

What is the "Imporeted namespaces" window (see below) in Project properties (VB)

Hi trogan,
This is the official document Description from
How to: Add or Remove Imported Namespaces (Visual Basic):
Imported namespaces are managed on the References page of the Project Designer. The imports you specify in this dialog box are passed directly to the compiler (/imports) and apply to all files in your project.
But I think we could understand it better with this document:
References and Namespaces in VB.NET
Note: This response contains a reference to a third party World Wide Web site. Microsoft is providing this information as a convenience to you.
Microsoft does not control these sites and has not tested any software or information found on these sites;
Therefore, Microsoft cannot make any representations regarding the quality, safety, or suitability of any software or information found there.
There are inherent dangers in the use of any software found on the Internet, and Microsoft cautions you to make sure that you completely understand the risk before retrieving any software from the Internet.
Best Regards,
Jack
We are trying to better understand customer views on social support experience, so your participation in this interview project would be greatly appreciated if you have time. Thanks for helping make community forums a great place.
Click
HERE to participate the survey.

Bug in JDeveloper Remove Unused Imports feature

Hi,
I just detected the following funny behavior in the Remove Unused Imports feature in JDeveloper:
Let's take the following dummy code:
package mypackage;
import oracle.jbo.domain.Date;
public class MyClass {
public MyClass() {
oracle.jbo.domain.Date oracleDate;
Date.getCurrentDate();
If I'm applying Remove Unused Imports on this code, import oracle.jbo.domain.Date will be eliminated.
Regards,
Dan

Hi Dan,
This is the expected behavior. Since you have explicitly referenced the Date class by its fully qualified name in the MyClass constructor, the import is not required, and hence is unused.
Thanks,
Brian
JDev Team

Can I use SuppressWarnings("unused") for unused imports?

Is it possible to use an annotation to suppress the warnings for a block of unused import statements?
I've tried adding
@SuppressWarnings("unused")
import java.util.*;
and Eclipse is reporting Syntax Error on Token(s), misplaced construct(s)
Are annotations intended for class and method definitions only?

The project I'm working on has dozens of unused imports in just about every file. (I didn't write 99% of it). I was hoping that perhaps there was an easy way suppress these warnings permanently. To be specific, we use an svn repository that includes only the source and ant build files. While I can import the project to an IDE (Eclipse to be specific), and from there turn off warnings for unused imports, my boss doesn't want any IDE specific projects added to the repository, so every time someone checks out the code, they'll have to disable the warnings again.
I work at a company that has co-op students as employees, and these students are usually are only here for three month periods at a time. I just thought it would be nice to spare myself and other non-student coworkers from repeatedly setting up the projects this way.
From what I can tell, I'm the only one who actually cares about compiler warnings. The majority are unused imports, but some of them have led to legitimate bugs. when you have 2658 warnings in a project, it pretty much renders the functionality of the compiler warning useless.
Thanks for the quick reply, btw.

0,801: Invalid reference document import namespace

I have a Sensor Edge Server in which I've configured a Edge Simulator Driver. I'm dispatching my events to a BPEL Process thro' a WebService call.
My eflow.xml looks like this.
===============================================================================

===============================================================================
<eflow>
     <components>
          <component name="callBpel" class="oracle.edge.tools.eflow.impl.BpelState" />
          <component name="matchEvent" class="oracle.edge.tools.eflow.impl.MatchEventState" />
          <component name="sendEvent" class="oracle.edge.tools.eflow.impl.SendEventState" />
          <component name="callWs" class="oracle.edge.tools.eflow.impl.WsState" />
     </components>
     <entry>
          <onEvent state='A.check'/>
     </entry>
     <states>
          <matchEvent name="A.check" control="matchEvent" type="200" x="100" y="200" >
               <case result="ok" next="good.event"/>
          </matchEvent>
          <callWs name="good.event" wsdl="http://localhost:7777/orabpel/default/BPELProcess/1.0/BPELProcess?wsdl" method="initiate" namespace="http://xmlns.oracle.com/BPELProcess" docRoot="MyRoot">
               <param name="id" type="integer">$event.id$</param>
               <param name="subType" type="integer">$event.subType$</param>
          </callWs>
     </states>
</eflow>
===============================================================================
My BPEL process refers an xsd file 'BPELProcess.xsd'.
===============================================================================

===============================================================================
<types>
     <xsd:schema xmlns:xsd="http://www.w3.org/2001/XMLSchema" xmlns:plnk="http://schemas.xmlsoap.org/ws/2003/05/partner-link/" xmlns:client="http://xmlns.oracle.com/BPELProcess">
     <xsd:import namespace="http://xmlns.oracle.com/BPELProcess" schemaLocation="BPELProcess.xsd"/>
</xsd:schema>
</types>
===============================================================================
I get the following error in Sensor Edge
Tue Jun 26 17:20:07 IST 2007(2):WsState: Failed init:>>
oracle.j2ee.ws.client.WebServiceProxyException: WSDL parsing failed
     0,801: Invalid reference document import namespace: http://xmlns.oracle.com/BPELProcess.
     at oracle.j2ee.ws.client.impl.DefaultWebServiceProxy.newInstanceFromService(DefaultWebServiceProxy.java:106)
I assume that I'm getting this error because Event Flow Dispatcher does not understand the schema as it's defined in an xsd file and Sensor Edge cannot find the xsd.
Can anybody help me with this. Where can I put my xsd file so that Sensor Edge can access it.
One solution is to define the schema inline in the BPELProcess.wsdl, but I do not want to do that for some particular reasons.
Please help!

Nimish, I don't have an answer to your question, but have a question for you. You talk about having the schema inline. Is there a way to have the wsdl document generated so that the schema is produced inline, instead of using a reference as in your case? If so, how do you do it?
Thanks,
Bob N

XSLT Mapper: a lot of unused import namespaces

Similar Messages

Maybe you are looking for