xsl:attribute name="xdofo:rowspancell-repeat-nextpage" xdofo:ctx="block" t

<xsl:attribute name="xdofo:rowspancell-repeat-nextpage" xdofo:ctx="block">true</xsl:attribute>
Hello, can you provide me some example on how to use this code? i tried putting this code in a field in a table however it doesn't do any changes in my report, the header still don't repeat.
i'm aware of the word functionality to repeat a header, but due to the structure of my table, that method will changes the output of my report. the reason is i have a looping condition in that header, so if i tried to repeat it, the looping also repeats.
to summarize my table outline:
<HEADER1>---repeating already
<HEADER2 with looping condition>---> the one that i want to repeat
both headers belongs to a one table
i tried separating the header 2 to another table but it ruins my report output
any methods on how this can be done?
thanks in advance! :)

Hi All
Thanks For Your Efforts and replays
could anyone pls raise SR for it ?Because I do not have Privilege to do so

Similar Messages

XSL attribute question

*<xsl:attribute name="xdofo:rowspancell-repeat-nextpage" xdofo:ctx="block">true</xsl:attribute>*
Hello, can you provide me some example on how to use this code? i tried putting this code in a field in a table however it doesn't do any changes in my report, the header still don't repeat.
i'm aware of the word functionality to repeat a header, but due to the structure of my table, that method will changes the output of my report. the reason is i have a looping condition in that header, so if i tried to repeat it, the looping also repeats.
to summarize my table outline:
<HEADER1>---repeating already
<HEADER2 with looping condition>---> the one that i want to repeat
both headers belongs to a one table
i tried separating the header 2 to another table but it destroys my report output
thanks in advance! :)

Hi
You may get help if you post your question on its forum.
XML DB
-Priyanka

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

Xalan: extension element, evaluating xsl:attribute in an extension

Hi,
Can I evaluate in an extension method of an extension class an <xsl:attribute ... ?
for example in:
 <test:layout figure="rectangle" >
 <xsl:attribute name="color"><xsl:value-of select="$var1" /></xsl:attribute>
 </test:layout>
having Test as the extension class, and "layout" the corresponding method, I need to evaluate attribute "color", I have test it and when Test.layout is called it does'nt has color attribute, is there any way to evaluate the <xsl:attribute ... expression to access the value of color ?
thanks for any help.

Hi, I found the answer, and here it is for any body with same dude:
String attrExpr = ((ElemExtensionCall)elem).getAttribute ( "color", context.getContextNode(), context.getTransformer() );
org.apache.xpath.XPathContext xctxt = context.getTransformer().getXPathContext();
XPath myxpath = new XPath(attrExpr, elem, xctxt.getNamespaceContext(), XPath.SELECT);
XObject xobj = myxpath.execute(xctxt, context.getContextNode(), elem);
return xobj.str(); // this is the value of the attribute.
in xslt: <test:entension1 color="@Attr" /> or any other xPath
I found it at Redirect.java
thanks to you all.

Do you support xsl:attribute-set?

I could not get xsl:attribute-set and xsl:use-attribute-sets to work. Do you support them?
regards
tomas y
null

The following simple test works for me using the 2.0.2.9, 2.0.2.10, and 2.1.0.0 Beta versions of Oracle XSLT processor:<xsl:stylesheet xmlns:xsl="http://www.w3.org/1999/XSL/Transform" version="1.0">
<xsl:template match="/">
<test xsl:use-attribute-sets="title-style"/>
</xsl:template>
<xsl:attribute-set name="title-style">
<xsl:attribute name="font-size">12pt</xsl:attribute>
<xsl:attribute name="font-weight">bold</xsl:attribute>
</xsl:attribute-set>
</xsl:stylesheet>Which produces the output:
<test font-size="12pt" font-weight="bold"/>
as expected when applied to any XML source document.
What particular use is not working for you?

Xsl:attribute error in oraxsl command line

Hi Forum,
I'm getting error XML-22047 when trying to use xsl:attribute.
Here's the test XML I'm using:
<?xml version="1.0" encoding="UTF-8"?>
<root>
 <level1>Test-Content</level1>
</root>
now, this is the stylesheet I'm using:
<?xml version="1.0" encoding="UTF-8"?>
<xsl:stylesheet xmlns:xsl="http://www.w3.org/1999/XSL/Transform" xmlns:mdm="schema.condes.org/mds/meta" version="2.0" xml:space="preserve">
 <xsl:output method="xml" version="1.0" encoding="UTF-8" indent="yes"/>
 <xsl:template match="/">
 <xsl:apply-templates/>
 </xsl:template>
 <xsl:template match="root">
 <Foo>
 <xsl:attribute name="test">testing attribute</xsl:attribute>
 <xsl:apply-templates/>
 </Foo>
 </xsl:template>
</xsl:stylesheet>
If I run this, it throws error XML-22047, invalid instantiation of 'attribute' in 'element' context (translated from the German error message...)
Has anybody seen this and could advice me some help?
Thanks, Jürgen

Use xsl:element instead of explicit element.
<xsl:template match="root">
<xsl:element name="Foo">
<xsl:attribute name="test">testing attribute</xsl:attribute>
<xsl:apply-templates/>
</xsl:element>
</xsl:template>

List of attribute names in XSL

Does anyone have a list of attribute names and what not for XSL? I'm trying to code some things in BI Publisher......like underlining and double underlines, etc but am having trouble finding this information. If someone has a list of all of these names that would be extremely helpful. Thanks.

Hey Vestrini,
I was wondering if their was any place that listed a good chunk of attribute names so each time I needed something I didn't have to google a specific attribute?
Also here is what I was using for underline that isn't working. If you could help me figure out how to underline or get a double underline for the totals I would appreciate it.
<?if:LINE_TYPE='T'?><xsl:attribute xdofo:ctx="block" name="text-decoration">underlined</xsl:attribute><?end if?>

Xsl attribute font-size doesnt work

Hi,
I wanted to set the font-size dynamically.
I tried as below:
<xsl:attribute xdofo:ctx="incontext" name="font-size">30pt</xsl:attribute>
<?attribute@incontext:font-size;'30pt'?>
nothing worked.
But If I give the same for font-weight it works.
Whereas If I use <fo:block font-size="30pt">TEXT</fo:block> it works as expected.
May I know why xsl attributes doesnt work in this case?
Thanks in Advance.

Hi,
If i understand, you want different font-size for different text blocks which contain more than one row?
E.g.
Some text in
first block
Some text in
second block
Some text in
third block
Something like that?

Price list -- pricing attribute names

hi,
I need to xtract data from the qp_pricing_attributes table, for price break lines and pricing attributes info.
The pricing_attribute is stored as 'PRICING_ATTRIBUTE1', 'PRICING_ATTRIBUTE2' etc.
I need to know the actual attribute for which the line is defined i.e. 'Item Quantity',
'Freight Cost' etc...
Where'll I get this info??
thx in adv..
regds,
poongothai

Hey Vestrini,
I was wondering if their was any place that listed a good chunk of attribute names so each time I needed something I didn't have to google a specific attribute?
Also here is what I was using for underline that isn't working. If you could help me figure out how to underline or get a double underline for the totals I would appreciate it.
<?if:LINE_TYPE='T'?><xsl:attribute xdofo:ctx="block" name="text-decoration">underlined</xsl:attribute><?end if?>

Use XML Node Value as Node name and as attribute name

im quite new to XML and XLST. I got an Open Office XML file that I transformed with XLST.
<?xml version="1.0" encoding="UTF-8"?>
<ooo_calc_export scriptVersion="2.2.0" scriptUpdate="2010-12-19" scriptURL="http://www.digitalimprint.com/misc/oooexport/" scriptAuthor="vjl">
 <ooo_sheet num="1" name="Blatt1">
 <ooo_row><Artikelnummer>C12-34567</Artikelnummer><ArttikelnummerAlt/><Details>AAA AAA AAA AAA</Details><Abmessungen/><Bildpfad>file:///cmyk/C12-34567.PSD</Bildpfad><EK>1234,-</EK><VK>3456,-</VK>
 </ooo_row>
 <ooo_row><Artikelnummer>C23-45678</Artikelnummer><ArttikelnummerAlt/><Details>BaB BaB BBB BBB</Details><Abmessungen/><Bildpfad>file:///cmyk/cmyk/C23-45678.PSD</Bildpfad><EK>2345,-</EK><VK>4567,-</VK>
 </ooo_row>
 <ooo_row><Artikelnummer>C34-56789</Artikelnummer><ArttikelnummerAlt/><Details>CaC CaC CaC CaC uli</Details><Abmessungen/><Bildpfad>file:///cmyk/cmyk/C34-56789.PSD</Bildpfad><EK>3456,-</EK><VK>5678,-</VK>
 </ooo_row>
 </ooo_sheet>
</ooo_calc_export>
I transformed the XML with the following XLST:
<?xml version="1.0" encoding="UTF-8"?>
<xsl:stylesheet xmlns:xsl="http://www.w3.org/1999/XSL/Transform" version="2.0">
<xsl:output method = "xml" version="1.0" encoding="UTF-8" indent="yes"/>
<xsl:strip-space elements="*"/>
<xsl:template match="ooo_sheet">
<xsl:element name="Import">
<xsl:for-each select="ooo_row">
<xsl:element name="Artikel">
<xsl:element name="Text">
 <xsl:copy-of select="Artikelnummer"/>
 <xsl:copy-of select="Details"/>
 <xsl:copy-of select="Abmessungen"/>
 <xsl:copy-of select="EK"/>
</xsl:element>
</xsl:element>
</xsl:for-each>
</xsl:element>
</xsl:template>
The result is:
<?xml version="1.0" encoding="UTF-8"?>
<Import>
 <Artikel>
 <Text>
 <Artikelnummer>C12-34567</Artikelnummer>
 <Details>AAA AAA AAA AAA</Details>
 <Abmessungen/>
 <EK>1234,-</EK>
 </Text>
 </Artikel>
 <Artikel>
 <Text>
 <Artikelnummer>C23-45678</Artikelnummer>
 <Details>BaB BaB BBB BBB</Details>
 <Abmessungen/>
 <EK>2345,-</EK>
 </Text>
 </Artikel>
 <Artikel>
 <Text>
 <Artikelnummer>C34-56789</Artikelnummer>
 <Details>CaC CaC CaC CaC uli</Details>
 <Abmessungen/>
 <EK>3456,-</EK>
 </Text>
 </Artikel>
</Import>
I need another child within the node "Artikel" named "Bild". It should have an "href" attribute. The value of the attribute should be the value in the node "Bildpfad".
The result of this transformation should be
<Artikel>
<Text>
 <Artikelnummer>C34-56789</Artikelnummer>
 <Details>CaC CaC CaC CaC uli</Details>
 <Abmessungen/>
 <EK>3456,-</EK>
</Text>
<Bild href="file:///cmyk/C12-34567.PSD"></Bild>
</Artikel>
I want to import this XML into Indesign. It seems that the images path needs to be in a href attribute so Indesign accepts the node as an image object.
Another problem is that Indesign won't import the original xml with selection of the listed xsl to tranform the xml. So I used another xml editor instead to perform the transformation.
Thank you all for your help!

Hi Dorian_fs,
I think we're still missing details here on what exactly it
is you're trying to do? Are you loading this XML via a data set? In
which case, Don's samples would apply? Or are you trying to load
XML independent of data sets and regions, in which case, you are
looking for something that simplifies the access of data from the
resulting XML document? If the latter than perhaps you want to use
XMLDocToObject:
http://labs.adobe.com/technologies/spry/samples/utils/XMLDocToObject.html
--== Kin ==--

ERROR[WSDL Parser] Attribute 'name' not found at: wsdl:documentation

Hello,
I'm currently having a problem generating the Java source code from a WSDL, because the WSDL2Service ant class bundled with the WLS install (in the /server/lib/webservices.jar library) does not comply with the WSDL XSD.
Check http://schemas.xmlsoap.org/wsdl/
Especially if you add a <wsdl:documentation> in your <wsdl:portType> you end up with a WSDLParser error, while the file perfectly validates through Eclipse:
 <wsdl:portType name="ImportPortType">
 <wsdl:documentation>
 Definitions of available operations through the webservice
 </wsdl:documentation>
 <wsdl:operation name="importData">
 <wsdl:input message="tns:ImportInput" />
 <wsdl:output message="tns:ImportOutput" />
 </wsdl:operation>
 </wsdl:portType> The error is:
[wsdl2Service] Generating web service from wsdl C:\Java\Workspaces\MyWorkspace/WebServices/wsdl/Import.wsdl
[wsdl2Service] weblogic.webservice.wsdl.WSDLParseException: ERROR[WSDL Parser] Attribute 'name' not found at:<wsdl:documentation>Definitions of available operations through the webservice
[wsdl2Service] </wsdl:documentation>
[wsdl2Service] at weblogic.webservice.wsdl.WSDLParser.getMustAttribute(WSDLParser.java:263)
[wsdl2Service] at weblogic.webservice.wsdl.WsdlPortType.parsePortType(WsdlPortType.java:29)
[wsdl2Service] at weblogic.webservice.wsdl.WsdlBinding.parseBinding(WsdlBinding.java:45)
[wsdl2Service] at weblogic.webservice.wsdl.WsdlPort.parsePort(WsdlPort.java:46)
[wsdl2Service] at weblogic.webservice.wsdl.WsdlService.parseService(WsdlService.java:37)
[wsdl2Service] at weblogic.webservice.wsdl.WsdlDefinitions.parseDefinition(WsdlDefinitions.java:38)
[wsdl2Service] at weblogic.webservice.wsdl.WSDLParser.visit(WSDLParser.java:71)
[wsdl2Service] at weblogic.webservice.WebServiceFactory.createFromWSDL(WebServiceFactory.java:111)
[wsdl2Service] at weblogic.webservice.tools.build.internal.WSDL2JavaServiceImpl.runClassgen(WSDL2JavaServiceImpl.java:210)
[wsdl2Service] at weblogic.webservice.tools.build.internal.WSDL2JavaServiceImpl.run(WSDL2JavaServiceImpl.java:147)
[wsdl2Service] at weblogic.ant.taskdefs.webservices.wsdl2service.WSDL2Service.doWSDL2JavaService(WSDL2Service.java:211)
[wsdl2Service] at weblogic.ant.taskdefs.webservices.wsdl2service.WSDL2Service.execute(WSDL2Service.java:131)
[wsdl2Service] at org.apache.tools.ant.UnknownElement.execute(UnknownElement.java:288)
[wsdl2Service] at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
[wsdl2Service] at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:39)
[wsdl2Service] at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25)
[wsdl2Service] at java.lang.reflect.Method.invoke(Method.java:585)
[wsdl2Service] at org.apache.tools.ant.dispatch.DispatchUtils.execute(DispatchUtils.java:105)
[wsdl2Service] at org.apache.tools.ant.Task.perform(Task.java:348)
[wsdl2Service] at org.apache.tools.ant.Target.execute(Target.java:357)
[wsdl2Service] at org.apache.tools.ant.Target.performTasks(Target.java:385)
[wsdl2Service] at org.apache.tools.ant.Project.executeSortedTargets(Project.java:1329)
[wsdl2Service] at org.apache.tools.ant.helper.SingleCheckExecutor.executeTargets(SingleCheckExecutor.java:38)
[wsdl2Service] at org.eclipse.ant.internal.ui.antsupport.EclipseSingleCheckExecutor.executeTargets(EclipseSingleCheckExecutor.java:30)
[wsdl2Service] at org.apache.tools.ant.Project.executeTargets(Project.java:1181)
[wsdl2Service] at org.apache.tools.ant.taskdefs.Ant.execute(Ant.java:416)
[wsdl2Service] at org.apache.tools.ant.taskdefs.CallTarget.execute(CallTarget.java:105)
[wsdl2Service] at org.apache.tools.ant.UnknownElement.execute(UnknownElement.java:288)
[wsdl2Service] at sun.reflect.GeneratedMethodAccessor1.invoke(Unknown Source)
[wsdl2Service] at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25)
[wsdl2Service] at java.lang.reflect.Method.invoke(Method.java:585)
[wsdl2Service] at org.apache.tools.ant.dispatch.DispatchUtils.execute(DispatchUtils.java:105)
[wsdl2Service] at org.apache.tools.ant.Task.perform(Task.java:348)
[wsdl2Service] at org.apache.tools.ant.Target.execute(Target.java:357)
[wsdl2Service] at org.apache.tools.ant.Target.performTasks(Target.java:385)
[wsdl2Service] at org.apache.tools.ant.Project.executeSortedTargets(Project.java:1329)
[wsdl2Service] at org.apache.tools.ant.helper.SingleCheckExecutor.executeTargets(SingleCheckExecutor.java:38)
[wsdl2Service] at org.eclipse.ant.internal.ui.antsupport.EclipseSingleCheckExecutor.executeTargets(EclipseSingleCheckExecutor.java:30)
[wsdl2Service] at org.apache.tools.ant.Project.executeTargets(Project.java:1181)
[wsdl2Service] at org.apache.tools.ant.taskdefs.Ant.execute(Ant.java:416)
[wsdl2Service] at org.apache.tools.ant.taskdefs.CallTarget.execute(CallTarget.java:105)
[wsdl2Service] at org.apache.tools.ant.UnknownElement.execute(UnknownElement.java:288)
[wsdl2Service] at sun.reflect.GeneratedMethodAccessor1.invoke(Unknown Source)
[wsdl2Service] at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25)
[wsdl2Service] at java.lang.reflect.Method.invoke(Method.java:585)
[wsdl2Service] at org.apache.tools.ant.dispatch.DispatchUtils.execute(DispatchUtils.java:105)
[wsdl2Service] at org.apache.tools.ant.Task.perform(Task.java:348)
[wsdl2Service] at org.apache.tools.ant.Target.execute(Target.java:357)
[wsdl2Service] at org.apache.tools.ant.Target.performTasks(Target.java:385)
[wsdl2Service] at org.apache.tools.ant.Project.executeSortedTargets(Project.java:1329)
[wsdl2Service] at org.apache.tools.ant.Project.executeTarget(Project.java:1298)
[wsdl2Service] at org.apache.tools.ant.helper.DefaultExecutor.executeTargets(DefaultExecutor.java:41)
[wsdl2Service] at org.eclipse.ant.internal.ui.antsupport.EclipseDefaultExecutor.executeTargets(EclipseDefaultExecutor.java:32)
[wsdl2Service] at org.apache.tools.ant.Project.executeTargets(Project.java:1181)
[wsdl2Service] at org.eclipse.ant.internal.ui.antsupport.InternalAntRunner.run(InternalAntRunner.java:423)
[wsdl2Service] at org.eclipse.ant.internal.ui.antsupport.InternalAntRunner.main(InternalAntRunner.java:137)
BUILD FAILED
C:\Java\Workspaces\MyWorkspace\EAR\ant\build.xml:22: The following error occurred while executing this line:
C:\Java\Workspaces\MyWorkspace\EAR\ant\build.xml:26: The following error occurred while executing this line:
C:\Java\Workspaces\MyWorkspace\EAR\ant\build_config.xml:65: weblogic.webservice.tools.build.WSBuildException: weblogic.webservice.wsdl.WSDLParseException: ERROR[WSDL Parser] Attribute 'name' not found at:<wsdl:documentation>Definitions of available operations through the webservice
 </wsdl:documentation> Digging through the WSDLPortType class (package weblogic.webservice.wsdl ) decompiled code, I clearly saw this kind of parsing does not respect the WSDL XSD:
public class WsdlPortType {
 public WsdlPortType() {
 operations = new ArrayList();
 void parsePortType(WSDLParser wsdlparser, XMLNode xmlnode, Port port) throws WSDLParseException {
 Iterator iterator = xmlnode.getChildren();
 do {
 if(!iterator.hasNext())
 break;
 XMLNode xmlnode1 = (XMLNode)iterator.next(); // THE NEXT XML NODE IS NOT COMPULSORILY THE <wsdl:operation> ONE!!!
 String s = wsdlparser.getMustAttribute("name", xmlnode1);
 if(wsdlparser.canHandleMethod(xmlnode1)) {
 weblogic.webservice.Operation operation = port.addOperation(s);
 WsdlOperation wsdloperation = new WsdlOperation();
 wsdloperation.parseOperation(wsdlparser, operation, xmlnode1);
 operations.add(wsdloperation);
 } while(true);
 private ArrayList operations;
} X-(
Edited by maxxyme at 03/13/2008 10:34 AM

I created a new project and tried to repeat the steps to import. Still getting the same error.
This is my Message type definition if that helps
<message name="Composite_Weather_ServiceRequestMessage">
 <part name="payload" type="tns1:NDFDgenRequest"/>
 </message>
 <message name="Composite_Weather_ServiceResponseMessage">
 <part name="payload" type="tns1:NDFDgenResponse"/>
 </message>

Entity Reference embedded within colspec attribute name-table col. heading

My team is working on a project that involves converting MS Word documents to XML. The XML is applied to a stylesheet (*.xsl) which generates a *.pdf document. Is it valid to include an xml entity reference within a colspec attribute name? For example, the xml document would contain the following code for a table:
<t id="t1109681052">TABLE 1.0 My Favorite Restaurants</t>
<tbl id="tbl921133606" val="1.0">
<TblHdg num="1">Table 1.0 My Favorite Restaurants </TblHdg>
<colspec id="colspec1148420628" name=" Restaurant Name" width="0.61875"/>
<colspec id="colspec201089067" name="Type of Authentic Cuisine" width="1.61875"/>
<colspec id="colspec201089069" name="Location" width="1.61875"/>
</tbl>
Is the following code valid in XML to produce the results in the sample table below when the XML is applied to a stylesheet (xsl)?
<colspec id="colspec201089067" name="Type of "Authentic" Cuisine" width="1.61875"/>
The desired table and column titles would be as follows:
Restaurant Name ---- Type of Authentic Cuisine ---- Location
Le Chantecler --------------->French The Negresco Hotel
Promenade des Anglais Nice France
La Coupola -------------------->French The Mirabeau Hotel
1 Princess Grace Ave
Monte Carlo Monaco
What is needed in the XML code to produce the table column heading with quotes embedded around the word "Authentic"?
Please advise. Thanks so much and have a prosperous and memorable holiday.

SOLUTION RESOLVED FOR THIS MESSAGE.

How to change the attribute name for a relation

When the Data Modeler engineers a logical model into a relational model it create table columns for the relations. The names of the generated columns are listed in the attributes list in the properties dialog of the relation. The actual name of the attribute gets calculated by the attribute name of the entity which is part of the relation. This is okay, if there is only one relation between two entities. But when there are two relations between two entities the second attribute gets a stupid number suffix. This makes it impossible to give the attribute a useful semantic meaning.
When I engineer the model into a relational model I can change the column name in the relational model. Changing the column name in the relational model is not perfect but it would be okay for me, if it would not be overwritten during the next engineering run.
So I have two questions:
How can I change the attribute name in the attributes section of the properties dialog of a relation? See here for screen shot:
http://public.ceving.de/2012050300/relationattribute.png
And if it is not possible:
How can I preserve any changes on column names in the relational model during a re-engineering run?
Edited by: 931739 on 03.05.2012 08:07

Hi,
I've logged an Enhancement request on this.
I don't believe it's possible to change it from the Entity or Relationship dialog, as it's not updatable in these dialogs.
What you can do is change it in the Relational Model, and then reverse engineer the change back to the Logical Model.
David

Get the attributes NAME and VALUE from an XML

I really love this forum :)
I load an XML an populate a Tree, from which I start to drag
items.
the xml looks like this:
<myTag attrName="attrValue"
otherAttrName="otherAttrValue"/>
var ds:DragSource = event.dragSource;
var var1:String =(event.dragInitiator as
Tree).value.@attrName;
-> the var1 variable has now: "attrValue"
my question is.. how can I get all the attributes' names? in
this example: attrName and otherAttrName (suppose I don't know the
structure of that xml node)
what about attributes values?
thank you!

The snippet below takes an xml node(nodeCur), loops over the
attributes list and builds an array that contains the attribute
name and value for each attribute. It comes from a sample app that
allows you to edit an xml file.
Sorry that the forum will remove the formatting
var aDPAttributes:Array = new Array();
var xlAttributes:XMLList = nodeCur.@*;
var attribute:Attribute;
for ( var i:int = 0; i < xlAttributes.length(); i++) {
aDPAttributes.push({name:xlAttributes [ i ]
.name(),value:xlAttributes [ i ] });
dgAttributes.dataProvider = aDPAttributes; //set the property
sheet dataProvider
Tracy

Cannot create or replace : The specified extended attribute name was invalid.

New problem arrived today. Trying to copy a file from 10.6 server with an XP (SP3) client. I get this error:
Cannot create or replace (file name here): The specified extended attribute name was invalid.
The contents of the file can be copied, but not the folder. Other files can be copied. There are no funny characters. The name is not too long. I propogated the permissions on the share and that had no affect. The problem exists on three different XP systems. Can't find extended properties that could be causeing a problem. Any ideas?

Nikon just released a Firmware update today for the D750

xsl:attribute name="xdofo:rowspancell-repeat-nextpage" xdofo:ctx="block" t

Similar Messages

Maybe you are looking for