XML C++ Generator

Hi,
I'm trying to run xmlcg on a Solaris box and I'm getting this
error:
ld.so.1: bin/xmlcg: fatal: relocation error: file bin/xmlcg:
symbol open64: referenced symbol not found
I'm guessing that I'm missing something from my LD_LIBRARY_PATH
but I don't know what it is. Any Ideas?
Thanks,
Robert Conklin
null

Robert Conklin (guest) wrote:
: Hi,
: I'm trying to run xmlcg on a Solaris box and I'm getting this
: error:
: ld.so.1: bin/xmlcg: fatal: relocation error: file bin/xmlcg:
: symbol open64: referenced symbol not found
: I'm guessing that I'm missing something from my
LD_LIBRARY_PATH
: but I don't know what it is. Any Ideas?
: Thanks,
: Robert Conklin
As stated in the readme, we only support Solaris 2.6. I am
guessing that you are using an earlier version of Solaris.
Oracle XML Team
http://technet.oracle.com
Oracle Technology Network
null

Similar Messages

ANN: XML Class Generator for Java Available

The Oracle XMCL Class Generator for Java is now available as an
initial beta release on the Oracle Technology Network at
http://technet.oracle.com. Select 'xml' from the Technology menu.
The XML Class Generator will generate a set of Java source files
based on an input DTD. The generated Java source files can then
be used to construct, optionally validate, and print a XML
document that is compliant to the DTD specified. This is an early
beta release and has the following features:
* Creates Java Classes from DTDs to enable the programmatic
construction of XML documents.
* Supports validation mode to assist debugging.
* Works with the Oracle XML Parser in Java.
* Creates documents conforming to the W3C XML 1.0
Recommendation.
* Supports creating documents in the following encodings:
UTF-8
UTF-16
ISO-10646-UCS-2
ISO-10646-UCS-4
US-ASCII
EBCDIC-CP-US
ISO-8859-1
Shift_SJIS
Oracle XML Team
http://technet.oracle.com
Oracle Technology Network
null

Thanks,
Rob
Oracle XML Team wrote:
: First, the link has been fixed. As to your access exception,
we
: have traced it to a difference between JDK 1.1.x and JDK 1.2.
: You can solve it by using a 1.1.x version of the JDK or wait
till
: our production version of our XML Parser becomes available
within
: a week which will work with 1.2.
: Oracle XML Team
: http://technet.oracle.com
: Rob Edagr (guest) wrote:
: : 1) The HREF on the download page for the NT version points
to
: : the version 102 parser not the classgen.
: : 2) After downloading and installing the classgen (by
guessing
: : what the url was) I ran it and get the following
: : C:\jdk1.2\xml\ora\classgen\sample>java SampleMain -root
: : wddxPacket wddx_0090.dtd
: : Exception in thread "main" java.lang.IllegalAccessError: try
to
: : access class oracle/xml/parser/XMLNode from class
: : oracle/xml/classgen/ClassGenerator
: : at oracle.xml.classgen.ClassGenerator.generate
(Compiled
: : Code)
: : at SampleMain.main(SampleMain.java:65)
: : Any idea on what the problem is (same error with sample dtd)
: : Rob
: : Oracle XML Team wrote:
: : : The Oracle XMCL Class Generator for Java is now available
as
: : an
: : : initial beta release on the Oracle Technology Network at
: : : http://technet.oracle.com. Select 'xml' from the
Technology
: : menu.
: : : The XML Class Generator will generate a set of Java source
: : files
: : : based on an input DTD. The generated Java source files can
: : then
: : : be used to construct, optionally validate, and print a XML
: : : document that is compliant to the DTD specified. This is
an
: : early
: : : beta release and has the following features:
: : : * Creates Java Classes from DTDs to enable the
programmatic
: : : construction of XML documents.
: : : * Supports validation mode to assist debugging.
: : : * Works with the Oracle XML Parser in Java.
: : : * Creates documents conforming to the W3C XML 1.0
: : : Recommendation.
: : : * Supports creating documents in the following
encodings:
: : : UTF-8
: : : UTF-16
: : : ISO-10646-UCS-2
: : : ISO-10646-UCS-4
: : : US-ASCII
: : : EBCDIC-CP-US
: : : ISO-8859-1
: : : Shift_SJIS
: : : Oracle XML Team
: : : http://technet.oracle.com
: : : Oracle Technology Network
: Oracle Technology Network
null

How to trigger web service automatically when xml file generated at static

Hi Experts,
I have developed web service to read content from XML file.
I need to setup like whenever new xml file generated on static location (eg:E:\xml_files) generated web service should trigger automatically.
My requirement:
1) XML FIle content: have 3 tags with nultiple records.
2) Configured Weblogic Apploication server on JDev 11g
3) Developed Java code to read XML content and store it in Oracle Database.
4) created web service and called java class.
above 4 points, which I did already.
I appreciate if any one help me out, when ever new file created on static location, web service should triggered automatically and stored the data in to data oracle DB.
Thanks,
Phani

Hope you are looking for a SOA Suite/OSB solution for this.
If SOA Suite - You can configure a JCA File Read adapter to read off the XML file and then use a mediator/composite to invoke your WS.
If OSB - You can configure a File read transport or a JCA Adapter to read off the XML file and then use a route node/service callout to invoke your WS.

XML Schema Generated By XMLSpy fails validation in JDev 10.1.3.0.4

Hi gurus,
I am trying to view an XML schema generated by XMLSpy in JDev 10.1.3.0.4 but got this error:
Error(6,74): <Line 6, Column 74>: XML-24523: (Error) Invalid value 'simpletypes\AmendmentReasonChargeType.xsd' for attribute: 'schemaLocation'
Now in the XML schema, there is this line that causes the above error:
<xs:include schemaLocation="simpletypes\AmendmentReasonChargeType.xsd"/>
The same XML schema can be opened in Visual Studio 2003 OK. Could anyone help me out here? Thank you!
Ben

There is a tool tip that displays over the line that causes the error and this is what it says,
value of attribute schemaLocation not of anyURI type. The value must be of the following type:
Type Name: anyURI Primitive Type: anyURI
What does it mean?
Thanks
Ben

Error in XML process generated

Hi,
please, I need your help. I have an XML develped in APEX 4.1.1. but I have a problem, because the "SRI_COMPRAS" table has 38 columns with 950 rows, and the xml is generated only when considering the first 14 columns of this table with all existing records. But I need generate this XML with all the columns of "SRI_COMPRAS".
The process is:
declare
begin
select xmlElement(
"iva",
xmlElement("numeroRuc",J.RUC),
xmlElement("mes", J.MES),
xmlElement(
"compras", (
select xmlAgg(
xmlElement(
"detalleCompra",
xmlElement("codSustento", K.COD_SUSTENTO),
xmlElement("tpldProv", K.TPLD_PROV ),
xmlElement("idProv", K.ID_PROV ),
xmlElement("tipoComprobante", K.TIPO_COMPROBANTE),
xmlElement("fechaRegistro",to_char(K.FECHA_REGISTRO, 'DD/MM/YYYY') ),
xmlElement("establecimiento", K.ESTABLECIMIENTO ),
xmlElement("puntoEmision", K.PUNTO_EMISION ),
xmlElement("secuencial", K.SECUENCIAL),
xmlElement("fechaEmision", to_char(K.FECHA_EMISION, 'DD/MM/YYYY') ),
xmlElement("autorizacion", K.AUTORIZACION ),
xmlElement("baseNoGraIva", K.BASE_NO_GRA_IVA ),
xmlElement("baseImponible", K.BASE_IMPONIBLE ),
xmlElement("baseImpGrav", K.BASE_IMP_GRAV ),
xmlElement("montoIce", K.MONTO_ICE ),
xmlElement("montoIva", K.MONTO_IVA ),
xmlElement("valorRetBienes", K.VALOR_RET_BIENES),
xmlElement("valorRetServicios",K.VALOR_RET_SERVICIOS),
xmlElement("valorRetServ100",K.VALOR_RET_SERV_100),
xmlElement("estabRetencion1", K.ESTAB_RETENCION_1),
xmlElement("ptoEmiRetencion1", K.PTO_EMI_RETENCION_1),
xmlElement("secRetencion1", K.SEC_RETENCION_1),
xmlElement("autRetencion1", K.AUT_RETENCION_1),
xmlElement("fechaEmiRet1", to_char(K.FECHA_EMI_RET_1,'DD/MM/YYYY')),
xmlElement("docModificado", K.DOC_MODIFICADO),
xmlElement("estabModificado", K.ESTAB_MODIFICADO),
xmlElement("ptoEmiModificado", K.PTO_EMI_MODIFICADO),
xmlElement("secModificado", K.SEC_MODIFICADO),
xmlElement("autModificado", K.AUT_MODIFICADO)
xmlElement(
"air", (
select xmlAgg (
xmlElement (
"detalleAir",
xmlForest (
P.COD_RET_AIR as "codRetAir",
from ANEXO_COMPRAS P
from SRI_COMPRAS K
) )).getClobVal()
into l_clob_XML
from ...
LOOP
buffer := DBMS_LOB.SUBSTR(l_clob_XML, text_1, text_2);
EXIT WHEN buffer IS NULL;
sys.htp.p(buffer);
text_1 := text_1 + text_2;
END LOOP;
end;
The error generate is: "error on line 2 at column 1: expect '>'"
Edited by: JohannaCevallos07 on Sep 28, 2012 6:37 AM

Hi,
Actually the problem occurs when the xml file is generated with all the columns of the tables. Not seeing any data in th xml file and includes that message of error.
When in the xml code I determined display all the information of the tables considering only specific columns (14 columns for example) the xml file is generated successfully with all the information contained in the table only for those columns. but I need this xml file is generated with all the information for the tables columns describes in the first post publicated. : (
Do you have any idea of the cause for this error? Can you help me, please?

Idocs are not equal to XML message generated

hi ,
i am facing problem when i using XI.its not generated idocs equal to XML message generated.

idocs equal to XML message
Do u mean that in ur file to idoc scenario, the no of messages sent by file is not equal to no of idocs generated? If yes, then first check in tcode sxmb_moni at XI for presence of message and check for error there
Please describe ur scenario a bit.
Regards,
Prateek

XML Data Generator BUG???

Hi,
I've been experimenting with the XML Data Generator (a Data Web Bean) in Jdev 3.2.2, and no matter what attributes I choose to display from my View Object, the bean displays ALL attributes.
Is this a BUG or Operator Error on my part?
Lachlan
[email protected]

oops, I spoke too broadly -- the Flex example does work --
but it fails if you have any qualifiers in the tag, so for example,
this works:
<name>
<first>{firstName.text}</first>
<last>{lastName.text}</last>
</name>
and this works:
<name first="{firstName.text}" last ="{lastName.text}"
/>
but this does NOT work:
<name>
<first type="person">{firstName.text}</first>
<last type="person">{lastName.text}</last>
</name>
so it IS probably a bug in the parser that handles the XML
tags, upon seeing one qualifying field within the tag, it assumes
that all of the data will be presented in the same way, and there
will be no bound data between the tag.

Problems with XML Instance Generator

Hi.
I still have problems with the XML instance Generator. I had the problem other people have commented here before:
parsing a grammar: newspaper.dtd
generating document #1
Exception in thread "main" java.lang.NoClassDefFoundError: org/apache/xml/serialize/XMLSerializer
at com.sun.msv.generator.Driver.run(Unknown Source)
at com.sun.msv.generator.Driver.main(Unknown Source)
I read somewhere that xercesImpl.jar was necessary. I have downoladed a version of it of about 3 Mb size, and now the message I receive is the following:
parsing a grammar: newspaper.dtd
generating document #1
Exception in thread "main" java.lang.NoClassDefFoundError: org/w3c/dom/ranges/DocumentRange
at java.lang.ClassLoader.defineClass0(Native Method)
at java.lang.ClassLoader.defineClass(ClassLoader.java:502)
at java.security.SecureClassLoader.defineClass(SecureClassLoader.java:123)
at java.net.URLClassLoader.defineClass(URLClassLoader.java:250)
at java.net.URLClassLoader.access$100(URLClassLoader.java:54)
at java.net.URLClassLoader$1.run(URLClassLoader.java:193)
at java.security.AccessController.doPrivileged(Native Method)
at java.net.URLClassLoader.findClass(URLClassLoader.java:186)
at java.lang.ClassLoader.loadClass(ClassLoader.java:299)
at sun.misc.Launcher$AppClassLoader.loadClass(Launcher.java:272)
at java.lang.ClassLoader.loadClass(ClassLoader.java:255)
at java.lang.ClassLoader.loadClassInternal(ClassLoader.java:315)
at com.sun.org.apache.xerces.internal.jaxp.DocumentBuilderImpl.newDocume
nt(DocumentBuilderImpl.java:206)
at com.sun.msv.generator.Driver.run(Unknown Source)
at com.sun.msv.generator.Driver.main(Unknown Source)
after executing the command: java -jar xmlgen.jar -dtd newspaper.dtd
All .jar files coming with the xmlgen.zip are in the same directory where I type the command. Does anybody know what am I doing wrong?
Thanks to all.

Hi,
I am also getting the same problem.
Thanks
-Manoj

IMPORTANT: XML Class Generator Feature Test

To Those of you who are using our XML Class Generator, we would
really like some feedback regarding your tests of the following
features:
1) validation -- turn it on/off with DTDs
2) character set encoding -- ask them to try different ones
3) DTDs -- included in the XML file and also have it as an
external DTD;
4) XML 1.0 conformance -- see if the XML documents created
conform to the spec;
5) print methods -- try them out
We would like to go production in the near future and need this
feedback.
Thanks,
Oracle XML Team
http://technet.oracle.com
Oracle Technology Network
null

Posted reply to:
Re: xml class generator NullPointerException when element type is base64Binary
-Blaise

XML Form Generator

Dear Sir,
I am in the midlle of developping a new Add-On where I have to create my own form. I having a bad time designing the form specially that iahve to deal with the xml file directly.
Can you please advise me if there is any xml fiorm generator where design my forma and then I generate the correspending xml file.
Best Regards

Hi
Some tools you can find on this [site|http://www.codegeneration.net/]. Certain, you need to create your own templates.
Example: one part of this [form|http://img58.imageshack.us/my.php?image=folder01yz0.jpg] was generated with [this product|http://translate.google.it/translate?u=http%3A%2F%2Fnuke.fabiofaieta.net%2F&hl=it&ie=UTF-8&sl=it&tl=en].
Or you can use Screen Painter.
Regards
Sierdna S.

XML Publisher generates PDF but concurrent program still completes in error

Hello,
I have a concurent program that is used everyday. It generates PDF output with an average of 500 pages. It completes normal majority of the times, but completes in error sporadicallly. Interestingly, when it completes in error, it still generates the PDF output successfully.
Question is why does it complete in error when all is good?
Please note that we just went live on R12 from 11i beginning of this year. This issue never occurred in 11i. Please advise what can be done to fix this issue.
Below is a log from one such submission. The log was rather long, so I'm only posting chunks from the beginning and end of the log, stripping the middle portion:
Receivables: Version : 12.0.0
Copyright (c) 1979, 1999, Oracle Corporation. All rights reserved.
XXBREG_RAXINV_NEW_XMLP module: Breg Invoice Print New Invoices - XMLP
Current system time is 22-JAN-2013 06:46:58
+-----------------------------
| Starting concurrent program execution...
+-----------------------------
Arguments
p_order_by='TRX_NUMBER'
p_cust_trx_class='INV'
p_cust_trx_type_id='1'
p_open_invoice='Y'
p_check_for_taxyn='N'
p_choice='NEW'
p_header_pages='1'
p_debug_flag='N'
p_message_level='10'
Forcing NLS_NUMERIC_CHARACTERS to: '.,' for XDO processing
APPLLCSP Environment Variable set to :
Current NLS_LANG and NLS_NUMERIC_CHARACTERS Environment Variables are :
American_America.AL32UTF8
Enter Password:
MSG-00100: DEBUG: AfterPForm_Trigger +
MSG-00100: DEBUG: Multi Org established.
MSG-00100: DEBUG: AfterParam_Procs.Get_Country_Details
MSG-00100: DEBUG: AfterParam_Procs.Switch_On_Debug
MSG-00100: DEBUG: AfterParam_Procs.Get_Trx_Number_Low
MSG-00100: DEBUG: AfterParam_Procs.Get_Trx_Number_High
MSG-00100: DEBUG: AfterParam_Procs.Get_Tax_Option
MSG-00100: DEBUG: AfterPForm_Trigger -
MSG-00100: DEBUG: BeforeReport_Trigger +
MSG-00100: DEBUG: BeforeReport_Procs.Populate_Printing_Option
MSG-00100: DEBUG: BeforeReport_Procs.Populate_Tax_Printing_Option
MSG-00100: DEBUG: BeforeReport_Trigger.Get_Message_Details
MSG-00100: DEBUG: BeforeReport_Trigger.Get_Org_Profile.
MSG-00100: DEBUG: Organization Id: 106
MSG-00100: DEBUG: BeforeReport_Trigger.Build_Where_Clause
MSG-00100: DEBUG: P_Choice: NEW
MSG-00500: DEBUG: About to build WHERE clause.
MSG-00500: DEBUG: WHERE clause built.
MSG-00555: :p_choice:NEW
MSG-00100: DEBUG: Choice is other than ADJ, setting ORDER BY.
MSG-00555: :p_sel_trx_number:a.trx_number
MSG-00555: :p_sel_trx_date:a.trx_date
MSG-00555: :p_sel_trx_id:a.customer_trx_id
MSG-00555: :p_sel_trx_type:types.type
MSG-00555: :p_br_where_clause:
MSG-00500: DEBUG: Table 1: AR_ADJUSTMENTS COM_ADJ,
AR_PAYMENT_SCHEDULES P,
RA_CUST_TRX_LINE_GL_DIST REC,
RA_CUSTOMER_TRX A,
HZ_CUST_ACCOUNTS B,
RA_TERMS T,
RA_TERMS_LINES TL,
RA_CUST_TRX_TYPES TYPES,
AR_LOOKUPS L_TYPES,
HZ_PARTIES      PARTY,
HZ_CUST_ACCT_SITES A_BILL,
HZ_PARTY_SITES PARTY_SITE,
HZ_LOCATIONS LOC,
HZ_CUST_SITE_USES U_BILL
MSG-00500: DEBUG: Table 2: RA_TERMS_LINES TL,
RA_CUST_TRX_TYPES TYPES,
AR_LOOKUPS L_TYPES,
     HZ_CUST_ACCOUNTS B,
HZ_PARTIES      PARTY,
HZ_CUST_SITE_USES U_BILL,
HZ_CUST_ACCT_SITES A_BILL,
HZ_PARTY_SITES PARTY_SITE,
HZ_LOCATIONS LOC,
AR_ADJUSTMENTS COM_ADJ,
RA_CUSTOMER_TRX A,
AR_PAYMENT_SCHEDULES P,
RA_TERMS T
MSG-00500: DEBUG: Where 1: A.BILL_TO_CUSTOMER_ID = B.CUST_ACCOUNT_ID
AND REC.CUSTOMER_TRX_ID = A.CUSTOMER_TRX_ID
AND REC.LATEST_REC_FLAG = 'Y'
AND REC.ACCOUNT_CLASS = 'REC'
AND P.PAYMENT_SCHEDULE_ID + DECODE(P.CLASS,
'INV', 0,
= COM_ADJ.PAYMENT_SCHEDULE_ID(+)
AND COM_ADJ.SUBSEQUENT_TRX_ID IS NULL
AND 'C' = COM_ADJ.ADJUSTMENT_TYPE(+)
AND A.COMPLETE_FLAG = 'Y'
AND A.CUST_TRX_TYPE_ID = TYPES.CUST_TRX_TYPE_ID
AND L_TYPES.LOOKUP_TYPE = 'INV/CM/ADJ'
AND A.PRINTING_OPTION IN ('PRI', 'REP')
AND L_TYPES.LOOKUP_CODE =
DECODE( TYPES.TYPE,'DEP','INV', TYPES.TYPE)
AND NVL(P.TERMS_SEQUENCE_NUMBER,nvl(TL.SEQUENCE_NUM,0))=nvl(TL.SEQUENCE_NUM,nvl(p.terms_sequence_number,0))
AND DECODE(P.PAYMENT_SCHEDULE_ID,'',0, NVL(T.PRINTING_LEAD_DAYS,0))=0
AND A.BILL_TO_SITE_USE_ID = U_BILL.SITE_USE_ID
AND U_BILL.CUST_ACCT_SITE_ID = A_BILL.CUST_ACCT_SITE_ID
AND A_BILL.party_site_id = party_site.party_site_id
AND B.PARTY_ID = PARTY.PARTY_ID
AND loc.location_id = party_site.location_id
AND NVL(LOC.LANGUAGE,'US') = 'US'
AND NVL(P.AMOUNT_DUE_REMAINING,0) <> 0
AND A.CUST_TRX_TYPE_ID = 1
AND TYPES.TYPE = 'INV'
AND A.TERM_ID = TL.TERM_ID(+)
AND A.TERM_ID = T.TERM_ID(+)
AND A.CUSTOMER_TRX_ID = P.CUSTOMER_TRX_ID(+)
AND A.PRINTING_PENDING = 'Y'
AND NVL(TL.SEQUENCE_NUM, 1) > NVL(A.LAST_PRINTED_SEQUENCE_NUM,0)
MSG-00500: DEBUG: Where 2: A.BILL_TO_CUSTOMER_ID = B.CUST_ACCOUNT_ID
AND P.PAYMENT_SCHEDULE_ID + DECODE(P.CLASS,
'INV', 0,
= COM_ADJ.PAYMENT_SCHEDULE_ID(+)
AND COM_ADJ.SUBSEQUENT_TRX_ID IS NULL
AND 'C' = COM_ADJ.ADJUSTMENT_TYPE(+)
AND A.COMPLETE_FLAG = 'Y'
AND A.CUSTOMER_TRX_ID = P.CUSTOMER_TRX_ID
AND A.CUST_TRX_TYPE_ID = TYPES.CUST_TRX_TYPE_ID
AND L_TYPES.LOOKUP_TYPE = 'INV/CM/ADJ'
AND A.PRINTING_OPTION IN ('PRI', 'REP')
AND L_TYPES.LOOKUP_CODE =
DECODE( TYPES.TYPE,'DEP','INV', TYPES.TYPE)
AND NVL(T.PRINTING_LEAD_DAYS,0) > 0
AND A.BILL_TO_SITE_USE_ID = U_BILL.SITE_USE_ID
AND U_BILL.CUST_ACCT_SITE_ID = A_BILL.CUST_ACCT_SITE_ID
AND A_BILL.PARTY_SITE_ID = PARTY_SITE.PARTY_SITE_ID
AND B.PARTY_ID = PARTY.PARTY_ID
AND LOC.LOCATION_ID = PARTY_SITE.LOCATION_ID
AND NVL(LOC.LANGUAGE,'US') = 'US'
AND NVL(P.TERMS_SEQUENCE_NUMBER,TL.SEQUENCE_NUM)=TL.SEQUENCE_NUM
AND NVL(P.AMOUNT_DUE_REMAINING,0) <> 0
AND A.CUST_TRX_TYPE_ID = 1
AND TYPES.TYPE = 'INV'
AND T.TERM_ID = P.TERM_ID
AND TL.TERM_ID(+) = T.TERM_ID
AND A.PRINTING_PENDING = 'Y'
AND P.TERMS_SEQUENCE_NUMBER > NVL(A.LAST_PRINTED_SEQUENCE_NUM,0)
MSG-00100: DEBUG: BeforeReport_Trigger -
MSG-05000: DEBUG: Trx No... 1010441
MSG-00100: DEBUG: Get_Country_Description.
MSG-00010: 06:47 1 Transaction: 1010441
MSG-00001: Line type : Line
MSG-00100: DEBUG: Get_Country_Description.
MSG-00100: DEBUG: Get_Country_Description.
MSG-05000: DEBUG: Remit To Address....
MSG-05000: DEBUG: Address Style:
MSG-05000: DEBUG: Address 1: PO Box 849991
MSG-05000: DEBUG: Address 2:
MSG-05000: DEBUG: Address 3:
MSG-05000: DEBUG: Address 4:
MSG-05000: DEBUG: City: Dallas
MSG-05000: DEBUG: County:
MSG-05000: DEBUG: State: TX
MSG-05000: DEBUG: Province:
MSG-05000: DEBUG: Postal Code: 75284
MSG-05000: DEBUG: Territory:
MSG-05000: DEBUG: Country_Code: US
MSG-05000: DEBUG: Customer Name:
MSG-05000: DEBUG: Bill To:
MSG-05000: DEBUG: First Name:
MSG-05000: DEBUG: Last Name:
MSG-05000: DEBUG: Mail Stop:
MSG-05000: DEBUG: Country Code: US
MSG-05000: DEBUG: Country Desc:
MSG-05000: DEBUG: Print Home Flag: N
MSG-05000: DEBUG: Width: 40
MSG-05000: DEBUG: Height Min: 6
MSG-05000: DEBUG: Height Max: 6
MSG-05000: DEBUG: Remit To Formatted... PO Box 849991
Dallas TX 75284
MSG-05000: DEBUG: Trx No... 1010442
MSG-00100: DEBUG: Get_Country_Description.
MSG-00010: 06:47 2 Transaction: 1010442
MSG-05000: DEBUG: Bill To Address....
MSG-05000: DEBUG: Address Style:
MSG-05000: DEBUG: Address 1: 6560 W ROGERS CIR
MSG-05000: DEBUG: Address 2: STE 19
MSG-05000: DEBUG: Address 3:
MSG-05000: DEBUG: Address 4:
MSG-05000: DEBUG: City: BOCA RATON
MSG-05000: DEBUG: County:
MSG-05000: DEBUG: State: FL
MSG-05000: DEBUG: Province:
MSG-05000: DEBUG: Postal Code: 33487-2746
MSG-05000: DEBUG: Territory:
MSG-05000: DEBUG: Country_Code: US
MSG-05000: DEBUG: Customer Name: THE BRACE SHOP
MSG-05000: DEBUG: Bill To:
MSG-05000: DEBUG: First Name: LORI
MSG-05000: DEBUG: Last Name: ESCALANTE
MSG-05000: DEBUG: Mail Stop:
MSG-05000: DEBUG: Country Code: US
MSG-05000: DEBUG: Country Desc:
MSG-05000: DEBUG: Print Home Flag: N
MSG-05000: DEBUG: Width: 40
MSG-05000: DEBUG: Height Min: 8
MSG-05000: DEBUG: Height Max: 8
MSG-05000: DEBUG: Bill To Formatted... LORI ESCALANTE
THE BRACE SHOP
6560 W ROGERS CIR
STE 19
BOCA RATON FL 33487-2746
MSG-05000: DEBUG: Ship To Address....
MSG-05000: DEBUG: Address Style:
MSG-05000: DEBUG: Address 1: 7014 E Appleton Circle
MSG-05000: DEBUG: Address 2:
MSG-05000: DEBUG: Address 3:
MSG-05000: DEBUG: Address 4:
MSG-05000: DEBUG: City: CENTENNIAL
MSG-05000: DEBUG: County:
MSG-05000: DEBUG: State: CO
MSG-05000: DEBUG: Province:
MSG-05000: DEBUG: Postal Code: 80112-1155
MSG-05000: DEBUG: Territory:
MSG-05000: DEBUG: Country_Code: US
MSG-05000: DEBUG: Customer Name: Kenneth Grimm
MSG-05000: DEBUG: Bill To:
MSG-05000: DEBUG: First Name:
MSG-05000: DEBUG: Last Name:
MSG-05000: DEBUG: Mail Stop:
MSG-05000: DEBUG: Country Code: US
MSG-05000: DEBUG: Country Desc:
MSG-05000: DEBUG: Print Home Flag: N
MSG-05000: DEBUG: Width: 40
MSG-05000: DEBUG: Height Min: 8
MSG-05000: DEBUG: Height Max: 8
MSG-05000: DEBUG: Ship To Formatted... Kenneth Grimm
7014 E Appleton Circle
CENTENNIAL CO 80112-1155
MSG-00001: In Line frame trigger
MSG-00001: Line Type: INV Source:OM Invoices
MSG-00001: In Line frame trigger
MSG-00001: Line Type: INV Source:OM Invoices
MSG-00001: In Line frame trigger
MSG-00001: Line Type: INV Source:OM Invoices
MSG-00001: In Line frame trigger
MSG-00001: Line Type: INV Source:OM Invoices
MSG-00001: In Line frame trigger
MSG-00001: Line Type: INV Source:OM Invoices
MSG-00001: In Line frame trigger
MSG-00001: Line Type: INV Source:OM Invoices
MSG-00001: In Line frame trigger
MSG-00001: Line Type: INV Source:OM Invoices
MSG-00001: In Line frame trigger
MSG-00001: Line Type: INV Source:OM Invoices
MSG-00001: In Line frame trigger
MSG-00001: Line Type: INV Source:OM Invoices
MSG-00001: In Line frame trigger
MSG-00001: Line Type: INV Source:OM Invoices
MSG-00001: In Line frame trigger
MSG-00001: Line Type: INV Source:OM Invoices
MSG-00001: In Line frame trigger
MSG-00001: Line Type: INV Source:OM Invoices
MSG-00001: In Line frame trigger
MSG-00001: Line Type: INV Source:OM Invoices
MSG-00001: In Line frame trigger
MSG-00001: Line Type: INV Source:OM Invoices
MSG-00001: In Line frame trigger
MSG-00001: Line Type: INV Source:OM Invoices
MSG-00001: In Line frame trigger
MSG-00001: Line Type: INV Source:OM Invoices
MSG-00001: In Line frame trigger
MSG-00001: Line Type: INV Source:OM Invoices
MSG-00001: In Line frame trigger
MSG-00001: Line Type: INV Source:OM Invoices
MSG-00001: In Line frame trigger
MSG-00001: Line Type: INV Source:OM Invoices
MSG-00001: In Line frame trigger
MSG-00001: Line Type: INV Source:OM Invoices
MSG-00001: In Line frame trigger
MSG-00001: Line Type: INV Source:OM Invoices
MSG-00001: In Line frame trigger
MSG-00001: Line Type: INV Source:OM Invoices
MSG-00001: In Line frame trigger
MSG-00001: Line Type: INV Source:OM Invoices
MSG-00001: In Line frame trigger
MSG-00001: Line Type: INV Source:OM Invoices
MSG-00001: In Line frame trigger
MSG-00001: Line Type: INV Source:OM Invoices
MSG-00001: In Line frame trigger
MSG-00001: Line Type: INV Source:OM Invoices
MSG-00001: In Line frame trigger
MSG-00001: Line Type: INV Source:OM Invoices
MSG-00001: In Line frame trigger
MSG-00001: Line Type: INV Source:OM Invoices
MSG-00001: In Line frame trigger
MSG-00001: Line Type: INV Source:OM Invoices
MSG-00001: In Line frame trigger
MSG-00001: Line Type: INV Source:OM Invoices
MSG-00001: In Line frame trigger
MSG-00001: Line Type: INV Source:OM Invoices
MSG-00001: In Line frame trigger
MSG-00001: Line Type: INV Source:OM Invoices
MSG-00001: In Line frame trigger
MSG-00001: Line Type: INV Source:OM Invoices
MSG-00001: In Line frame trigger
MSG-00001: Line Type: INV Source:OM Invoices
MSG-00001: In Line frame trigger
MSG-00001: Line Type: INV Source:OM Invoices
MSG-00001: In Line frame trigger
MSG-00001: Line Type: INV Source:OM Invoices
MSG-00001: Line type : Line
MSG-00001: Line type : Line
MSG-00001: Line type : Line
MSG-00001: Line type : Line
MSG-00001: Line type : Line
MSG-00001: Line type : Line
MSG-00001: Line type : Line
MSG-00001: Line type : Line
MSG-00001: Line type : Line
MSG-00001: Line type : Line
MSG-00001: Line type : Line
MSG-00001: Line type : Line
MSG-00001: Line type : Line
MSG-00001: Line type : Line
MSG-00001: Line type : Line
MSG-00001: Line type : Line
MSG-00001: Line type : Line
MSG-00001: Line type : Line
MSG-00001: Line type : Line
MSG-00001: Line type : Line
MSG-00001: Line type : Line
MSG-00001: Line type : Line
MSG-00001: Line type : Line
MSG-00100: DEBUG: Get_Country_Description.
MSG-00100: Oracle Error in call to arp_adds.location_description -6503
MSG-05000: DEBUG: Remit To Address....
MSG-05000: DEBUG: Address Style:
MSG-05000: DEBUG: Address 1: PO Box 849991
MSG-05000: DEBUG: Address 2:
MSG-05000: DEBUG: Address 3:
MSG-05000: DEBUG: Address 4:
MSG-05000: DEBUG: City: Dallas
MSG-05000: DEBUG: County:
MSG-05000: DEBUG: State: TX
MSG-05000: DEBUG: Province:
MSG-05000: DEBUG: Postal Code: 75284
MSG-05000: DEBUG: Territory:
MSG-05000: DEBUG: Country_Code: US
MSG-05000: DEBUG: Customer Name:
MSG-05000: DEBUG: Bill To:
MSG-05000: DEBUG: First Name:
MSG-05000: DEBUG: Last Name:
MSG-05000: DEBUG: Mail Stop:
MSG-05000: DEBUG: Country Code: US
MSG-05000: DEBUG: Country Desc:
MSG-05000: DEBUG: Print Home Flag: N
MSG-05000: DEBUG: Width: 40
MSG-05000: DEBUG: Height Min: 6
MSG-05000: DEBUG: Height Max: 6
MSG-05000: DEBUG: Remit To Formatted... PO Box 849991
Dallas TX 75284
MSG-05000: DEBUG: Trx No... 1010930
MSG-00100: DEBUG: Get_Country_Description.
MSG-00010: 06:47 506 Transaction: 1010930
MSG-05000: DEBUG: Bill To Address....
MSG-05000: DEBUG: Address Style:
MSG-05000: DEBUG: Address 1: 4412 MANILLA ROAD SE
MSG-05000: DEBUG: Address 2: UNIT 7
MSG-05000: DEBUG: Address 3:
MSG-05000: DEBUG: Address 4:
MSG-05000: DEBUG: City: CALGARY
MSG-05000: DEBUG: County:
MSG-05000: DEBUG: State:
MSG-05000: DEBUG: Province: ALBERTA
MSG-05000: DEBUG: Postal Code: T2G 4B7
MSG-05000: DEBUG: Territory:
MSG-05000: DEBUG: Country_Code: CA
MSG-05000: DEBUG: Customer Name: MEDLINES INC DBA PRO CARE MEDICAL LTD
MSG-05000: DEBUG: Bill To:
MSG-05000: DEBUG: First Name:
MSG-05000: DEBUG: Last Name:
MSG-05000: DEBUG: Mail Stop:
MSG-05000: DEBUG: Country Code: US
MSG-05000: DEBUG: Country Desc:
MSG-05000: DEBUG: Print Home Flag: N
MSG-05000: DEBUG: Width: 40
MSG-05000: DEBUG: Height Min: 8
MSG-05000: DEBUG: Height Max: 8
MSG-05000: DEBUG: Bill To Formatted... Attn: Accounts Payable
MEDLINES INC DBA PRO CARE MEDICAL LTD
4412 MANILLA ROAD SE
UNIT 7
CALGARY ALBERTA T2G 4B7
Canada
MSG-05000: DEBUG: Ship To Address....
MSG-05000: DEBUG: Address Style:
MSG-05000: DEBUG: Address 1: 4412 MANILLA ROAD SE Unit 7
MSG-05000: DEBUG: Address 2: PH:403 287 0993
MSG-05000: DEBUG: Address 3:
MSG-05000: DEBUG: Address 4:
MSG-05000: DEBUG: City: CALGARY
MSG-05000: DEBUG: County:
MSG-05000: DEBUG: State: ALBERTA
MSG-05000: DEBUG: Province: ALBERTA
MSG-05000: DEBUG: Postal Code: T2G 4B7
MSG-05000: DEBUG: Territory:
MSG-05000: DEBUG: Country_Code: CA
MSG-05000: DEBUG: Customer Name: MEDLINES INC DBA PRO CARE MEDICAL LTD
MSG-05000: DEBUG: Bill To:
MSG-05000: DEBUG: First Name:
MSG-05000: DEBUG: Last Name:
MSG-05000: DEBUG: Mail Stop:
MSG-05000: DEBUG: Country Code: US
MSG-05000: DEBUG: Country Desc:
MSG-05000: DEBUG: Print Home Flag: N
MSG-05000: DEBUG: Width: 40
MSG-05000: DEBUG: Height Min: 8
MSG-05000: DEBUG: Height Max: 8
MSG-05000: DEBUG: Ship To Formatted... MEDLINES INC DBA PRO CARE MEDICAL LTD
4412 MANILLA ROAD SE Unit 7
PH:403 287 0993
CALGARY ALBERTA ALBERTA T2G 4B7
Canada
MSG-00001: In Line frame trigger
MSG-00001: Line Type: INV Source:OM Invoices
MSG-00001: In Line frame trigger
MSG-00001: Line Type: INV Source:OM Invoices
MSG-00001: In Line frame trigger
MSG-00001: Line Type: INV Source:OM Invoices
MSG-00001: In Line frame trigger
MSG-00001: Line Type: INV Source:OM Invoices
MSG-00001: In Line frame trigger
MSG-00001: Line Type: INV Source:OM Invoices
MSG-00001: In Line frame trigger
MSG-00001: Line Type: INV Source:OM Invoices
MSG-00001: In Line frame trigger
MSG-00001: Line Type: INV Source:OM Invoices
MSG-00001: In Line frame trigger
MSG-00001: Line Type: INV Source:OM Invoices
MSG-00001: In Line frame trigger
MSG-00001: Line Type: INV Source:OM Invoices
MSG-00001: In Line frame trigger
MSG-00001: Line Type: INV Source:OM Invoices
MSG-00001: In Line frame trigger
MSG-00001: Line Type: INV Source:OM Invoices
MSG-00001: In Line frame trigger
MSG-00001: Line Type: INV Source:OM Invoices
MSG-00001: In Line frame trigger
MSG-00001: Line Type: INV Source:OM Invoices
MSG-00001: In Line frame trigger
MSG-00001: Line Type: INV Source:OM Invoices
MSG-00001: In Line frame trigger
MSG-00001: Line Type: INV Source:OM Invoices
MSG-00001: In Line frame trigger
MSG-00001: Line Type: INV Source:OM Invoices
MSG-00001: In Line frame trigger
MSG-00001: Line Type: INV Source:OM Invoices
MSG-00001: In Line frame trigger
MSG-00001: Line Type: INV Source:OM Invoices
MSG-00001: In Line frame trigger
MSG-00001: Line Type: INV Source:OM Invoices
MSG-00001: In Line frame trigger
MSG-00001: Line Type: INV Source:OM Invoices
MSG-00001: In Line frame trigger
MSG-00001: Line Type: INV Source:OM Invoices
MSG-00001: In Line frame trigger
MSG-00001: Line Type: INV Source:OM Invoices
MSG-00001: In Line frame trigger
MSG-00001: Line Type: INV Source:OM Invoices
MSG-00001: Line type : Line
MSG-00001: Line type : Line
MSG-00001: Line type : Line
MSG-00001: Line type : Line
MSG-00001: Line type : Line
MSG-00001: Line type : Line
MSG-00001: Line type : Line
MSG-00001: Line type : Line
MSG-00001: Line type : Line
MSG-00001: Line type : Line
MSG-00001: Line type : Line
MSG-00001: Line type : Line
MSG-00001: Line type : Line
MSG-00001: Line type : Line
MSG-00001: Line type : Line
MSG-00001: Line type : Line
MSG-00001: Line type : Line
MSG-00001: Line type : Line
MSG-00001: Line type : Line
MSG-00001: Line type : Line
MSG-00001: Line type : Line
MSG-00100: DEBUG: Get_Country_Description.
MSG-05000: DEBUG: Remit To Address....
MSG-05000: DEBUG: Address Style:
MSG-05000: DEBUG: Address 1: PO Box 849991
MSG-05000: DEBUG: Address 2:
MSG-05000: DEBUG: Address 3:
MSG-05000: DEBUG: Address 4:
MSG-05000: DEBUG: City: Dallas
MSG-05000: DEBUG: County:
MSG-05000: DEBUG: State: TX
MSG-05000: DEBUG: Province:
MSG-05000: DEBUG: Postal Code: 75284
MSG-05000: DEBUG: Territory:
MSG-05000: DEBUG: Country_Code: US
MSG-05000: DEBUG: Customer Name:
MSG-05000: DEBUG: Bill To:
MSG-05000: DEBUG: First Name:
MSG-05000: DEBUG: Last Name:
MSG-05000: DEBUG: Mail Stop:
MSG-05000: DEBUG: Country Code: US
MSG-05000: DEBUG: Country Desc:
MSG-05000: DEBUG: Print Home Flag: N
MSG-05000: DEBUG: Width: 40
MSG-05000: DEBUG: Height Min: 6
MSG-05000: DEBUG: Height Max: 6
MSG-05000: DEBUG: Remit To Formatted... PO Box 849991
Dallas TX 75284
MSG-05000: DEBUG: Bill To Address....
MSG-05000: DEBUG: Address Style:
MSG-05000: DEBUG: Address 1: 8206 LEESBURG PIKE
MSG-05000: DEBUG: Address 2: STE 409
MSG-05000: DEBUG: Address 3:
MSG-05000: DEBUG: Address 4:
MSG-05000: DEBUG: City: VIENNA
MSG-05000: DEBUG: County:
MSG-05000: DEBUG: State: VA
MSG-05000: DEBUG: Province:
MSG-05000: DEBUG: Postal Code: 22182
MSG-05000: DEBUG: Territory:
MSG-05000: DEBUG: Country_Code: US
MSG-05000: DEBUG: Customer Name: NOVA ORTHOPAEDIC AND SPORTS MEDICINE
MSG-05000: DEBUG: Bill To:
MSG-05000: DEBUG: First Name: TAYLOR
MSG-05000: DEBUG: Last Name: CRIGLER
MSG-05000: DEBUG: Mail Stop:
MSG-05000: DEBUG: Country Code: US
MSG-05000: DEBUG: Country Desc:
MSG-05000: DEBUG: Print Home Flag: N
MSG-05000: DEBUG: Width: 40
MSG-05000: DEBUG: Height Min: 8
MSG-05000: DEBUG: Height Max: 8
MSG-05000: DEBUG: Bill To Formatted... TAYLOR CRIGLER
NOVA ORTHOPAEDIC AND SPORTS MEDICINE
8206 LEESBURG PIKE
STE 409
VIENNA VA 22182
MSG-05000: DEBUG: Ship To Address....
MSG-05000: DEBUG: Address Style:
MSG-05000: DEBUG: Address 1: 8206 LEESBURG PIKE
MSG-05000: DEBUG: Address 2: STE 409
MSG-05000: DEBUG: Address 3:
MSG-05000: DEBUG: Address 4:
MSG-05000: DEBUG: City: VIENNA
MSG-05000: DEBUG: County:
MSG-05000: DEBUG: State: VA
MSG-05000: DEBUG: Province:
MSG-05000: DEBUG: Postal Code: 22182
MSG-05000: DEBUG: Territory:
MSG-05000: DEBUG: Country_Code: US
MSG-05000: DEBUG: Customer Name: NOVA ORTHOPAEDIC AND SPORTS MEDICINE
MSG-05000: DEBUG: Bill To:
MSG-05000: DEBUG: First Name: TAYLOR
MSG-05000: DEBUG: Last Name: CRIGLER
MSG-05000: DEBUG: Mail Stop:
MSG-05000: DEBUG: Country Code: US
MSG-05000: DEBUG: Country Desc:
MSG-05000: DEBUG: Print Home Flag: N
MSG-05000: DEBUG: Width: 40
MSG-05000: DEBUG: Height Min: 8
MSG-05000: DEBUG: Height Max: 8
MSG-05000: DEBUG: Ship To Formatted... TAYLOR CRIGLER
NOVA ORTHOPAEDIC AND SPORTS MEDICINE
8206 LEESBURG PIKE
STE 409
VIENNA VA 22182
MSG-00001: In Line frame trigger
MSG-00001: Line Type: INV Source:OM Invoices
MSG-00001: In Line frame trigger
MSG-00001: Line Type: INV Source:OM Invoices
MSG-00001: In Line frame trigger
MSG-00001: Line Type: INV Source:OM Invoices
MSG-00001: In Line frame trigger
MSG-00001: Line Type: INV Source:OM Invoices
MSG-00001: In Line frame trigger
MSG-00001: Line Type: INV Source:OM Invoices
MSG-00001: In Line frame trigger
MSG-00001: Line Type: INV Source:OM Invoices
MSG-00001: In Line frame trigger
MSG-00001: Line Type: INV Source:OM Invoices
MSG-00001: In Line frame trigger
MSG-00001: Line Type: INV Source:OM Invoices
MSG-00001: In Line frame trigger
MSG-00001: Line Type: INV Source:OM Invoices
MSG-00001: In Line frame trigger
MSG-00001: Line Type: INV Source:OM Invoices
MSG-00001: In Line frame trigger
MSG-00001: Line Type: INV Source:OM Invoices
MSG-00001: In Line frame trigger
MSG-00001: Line Type: INV Source:OM Invoices
MSG-00001: In Line frame trigger
MSG-00001: Line Type: INV Source:OM Invoices
MSG-00001: In Line frame trigger
MSG-00001: Line Type: INV Source:OM Invoices
MSG-00001: In Line frame trigger
MSG-00001: Line Type: INV Source:OM Invoices
MSG-00001: In Line frame trigger
MSG-00001: Line Type: INV Source:OM Invoices
MSG-00001: In Line frame trigger
MSG-00001: Line Type: INV Source:OM Invoices
MSG-00001: In Line frame trigger
MSG-00001: Line Type: INV Source:OM Invoices
MSG-00001: In Line frame trigger
MSG-00001: Line Type: INV Source:OM Invoices
MSG-00001: In Line frame trigger
MSG-00001: Line Type: INV Source:OM Invoices
MSG-00001: In Line frame trigger
MSG-00001: Line Type: INV Source:OM Invoices
REP-0069: Internal error
REP-57054: In-process job terminated:Finished successfully
MSG-00100: DEBUG: BeforeReport_Trigger +
MSG-00100: DEBUG: BeforeReport_Procs.Populate_Printing_Option
MSG-00100: DEBUG: BeforeReport_Procs.Populate_Tax_Printing_Option
MSG-00100: DEBUG: BeforeReport_Trigger.Get_Message_Details
MSG-00100: DEBUG: BeforeReport_Trigger.Get_Org_Profile.
MSG-00100: DEBUG: Organization Id: 106
MSG-00100: DEBUG: BeforeReport_Trigger.Build_Where_Clause
MSG-00100: DEBUG: P_Choice: NEW
MSG
Report Builder: Release 10.1.2.3.0 - Production on Tue Jan 22 06:47:00 2013
Copyright (c) 1982, 2005, Oracle. All rights reserved.
Start of log messages from FND_FILE
End of log messages from FND_FILE
Program exited with status 1
Concurrent Manager encountered an error while running Oracle*Report for your concurrent request 945196.
Review your concurrent request log and/or report output file for more detailed information.
Successfully resubmitted concurrent program XXBREG_RAXINV_NEW_XMLP with request ID 953242 to start at 23-JAN-2013 05:15:00 (ROUTINE=AFPSRS)
Executing request completion options...
Output file size:
13010844
------------- 1) PUBLISH -------------
Beginning post-processing of request 945196 on node EBSAPPPROD at 22-JAN-2013 06:49:36.
Post-processing of request 945196 completed at 22-JAN-2013 06:49:59.
Finished executing request completion options.
Concurrent request completed
Current system time is 22-JAN-2013 06:49:59
Regards,
Smita

Hi,
Since you said the behavior is sporadic and also the program was running good in 11i instance, I think its a problem with the data [or select query in the concurrent program] .
Ideal scenario:
1. Upon the concurrent program completing in error the pdf should not be generated in first place, since it misguides the obtained report. [Concurrent Program should be modified accordingly, before calling the pdf generation logic you need to check the status of the concurrent program].
2. It is not likely that the pdf generation should error out upon concurrent program's error, since the concurrent program could have a soft closure of its schema definition [inspite of an uncaught/unhandled exception]
eg:
<schema def>
<Xml element 1> </Xml element 1>
<Xml element 2> </Xml element 2>
<Xml element 3> </Xml element 3>
*_ <while generating elements 4, 5 and so on concurrent program could have errored out, but still the schema definition is valid so the pdf is generated>_*
</schema def>
Solution:
Next time when you get the same behaviour, try running the concurrent program and handle the exception for that scenario, this should resolve your issue.
Regards,
Yuvaraj

Using XML to generate site structure

Well. I'll describe my problem in brief.
I want to generate XML in my servlets and then perform XSL-transformation. This allows me to separate data from the representation. For example:
<menu>
<item name="Home">http://nome.com</item>
</menu>and then I'll create a stylesheet that will generate proper left column with beautiful menu. The idea seems to be beautiful and probably is not a new one. I don't know if there some similar solutions. I'm interesting in a XML-dictionary and XSL stylesheets. Of course, I can make my own dictionary and stylesheet, but may be there are some powerful examples?

It is possible to use an xml document to build a
graphic. The web3d.org is working on that project.
As VRML Viewer can view and edit vrml 3D file, a well-designed Java3Dviewer can visualize the scene defined in a XML file.
The plug-in allows programs to run inside web browser, if you design a Java program to view 3D data defined in a XML file, users can run this program in their desktop with Java plug-in.
So research Java3d API and do it.
regards,
Louis

How do I fill by chunks a clob inside a table while XML is generated?

Hello everybody:
Needed to generate a single XML file from around 50 million rows, where the XML ouput matches not only row data but another default values for another elements and attributes (not from database but using strings and types with default values). Its generation will be a monthly task, so the process will repeat time by time. For generating that document, currently focus is based on using a batch process relying on Spring Batch, by using a single JDBC query where a join happens between a table and a materialized view (Both are datawarehouses, so it is not expected a change onto the data, and are single, non-partitioned tables). From my point of view, that approach uses: database resources, network resources, disk resources, and processing resources, including the price of making the join, sending to network, creating objects, validating, and making the file, finally wasting too much time generating that XML file. Promisse above that approach is to restart from the last execution point (savepoints) and to process by chunks of data (ResultSets). That processs currently is in development.
Seen Oracle has XML capabilites, another approach may be delegating the complete generation of that file to the database (Current version in use here is 10g release 2). My current approach is to generate a clob where I will put all the XML throughput and putting it inside a table (My first approach was to put directly into a disk file, unfortunately, isn't possible because internal policies). Considering limitations on memory, processing and disk space, needed to append a single row-as-xml to the clob as soon as it is rendered, and putting the clob inside the field as soon as possible, or putting the clob inside the field, and appending into it as the data is generated (preffered approach); also, considering its a very large operation, needed to make savepoints for each chunk of data processed (each 20,000 rows, as example). Some way I think it may be done is making a temporary clob, filling the clob while getting the rowid, using that rowid as savepoint (No other CRUD operations awaited for the table and the materialized view), and later appending the clob to the clob(s) in table (is there some way for append one clob to another one in table?). Explained all those points, how do I manage the process in order to achieve that goals, using a PL/SQL stored procedure while using built-in functions?.
Update: I did a small pseudocode where I describe my current approach:
Defining a cursor;
Creating a segment clob;
Creating a temporary clob;
Defining a chunk size;
Defining a temp rowid variable;
Defining a control number to be 0;
While cursor
     getting rowid and generating next row as xml into a temporary clob (XMLSerialize):
     increment the control number;
     if control number equals 1
write rowid variable to a control table;
     append the temporary clob to a segment clob;
     if control number is equals than the chunk size defined:
          append the segment clob to the clob inside a control table;
          restart the control number to be 0;
     else
          continue;
At this time, I'm with doubt about how to append the segment clob directly to the clob inside the control table (I find using that clob as PL/SQL variable would use too much memory and swap).
Any help shall be apreciated. Thanks in advance.

Well, of course it's looping. That's what the "while" statement does. What you need is more like this:
if (tableNumberJTextField.getText().equals("")){
JOptionPane.showMessageDialog(null, "Table Number cannot be empty","Error", JOptionPane.ERROR_MESSAGE);
tableNumberJTextField.requestFocusInWindow();
}and you want this code to be called every time tableNumberJTextField loses focus.

How to view XML file generated by Reports 6i in browser ?

Hi,
I have generated a report in XML file format. However, when I open this file in a browser, it displays the contents in the browser in the following fashion :
<?xml version="1.0" ?>
- 
- <MSIO1O>
- <LIST_G_CMEM_CD>
- <G_CMEM_CD>
<STATUS>Inactive</STATUS>
<CODE1>106</CODE1>
<NAME1>-</NAME1>
<STATUS_DATE1>11-OCT-00</STATUS_DATE1>
<EXCHANGE1>BSE</EXCHANGE1>
</G_CMEM_CD>
I want to display this content in a user-friendly mode. Because the user can not understand in the above format.
Does IE or Netscape support the XML file ??
I have heard that to view the XML file, one has to install XML Parcels. Is it true ??
I am using Reports 6i & IE 5.0
Your help will be appreciated.
Thanks.
M@yur
null

What you are seeing in your browser is XML.
IE 4 and above will display the XML correctly.
XML is not ment to be beautiful for this you get other formats HTMLCSS etc.
To get XML to be more nicely output you need to apply XSL on top of it. You can specify XSL tag in the reports XML prolog property.

Ns0 prefix not attached in the xml structure generated using Content Master

Hello Everyone,
I am parsing a tabdelimited file using the Content Master Studio.
I am providing the message type xsd as the schema file.
After writing all the parsing logic the xml file which is getting generated is in the below mentioned format
<?xml version="1.0" encoding="UTF-8"?>
<ReadExcel xmlns="urn:readexcel.com">
<ROW>
<NAME>Rahul</NAME>
<AGE>24</AGE>
<Location>Mumbai</Location>
</ROW>
<ROW>
<NAME>Vinit</NAME>
<AGE>25</AGE>
<Location>Mumbai</Location>
</ROW>
</ReadExcel>
but since the ns0 prefix is not getting attached the mapping program is failing in XI.
<ns0:ReadExcel xmlns:ns0="urn:readexcel.com">
I guess the people who have used Content master studio might have also faced the similar problem.
Please suggest me some solution
Thanks and Regards
Rahul Nawale

Hi Rahul,
the namespace prefic ns0 is only a placeholder for the namespace urn:readexcel.com. This namespace can also be represented by another prefix or even by the empty prefix.
E.g. the document you have pasted is totally equivalent to the document
<?xml version="1.0" encoding="UTF-8"?>
<ns0:ReadExcel xmlns:ns0="urn:readexcel.com">
<ns0:ROW>
<ns0:NAME>Rahul</ns0:NAME>
<ns0:AGE>24</ns0:AGE>
<ns0:Location>Mumbai</ns0:Location>
</ns0:ROW>
<ns0:ROW>
<ns0:NAME>Vinit</ns0:NAME>
<ns0:AGE>25</ns0:AGE>
<ns0:Location>Mumbai</ns0:Location>
</ns0:ROW>
</ns0:ReadExcel>
However, it is not possible to model this document via a Message type in the Integration Repository. The XML instance from a Message type will look like this:
<?xml version="1.0" encoding="UTF-8"?>
<ns0:ReadExcel xmlns:ns0="urn:readexcel.com">
<ROW>
<NAME>Rahul</NAME>
<AGE>24</AGE>
<Location>Mumbai</Location>
</ROW>
<ROW>
<NAME>Vinit</NAME>
<AGE>25</AGE>
<Location>Mumbai</Location>
</ROW>
</ns0:ReadExcel>
Indeed, in the root tag all documents are equivalent (it has name ReadExcel and namespace urn:readexcel.com). But for the subelements (ROW, NAME,...) there is a fundemental difference. In your example (and my first example) these elements have namespace urn:readexcel.com, too. In my second example those elements have empty namespace. Indeed, all XML documents modelled as Message types have an empty namespace for all non-root elements.
Message types are simply not suitable to model a document as you have posted. However, there is simple help. Just download the schema for the Message type to your local file system. Add attribute elementFormDefault="qualified" to the root tag of that schema. Upload that schema as External Definition. This External Definition will have one External Message. Define your mapping using that schema.
For more background on that topic I recommend reading the specifications on XML namespaces and XML schema.
Greetings
Stephan

XML Messages generated by XI using namespace aliases...

I have a question regarding the XML messages that are generated by XI as part of the mapping, etc.
I receive e.g. the following XML document in the payload of my message sent to a legacy system:
<ns1:ArticleRequest xmlns:ns1="http://www.basis.ko.com/XMLSchemas/ArticleRequest/2.0" function="retrieve">
     <ns1:ArticleNumber>109</ns1:ArticleNumber>
</ns1:ArticleRequest>
Unfortunately the system cannot handle the ns1: prefixes correctly and would prefer if the XML message were using the default namespace.
Can XI be configured to produce the XML using the default namespace (in case the interface has just one namespace this should be semantically identical)
<ArticleRequest xmlns="http://www.basis.ko.com/XMLSchemas/ArticleRequest/2.0" function="retrieve">
     <ArticleNumber>109</ArticleNumber>
</ArticleRequest>
and furthermore, is there a way to include the xsi:schemaLocation attribute in the resulting XML document?
like this:
<ArticleRequest xmlns:ns1="http://www.basis.ko.com/XMLSchemas/ArticleRequest/2.0" function="retrieve" xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance" xsi:schemaLocation="http://www.basis.ko.com/XMLSchemas/ArticleRequest/2.0 ArticleRequest.xsd" >
     <ArticleNumber>109</ArticleNumber>
</ArticleRequest>
kind regards for your help,
Peter

Hi Udo,
I'm not sure how the XSL Mapping can remove the namespace alias and exchange it with default namespace. The xsl:copy-of just does a duplication of the selected node. Do you have any additional input on this one?
Regarding the second hint, 'manipulate the field XML namespace in the message type', I could not find a place where to do this - as I am using 'External Definition' (XSDs imported into XI). Still when I change the namespace I will always receive the prefix in front of each element.
Any additional help is highly appreciated.
regards,
Peter

XML C++ Generator

Similar Messages

Maybe you are looking for