Hi
I want to take an XML file and transform it into a pipe-delimited format. What is the best tool to use for this? I have libxml2 which seems to be the best xml parser around.
The xml file will have the following format.
<Txn>
<Date>120504</Date>
<id>99</id>
<Items>
<Item>... (1 Reply)
I want to use wget comment to parse an xml parse that exist in an online website. How can I connect it using shell script through Unix and how can I parse it?? (1 Reply)
I have a xml file attached. I need to parse parameterId and its value
My output should be like
151515 38
151522 32769
and so on..
Please help me. Its urgent (6 Replies)
Learned People,
Hello !
Till today, for the most part, all of the tricky questions/situations that I encountered were already posted by other folks and all I had to do was peruse through these one at a time and I could find some sort of an answer and all I had to do was add some minor tweaks... (5 Replies)
I had a big XML and from which I have to make a layout as below
*TOTAL+CB | *CB+FX | CS |*IR | *TOTAL |
--------------------------------------------------------------------------------------------------
|CB FX | | | |
DMFXNY EMSGFX... (6 Replies)
I am trying to parse an xml file and trying to grab certain values and inserting them into database table. I have the following xml that I am parsing:
<dd:service name="locator" link="false">
<dd:activation mode="manual" />
<dd:run mode="direct_persistent" proxified="false" managed="true"... (7 Replies)
I am trying to parse the XML Google contact file using tools like xmllint and I even dived into the XSL Style Sheets using xsltproc but I get nowhere.
I can not supply any sample file as it contains private data but you can download your own contacts using this script:
#!/bin/sh
# imports... (9 Replies)
HI
I want to parse below file in to two output :-
Input :-
?xml version="1.0" encoding="UTF-8"?>
<bulkCmConfigDataFile xmlns:un="utranNrm.xsd"
<configData dnPrefix="Undefined">
<xn:SubNetwork id="ONRM_ROOT_MO_R">
<xn:MeContext id="C136">
... (3 Replies)
I have an xml file where the format looks like below
<SESSIONCOMPONENT REFOBJECTNAME ="pre_session_command" REUSABLE ="NO" TYPE ="Pre-session command">
<TASK DESCRIPTION ="" NAME ="pre_session_command" REUSABLE ="NO" TYPE ="Command" VERSIONNUMBER ="1">
... (8 Replies)
Discussion started by: r_t_1601
8 Replies
LEARN ABOUT MOJAVE
log::message::item5.18
Log::Message::Item(3pm) Perl Programmers Reference Guide Log::Message::Item(3pm)NAME
Log::Message::Item - Message objects for Log::Message
SYNOPSIS
# Implicitly used by Log::Message to create Log::Message::Item objects
print "this is the message's id: ", $item->id;
print "this is the message stored: ", $item->message;
print "this is when it happened: ", $item->when;
print "the message was tagged: ", $item->tag;
print "this was the severity level: ", $item->level;
$item->remove; # delete the item from the stack it was on
# Besides these methods, you can also call the handlers on
# the object specifically.
# See the Log::Message::Handlers manpage for documentation on what
# handlers are available by default and how to add your own
DESCRIPTION
Log::Message::Item is a class that generates generic Log items. These items are stored on a Log::Message stack, so see the Log::Message
manpage about details how to retrieve them.
You should probably not create new items by yourself, but use the storing mechanism provided by Log::Message.
However, the accessors and handlers are of interest if you want to do fine tuning of how your messages are handled.
The accessors and methods are described below, the handlers are documented in the Log::Message::Handlers manpage.
Methods and Accessors
remove
Calling remove will remove the object from the stack it was on, so it will not show up any more in subsequent fetches of messages.
You can still call accessors and handlers on it however, to handle it as you will.
id
Returns the internal ID of the item. This may be useful for comparing since the ID is incremented each time a new item is created.
Therefore, an item with ID 4 must have been logged before an item with ID 9.
when
Returns the timestamp of when the message was logged
message
The actual message that was stored
level
The severity type of this message, as well as the name of the handler that was called upon storing it.
tag
Returns the identification tag that was put on the message.
shortmess
Returns the equivalent of a "Carp::shortmess" for this item. See the "Carp" manpage for details.
longmess
Returns the equivalent of a "Carp::longmess" for this item, which is essentially a stack trace. See the "Carp" manpage for details.
parent
Returns a reference to the Log::Message object that stored this item. This is useful if you want to have access to the full stack in a
handler.
SEE ALSO
Log::Message, Log::Message::Handlers, Log::Message::Config
AUTHOR
This module by Jos Boumans <kane@cpan.org>.
Acknowledgements
Thanks to Ann Barcomb for her suggestions.
COPYRIGHT
This module is copyright (c) 2002 Jos Boumans <kane@cpan.org>. All rights reserved.
This library is free software; you may redistribute and/or modify it under the same terms as Perl itself.
perl v5.18.2 2014-01-06 Log::Message::Item(3pm)