Blue brackets in TransformXSL = optional elements?

When I open a TransformXSL mapping windows with two strucuture (source and target)
then some of the element name icons have blue brackets [<.>]
Does that mean that these elements are optional?
Peter

Hi Peter,
Yes it is for optional elements.
Cheers-
Sreejit

Similar Messages

Green or blue hue when printing in Elements 11

I get a green or blue hue when printing in Elements 11. Printer color control is off. Need help to eliminate color hue when printing.

Oh yes it has Barbara. David is right. Have a look at Elements 5. I got that free and would still be using it if I hadn't had to upgraded to Windows 7. I've now had to buy Elements 11 because Elements 5 wouldn't load and Elements 11 does not have that fascility that David laments. I used that printing option almost exclusively for printing cards and I bitterly regret not having it now. I'm very disappointed with these printing options in Elements 11. The problem is that Photoshop eminates from the one country in 180 that seems manacled to its imperial measurements that the rest of the world has to keep wading through. I expect that to acquire my favourite printing fascility I shall have to get the full verson. I have seen it in screenshots, so I know that it is there. It's all very well for Barbara to say resize before entering the print window but this is just trial and error and takes forever. In the meantime I shall continue to spend ages working round this cumbersome resizing problem each time I print my cards.

How to develop ALV and select-option element in BSP? Help!

Hi Experts,
I have a requirement where I have a selection screen with 3 select-option elements and a search button. On clicking the search button an ALV table report has to be shown.
The ALV table is used for new row/rows entry, delete row/rows and update row/rows data. This is something like table control in normal ABAP.
Additionaly, I want the download to Excel, sorting, filtering, column swapping options in ALV.
How can I achieve this in BSP?
Is there any existing SElect-option and ALV component in BSP?
Any code sample will be really helpfull.
How much development time will it take?
Please help!
Thanks
Gopal

I think you will find that most of what you are looking for does NOT exist out of the box for BSP. There is no delivered selection-option or value help. I ended up creating my own over the years (You can find some versions online here in SDN in my weblogs - however a complete implementation of select-options was only delivered along with the Advanced BSP Programming book).
There is no ALV either. However with the htmlb:tableView, you can acomplish quite a bit. You may have to learn about table view iterators to get it all done. Downloading to Excel also isn't delivered. I developed a reusable BSP Extension element for this as well (can be found on SDN in my weblogs or with the Advanced BSP Programming book).
If you plan to recreate all these elements by yourself, your project will take some time. It took a while to build so many complex UI elements.
What release are you running on? In Netweaver04S you have Web Dynpro ABAP. WDA has delivered components for value help, select-options, and ALV.

Optional elements not supported in XML parser for java

I am using v2 parser version 2.0.2.8.0 for java. Looks like this parser does not support optional elements.
My DTD looks like
<!ELEMENT Graph (Background, ImageSize)?>
<!ELEMENT ImageSize EMPTY>
<!ATTLIST ImageSize
width CDATA #IMPLIED
height CDATA #IMPLIED >
<!ELEMENT Background EMPTY>
<!ATTLIST Background
fillColor CDATA #IMPLIED>
If I set the XML following XML
<?xml version="1.0" ?>
<Graph>
<ImageSize width="422" height="477"/>
</Graph>
I am getting XMLParseException :Invalid element 'ImageSize' in content of 'Graph', expected elements '[Background]'
The parser expects all the elements to be present in the XML although the elements are defined as optional in the DTD. It used to work fine until v2 parser version 2.0.2.7.0. Is this a bug?
null

The value of JAXP is that it allows one to
freely switch parsers without changing any code. I have an application that uses the JAXP interfaces to create my DOM parser. I am using the Xerces-J parser now. I wanted to try Oracle's parser to see how it compares. To my great surprise, I found the Oracle DOM parser doesn't support JAXP. Because of this I have to CHANGE my code to user the Oracle DOM parser. Thus defeating the purpose of coding my app to the JAXP interface.
I have to add that I am surprised to see that a developer of Oracle's XML parser has to even ask what the value of JAXP is. I would think that being a parser developer, you would know and understand the value of JAXP.
I would like to know why Oracle has chosen not to support JAXP? Or have you just not even thought about whether or not you should support it.
Thanks,
Keith Jensen
<BLOCKQUOTE><font size="1" face="Verdana, Arial">quote:</font><HR>Originally posted by Steven Muench ([email protected]):
What is the perceived value in implementing the JAXP standard? We already implement SAX, have plans for SAX2, and are working with other XSLT vendors on the TRAX api for XSLT processors.
If there is strong customer demand, we'll clearly consider it, but at the moment that has not been the case.<HR></BLOCKQUOTE>
null

Can't update XML with optional element

Hi,
I'm trying to update an XML document (global XML Schema based) with an optional element (insert an optional element into an existing xml document).
The update statement seems to work but the optional element is missing when I select the document!
How can I update (insert) an optional element in an XML document?
Thanx for your comments,
Markus
My scenario:
============
XML Schema:
<?xml version='1.0'?>
<xsd:schema xmlns:xsd="http://www.w3.org/2001/XMLSchema"
xmlns:xdb="http://xmlns.oracle.com/xdb">
<xsd:element name="TestUpdate" xdb:defaultTable="TESTUPDATE">
<xsd:complexType>
<xsd:sequence>
<xsd:element name="anElement" type="xsd:string" />
<xsd:element name="optElement" type="xsd:string" minOccurs="0" />
</xsd:sequence>
</xsd:complexType>
</xsd:element>
</xsd:schema>
SQL:
begin
dbms_xmlschema.registerSchema('xsd/TestUpdate.xsd',
getDocument('testupdate.xsd'),
FALSE);
end;
ALTER TABLE TestUpdate
add constraint VALID_TestUpdate
check (XMLIsValid(sys_nc_rowinfo$)=1);
INSERT INTO TestUpdate values (xmltype(getDocument('TestUpdate.xml')))
update TestUpdate x
SET x = UPDATEXML(value(x),
'/TestUpdate/optElement','<optElement> my optional Element</optElement>');
==> Message is: 1 row updated !!!!!!!!!!
SQL> select * from testupdate;
SYS_NC_ROWINFO$
<TestUpdate xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance" xsi:noNamespac
eSchemaLocation="xsd/TestUpdate.xsd">
<anElement>more text....</anElement>
</TestUpdate>
==> No UPADATE performed!!!

Thanks Pete,
XPath evaluation may return no data and may cause the trouble of giving an 'success' answer.
On the other side I have rewritten the statement:
SQL> update testupdate x set x.XMLData."optElement" = ' just some text';
SQL> select * from testupdate;
SYS_NC_ROWINFO$
<TestUpdate xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance" xsi:noNamespac
eSchemaLocation="xsd/TestUpdate.xsd">
<anElement>more text....</anElement>
</TestUpdate>
===> no UPDATE ???????
SQL> select x.xmldata."optElement" from testupdate x;
XMLDATA.optElement
just some text
===> WOW, row is updated!!!!!!!!
This result is more wired than before :-)
(at least for myself)
Can somebody explain the result?
bye,
Markus

Best way to handle optional elements in XSLT

Hi All,
I'v wondering if there are any better ways to handle optional fields in XSLT.
For example if my Person Type has 5 fields and 3 of them are optional:
<xs:complexType name="PersonType">
<xs:element name="PersonID" min="1"/>
<xs:element name="PIN" min="1"/>
<xs:element name="FirstName" min="0"/>
<xs:element name="MiddleName" min="0"/>
<xs:element name="LastName" min="0"/>
</xs:complexType>
In my xslt file, if I do somthing like:
<Person>
<FirstName>
<xsl:value-of select="PersonType/FirstName"/>
</FirstName>
</Person>
I might get an empty FirstName element in my output xml file. (like <FirstName/>) This has caused some very weired behavour with Oracle v2 parser because optional means the node may not be present in the xml not the node is there but empty.
The only way I can think of solving this is to put <xsl:if test> around every single optional element to test if it exist in the source file. If it does then generate the element in the destination file. But in this way, if the source file is very complicated, then you would have to wrap each element with a <xsl:test> which is very ugly to me.
Do anyone know if there is a more generic way that we can solve this issue?
Thanks,
Larry

Dharmendra,
The answer you gave is very very helpful. The only thing that I can think of here is that it might accidentally delete the fields that have been set empty deliberately.
Maybe, this is one of the grey areas in XML Schema that I do not understand very well yet. In xml, if you define an element to be a string type and mandatory (minOccurs="1"), for exampe the following xml
<Name></Name>
will be valid against the schema because the Name element is present in the xml payload. However, it has no value or has a valud of empty string. I know that this is only a problem with string type. If it is boolean, then it has to be either true of false, being empty won't satisfy the schema validator. But with String it is a bit trickier, because String can be empty. Maybe this issue should be stopped when designing your xml schema by specifying the mininum length (>0) in the schema. Any suggestions would be welcomed.
Cheers,
Larry

Creating optional elements using SQL / XML functions

Hi,
I am struggling with some SQL / XML functionality in order to create some optional elements in a XMLType.
I have one table with data to be generated into an XML document. The table looks like this (only the attributes related to the problem are shown):
msg_id (pk)
geslacht_hoofdverzekerde
geboortedatum_hoofdverzekerde
geslacht_medeverzekerde
geboortedatum_medeverzekerde
I have to create an XML document that looks like this:
<ber:rekenparameters>
<ber:verzekerde>
<ber:codeRelatierol>HVZ</ber:codeRelatierol>
<ber:geslacht>M</ber:geslacht>
<ber:datumGeboorte>01-01-1960</ber:datumGeboorte>
</ber:verzekerde>
<ber:verzekerde>
<ber:codeRelatierol>MVZ</ber:codeRelatierol>
<ber:geslacht>V</ber:geslacht>
<ber:datumGeboorte>01-01-1961</ber:datumGeboorte>
</ber:verzekerde>
</ber:rekenparameters>
Where <ber:codeRelatierol> is hard coded: i.c. of hoofverzekerde 'HVZ' in case of medeverzekerde 'MVZ'.
Geslacht en datumGeboorte are taken form the table.
The element <ber:verzekerde> is obligatiry for hoofdverzekerde but optional for medeverzekerde: only in case geslacht_medeverzekerde and geboortedatum_medeverzekerde are not null this 2nd <ber:verzekerde> element has to be added.
I created the next SQL (I skipped some stuff in order to focus on the problem):
CREATE OR REPLACE
VIEW dps_v_berekening_berichten
AS
SELECT msg_id as msg_id
, XMLElement( "ber:berekening"
, XMLAttributes( 'http://www.w3.org/2001/XMLSchema-instance' AS "xmlns:xsi"
, 'http://www.mycompany.nl/berekenen' AS "xmlns:ber"
, 'http://www.mycompany.nl/berekenen http://www.mycompany.nl/berekenen/berekening.xsd' AS "xsi:schemaLocation"
, XMLElement( "ber:nummerRekenRegel"
, XMLAttributes( 'http://www.mycompany.nl/berekenen' AS "xmlns:ber" )
, 1
, XMLElement( "ber:rekenparameters"
, XMLAttributes( 'http://www.mycompany.nl/berekenen' AS "xmlns:ber" )
, XMLElement( "ber:codeEvolutie" ) -- Empty
, XMLElement( "ber:verzekerde"
, XMLForest ( 'HVZ' AS "ber:codeRelatierol"
, xoa.geslacht_hoofdverzekerde AS "ber:geslacht"
, xoa.geboortedatum_hoofdverzekerde AS "ber:datumGeboorte"
, XMLElement( "ber:verzekerde"
, XMLForest ( 'MVZ' AS "ber:codeRelatierol"
, xoa.geslacht_medeverzekerde AS "ber:geslacht"
, xoa.geboortedatum_medeverzekerde AS "ber:datumGeboorte"
-- Some more elements.
) AS bericht
FROM DST_UP1_XML_OUTDATA xoa
The problem is that the XMLForest always creates an <ber:verzekerde> element for medeverzekerde. I tried to create an inline view with just the "vezekerde"attributes and conditionally joining this inline view with the dst_up1_xml_outdata table. That didn't solve my problem. Because in case of a medeverzekerde available it returned two XML documenst: one that included the hoofdverzekerde and one that included the medeverzekerde. And obviously that's not what I want.
I imagine I have to juggle with some of these SQL / XML functions although I cannot put the finger on the exact differences between some of these (XMLElement, XMLForest, XMLAgg, XMLSequence). The examples shown in de XML DB Developer's Guide don't seem to adress my problem.
Help !

Hi, are you talking about this part that you don't want to be there? I am not so clear about your requirements.
XMLElement( "ber:verzekerde"
, XMLForest ( 'MVZ' AS "ber:codeRelatierol"
, xoa.geslacht_medeverzekerde AS "ber:geslacht"
, xoa.geboortedatum_medeverzekerde AS "ber:datumGeboorte"
If you want to control certain subelements so they don't appear, do not use xmlforest. Use xmlelement instead so it is easier to control it using case when. Mark (of Oracle, he should be here soon since OOW is over) showed me this technique and it helps tremendously, because oftentimes XDB will return an empty tag even though your consumers don't like it!
try something like this,
(case when xoa.geboortedatum_medeverzekerde = 'MVZ' then
xmlelement("ber:verzekerde",
xmlelement("What you want", colname),
xmlelement("ber:codeRelatierol", 'MVZ'),
(case when colname is not null or = some other value then
xmlelement("Rest", colname))
end)
end),
You may have to twig some details there. But the key is to use the case when construct to get rid of unwanted elements or empty elements. So you should only have the elements if you have a value of 'MVZ'. Hope this helps.
Ben

Map optional elements to attributes

Hi,
I am mapping 5 optional elements to a element which has 2 attributes. I simplified my map to only check 1 optional element and then my map looks like below:
So I check if the element PruchseOrderNumber which is optional exists in the source. If that's true I use 3 value mappings to write the destination fields userfield, id and datatype.
But when I test the map I get a lot of Output validation errors. They are:
Output validation error: The required attribute 'id' is missing
Output validation error: The required attribute 'datatype' is missing
The output XML looks like below:
The first instance is created where there is no PurchaseOrderNumber and the second instance is when there is a PurchaseOrderNumber. But the first instance already creates a closed tag userfield. How do I get rid of this tag so my output validations are gone?

Hi Ronald,
One way to get rid of the empty nodes in your map by using a custom functoid and use XSLT script mentioned in this article.
Remove empty nodes in BizTalk by using XSLT
Rachit
Please mark as answer or vote as helpful if my reply does

Append or remove optional element

Hi!
I have a schema based XMLType table, which has a optional element.
How could I append(or remove) an optional element to(from) a xml instance in the XMLType table?.
I need a help !!!
Thanks.

I have the same problem!My version is 9.2.0.1.I also have searched the whole xml db forum but with no satisfied answer. Hope you can help!

Optional Elements

hi guys,
i have a set of optional elements in my xml, sometimes they will populated other times not. jaxb unmarshalls the document but when i go to check for one of the elements that is not there it a null pointer exception is thrown. has anyone got a suggestion for working around this.
kind regards,
michael

Or
if (something != null)
// use it
} else {
// don't use it
}But seriously, this is basic Java stuff that you should learn soon after HelloWorld. You may be getting ahead of yourself using JAXB.

ERROR Cannot create target (optional) element - SUPPRESS value

HI, XI/PI experts!
I am new in PI 7.1 (Ehp1 SP 7), previously work with PI 7.0.
I faced with problem of mapping optional target element, when queue has just SUPPRESS element. I expected to suppressing mapping of the target element, but mapping program raise exception:
Cannot create target element
/ns0:Messages/ns0:Message1/MT_DiadocMethods/ConnectInfo/TraceInfo/Folder.
Values missing in queue context.
Target XSD requires a value for this element, but the target-field mapping does not create one.
Check whether the XML instance is valid for the source XSD,
and whether the target-field mapping fulfils the requirement of the target XSD
XSD Folder declaration:
<xsd:element name="Folder" type="xsd:string" minOccurs="0">
            <xsd:annotation>
               <xsd:documentation>
               u043Au0430u0442u0430u043Bu043Eu0433 u0434u043Bu044F u0442u0440u0430u0441u0438u0440u043Eu0432u043Au0438 u0447u0435u0440u0435u0437 u0444u0430u0439u043Bu044B
               </xsd:documentation>
            </xsd:annotation>
         </xsd:element>
[http://imagepost.ru/?v=queue_for_optional_element_fol.PNG|http://imagepost.ru/?v=queue_for_optional_element_fol.PNG]
If put mapWithDeffault with value "hello" between ifWithoutElse and target element Folder, then exceptions not raised, but target element also not created
15:53:03 Start of test
Compilation of MM_Diadoc_DownloadNewEvents__DiadocMethods_q successful
Document start
Start tag [ns0:Messages]
Add raw attribute [ xmlns:ns0="http://sap.com/xi/XI/SplitAndMerge"]
Start tag [ns0:Message1]
Start tag [MT_DiadocMethods]
Start tag [ConnectInfo]
Start tag [trace_level]
Put value [4]
Close tag [trace_level]
Start tag [TraceInfo]
Start tag [TraceViaMail]
Close tag [TraceViaMail]
Close tag [TraceInfo]
Close tag [ConnectInfo]
Close tag [MT_DiadocMethods]
Close tag [ns0:Message1]
Close tag [ns0:Messages]
Document end
Execution of mapping on server took 1160 milliseconds Executed successfully
15:53:05 End of test
<Display Queue> show that queue after mapWithDeffault has <null> value:
[http://imagepost.ru/?v=mapwithdeffault.PNG|http://imagepost.ru/?v=mapwithdeffault.PNG]
Inserting mapWithDeffault is workaround for this situation, but I am interesting to understand principle of SUPPRESS in 7.1
Thanks in advance and sorry for my English !

Hi,
To understand the Suppress you can refer the below blog
/people/stefan.grube/blog/2006/01/09/the-use-of-suppress-in-the-xi-30-graphical-mapping-tool

JAXB, element order and optional elements

Hi,
I am trying to write a program that depends on JAXB and I am encountering a number of problems. The first is that the party from which we get our XML data from is capable of sending the elements in a given element in any order and JAXB is very stringent about order, is there any way to override this behaviour? The next, is if an element, that has children, is marked as optional in the DTD, JAXB will treat it as mandatory which also creates problems for us as some of these type of elements are optional.
Does anyone know when JAXB ea2 is due?

To your second topic, this is a known bug in the EA, see
http://developer.java.sun.com/developer/bugParade/bugs/4497267.html
To the first topic: If you define the DTD in a way, that the element order is not fixed, then JAXB should accept that. E.g. instead of<!ELEMENT foo (a,b,c)>you could write<!ELEMENT foo ((a|b|c)*)>Of course, this is even looser, as it does not prevent you from sending multiple instances of a, b and c, and the generated code does not contain a getA, getB and getC method, but just a getContent returning a List.

Can't set Optional Element to Nil in Xquery Transformation

I am new to Workshop and I am performing a transformation between two XML files that I will call source and target for example. I have multiple time/date elements that are optional in the target XML schema. I want to know how to set their values to null (nil?) if there is no data in the corresponding source XML schema element. Any ideas?
I get syntax errors with xquery set up like this:
if (data($iter_requestXML1/mySourceDate) != "" ) then
xs:date($iter_requestXML1/mySourceDate)
else
(nil)
I want to do something like above, but I don't know the right syntax.
However if I leave the "else" clause as:
else ()
Then I don't have a syntax error, but I get an exception whenever I try to reference the target XML element whenever their was no data for this element.
In the last example, I am thinking I get the reference error because the element was never initialized to NULL or NIL. But I don't know how to set it. Please Help!

1st : It runs perfectly fine at 1280x1024@75Hz in Windows XP/Vista, so there is no reason it shouldn't work in Linux. In Nvidia-panel there is even the 75Hz option in the drop-down list when resolution is 1280x1024.
2nd : It isn't easy on the eyes at 60Hz compared to 75Hz, even more when i play games (Quake 3 for example).
Last edited by Kaloos (2009-04-27 21:22:18)

Blu Ray EASY EXPORT option in new FCP 7

Would love to hear from anyone who has tried the new feature Easy Export in FCP 7 upgrade for Intel Macs, particularly the Blu Ray burning export from within FCP 7 to Blu Ray Disc. What is the quality (limits) and do we finally have actual Chapter Marker Options, and truely custom background / menu image options? I'm considering finally giving up on my PowerPC G4, and going with a new Intel based Mac, or wait a little longer if this upgrade is not worth it.
I'm currently burning Blu Rays with Toast 10 and a LaCie BD Drive with great results.

What is the quality (limits) and do we finally have actual Chapter Marker Options, and truely custom background / menu image options?
Some details on what is new, there is a link for the movie for sharing
http://www.apple.com/finalcutstudio/whats-new.html, also a link for a PDF about in depth (page 55 indicates you can use third party templates or your own. Someone mentioned it is XML based, but not sure if anyone has given it a whirl yet. I ordered my upgrades when it was announced, should have it soon, don't know when I will try though.
I'm considering finally giving up on my PowerPC G4, and going with a new Intel based Mac, or wait a little longer if this upgrade is not worth it.
I'm currently burning Blu Rays with Toast 10 and a LaCie BD Drive with great results.
Your answer may be in those two sentences. Not sure which version of Final Cut and the rest you are running, and disregarding the blu-ray issue for a moment, if you system is working for you, and you are getting good results, that is one thing in favor of not changing right now. If the total of all the changes in the Studio are appealing, then perhaps it would be worth it. Right now you are burning blu-ray with results you like.
Alot of it depends on budget and the rest. Plus the new Intel will smoke in terms of speed and workflow. OTH, if those things are not jamming you up, well, maybe holding would be the prudent move. (Though of course the incremental change in the machine configuration would be something to make your head spin....:) )

Has a stop marker any function when burning blu-ray discs with Premiere Elements 12?

Stop marker when burning blu-ray discs with Pre 12. Does it works?

Amiral
No.
This applies to Premiere Elements any version.
Stop markers placed on the Premiere Elements Timeline destined for burn to Blu-ray disc format on Blu-ray disc are not recognized at playback of that disc using the Blu-ray player.
If you need Blu-ray disc with stop markers, you can export your Premiere Elements Timeline content to an appropriate file type that will be compatible with a 3rd party software which will get the job done. I have heard that a software such as DVD Architect can do that, but I have not been there and done that.
Stop markers function at playback of DVD-VIDEO on DVD disc only. And, never place a stop marker at the end of the last item on that Timeline.
http://help.adobe.com/en_US/premiereelements/using/WS09e4b3c48f3a79fc19b622510385d4355c-7e 19.html
Please do not hesitate to ask if you need clarification on anything written.
Thank you.
ATR
Add On...I have found that the situation is the same for stop markers and AVCHD on DVD and Blu-ray disc format on Blu-ray disc.

Blue brackets in TransformXSL = optional elements?

Similar Messages

Maybe you are looking for