Siva shanmugam

+ Follow
since Jul 18, 2002
Merit badge: grant badges
For More
Cows and Likes
Total received
In last 30 days
Total given
Total received
Received in last 30 days
Total given
Given in last 30 days
Forums and Threads
Scavenger Hunt
expand Ranch Hand Scavenger Hunt
expand Greenhorn Scavenger Hunt

Recent posts by Siva shanmugam

Hi folks,
We have developed a shopping protal which was developed using java,javabean,jsp and servelt.During developement time we used to restart the tomcat server frequenlty so we haven't faced the OutOfMemory problem.But now in deployment stage we are getting this Exception after some amount of time.We think it due to memory leak.So we need to know,has anybody faced these kind of problem during deployment stage and how to proceed to resolve this issue.
Thanks in advance
20 years ago
Hai Jayadev & Ranchers,
my question is ,
"Why do we need to use final attribute in element declarations ?"
The effect of specifying the finalDefault attribute is equivalent to
specifying a final attribute on every type definition and element declaration in the schema.
If you define a finalDefault attribute with "#all" as a value
you can't derive a new complexType or a simpleType from exiting complexType
and simpleType,that are defined in that schema.
But what is the use of defining an element with final attribute which can have
a value restriction or extension or #all ?
This is the rule while using translate() function
1. If a character in the original string appears in the second argument string,its is replaced with the "corresponding " character in the third argument string
2.If a character in the originalstring appears in the second argument string and there is no corresponding character in the third argument string,then the character is deleted.
3.If a character in the second argument string appear more than once,the first occurance determines the replacement character.
4.If the third argument string is larger than the second string extra characters are ignored.
Ref:- XSLT by Doug Tidwell
It might be because of the place you are using the id function.
In <xsl:apply-templates> it selects all the text value of the nodes.
In <xsl:value-of> it selects the only first node's text value which is in the resultant node set.
Local Name is an Unqualified Name of an element,ie only element name.
QName is a qualifed Name of an element.
Local Name -> Test
qName -> myURI:Test
Hai Jayadev
this is my explanation for your reply
UserTable ----
UserID (primary key)
OrdersTable ----
UserIDField (foreign key)
Now, in the above scenario, wouldn't i like to have the row information in the table holding the primary key to include the stuff of the row info of the corresponding table with the foreign key i.e, when i mention an XML element for the above scenario, i would like to have something like -
Copy the data in a relationship into the element for the row containing the foreign key.
<Name> Jayadev </Name>
<ItemOrdered> XML Book </ItemOrdered>

In the example you have created an xml file for the orders table.
The related data for the UserIdField is in UserTable,So we are copying the info related to the UserId from UserTable
and inserted in the place of foreign key.
If i am correct you are also referring the same answer "C".
For Q2
C can also be a correct ans
For Example if u have 2 tables in database like
User Tbl
UsrId primarykey,
UsrName ,
AddrId foreignKey
Addr Tbl
AddrId primaryKey,

If you create an Xml file for the user tbl,the structure can be like this
In the above case we have copied address details into User detail element.So "C" is my choice.But "D" is meanigless bcase
you cann't include the user details into address details and its against an RDBMS rule also.
I have tried the above code.But the response is the same.
I am trying to validate an xml file against a schema.
Schema file mySchema.xsd
------ ---- ------------
<?xml version="1.0"?>
<xsd:schema xmlns:xsd="" targetNamespace="" xmlns="">
<xs:element name="Parent">
<xs:element name="Child"/>
Xml File
<?xml version="1.0"?>
<Parent xmlns:xsi=""
xsi:schemaLocation=" mySchema.xsd"
While parsing the xml file using xerces DOM i am getting the following error.
Error General Schema Error: Grammar with uri 2: , can not found.
Error Element type "Parent" must be declared.
Error Element type "Child" must be declared.

I think the namespace which is refered in xml file is not understood by the parser.
Can anyone tell me, how can i make the parser to understand the Schema ?
Can anyone tell me,
Is it is possible to redefine the elements in Internal DTD subset which are already defined in external DTD subset ?
External DTD file ex1.dtd is like this
<!ELEMENT eleName (#PCDATA)>

Xml file is like this
<?xml version="1.0" encoding="utf-8" standalone="no" ?>
<!DOCTYPE eleName SYSTEM "ex1.dtd"
<!ELEMENT eleName (childElement1|childElement2)*>
] >
This above code works fine in IE 6.0
but it gives, Element type "eleName" must not be declared more than once
Error in Xerces Parser.
Thank you very much andreas mueller
Can anyone tell me,what is the document order and reverse document order, regarding to XPath syntax?

Originally posted by William Brogden:
Which package are you using to do this? Is it possible that including/excluding PIs is controlled by some setting?

I am using Xerces Parser to do that.
while writing the DOM Document object to file ,whatever processing instruction(PI) nodes added to the DOM Document object disappears in the resultant XML file.