|
This code:
xquery version "1.0";
let $doc := element data {
element row {'abc'},
element row {'def'}
}
return
element results {
for $a in $doc/node()
return
$a/node()
}
returns (as expected)
<results>abcdef</results>
If I change the last line to $fn:replace($a/node(), 'x', 'y'), i.e.,
xquery version "1.0";
let $doc := element data {
element row {'abc'},
element row {'def'}
}
return
element results {
for $a in $doc/node()
return
fn:replace($a/node(), 'x', 'y')
}
The results contain a space between the 'c' and 'd':
<results>abc def</results>
Does anyone have a clue as to where this is coming from? Note that the replace is looking for a character that's not there, so the search string should not be changed.
Thanks.
|
|
|
|
|
i hav made an xml file..as well as an xsd file..i need to refer this xsd file in the xml file..
what should i include in the <xs:schema> tag of the xsd file..?? and what to include in the <root> tag of the xml file..
these r my xsd and xml files respectively..
<code><?xml version="1.0"?>
<xs:schema>
<xs:element name="details">
<xs:complexType>
<xs:sequence>
<xs:element name="name" type="xs:string">
<xs:element name="age" type="xs:string">
<xs:sequence>
<xs:complexType>
<xs:element>
<xs:schema>
<?xml version="1.0"?>
<details>
<name>abc</name>
<age>22</age>
<details></code>
i am new to xml..i require your help..
thanks a lot in advance..
|
|
|
|
|
Hi,
you have to change the root of your schema file to
<xs:schema xmlns:xs="http://www.w3.org/2001/XMLSchema" targetNamespace="http://mynamespace/mydetails">
This will define the xs prefix and the namespace you want to create.
Within your xml file you have to put a reference to the schema by changing the root to this:
<details xmlns="http://mynamespace/mydetails">
Here the namespace is imported without a prefix. But pay attention if you need to validate the xml (if it is valid according to the schema). The reference will be resolved by a DefaultResolver. This one will not find the schema file until you give it a hint.
Simple code to validate an XML file against a schema file (XSD)[^]
Regards
Sebastian
|
|
|
|
|
Do not spam the forums  This has nothing to do with XML or XSL
I know the language. I've read a book. - _Madmatt
|
|
|
|
|
Hi
If My XML is:
<person>
<name>Sue</name>
<email>bob@example.com</email>
</person/>
<person>
<name>Sue</name>
<email>sue@example.com</email>
</person>
In C# if I know bob's name how can I get his email address???
Thank You
|
|
|
|
|
You want to use an XPathNavigator[^].
Then use an XPath expression like "//person[name='Bob']/email" to select the email node or "//person[name='Bob']/email/text()" to select the email value.
Here's an example that's very close to what you want.Java, Basic, who cares - it's all a bunch of tree-hugging hippy cr*p
CodeProject MVP for 2010 - who'd'a thunk it!
|
|
|
|
|
Thanks, but I have solved it by using LINQ
|
|
|
|
|
GIDS is the Biggest Independent Summit for India's IT Professional Ecosystem. Registration for Event Open.
Bangalore, February 26, 2010: JavaServer Faces is a Java-based Web application framework intended developed to simplify development integration of Web-based user interfaces. It is often mentioned together with Ajax, a combination of technologies that makes it possible to create rich user interfaces. Since JSF supports multiple output formats, Ajax-enabled components can easily be added to enrich JSF-based user interfaces. Oracle's Frank Nimphius says that Service Oriented Architecture (SOA) has become a reality in modern software development but Web services don't have a user interface. This is fine if communication is between machines. But what about human interaction like in data entry and work flow? Users need an application display they feel comfortable working with. So what about building Web 2.0 user interfaces for service oriented architectures? Does it work, or does it hurt - and if so, how bad is it? Frank is coming this summer to India's biggest summit for the software developer ecosystem - Great Indian Developer Summit (http://www.developersummit.com/) to show how JavaServer Faces can be used to build compelling Ajax user interfaces for Web Services models giving end users a comfortable working environment that includes client side validation and user interface customization.
In his second session at GIDS 2010, Frank addresses the topic of implementing automatic UI refreshes. To web application users, it must appear as if the Web reinvents itself once a year with more interactive UIs, increasing performance through partial page refreshes, and desktop-like usability patterns that allow users to become as productive using web applications as they are using real desktop clients. One technical detail, though, hasn't changed in the past and is unlikely to change in the near future: HTTP. Hypertext Transfer Protocol is based on the request-response principle in which the client sends a query to the server and the server responds with the requested data. Between requests, no connection is maintained between the client and the server that would allow server-side logic to send more data unasked. Any changes in the underlying data layer used by an application are first detected within the next client request. Hopefully, it doesn't come to you by surprise when we say that in the modern days of Web 2.0 and Rich Enterprise Applications (REA), the Web still is disconnected and stateless. So, in these modern days of Web 2.0 and Rich Enterprise Applications (REA), is the Web still is disconnected and stateless? Not really, because you frequently use some applications on the Web that update their client UIs with server-side changes without your needing to do anything. The question, therefore, is how this was accomplished and whether you can do the same in JavaServer Faces. In his session, Frank will guide attendees through the options that are available in AJAX and other implementation technologies of Rich Internet Applications (RIA) to implement automatic UI refreshes.
Frank Nimphius is a principal product manager for application development tools at Oracle Corporation since 1999. He actively contributes to the development of Oracle JDeveloper and the Oracle Application Development Framework (ADF). He represents the Oracle J2EE development team at J2EE conferences world wide, including various Oracle user groups and the Oracle Open World conference. The talk 'Building Web 2.0 User Interfaces for Web Service Models using JSF' will be co-presented by Jobinesh Purushothaman. Jobinesh Purushothaman is an enterprise Java specialist with 10+ years of experience in the industry. He is involved in design and architectural decisions of various products using ADF and JavaEE technologies. He is interested in developing more simplified enterprise technologies where developers can focus on their business solutions rather on the technology complexities.
About Great Indian Developer Summit
Great Indian Developer Summit is the gold standard for India's software developer ecosystem for gaining exposure to and evaluating new projects, tools, services, platforms, languages, software and standards. Packed with premium knowledge, action plans and advise from been-there-done-it veterans, creators, and visionaries, the 2010 edition of Great Indian Developer Summit features focused sessions, case studies, workshops and power panels that will transform you into a force to reckon with. Featuring 3 co-located conferences: GIDS.NET, GIDS.Web, GIDS.Java and an exclusive day of in-depth tutorials - GIDS.Workshops, from 20 April to 24 April at the IISc campus in Bangalore.
At GIDS you'll participate in hundreds of sessions encompassing the full range of Microsoft computing, Java, Agile, RIA, Rich Web, open source/standards, languages, frameworks and platforms, practical tutorials that deep dive into technical skill and best practices, inspirational keynote presentations, an Expo Hall featuring dozens of the latest projects and products activities, engaging networking events, and the interact with the best and brightest of speakers from around the world.
For further information on GIDS 2010, please visit the summit on the web http://www.developersummit.com/
A Saltmarch Media Press Release
E: info@saltmarch.com
Ph: +91 80 4005 1000
|
|
|
|
|
I am using Visual Studio 2005 to create my first XML Schema. Generally it's going well. The intellisense in VS is very helpful.
My only issue is that VS is flagging the element "Well" in my example, saying "The type attribute cannot be present with either simpleType or complexType." I'm not sure how to structure it if this way isn't acceptable. I've also included a XML snippet of what I am trying define in the schema.
Any help appreciated.
<xsd:element name="Well_Volumes">
<xsd:complexType>
<xsd:sequence>
<xsd:element name="Well" type="xsd:decimal">
<xsd:complexType>
<xsd:attribute name="channel" type="xsd:string"/>
<xsd:attribute name="dispense_order" type="xsd:string"/>
<xsd:attribute name="plate_column" type="xsd:string"/>
<xsd:attribute name="plate_row" type="xsd:string"/>
</xsd:complexType>
</xsd:element>
</xsd:sequence>
</xsd:complexType>
</xsd:element>
<br/>
<br/>
<Well_Volumes>
<Well channel="A" dispense_order="1" plate_column="1" plate_row="1">0.209</Well>
<Well channel="A" dispense_order="2" plate_column="2" plate_row="1">0.212</Well>
<Well channel="A" dispense_order="3" plate_column="3" plate_row="1">0.219</Well>
<Well channel="B" dispense_order="1" plate_column="4" plate_row="2">0.212</Well>
<Well channel="B" dispense_order="2" plate_column="5" plate_row="2">0.222</Well>
<Well channel="B" dispense_order="3" plate_column="6" plate_row="2">0.212</Well>
</Well_Volumes>
|
|
|
|
|
Thanks everyone, but never mind. Although it makes perfect sense to me, apparently an element can not include both attributes and a value. Hmmm... Maybe in the next version.
Below is how I am fixing the problem.
<xsd:element name="Well_Volumes">
<xsd:complexType>
<xsd:sequence>
<xsd:element name="Well">
<xsd:complexType>
<xsd:sequence>
<xsd:element name="volume" type="xsd:decimal"/>
</xsd:sequence>
<xsd:attribute name="channel" type="xsd:string"/>
<xsd:attribute name="dispense_order" type="xsd:string"/>
<xsd:attribute name="plate_column" type="xsd:string"/>
<xsd:attribute name="plate_row" type="xsd:string"/>
</xsd:complexType>
</xsd:element>
</xsd:sequence>
</xsd:complexType>
</xsd:element>
|
|
|
|
|
You need a simpleContent[^] element as a child of the complexType.
Then extend the simple type with attributes - like this:
<xsd:element name="Well_Volumes">
<xsd:complexType>
<xsd:sequence maxOccurs="unbounded">
<xsd:element name="Well">
<xsd:complexType>
<xsd:simpleContent>
<xsd:extension base="xsd:decimal">
<xsd:attribute name="channel" type="xsd:string"/>
<xsd:attribute name="dispense_order" type="xsd:string"/>
<xsd:attribute name="plate_column" type="xsd:string"/>
<xsd:attribute name="plate_row" type="xsd:string"/>
</xsd:extension>
</xsd:simpleContent>
</xsd:complexType>
</xsd:element>
</xsd:sequence>
</xsd:complexType>
</xsd:element>Java, Basic, who cares - it's all a bunch of tree-hugging hippy cr*p
CodeProject MVP for 2010 - who'd'a thunk it!
|
|
|
|
|
1. Read the section "How to get an answer to your question" above, especially the second point.
2. Everyone loves it to answer questions ASAP or URGENT.  Greetings
Covean
|
|
|
|
|
I have some xsl that generally works, except when there are multiple children in a node.
What I get is:
<File>
<Person>Person Name</Person>
<Title>Title 1</Title>
<BoxLocation>Location 1</BoxLocation>
<FileName>File Name 1 </FileName>
<VersionNumber>Version 1</VersionNumber>
<Title>Title 2</Title>
<BoxLocation>Location 2</BoxLocation>
<FileName>File Name 2</FileName>
<VersionNumber>Version 2</VersionNumber>
</File>
What I am after is:
<File>
<Person>Person Name</Person>
<Title>Title 1</Title>
<BoxLocation>Location 1</BoxLocation>
<FileName>File Name 1 </FileName>
<VersionNumber>Version 1</VersionNumber>
</File>
<File>
<Person>Person Name</Person>
<Title>Title 2</Title>
<BoxLocation>Location 2</BoxLocation>
<FileName>File Name 2</FileName>
<VersionNumber>Version 2</VersionNumber>
</File>
The relevant part of the xsl is:
<xsl:for-each select="DBFile">
<File>
<xsl:for-each select="Title">
<Person>
<xsl:value-of select="."/>
</Person>
</xsl:for-each>
<xsl:for-each select="DBPart">
<xsl:for-each select="DBDocument">
<xsl:for-each select="Title">
<Title>
<xsl:value-of select="."/>
</Title>
</xsl:for-each>
<xsl:for-each select="DBMetadataFieldValue">
<xsl:for-each select="DBMetadataValue">
<xsl:for-each select="Text">
<BoxLocation>
<xsl:value-of select="."/>
</BoxLocation>
</xsl:for-each>
</xsl:for-each>
</xsl:for-each>
<xsl:for-each select="DBVersion">
<xsl:for-each select="ArchiveFileName">
<FileName>
<xsl:value-of select="."/>
</FileName>
</xsl:for-each>
<xsl:for-each select="Number">
<VersionNumber>
<xsl:value-of select="."/>
</VersionNumber>
</xsl:for-each>
</xsl:for-each>
</xsl:for-each>
</xsl:for-each>
</File>
</xsl:for-each>
Any advice or assistance pointing me in the right direction will be greatly appreciated.
|
|
|
|
|
Show us the input...
Are you expecting there to be multiple DBPart, DBDocument, etc child nodes? 'Cause if not, the xsl:for-each loops really clutter things up...Java, Basic, who cares - it's all a bunch of tree-hugging hippy cr*p
CodeProject MVP for 2010 - who'd'a thunk it!
|
|
|
|
|
Hi Stuart,
Thanks for the reply.
The input is quite large. I am working on trying to scale down a sample (and remove sensitive data).
The basic form of the input is:
DBArchive
DBAccount
DBFolder
DBFolder
DBFile
DBPart
DBDocument
There are one, two or three DBDocument nodes inside a DBPart node
My thinking at the moment is that the approach of the xsl is wrong and it should use templates more, but I have very little experience with this stuff and am trying to get my head around how xsl templates work. I assume that I need to get the DBDocument information first,and then go back and fill in the rest. I just don't know how to do that.
Cheers.
(I am in Queensland (Aus), so have gone home now.
|
|
|
|
|
If you can provide a sample, I'm quite happy to help you with your xsl. I've a fair amount of experience with XSL over the years  Java, Basic, who cares - it's all a bunch of tree-hugging hippy cr*p
CodeProject MVP for 2010 - who'd'a thunk it!
|
|
|
|
|
I have removed data from nodes I am not interested in, but left the nodes so you can get a feel for the structure.
There are two records (DBFile nodes) here - the first one has a single file, the second has two files (i.e. 2 DBDocument nodes).
Person 2 should end up with two records - one for File 2 and one for File 3.
Cheers,
<!DOCTYPE DBArchive SYSTEM "http://support.docbanq.com/DTDs/DocBanqArchive_Version2.dtd">
<DBArchive>
<ArchiveVersion attrname="String"></ArchiveVersion>
<DBAccount attrname="Account">
<Name attrname="String"></Name>
<Identifier attrname="String"></Identifier>
<Number attrname="Integer"></Number>
<DBFolder attrname="Content">
<DBIdentifier attrname="Identifier">
<Value attrname="String"></Value>
</DBIdentifier>
<MaximumVersions attrname="Integer"/>
<InheritPermission attrname="Boolean"></InheritPermission>
<HideFromUnprivilegedUser attrname="Boolean"/>
<Description attrname="String"></Description>
<Title attrname="String"></Title>
<SpaceUsageKB attrname="Integer"></SpaceUsageKB>
<DBAccountUser attrname="CreatedBy">
<LoginID attrname="String"></LoginID>
</DBAccountUser>
<CreatedDateTime attrname="Datetime"></CreatedDateTime>
<ObjectID attrname="Identifier"></ObjectID>
<DBFolder attrname="Object">
<DBIdentifier attrname="Identifier">
<Value attrname="String"></Value>
</DBIdentifier>
<MaximumVersions attrname="Integer"/>
<InheritPermission attrname="Boolean"></InheritPermission>
<HideFromUnprivilegedUser attrname="Boolean"/>
<Description attrname="String"></Description>
<Title attrname="String"></Title>
<SpaceUsageKB attrname="Integer"></SpaceUsageKB>
<DBAccountUser attrname="CreatedBy">
<LoginID attrname="String"></LoginID>
</DBAccountUser>
<CreatedDateTime attrname="Datetime"></CreatedDateTime>
<ObjectID attrname="Identifier"></ObjectID>
<DBFile attrname="Object">
<DBIdentifier attrname="Identifier">
<Value attrname="String"></Value>
</DBIdentifier>
<DisposalScheduleSet attrname="Date"></DisposalScheduleSet>
<ActionDate attrname="Date"></ActionDate>
<DisposalAction attrname="String"></DisposalAction>
<Description attrname="String"></Description>
<Title attrname="String">Person Name 1</Title>
<SpaceUsageKB attrname="Integer"></SpaceUsageKB>
<DBAccountUser attrname="CreatedBy">
<LoginID attrname="String"></LoginID>
</DBAccountUser>
<CreatedDateTime attrname="Datetime"></CreatedDateTime>
<ObjectID attrname="Identifier"></ObjectID>
<DBPart attrname="Object">
<Number attrname="Integer"></Number>
<ContentFrom attrname="Date"/>
<ContentTo attrname="Date"/>
<PhysicallyExists attrname="Boolean"></PhysicallyExists>
<DBParticipant attrname="BorrowedBy"/>
<DBParticipant attrname="Custodian"/>
<DBLocation attrname="Location"/>
<DBRecordStatus attrname="Status">
<Value attrname="String"></Value>
</DBRecordStatus>
<ActionedDateTime attrname="Datetime"></ActionedDateTime>
<DBAccountUser attrname="ActionedBy">
<LoginID attrname="String"></LoginID>
</DBAccountUser>
<Description attrname="String"></Description>
<Title attrname="String"></Title>
<SpaceUsageKB attrname="Integer"></SpaceUsageKB>
<DBAccountUser attrname="CreatedBy">
<LoginID attrname="String"></LoginID>
</DBAccountUser>
<CreatedDateTime attrname="Datetime"></CreatedDateTime>
<ObjectID attrname="Identifier"></ObjectID>
<DBDocument attrname="Object">
<DBUser attrname="CheckedOutBy"/>
<CheckedOutDateTime attrname="Datetime"/>
<CheckedOutReason attrname="String"></CheckedOutReason>
<DBIdentifier attrname="Identifier">
<Value attrname="String"></Value>
</DBIdentifier>
<Title attrname="String">Title 1</Title>
<SpaceUsageKB attrname="Integer"></SpaceUsageKB>
<DBAccountUser attrname="CreatedBy">
<LoginID attrname="String"></LoginID>
</DBAccountUser>
<CreatedDateTime attrname="Datetime"></CreatedDateTime>
<ObjectID attrname="Identifier"></ObjectID>
<Description attrname="String"></Description>
<DBMetadataFieldValue attrname="MetadataFieldValue">
<DBMetadataField attrname="MetadataField">
<FieldName attrname="String">Box Location</FieldName>
<Type attrname="String"></Type>
<Rule attrname="String"></Rule>
</DBMetadataField>
<DBMetadataValue attrname="MetadataValue">
<Text attrname="String">Location 1</Text>
<Date attrname="Date"/>
<DBParticipant attrname="Participant"/>
</DBMetadataValue>
</DBMetadataFieldValue>
<DBVersion attrname="Version">
<ArchiveFileName attrname="String">File Name 1</ArchiveFileName>
<Number attrname="Integer">Version 1</Number>
<FileExtension attrname="String"></FileExtension>
<FileAvailable attrname="Boolean"></FileAvailable>
<PhysicalSpaceUsage attrname="Integer"></PhysicalSpaceUsage>
<CreatedDateTime attrname="Datetime"></CreatedDateTime>
<DBAccountUser attrname="CreatedBy">
<LoginID attrname="String"></LoginID>
</DBAccountUser>
<Comments attrname="String"></Comments>
<IndexString attrname="String"></IndexString>
</DBVersion>
</DBDocument>
</DBPart>
</DBFile>
<DBFile attrname="Object">
<DBIdentifier attrname="Identifier">
<Value attrname="String"></Value>
</DBIdentifier>
<DisposalScheduleSet attrname="Date"></DisposalScheduleSet>
<ActionDate attrname="Date"></ActionDate>
<DisposalAction attrname="String"></DisposalAction>
<Description attrname="String"></Description>
<Title attrname="String">Person Name 2</Title>
<SpaceUsageKB attrname="Integer"></SpaceUsageKB>
<DBAccountUser attrname="CreatedBy">
<LoginID attrname="String"></LoginID>
</DBAccountUser>
<CreatedDateTime attrname="Datetime"></CreatedDateTime>
<ObjectID attrname="Identifier"></ObjectID>
<DBPart attrname="Object">
<Number attrname="Integer"></Number>
<ContentFrom attrname="Date"/>
<ContentTo attrname="Date"/>
<PhysicallyExists attrname="Boolean"></PhysicallyExists>
<DBParticipant attrname="BorrowedBy"/>
<DBParticipant attrname="Custodian"/>
<DBLocation attrname="Location"/>
<DBRecordStatus attrname="Status">
<Value attrname="String"></Value>
</DBRecordStatus>
<ActionedDateTime attrname="Datetime"></ActionedDateTime>
<DBAccountUser attrname="ActionedBy">
<LoginID attrname="String"></LoginID>
</DBAccountUser>
<Description attrname="String"></Description>
<Title attrname="String"></Title>
<SpaceUsageKB attrname="Integer"></SpaceUsageKB>
<DBAccountUser attrname="CreatedBy">
<LoginID attrname="String"></LoginID>
</DBAccountUser>
<CreatedDateTime attrname="Datetime"></CreatedDateTime>
<ObjectID attrname="Identifier"></ObjectID>
<DBDocument attrname="Object">
<DBUser attrname="CheckedOutBy"/>
<CheckedOutDateTime attrname="Datetime"/>
<CheckedOutReason attrname="String"></CheckedOutReason>
<DBIdentifier attrname="Identifier">
<Value attrname="String"></Value>
</DBIdentifier>
<Title attrname="String">Title 2</Title>
<SpaceUsageKB attrname="Integer"></SpaceUsageKB>
<DBAccountUser attrname="CreatedBy">
<LoginID attrname="String"></LoginID>
</DBAccountUser>
<CreatedDateTime attrname="Datetime"></CreatedDateTime>
<ObjectID attrname="Identifier"></ObjectID>
<Description attrname="String"></Description>
<DBMetadataFieldValue attrname="MetadataFieldValue">
<DBMetadataField attrname="MetadataField">
<FieldName attrname="String">Box Location</FieldName>
<Type attrname="String"></Type>
<Rule attrname="String"></Rule>
</DBMetadataField>
<DBMetadataValue attrname="MetadataValue">
<Text attrname="String">Location 2</Text>
<Date attrname="Date"/>
<DBParticipant attrname="Participant"/>
</DBMetadataValue>
</DBMetadataFieldValue>
<DBVersion attrname="Version">
<ArchiveFileName attrname="String">File Name 2</ArchiveFileName>
<Number attrname="Integer">Version 2</Number>
<FileExtension attrname="String"></FileExtension>
<FileAvailable attrname="Boolean"></FileAvailable>
<PhysicalSpaceUsage attrname="Integer"></PhysicalSpaceUsage>
<CreatedDateTime attrname="Datetime"></CreatedDateTime>
<DBAccountUser attrname="CreatedBy">
<LoginID attrname="String"></LoginID>
</DBAccountUser>
<Comments attrname="String"></Comments>
<IndexString attrname="String"></IndexString>
</DBVersion>
</DBDocument>
<DBDocument attrname="Object">
<DBUser attrname="CheckedOutBy"/>
<CheckedOutDateTime attrname="Datetime"/>
<CheckedOutReason attrname="String"></CheckedOutReason>
<DBIdentifier attrname="Identifier">
<Value attrname="String"></Value>
</DBIdentifier>
<Title attrname="String">Title 3</Title>
<SpaceUsageKB attrname="Integer"></SpaceUsageKB>
<DBAccountUser attrname="CreatedBy">
<LoginID attrname="String"></LoginID>
</DBAccountUser>
<CreatedDateTime attrname="Datetime"></CreatedDateTime>
<ObjectID attrname="Identifier"></ObjectID>
<Description attrname="String"></Description>
<DBMetadataFieldValue attrname="MetadataFieldValue">
<DBMetadataField attrname="MetadataField">
<FieldName attrname="String">Box Location</FieldName>
<Type attrname="String"></Type>
<Rule attrname="String"></Rule>
</DBMetadataField>
<DBMetadataValue attrname="MetadataValue">
<Text attrname="String">Location 3</Text>
<Date attrname="Date"/>
<DBParticipant attrname="Participant"/>
</DBMetadataValue>
</DBMetadataFieldValue>
<DBVersion attrname="Version">
<ArchiveFileName attrname="String">File Name 3</ArchiveFileName>
<Number attrname="Integer">Version 3</Number>
<FileExtension attrname="String"></FileExtension>
<FileAvailable attrname="Boolean"></FileAvailable>
<PhysicalSpaceUsage attrname="Integer"></PhysicalSpaceUsage>
<CreatedDateTime attrname="Datetime"></CreatedDateTime>
<DBAccountUser attrname="CreatedBy">
<LoginID attrname="String"></LoginID>
</DBAccountUser>
<Comments attrname="String"></Comments>
<IndexString attrname="String"></IndexString>
</DBVersion>
</DBDocument>
</DBPart>
</DBFile>
</DBFolder>
</DBFolder>
</DBAccount>
</DBArchive>
|
|
|
|
|
Solved it (with a bit of xPath trickery).
The answer was to go to each file node and then back track through parent levels to get the other data.
<xsl:for-each select="DBAccount/DBFolder/DBFile/DBPart/DBDocument/DBVersion">
<File>
<Person>
<xsl:value-of select="../../../Title"/>
</Person>
<Title>
<xsl:value-of select="../Title"/>
</Title>
<BoxLocation>
<xsl:value-of select="../DBMetadataFieldValue/DBMetadataValue/Text"/>
</BoxLocation>
<FileName>
<xsl:value-of select="./ArchiveFileName"/>
</FileName>
<VersionNumber>
<xsl:value-of select="./Number"/>
</VersionNumber>
</File>
</xsl:for-each>
|
|
|
|
|
| Yeah - I'd was just looking at it and realising that you needed some way of determining what indicated unique files...which you've done... Java, Basic, who cares - it's all a bunch of tree-hugging hippy cr*p
CodeProject MVP for 2010 - who'd'a thunk it!
|
|
|
|
|
I have a very large XMLDocument with 56,000 child records each having 8 child field elements. The application that i have written performs a complicated process on the XML. It can process 10,000 records in 5 minutes and 20,000 in 25 minutes (increases exponentially) but takes maybe 10 hours to process the 56,000 record (which is unacceptable). Whats the best way to de-batch this XML Document into bite size chunks (eg 10,000 and after 5 iteration will process 50,000. which will execute in 25-30 minutes processing time)
Thanks.
|
|
|
|
|
How many megabytes is your xml file?
Does the "complicated process" operate on
only one of the 56,000 children independantly,
without refferencing the other children ?
Show me a childNode and tell me about
this "complicated process".
How much free memory does your computer have available ?
|
|
|
|
|
There is a sample of the child record. And there are 56,000 of them in the xml document. I can realy give you the full details of what the complicated process is doing but part of it is using the Muenchian Method grouping on 'cost_centre' and 'expense_code'.
The app is runningon a dev box 2.50GH, 2GB.
It has 1/2GB free when app is not running
<Transaction>
<Entry>
<payroll_id>payroll_id_0</payroll_id>
<payroll_nm>payroll_nm_0</payroll_nm>
<payRunDate>payRunDate_0</payRunDate>
<payRunID>payRunID_0</payRunID>
<empno>10</empno>
<surname>surname_0</surname>
<forename>forename_0</forename>
<pos_ref>pos_ref_0</pos_ref>
<pos_name>pos_name_0</pos_name>
<element_id>element_id_0</element_id>
<element_name>element_name_0</element_name>
<cost_centre>c11</cost_centre>
<expense_code>e11</expense_code>
<debit_credit>debit_credit_0</debit_credit>
<amount>10</amount>
<signed_amount>10</signed_amount>
</Entry>
<Entry>
....
</Entry>
</Transaction>
|
|
|
|
|
Why is this invalid?
<xsl:choose>
<xsl:when test="position() mod 2 = 1">
<tr bgcolor="Silver">
</xsl:when>
<xsl:otherwise>
<tr>
</xsl:otherwise>
</xsl:choose>
...
</tr>
Internet Explorer reports the error "End tag 'xsl:when' does not match the start tag 'tr'"
|
|
|
|
|
The line:
<tr bgcolor="Silver">
is unclosed, so the next closing tag should be </tr> rather than </xsl:when>.txtspeak is the realm of 9 year old children, not developers. Christian Graus
|
|
|
|
|
The previous answer told you why the error occurred - here's a solution:
<tr>
<xsl:if test="position() mod 2 = 1">
<xsl:attribute name="bgcolor">Silver</xsl:attribute>
</xsl:if>
...
</tr>Java, Basic, who cares - it's all a bunch of tree-hugging hippy cr*p
CodeProject MVP for 2010 - who'd'a thunk it!
|
|
|
|
General 
News 
Suggestion 
Question 
Bug 
Answer 
Joke 
Praise 
Rant 
Admin 
Submit an article or tip
