Error while generating an XML Document from XML Schema with JAXB

Hi,
I am following this OTN tutorial to generate the XML document from Java classes got from the XSD document.
http://www.oracle.com/technology/pub/notes/technote_jaxb.html
I am able to generate all the Java classes but getting error on compiling the XMLConstructor.java class which is use for generating the XML document :
I am using JDK 1.5 and
Oracle 10g XML Developer's Kit (XDK) Production for Java. xdk_nt_10_1_0_2_0_production
(though these are warnings I am not able to run it.)
Error
C:\Prototype\classes\jaxbderived\catalog>javac -Xlint XMLConstructor.java
warning: [path] bad path element "%CLASSPATH%": no such file or directory
XMLConstructor.java:42: warning: [unchecked] unchecked call to add(E) as a member of the raw type java.util.List
journalList.add(journal);
^
XMLConstructor.java:46: warning: [unchecked] unchecked call to add(E) as a membe
r of the raw type java.util.List
articleList.add(article);
Thanks
Sanjeev ([email protected])

Use JDK 1.4.

Similar Messages

WE60 - Error while generating the xml schema

Hi
Using the transaction WE60 I am trying to generate an XML schema for the BASIC type : DEBMDM06, Segment release - 7 and record type version - 3. Following error message is displayed. "Structure of segment E1T023W is unknown". Kindly let me know how to generate an XML schema successfully and what is the reason for this error to come up
Regards
Aruna

Hi Aruna,
It seems a dictionary error but it doesn't occurs to me. I can download the XML schema without problems in SAP ECC 6.0.
If you let me know your email I can send it zipped to you.
Reward points if helps.
Roger

B2B Error while generating 850 EDI Document

Hi All,
We are facing the following error in B2B while generating an EDI 850 outbound document.
To give a brief background of our process:
We are using a BPEL process to pick a fixed length file from FTP adapter and then transform it and provide it to B2B for converting it into an EDI 850 Purchase Order. The BPEL part of the Process is working fine and it is successfully transforming the fixed length file into intermediate XML that it gives to B2B engine.
In B2B, the ECS file that we use has been generated from an XSD and we upload the corresponding ECS and XSD in B2B during configuration.
But we get the following error when B2B converts it into EDI 850 format.
Error Brief :
5084: XEngine error - Invalid data.
I am also giving around 100 lines from the b2b log before this error occurred.
2006.10.30 at 01:50:14:416: Thread-11: B2B - (DEBUG) oracle.tip.adapter.b2b.document.edi.EDIDocumentPlugin:traceParameters Parameter AcknowledgementType = 997
2006.10.30 at 01:50:14:416: Thread-11: B2B - (DEBUG) oracle.tip.adapter.b2b.document.edi.EDIDocumentPlugin:traceParameters Parameter GroupSenderID = 19508030411I
2006.10.30 at 01:50:14:416: Thread-11: B2B - (DEBUG) oracle.tip.adapter.b2b.document.edi.EDIDocumentPlugin:traceParameters Parameter InterchangeECSFileBlob
2006.10.30 at 01:50:14:416: Thread-11: B2B - (DEBUG) oracle.tip.adapter.b2b.document.edi.EDIDocumentPlugin:traceParameters Parameter InterchangeAuthorizationInfoQual = 00
2006.10.30 at 01:50:14:416: Thread-11: B2B - (DEBUG) oracle.tip.adapter.b2b.document.edi.EDIDocumentPlugin:traceParameters Parameter GroupID = PO
2006.10.30 at 01:50:14:416: Thread-11: B2B - (DEBUG) oracle.tip.adapter.b2b.document.edi.EDIDocumentPlugin:traceParameters Parameter TagDelimiter = null
2006.10.30 at 01:50:14:417: Thread-11: B2B - (DEBUG) oracle.tip.adapter.b2b.document.edi.EDIDocumentPlugin:traceParameters Parameter TransactionECSFileKey = 1BA24E3F6DB690CAE0430A0B3E7290CA-274-1-42
2006.10.30 at 01:50:14:417: Thread-11: B2B - (DEBUG) oracle.tip.adapter.b2b.document.edi.EDIDocumentPlugin:traceParameters Parameter InterchangeSecurityInfoQual = 00
2006.10.30 at 01:50:14:417: Thread-11: B2B - (DEBUG) oracle.tip.adapter.b2b.document.edi.EDIDocumentPlugin:traceParameters Parameter GroupECSFileBlob
2006.10.30 at 01:50:14:417: Thread-11: B2B - (DEBUG) oracle.tip.adapter.b2b.document.edi.EDIDocumentPlugin:traceParameters Parameter TPName = CANON
2006.10.30 at 01:50:14:417: Thread-11: B2B - (DEBUG) oracle.tip.adapter.b2b.document.edi.EDIDocumentPlugin:traceParameters Parameter TransactionImplementationReference = null
2006.10.30 at 01:50:14:417: Thread-11: B2B - (DEBUG) oracle.tip.adapter.b2b.document.edi.EDIDocumentPlugin:traceParameters Parameter ReplacementChar = null
2006.10.30 at 01:50:14:417: Thread-11: Repository - (DEBUG) CatalogDriver manager == oracle.tip.model.metadata.CatalogMetaManager@9f90cf3
2006.10.30 at 01:50:14:417: Thread-11: Repository - (DEBUG) CatalogMetaManager getDriverjava.lang.InheritableThreadLocal@72418cf0 oracle.tip.repos.core.driver.CatalogDriver@121ccf4
2006.10.30 at 01:50:14:418: Thread-11: B2B - (DEBUG) oracle.tip.adapter.b2b.document.edi.ISelectorImpl:ISelectorImpl Enter
2006.10.30 at 01:50:14:419: Thread-11: B2B - (DEBUG) oracle.tip.adapter.b2b.document.edi.ISelectorImpl:ISelectorImpl fullOutboundBatching = false
2006.10.30 at 01:50:14:419: Thread-11: B2B - (DEBUG) oracle.tip.adapter.b2b.document.edi.ISelectorImpl:ISelectorImpl validateEnvelope = true
2006.10.30 at 01:50:14:419: Thread-11: B2B - (DEBUG) oracle.tip.adapter.b2b.document.edi.ISelectorImpl:ISelectorImpl Leave
2006.10.30 at 01:50:14:419: Thread-11: Repository - (DEBUG) LargeStringImpl.getString() - object OID - 20D326898FA9D054E0430A0B3E72D054-11-1-1
2006.10.30 at 01:50:14:421: Thread-11: B2B - (DEBUG) oracle.tip.adapter.b2b.document.edi.ISelectorImpl:doLookup Enter
2006.10.30 at 01:50:14:421: Thread-11: B2B - (DEBUG) oracle.tip.adapter.b2b.document.edi.ISelectorImpl:doLookup key = ec_DataNodeName, val = [Interchange]
2006.10.30 at 01:50:14:421: Thread-11: B2B - (DEBUG) oracle.tip.adapter.b2b.document.edi.ISelectorImpl:doLookup return = true
2006.10.30 at 01:50:14:422: Thread-11: B2B - (DEBUG) oracle.tip.adapter.b2b.document.edi.ISelectorImpl:doLookup return = true
2006.10.30 at 01:50:14:422: Thread-11: B2B - (DEBUG) oracle.tip.adapter.b2b.document.edi.ISelectorImpl:cloneSelector Enter
2006.10.30 at 01:50:14:422: Thread-11: B2B - (DEBUG) oracle.tip.adapter.b2b.document.edi.ISelectorImpl:cloneSelector Return = oracle.tip.adapter.b2b.document.edi.ISelectorImpl@34c90cf5
2006.10.30 at 01:50:14:422: Thread-11: B2B - (DEBUG) oracle.tip.adapter.b2b.document.edi.ISelectorImpl:getValue Param Name = InterchangeSenderQual
2006.10.30 at 01:50:14:422: Thread-11: B2B - (DEBUG) oracle.tip.adapter.b2b.document.edi.ISelectorImpl:getValue Value = 01
2006.10.30 at 01:50:14:422: Thread-11: B2B - (DEBUG) oracle.tip.adapter.b2b.document.edi.ISelectorImpl:getValue Param Name = InterchangeSenderID
2006.10.30 at 01:50:14:422: Thread-11: B2B - (DEBUG) oracle.tip.adapter.b2b.document.edi.ISelectorImpl:getValue Value = 195080304
2006.10.30 at 01:50:14:422: Thread-11: B2B - (DEBUG) oracle.tip.adapter.b2b.document.edi.ISelectorImpl:getValue Param Name = InterchangeReceiverQual
2006.10.30 at 01:50:14:422: Thread-11: B2B - (DEBUG) oracle.tip.adapter.b2b.document.edi.ISelectorImpl:getValue Value = 01
2006.10.30 at 01:50:14:423: Thread-11: B2B - (DEBUG) oracle.tip.adapter.b2b.document.edi.ISelectorImpl:getValue Param Name = InterchangeReceiverID
2006.10.30 at 01:50:14:423: Thread-11: B2B - (DEBUG) oracle.tip.adapter.b2b.document.edi.ISelectorImpl:getValue Value = 0415306925
2006.10.30 at 01:50:14:423: Thread-11: B2B - (DEBUG) oracle.tip.adapter.b2b.document.edi.ISelectorImpl:getValue Param Name = InterchangeControlVersion
2006.10.30 at 01:50:14:423: Thread-11: B2B - (DEBUG) oracle.tip.adapter.b2b.document.edi.ISelectorImpl:getValue Value = 00401
2006.10.30 at 01:50:14:423: Thread-11: B2B - (DEBUG) oracle.tip.adapter.b2b.document.edi.ISelectorImpl:doLookup Enter
2006.10.30 at 01:50:14:423: Thread-11: B2B - (DEBUG) oracle.tip.adapter.b2b.document.edi.ISelectorImpl:doLookup key = ec_DataNodeName, val = [Group]
2006.10.30 at 01:50:14:423: Thread-11: B2B - (DEBUG) oracle.tip.adapter.b2b.document.edi.ISelectorImpl:doLookup return = true
2006.10.30 at 01:50:14:423: Thread-11: B2B - (DEBUG) oracle.tip.adapter.b2b.document.edi.ISelectorImpl:doLookup return = true
2006.10.30 at 01:50:14:423: Thread-11: B2B - (DEBUG) oracle.tip.adapter.b2b.document.edi.ISelectorImpl:cloneSelector Enter
2006.10.30 at 01:50:14:424: Thread-11: B2B - (DEBUG) oracle.tip.adapter.b2b.document.edi.ISelectorImpl:cloneSelector Return = oracle.tip.adapter.b2b.document.edi.ISelectorImpl@2c760cf5
2006.10.30 at 01:50:14:424: Thread-11: B2B - (DEBUG) oracle.tip.adapter.b2b.document.edi.ISelectorImpl:getValue Param Name = GroupID
2006.10.30 at 01:50:14:424: Thread-11: B2B - (DEBUG) oracle.tip.adapter.b2b.document.edi.ISelectorImpl:getValue Value = PO
2006.10.30 at 01:50:14:424: Thread-11: B2B - (DEBUG) oracle.tip.adapter.b2b.document.edi.ISelectorImpl:getValue Param Name = GroupSenderID
2006.10.30 at 01:50:14:424: Thread-11: B2B - (DEBUG) oracle.tip.adapter.b2b.document.edi.ISelectorImpl:getValue Value = 19508030411I
2006.10.30 at 01:50:14:424: Thread-11: B2B - (DEBUG) oracle.tip.adapter.b2b.document.edi.ISelectorImpl:getValue Param Name = GroupReceiverID
2006.10.30 at 01:50:14:424: Thread-11: B2B - (DEBUG) oracle.tip.adapter.b2b.document.edi.ISelectorImpl:getValue Value = 0415306925
2006.10.30 at 01:50:14:424: Thread-11: B2B - (DEBUG) oracle.tip.adapter.b2b.document.edi.ISelectorImpl:getValue Param Name = GroupVersionNumber
2006.10.30 at 01:50:14:424: Thread-11: B2B - (DEBUG) oracle.tip.adapter.b2b.document.edi.ISelectorImpl:getValue Value = 004010
2006.10.30 at 01:50:14:425: Thread-11: B2B - (DEBUG) oracle.tip.adapter.b2b.document.edi.ISelectorImpl:doLookup Enter
2006.10.30 at 01:50:14:425: Thread-11: B2B - (DEBUG) oracle.tip.adapter.b2b.document.edi.ISelectorImpl:doLookup key = ec_DataNodeName, val = [Transaction]
2006.10.30 at 01:50:14:425: Thread-11: B2B - (DEBUG) oracle.tip.adapter.b2b.document.edi.ISelectorImpl:doLookup return = true
2006.10.30 at 01:50:14:425: Thread-11: B2B - (DEBUG) oracle.tip.adapter.b2b.document.edi.ISelectorImpl:doLookup return = true
2006.10.30 at 01:50:14:425: Thread-11: B2B - (DEBUG) oracle.tip.adapter.b2b.document.edi.ISelectorImpl:cloneSelector Enter
2006.10.30 at 01:50:14:425: Thread-11: B2B - (DEBUG) oracle.tip.adapter.b2b.document.edi.ISelectorImpl:cloneSelector Return = oracle.tip.adapter.b2b.document.edi.ISelectorImpl@25070cf5
2006.10.30 at 01:50:14:425: Thread-11: B2B - (DEBUG) oracle.tip.adapter.b2b.document.edi.ISelectorImpl:getValue Param Name = TransactionID
2006.10.30 at 01:50:14:425: Thread-11: B2B - (DEBUG) oracle.tip.adapter.b2b.document.edi.ISelectorImpl:getValue Value = 850
2006.10.30 at 01:50:14:427: Thread-11: B2B - (DEBUG) oracle.tip.adapter.b2b.document.edi.ISelectorImpl:getValue Param Name = SegmentDelimiter
2006.10.30 at 01:50:14:427: Thread-11: B2B - (DEBUG) oracle.tip.adapter.b2b.document.edi.ISelectorImpl:getValue Value = 0x0A
2006.10.30 at 01:50:14:427: Thread-11: B2B - (DEBUG) oracle.tip.adapter.b2b.document.edi.ISelectorImpl:getValue Param Name = ElementDelimiter
2006.10.30 at 01:50:14:427: Thread-11: B2B - (DEBUG) oracle.tip.adapter.b2b.document.edi.ISelectorImpl:getValue Value = 0x7D
2006.10.30 at 01:50:14:427: Thread-11: B2B - (DEBUG) oracle.tip.adapter.b2b.document.edi.ISelectorImpl:getValue Param Name = SubelementDelimiter
2006.10.30 at 01:50:14:427: Thread-11: B2B - (DEBUG) oracle.tip.adapter.b2b.document.edi.ISelectorImpl:getValue Value = 0x3E
2006.10.30 at 01:50:14:427: Thread-11: B2B - (DEBUG) oracle.tip.adapter.b2b.document.edi.ISelectorImpl:getValue Param Name = RepeatingSeparator
2006.10.30 at 01:50:14:427: Thread-11: B2B - (DEBUG) oracle.tip.adapter.b2b.document.edi.ISelectorImpl:getValue Value = null
2006.10.30 at 01:50:14:428: Thread-11: B2B - (DEBUG) oracle.tip.adapter.b2b.document.edi.ISelectorImpl:getValue Param Name = ReplacementChar
2006.10.30 at 01:50:14:428: Thread-11: B2B - (DEBUG) oracle.tip.adapter.b2b.document.edi.ISelectorImpl:getValue Value = null
2006.10.30 at 01:50:14:428: Thread-11: B2B - (DEBUG) oracle.tip.adapter.b2b.document.edi.ISelectorImpl:reset Enter
2006.10.30 at 01:50:14:428: Thread-11: B2B - (DEBUG) oracle.tip.adapter.b2b.document.edi.ISelectorImpl:reset Leave
2006.10.30 at 01:50:14:428: Thread-11: B2B - (DEBUG) oracle.tip.adapter.b2b.document.edi.ISelectorImpl:getValue Param Name = TPName
2006.10.30 at 01:50:14:428: Thread-11: B2B - (DEBUG) oracle.tip.adapter.b2b.document.edi.ISelectorImpl:getValue Value = CANON
2006.10.30 at 01:50:14:429: Thread-11: B2B - (DEBUG) oracle.tip.adapter.b2b.document.edi.ISelectorImpl:doCommit Enter
2006.10.30 at 01:50:14:429: Thread-11: B2B - (DEBUG) oracle.tip.adapter.b2b.document.edi.ISelectorImpl:doCommit Leave
2006.10.30 at 01:50:14:429: Thread-11: B2B - (DEBUG) oracle.tip.adapter.b2b.document.edi.EDIDocumentPlugin:processOutgoingDocument XML = 1
2006.10.30 at 01:50:14:429: Thread-11: B2B - (DEBUG) oracle.tip.adapter.b2b.document.edi.EDIDocumentPlugin:processOutgoingDocument no result from XDataToNative
2006.10.30 at 01:50:14:442: Thread-11: B2B - (DEBUG) iAudit report :
Error Brief :
5084: XEngine error - Invalid data.
iAudit Report :
<?xml version="1.0" encoding="UTF-16"?><AnalyzerResults Guid="{06B942E5-E267-DB11-9E73-006163130000}" InterchangeReceived="1" InterchangeProcessed="1" InterchangeAccepted="0"> <ExecutionDate>Monday, October 30, 2006</ExecutionDate> <ExecutionTime>01:50:14 AM (EST)</ExecutionTime> <AnalyzerReturn>Failed</AnalyzerReturn> <NumberOfErrors>1</NumberOfErrors> <ErrorByCategory> <Category Name="Rejecting"> <Severity Name="Normal">1</Severity> </Category> </ErrorByCategory> <Status>Finished</Status> <DataFile> <FilePath/> <FileName/> <LastModified/> <FileSize/> <DataURL>file://</DataURL> </DataFile> <Interchange Guid="{424043E5-E267-DB11-9E73-006163130000}" InterchangeAckCode="R" FunctionalGroupReceived="1" FunctionalGroupProcessed="1" FunctionalGroupAccepted="0" RError="0" NError="0" OtherWI="0"> <DataXPointer> <StartPos>0</StartPos> <Size>1337</Size> </DataXPointer> <NodeInfo> <Links> <Link Name="InterchangeSenderQual">01</Link> <Link Name="InterchangeSenderID">195080304</Link> <Link Name="InterchangeReceiverQual">01</Link> <Link Name="InterchangeReceiverID">0415306925</Link> <Link Name="InterchangeControlVersion">00401</Link> </Links> <Properties> <Property Name="Standard">X12</Property> <Property Name="SegmentDelimiter">0xa</Property> <Property Name="ElementDelimiter">0x7d</Property> <Property Name="SubelementDelimiter">0x3e</Property> <Property Name="RepeatingSeparator"/> <Property Name="ReplacementChar">0x20</Property> </Properties> </NodeInfo> <FunctionalGroup Guid="{F28543E5-E267-DB11-9E73-006163130000}" FunctionalGroupAckCode="R" TransactionSetsIncluded="0" TransactionSetsReceived="1" TransactionSetsProcessed="1" TransactionSetsAccepted="0" RError="0" NError="0" OtherWI="0"> <DataXPointer> <StartPos>0</StartPos> <Size>1337</Size> </DataXPointer> <NodeInfo> <Links> <Link Name="GroupSenderID">19508030411I</Link> <Link Name="GroupReceiverID">0415306925</Link> <Link Name="GroupVersionNumber">004010</Link> </Links> <Properties> <Property Name="GroupID">PO</Property> </Properties> </NodeInfo> <Transaction Guid="{33303938-3738-3533-3630-353932353933}" TransactionAckCode="R" RError="1" NError="0" OtherWI="0"> <DataXPointer> <StartPos>0</StartPos> <Size>1337</Size> </DataXPointer> <NodeInfo> <Links> <Link Name="TransactionID">850</Link> </Links> <Properties/> </NodeInfo> <TransactionErrors> <Error ErrorCode="{F35AFE03-C479-4F96-B4F1-2EF36DABC5FE}" Severity="Normal" Category="Rejecting" Index="1" ID="50840000"> <ErrorBrief>5084: XEngine error - Invalid data.</ErrorBrief> <ErrorMsg>Invalid data.</ErrorMsg> <ErrorObjectInfo> <Parameter Name="ErrorLevel">0</Parameter> <Parameter Name="Name">XData2Native</Parameter> <Parameter Name="_ec_dn_guid_">{33303938-3738-3533-3630-353932353933}</Parameter> <Parameter Name="_ec_index">0</Parameter> <Parameter Name="ec_error_scope">Transaction</Parameter> </ErrorObjectInfo> <ErrorDataInfo> <Part1/> <ErrData/> <Part3/> <DataXPointer> <StartPos>0</StartPos> <Size>0</Size> </DataXPointer> </ErrorDataInfo> </Error> </TransactionErrors> </Transaction> </FunctionalGroup> </Interchange></AnalyzerResults>
2006.10.30 at 01:50:14:443: Thread-11: B2B - (DEBUG) oracle.tip.adapter.b2b.document.edi.EDIDocumentPlugin:processOutgoingDocument sErrorGuid = {F35AFE03-C479-4F96-B4F1-2EF36DABC5FE}
2006.10.30 at 01:50:14:443: Thread-11: B2B - (DEBUG) oracle.tip.adapter.b2b.document.edi.EDIDocumentPlugin:processOutgoingDocument sDescription = Invalid data.
2006.10.30 at 01:50:14:443: Thread-11: B2B - (DEBUG) oracle.tip.adapter.b2b.document.edi.EDIDocumentPlugin:processOutgoingDocument sBrDescription = 5084: XEngine error - Invalid data.
2006.10.30 at 01:50:14:443: Thread-11: B2B - (DEBUG) oracle.tip.adapter.b2b.document.edi.EDIDocumentPlugin:processOutgoingDocument sParameterName = ErrorLevel sParameterValue = 0
2006.10.30 at 01:50:14:443: Thread-11: B2B - (DEBUG) oracle.tip.adapter.b2b.document.edi.EDIDocumentPlugin:processOutgoingDocument sParameterName = Name sParameterValue = XData2Native
2006.10.30 at 01:50:14:443: Thread-11: B2B - (DEBUG) oracle.tip.adapter.b2b.document.edi.EDIDocumentPlugin:processOutgoingDocument sParameterName = ecdn_guid_ sParameterValue = {33303938-3738-3533-3630-353932353933}
2006.10.30 at 01:50:14:443: Thread-11: B2B - (DEBUG) oracle.tip.adapter.b2b.document.edi.EDIDocumentPlugin:processOutgoingDocument sParameterName = ecindex sParameterValue = 0
2006.10.30 at 01:50:14:444: Thread-11: B2B - (DEBUG) oracle.tip.adapter.b2b.document.edi.EDIDocumentPlugin:processOutgoingDocument sParameterName = ec_error_scope sParameterValue = Transaction
2006.10.30 at 01:50:14:444: Thread-11: B2B - (DEBUG) oracle.tip.adapter.b2b.document.edi.EDIDocumentPlugin:processOutgoingDocument added Hash Key = {33303938-3738-3533-3630-353932353933}
2006.10.30 at 01:50:14:444: Thread-11: B2B - (DEBUG) oracle.tip.adapter.b2b.document.edi.EDIDocumentPlugin:processOutgoingDocument batch Position = 0
2006.10.30 at 01:50:14:444: Thread-11: B2B - (ERROR) Error -: AIP-51505: General Validation Error
     at oracle.tip.adapter.b2b.document.edi.EDIDocumentPlugin.processOutgoingDocument(EDIDocumentPlugin.java:1668)
     at oracle.tip.adapter.b2b.msgproc.Request.outgoingRequestPostColab(Request.java:1132)
     at oracle.tip.adapter.b2b.msgproc.Request.outgoingRequest(Request.java:710)
     at oracle.tip.adapter.b2b.engine.Engine.processOutgoingMessage(Engine.java:821)
     at oracle.tip.adapter.b2b.data.MsgListener.onMessage(MsgListener.java:532)
     at oracle.tip.adapter.b2b.data.MsgListener.run(MsgListener.java(Compiled Code))
     at java.lang.Thread.run(Thread.java:568)
If anybody has faced a similar issue, then please post on how to overcome this error.
Thanks In Advance,
Dibya

Hi,
I am facing a similar problem.
I am trying to transfer a xml in 850 format with internal properties of Interchange,Group and Transaction from BPEL to B2B.My BPEL setup consist of :
A partnerlink which read xml in 850 format using file adapter.
A receive Activity which receive the data.
I have created a partnerlink which use AQ Adapter to enqueue data in IP_OUT_QUEUE.
A invoke Activity invokes this partnerlink.
Then I have assigned the read data in Receive to input variable of Invoke activity.
I have used another Assign Activity to populate the Header; and passed this header in Invoke Activity.
In B2B I have created two trading partner one remote and one host, defined a business action and defined the Communication capability for them. I am using FTP1.0 . I defined a agreement and deployed the configuration in b2b server.
The ecs and xsd I am using is the one provided with Purchase order tutorial, it contains only ST-SE,I have also tried with envelope segments for 4010-namely
ISA-->GS-GE-->IEA.When I am turning off validation and translation its throwing the input XML as output in the .dat file. If I turn on Translation I am getting unrecognized data last known segment is GSA.In this case the input XML had internal properties of Interchange and Group.If I remove the transaction part from ST-SE the dat file is generated in native dat format but with ISA -GS-GE -IEA but no transaction portion.
As a work around I tried seperate group ecs,interchange ecs and transaction ecs and tried to pass a 850 xml with only transaction fields.
I have tried with no ecs file at all and in that case the dat file is also generated.So does this mean that B2B have seeded ecs file which it use as default if I dont use any ecs file?
It seems from the post you have successfully completed this part can u send me :
1>The 850 ecs and xsd file you used.
2>If you have used any group ecs and interchange ecs.
3>The input you are sending in BPEL.
4>The BPEL process and B2B export xml you are using in zipped format.
My mail ID: [email protected]
phone:09831964607
I tried out different ways suggested in the post but nothing seem to be working for me,I am still getting the invalid data error and if it is creating the dat file only envelope segments are created.
If you send me the working example I can work on it as baseline, this will be of great help in my work.

Error while generating java client code from wsdl file

I am trying to generate a java client code from WSDL file um_workflowSaveCreateProfile.wsdl which includes um_workflowSaveCreateProfile_interface.wsdl file, so I am keeping both the files in the same folder and trying to generate the client code but it is showing me the below error highlighted .
um_workflowSaveCreateProfile.wsdl
<definitions xmlns="http://schemas.xmlsoap.org/wsdl/" xmlns:soap="http://schemas.xmlsoap.org/wsdl/soap/" xmlns:http="http://schemas.xmlsoap.org/wsdl/http/" xmlns:xsd="E:/DIPPWF/XMLSchema" xmlns:soapenc="http://schemas.xmlsoap.org/soap/encoding/" xmlns:oblix="http://www.oblix.com/" xmlns:obinterface="http://www.oblix.com/wsdl/um_workflowSaveCreateProfile_interface" xmlns:mime="http://schemas.xmlsoap.org/wsdl/mime/" xmlns:tns="http://www.oblix.com/wsdl/um_workflowSaveCreateProfile" targetNamespace="http://www.oblix.com/wsdl/um_workflowSaveCreateProfile">
     <import namespace="D:/DIPP/WSDL/um_workflowSaveCreateProfile_interface" location="um_workflowSaveCreateProfile_interface.wsdl"/>
     <service name="OblixIDXML_um_workflowSaveCreateProfile_Service">
          <port name="OblixIDXML_um_workflowSaveCreateProfile_Port" binding="obinterface:OblixIDXML_um_workflowSaveCreateProfile_Binding">
               <soap:address location="http://localhost:7777/identity/oblix/apps/userservcenter/bin/userservcenter.cgi"/>
          </port>
     </service>
</definitions>
um_workflowSaveCreateProfile_interface.wsdl
<definitions xmlns="http://schemas.xmlsoap.org/wsdl/" xmlns:soap="http://schemas.xmlsoap.org/wsdl/soap/" xmlns:http="http://schemas.xmlsoap.org/wsdl/http/" xmlns:xsd="http://www.w3.org/2001/XMLSchema" xmlns:soapenc="http://schemas.xmlsoap.org/soap/encoding/" xmlns:oblix="http://www.oblix.com/" xmlns:oblixxmllocalschema="http://www.oblix.com/OblixXMLLocalSchema" xmlns:mime="http://schemas.xmlsoap.org/wsdl/mime/" xmlns:tns="http://www.oblix.com/wsdl/um_workflowSaveCreateProfile_interface" targetNamespace="http://www.oblix.com/wsdl/um_workflowSaveCreateProfile_interface">
     <types>
          <xsd:schema targetNamespace="http://www.oblix.com/" elementFormDefault="qualified"
               xmlns="http://www.oblix.com/"
               xmlns:xsd="http://www.w3.org/2001/XMLSchema">
                    <xsd:include schemaLocation="../XMLSchema/common_parameters.xsd" />
                    <xsd:include schemaLocation="../XMLSchema/common_authentication.xsd" />
                    <xsd:include schemaLocation="../XMLSchema/workflowSaveCreateProfile.xsd" />
          </xsd:schema>
          <xsd:schema targetNamespace="http://www.oblix.com/OblixXMLLocalSchema" xmlns:xsd="http://www.w3.org/2001/XMLSchema">
               <xsd:element name="request">
                    <xsd:complexType>
                         <xsd:sequence>
                              <xsd:element name="params">
                                   <xsd:complexType>
                                        <xsd:sequence>
                                             <xsd:element ref="oblix:ObWorkflowName"/>
                                             <xsd:element ref="oblix:ObDomainName"/>
                                             <xsd:element ref="oblix:ObWfComment" minOccurs="0"/>
                                             <xsd:element ref="oblix:noOfFields"/>
                                             <xsd:element ref="oblix:AttributeParams"/>
                                        </xsd:sequence>
                                   </xsd:complexType>
                              </xsd:element>
                         </xsd:sequence>
                         <xsd:attribute name="version" type="xsd:string" use="optional"/>
                         <xsd:attribute name="application" type="xsd:string" use="required" />
                         <xsd:attribute name="function" type="xsd:string" use="required" />
                         <xsd:attribute name="mode" type="xsd:string" use="optional"/>
                    </xsd:complexType>
               </xsd:element>
          </xsd:schema>
     </types>
     <message name="OblixIDXMLInput">
          <part name="authentication" element="oblix:authentication"/>
          <part name="request" element="oblixxmllocalschema:request"/>
     </message>
     <message name="OblixIDXMLOutput">
          <part name="body" element="oblix:Oblix"/>
     </message>
     <portType name="OblixIDXMLPortType">
          <operation name="OblixIDXML_um_workflowSaveCreateProfile">
               <input message="tns:OblixIDXMLInput"/>
               <output message="tns:OblixIDXMLOutput"/>
          </operation>
     </portType>
     <binding name="OblixIDXML_um_workflowSaveCreateProfile_Binding" type="tns:OblixIDXMLPortType">
          <soap:binding style="document" transport="http://schemas.xmlsoap.org/soap/http"/>
          <operation name="OblixIDXML_um_workflowSaveCreateProfile">
               <soap:operation soapAction="http://www.oblix.com/"/>
               <input>
                    <soap:body use="literal"/>
               </input>
               <output>
                    <soap:body use="literal"/>
               </output>
          </operation>
     </binding>
</definitions>
I am using WSDL2 Java for generating the client code .
Please suggest where am I wrong .
E:\axis2-1.4\bin>WSDL2Java -uri E:\DIPPWF\um_workflowSaveCreateProfile.wsdl -p R
ND -d adb -s -o build\client--http-proxy-host 10.74.93.35 --http-proxy-port 80
Using AXIS2_HOME: E:\axis2-1.4
Using JAVA_HOME: C:\Program Files\Java\jdk1.6.0_02
Retrieving document at 'E:\DIPPWF\um_workflowSaveCreateProfile.wsdl'.
Retrieving document at 'um_workflowSaveCreateProfile_interface.wsdl', relative t
o 'file:/E:/DIPPWF/um_workflowSaveCreateProfile.wsdl'.
Retrieving schema at 'E:/DIPPWF/XMLSchema/common_parameters.xsd', relative to 'f
ile:/E:/DIPPWF/um_workflowSaveCreateProfile_interface.wsdl'.
Retrieving schema at 'E:/DIPPWF/XMLSchema/common_authentication.xsd', relative t
o 'file:/E:/DIPPWF/um_workflowSaveCreateProfile_interface.wsdl'.
Retrieving schema at 'E:/DIPPWF/XMLSchema/workflowSaveCreateProfile.xsd', relati
ve to 'file:/E:/DIPPWF/um_workflowSaveCreateProfile_interface.wsdl'.
Retrieving schema at 'navbar.xsd', relative to 'file:/E:/DIPPWF/XMLSchema/workfl
owSaveCreateProfile.xsd'.
Retrieving schema at 'searchform.xsd', relative to 'file:/E:/DIPPWF/XMLSchema/wo
rkflowSaveCreateProfile.xsd'.
Retrieving schema at 'component_basic.xsd', relative to 'file:/E:/DIPPWF/XMLSche
ma/workflowSaveCreateProfile.xsd'.
Retrieving schema at 'displaytype.xsd', relative to 'file:/E:/DIPPWF/XMLSchema/c
omponent_basic.xsd'.
Retrieving schema at 'error.xsd', relative to 'file:/E:/DIPPWF/XMLSchema/compone
nt_basic.xsd'.
Retrieving schema at 'component_workflowTicket.xsd', relative to 'file:/E:/DIPPW
F/XMLSchema/workflowSaveCreateProfile.xsd'.
Retrieving document at 'E:\DIPPWF\um_workflowSaveCreateProfile.wsdl'.
Retrieving document at 'um_workflowSaveCreateProfile_interface.wsdl', relative t
o 'file:/E:/DIPPWF/um_workflowSaveCreateProfile.wsdl'.
Retrieving schema at 'E:/DIPPWF/XMLSchema/common_parameters.xsd', relative to 'f
ile:/E:/DIPPWF/um_workflowSaveCreateProfile_interface.wsdl'.
Retrieving schema at 'E:/DIPPWF/XMLSchema/common_authentication.xsd', relative t
o 'file:/E:/DIPPWF/um_workflowSaveCreateProfile_interface.wsdl'.
Retrieving schema at 'E:/DIPPWF/XMLSchema/workflowSaveCreateProfile.xsd', relati
ve to 'file:/E:/DIPPWF/um_workflowSaveCreateProfile_interface.wsdl'.
Retrieving schema at 'navbar.xsd', relative to 'file:/E:/DIPPWF/XMLSchema/workfl
owSaveCreateProfile.xsd'.
Retrieving schema at 'searchform.xsd', relative to 'file:/E:/DIPPWF/XMLSchema/wo
rkflowSaveCreateProfile.xsd'.
Retrieving schema at 'component_basic.xsd', relative to 'file:/E:/DIPPWF/XMLSche
ma/workflowSaveCreateProfile.xsd'.
Retrieving schema at 'displaytype.xsd', relative to 'file:/E:/DIPPWF/XMLSchema/c
omponent_basic.xsd'.
Retrieving schema at 'error.xsd', relative to 'file:/E:/DIPPWF/XMLSchema/compone
nt_basic.xsd'.
Retrieving schema at 'component_workflowTicket.xsd', relative to 'file:/E:/DIPPW
F/XMLSchema/workflowSaveCreateProfile.xsd'.
*[ERROR] More than one part for message OblixIDXMLInput*
org.apache.axis2.description.WSDL11ToAxisServiceBuilder$WSDLProcessingException:
More than one part for message OblixIDXMLInput
at org.apache.axis2.description.WSDL11ToAxisServiceBuilder.addQNameRefer
ence(WSDL11ToAxisServiceBuilder.java:1162)
at org.apache.axis2.description.WSDL11ToAxisServiceBuilder.addQNameRefer
ence(WSDL11ToAxisServiceBuilder.java:1085)
at org.apache.axis2.description.WSDL11ToAxisServiceBuilder.populateBindi
ng(WSDL11ToAxisServiceBuilder.java:686)
at org.apache.axis2.description.WSDL11ToAxisServiceBuilder.populateEndpo
int(WSDL11ToAxisServiceBuilder.java:538)
at org.apache.axis2.description.WSDL11ToAxisServiceBuilder.populateEndpo
ints(WSDL11ToAxisServiceBuilder.java:489)
at org.apache.axis2.description.WSDL11ToAxisServiceBuilder.populateServi
ce(WSDL11ToAxisServiceBuilder.java:363)
at org.apache.axis2.description.WSDL11ToAllAxisServicesBuilder.populateA
llServices(WSDL11ToAllAxisServicesBuilder.java:107)
at org.apache.axis2.wsdl.codegen.CodeGenerationEngine.<init>(CodeGenerat
ionEngine.java:147)
at org.apache.axis2.wsdl.WSDL2Code.main(WSDL2Code.java:35)
at org.apache.axis2.wsdl.WSDL2Java.main(WSDL2Java.java:24)
Exception in thread "main" org.apache.axis2.wsdl.codegen.CodeGenerationException
: Error parsing WSDL
at org.apache.axis2.wsdl.codegen.CodeGenerationEngine.<init>(CodeGenerat
ionEngine.java:153)
at org.apache.axis2.wsdl.WSDL2Code.main(WSDL2Code.java:35)
at org.apache.axis2.wsdl.WSDL2Java.main(WSDL2Java.java:24)
Caused by: org.apache.axis2.AxisFault: More than one part for message OblixIDXML
Input
at org.apache.axis2.AxisFault.makeFault(AxisFault.java:430)
at org.apache.axis2.description.WSDL11ToAxisServiceBuilder.populateServi
ce(WSDL11ToAxisServiceBuilder.java:397)
at org.apache.axis2.description.WSDL11ToAllAxisServicesBuilder.populateA
llServices(WSDL11ToAllAxisServicesBuilder.java:107)
at org.apache.axis2.wsdl.codegen.CodeGenerationEngine.<init>(CodeGenerat
ionEngine.java:147)
... 2 more
Caused by: org.apache.axis2.description.WSDL11ToAxisServiceBuilder$WSDLProcessin
gException: More than one part for message OblixIDXMLInput
at org.apache.axis2.description.WSDL11ToAxisServiceBuilder.addQNameRefer
ence(WSDL11ToAxisServiceBuilder.java:1162)
at org.apache.axis2.description.WSDL11ToAxisServiceBuilder.addQNameRefer
ence(WSDL11ToAxisServiceBuilder.java:1085)
at org.apache.axis2.description.WSDL11ToAxisServiceBuilder.populateBindi
ng(WSDL11ToAxisServiceBuilder.java:686)
at org.apache.axis2.description.WSDL11ToAxisServiceBuilder.populateEndpo
int(WSDL11ToAxisServiceBuilder.java:538)
at org.apache.axis2.description.WSDL11ToAxisServiceBuilder.populateEndpo
ints(WSDL11ToAxisServiceBuilder.java:489)
at org.apache.axis2.description.WSDL11ToAxisServiceBuilder.populateServi
ce(WSDL11ToAxisServiceBuilder.java:363).
Thanks in advance.
akshay

Hello,
Were you able to resolve this issue ?
I am seeing the same issue and at my wits end.
regards
Amit

Getting error while generating Business Blueprint Document for Project

Hello Experts,
I hv created a project in Solution manager 3.2 through solar_project_admin . Now iam in the phase of defining its Business Blueprint . I hv completed the steps, at the end when iam generating Business Blueprint document ,following error is being displayed:
<b>Blueprint document cannot be created. Check the selection
Message no. SOLAR110
Diagnosis
A Business Blueprint document created for the selected selection options would contain no structure elements. It would be empty, so it is not created.
Procedure
Choose less restrictive selection options, especially the option
"Print Structure Elements: Complete Selection" in the "Options" tab.</b>
I hv checked this error and the option displayed above in the error message but no such option is being displayed anywhere,can anyone plz help me out with how to resolve this problem?
Requested to revert at earliest as iam stuck with this since many days,My email id is <b>[email protected]</b> .
Regards,
Saumya

Hello Horst ,
Thanks for ur reply.I hv now again tried to Generate Blueprint Document with unselecting option Only with Documents but in the structure selection when i tick on all the options given in tat structure then regenerate Business blueprint Document ,following error message is displayed:
<b>Error 130: Business Blueprint cannot be generated
Message no. AI_SOLAR08130</b>
For this error no long text/ explaination exists .But when i try to generate Business Blueprint Document with unselecting option Only with Documents but in the structure selection unticking on all the options given in tat structure then following error message is displayed:
<b>Blueprint document cannot be created. Check the selection
Message no. SOLAR110
Diagnosis
A Business Blueprint document created for the selected selection options would contain no structure elements. It would be empty, so it is not created.
Procedure
Choose less restrictive selection options, especially the option
"Print Structure Elements: Complete Selection" in the "Options" tab.</b>
Plz revert back, wt shld i do now?
Regards,
Saumya

Error while generating stack.xml file in solman

Hi All,
I am unable to generate a stack.xml file in solman, below is the error.
Also, how to select a patch for Java stack JVM in solman. Please help me.
Thanks,
Dheeraj

Hi Kartik,
Thanks for the info.
I am trying to upgrade SAP JVM from 6.1.49 to 6.1.64,
I tried by manually downloading the file and upload it through SUM it was not successful.
Now I am trying with stack.xml and some product instance are not installed.
Any suggestions??
Regards,
Dheeraj

Error while generating an XML File.

Hello All,
Help me regarding My Doubt.
I have created a Procedure Which will create an XML File.
I am Using the XMLDOM Package to create the File.
I am passing the XMLFILE to a CLOB Field.
XMLDOM.writeToClob(DOC, P_XMLFILE);
But When I am Running the Procedure I am getting the List of Errors.
ORA-29280: invalid directory path
ORA-06512: at "SYS.UTL_FILE", line 33
ORA-06512: at "SYS.UTL_FILE", line 436
ORA-06512: at "XDB.DBMS_XSLPROCESSOR", line 217
ORA-29280: invalid directory path
ORA-29280: invalid directory path
ORA-06512: at "XDB.DBMS_XMLDOM", line 4416
ORA-06512: at "K5ESK_LDB2.PR_CREATE_XMLFILE", line 26
I dont know the Reason why the Errors are Comming.
Does It Require I should change the System Setting to Make sure that XMLDOM will work Properly

Dear Member,
The Below is the Code I am using.
CREATE OR REPLACE PROCEDURE pr_create_xmlfile(P_XMLFILE IN OUT CLOB)
doc xmldom.DOMDocument;
main_node xmldom.DOMNode;
root_node xmldom.DOMNode;
user_node xmldom.domnode;
item_node xmldom.domnode;
root_elmt xmldom.DOMElement;
item_elmt xmldom.DOMElement;
item_text xmldom.domtext;
CURSOR get_data(p_deptno IN NUMBER)
IS
SELECT EMPNO,
ENAME,
DEPTNO,
ROWNUM Rec_Num
FROM emp WHERE deptno = p_deptno;
BEGIN
doc := xmldom.newdomdocument;
-- Create the Main Node
main_node := xmldom.makenode(doc);
-- Create the Root Element.
root_elmt := xmldom.createelement(doc,'EMPSET');
-- Attach this Root Element to the Main Node.
root_node := xmldom.appendchild(main_node,xmldom.makenode(root_elmt));
xmldom.writetofile(doc,'c:\temp\test.xml');
xmldom.freedocument(doc);
FOR rec_data IN get_data(10) LOOP
<EMP num="1">
<EMP_NO>7782</EMP_NO>
<NAME>CLARK</NAME>
<DEPT_NO>10</DEPT_NO>
</EMP>
-- Create a Main Element
item_elmt := xmldom.createelement(doc,'EMP');
-- Creating an Attribute to the Emp Element
xmldom.setattribute(item_elmt,'Num',rec_data.rec_num);
-- Attaching this EMP Element as Child Record to the Root Node.
user_node := xmldom.appendchild(root_node,xmldom.makenode(item_elmt));
-- Creating another EMP_NO Element
item_elmt := xmldom.createelement(doc,'EMP_NO');
-- Attaching the EMP_NO Element to the EMP Element as Child Element
item_node := xmldom.appendchild(user_node,xmldom.makenode(item_elmt));
-- Creating a Text Node with the Empno data
item_text := xmldom.createtextnode(doc,rec_data.empno);
-- Attaching this Text Node as Child to the EMP_NO Element.
item_node := xmldom.appendchild(item_node,xmldom.makenode(item_text));
END LOOP;
XMLDOM.writeToClob(DOC, P_XMLFILE);
XMLDOM.FREEDOCUMENT(DOC);
Errors
ORA - 29280 --> A corresponding directory object does not exist.
Action --> Correct the directory object parameter, or create a corresponding directory object with the
CREATE DIRECTORY command
ORA - 06512 --> Backtrace message as the stack is unwound by unhandled exceptions
Action --> Fix the problem causing the exception or write an exception handler for this condition.
END;

Weblogic 8.1 :: Getting error while generating Client java class from WSDL

Hi,
For SOAP webservice, I am using ant script to generate java client from WSDL but getting below error. Please inform if any suggestion to resolve this.
Also let me know if any other alternative to generate client java code.
Ant script:
===========
<project name="project" default="generateClientJar">
     <property file="build.property">
     </property>
     <taskdef name="clientgen" classname="weblogic.ant.taskdefs.webservices.clientgen.ClientGenTask">
          <classpath>
               <fileset dir="${build_lib.dir}" includes="*.jar" />
          </classpath>
     </taskdef>
     <path id="compile_path">
          <pathelement location="C:/jar/wls-api.jar" />
          <pathelement location="${build_lib.dir}/weblogic.jar" />
          <pathelement location="C:/jar/webserviceclient+ssl.jar" />
          <pathelement location="D:/Java_Src_10.1.0/nextgen_arch/wlpatch/webservices.jar" />
     </path>
     <target name="generateClientJar" depends="generate.client">
<clientgen wsdl="${wsdl.file}" classpathref="compile_path"
serviceName="${service.name}"
packageName= "${client.pkg}"
clientJar="${ws.client.name}" />
     </target>
     <target name="generate.client" description="Generate web-services client">
          <property name="wsdl.file" value="${sms.wsdl.file}"/>
          <property name="client.pkg" value="${sms.client.pkg}"/>
          <property name="ws.client.name" value="${ws.sms.name}"/>
          <property name="service.name" value="${sms.service.name}"/>
     </target>
</project>
build.property file
===========
base=C:/SMS
lib=E:/jar_path
sms.wsdl.file=${base}/SMS.wsdl
sms.client.pkg=com.db.dbdi.gtbportal.sms.client
ws.sms.name=${lib}/ws_SmsService_client.jar
sms.service.name=SMSService
build_lib.dir = E:/jar_path
Error log:
================
Buildfile: D:\Java_Src_10.1.0\ant\build_weblogic8.xml
generate.client:
generateClientJar:
[clientgen] Generating client jar for C:/SMS/SMS.wsdl ...
[clientgen] C:\Documents and Settings\amitkumar.patel\Local Settings\Temp\ws_SmsService_client.jar699419996\com\db\dbdi\gtbportal\sms\client\SMSPort.java:15: parameters is already defined in sendSMS(com.db.portal.webservices.sms.SendSMS,com.db.portal.webservices.sms.holders.SendSMSResponseHolder)
[clientgen] public void sendSMS(com.db.portal.webservices.sms.SendSMS parameters, com.db.portal.webservices.sms.holders.SendSMSResponseHolder parameters)
[clientgen] ^
[clientgen] C:\Documents and Settings\amitkumar.patel\Local Settings\Temp\ws_SmsService_client.jar699419996\com\db\dbdi\gtbportal\sms\client\SMSPort.java:21: parameters is already defined in getStatus(com.db.portal.webservices.sms.GetStatus,com.db.portal.webservices.sms.holders.GetStatusResponseHolder)
[clientgen] public void getStatus(com.db.portal.webservices.sms.GetStatus parameters, com.db.portal.webservices.sms.holders.GetStatusResponseHolder parameters)
[clientgen] ^
[clientgen] C:\Documents and Settings\amitkumar.patel\Local Settings\Temp\ws_SmsService_client.jar699419996\com\db\dbdi\gtbportal\sms\client\SMSPort_Stub.java:20: parameters is already defined in sendSMS(com.db.portal.webservices.sms.SendSMS,com.db.portal.webservices.sms.holders.SendSMSResponseHolder)
[clientgen] public void sendSMS(com.db.portal.webservices.sms.SendSMS parameters, com.db.portal.webservices.sms.holders.SendSMSResponseHolder parameters)
[clientgen] ^
[clientgen] C:\Documents and Settings\amitkumar.patel\Local Settings\Temp\ws_SmsService_client.jar699419996\com\db\dbdi\gtbportal\sms\client\SMSPort_Stub.java:39: parameters is already defined in getStatus(com.db.portal.webservices.sms.GetStatus,com.db.portal.webservices.sms.holders.GetStatusResponseHolder)
[clientgen] public void getStatus(com.db.portal.webservices.sms.GetStatus parameters, com.db.portal.webservices.sms.holders.GetStatusResponseHolder parameters)
[clientgen] ^
[clientgen] Note: C:\Documents and Settings\amitkumar.patel\Local Settings\Temp\ws_SmsService_client.jar699419996\com\db\dbdi\gtbportal\sms\client\SMSService.java uses or overrides a deprecated API.
[clientgen] Note: Recompile with -deprecation for details.
[clientgen] 4 errors
*[*clientgen] java.io.IOException: Compiler failed executable.exec**
[clientgen] at weblogic.utils.compiler.CompilerInvoker.compileMaybeExit(CompilerInvoker.java:470)
[clientgen] at weblogic.utils.compiler.CompilerInvoker.compile(CompilerInvoker.java:328)
[clientgen] at weblogic.utils.compiler.CompilerInvoker.compile(CompilerInvoker.java:336)
[clientgen] at weblogic.webservice.tools.build.internal.CompilerHelper.compileFiles(CompilerHelper.java:80)
[clientgen] at weblogic.webservice.tools.build.internal.ClientGenImpl.compileStubs(ClientGenImpl.java:627)
[clientgen] at weblogic.webservice.tools.build.internal.ClientGenImpl.generateStub(ClientGenImpl.java:572)
[clientgen] at weblogic.webservice.tools.build.internal.ClientGenImpl.doClientGenFromWsdl(ClientGenImpl.java:409)
[clientgen] at weblogic.webservice.tools.build.internal.ClientGenImpl.run(ClientGenImpl.java:340)
[clientgen] at weblogic.ant.taskdefs.webservices.clientgen.ClientGenTask.doClientGen(ClientGenTask.java:351)
[clientgen] at weblogic.ant.taskdefs.webservices.clientgen.ClientGenTask.execute(ClientGenTask.java:208)
[clientgen] at org.apache.tools.ant.UnknownElement.execute(UnknownElement.java:275)
[clientgen] at org.apache.tools.ant.Task.perform(Task.java:364)
[clientgen] at org.apache.tools.ant.Target.execute(Target.java:341)
[clientgen] at org.apache.tools.ant.Target.performTasks(Target.java:369)
[clientgen] at org.apache.tools.ant.Project.executeSortedTargets(Project.java:1216)
[clientgen] at org.apache.tools.ant.Project.executeTarget(Project.java:1185)
[clientgen] at org.apache.tools.ant.helper.DefaultExecutor.executeTargets(DefaultExecutor.java:40)
[clientgen] at org.eclipse.ant.internal.ui.antsupport.EclipseDefaultExecutor.executeTargets(EclipseDefaultExecutor.java:32)
[clientgen] at org.apache.tools.ant.Project.executeTargets(Project.java:1068)
[clientgen] at org.eclipse.ant.internal.ui.antsupport.InternalAntRunner.run(InternalAntRunner.java:423)
[clientgen] at org.eclipse.ant.internal.ui.antsupport.InternalAntRunner.main(InternalAntRunner.java:137)
BUILD FAILED
D:\Java_Src_10.1.0\ant\build_weblogic8.xml:34: weblogic.webservice.tools.build.WSBuildException: Compiler failed executable.exec - with nested exception:
[java.io.IOException: Compiler failed executable.exec]
Total time: 1 minute 12 seconds

Hi,
Can u Please post the WSDL..here. I remember long back i resolved this kind of issue...when i was getting "*parameters is already defined in - - -*" while using ClientGen.
Once i will get the WSDL may be i can recall it...
If u have any problem in Posting the WSDL..in Forums .. then let me know I will send my E-Mail Address...
As far as i remember ..it usually happens when we Run ClientGen task of WLS81 ON the WebService/WSDL generated by WebLogic 9.x or Above. Please let me know if this is the Case with you as well... . I remember there is a Patch for it...for WLS8 ClientGen task...I dont remember the Patch Number Exactly.
Just For testing:
Just Use WLS9.x ClientGen task On the Same WSDL
<taskdef name="clientgen" classname="weblogic.wsee.tools.anttasks.ClientGenTask" />
I am sure you will not see this issue... because the issue is there only with WLS8 Clientgen...
Thanks
Jay SenSharma
http://jaysensharma.wordpress.com (WebLogic Wonders Are Here)
Edited by: Jay SenSharma on Jan 8, 2010 4:32 PM
Edited by: Jay SenSharma on Jan 8, 2010 4:34 PM

Error while generating a flat file from oracle database

i have imported three knowledge modules for the interafce.
LKM SQL to SQL
IKM SQL to FILE Append
CKM oracle
I have tried executing the interface in following ways
1. checked the staging area different from target and choosed SUNOPSIS_MEMORY_ENGINE. three boxes appeared in the flow but i could not see any of the knowledge modules in the flow and i could not select form the drop down also.
all the three boxes were showing the error.
2. checked the staging area different from target and choosed a oracle logical schema. my flow has two boxes.
For the source i have given LKM SQL to SQL and for target i have given IKM SQL to FILE append
But the interface is erroring out while creating the load table... the error message is missing parameter
IS there anything i have to do apart from this

if your file ouput file has Date field,Numeric field then there is a chance for failure. Try making all the output fields as Varchar2.
-app

Error while generating xml file Data Model

Hi ,
I am creating data mode in OBIEE through the query builder and trying to generate xml from it but the following exception occurs while generating the XML
"The XML page cannot be displayed
Cannot view XML input using XSL style sheet. Please correct the error and then click the Refresh button, or try again later.
The following tags were not closed: DATA_DS. Error processing resource 'http://localhost:7002/xmlpserver/servlet/xdo'. "
Could you please sort this out.
Thanks
Govindan P

Hi,
I found the issue and corrected it. :)
This was happened only because of the Version problem of Report Builder with Oracle Applications.
Reports Builder 10g is not compatiblie with Oracle Applications 11.5.10.
Oracle 11.5+ will always expect the RDF from Reports 6i version. Because of this, the endocing was damaged.
You can observe in the earlier post as encoding="&Endoding". Here +&Encoding should be replaced by some encoding mechanism like "UTF-8".+
Finally corrected the version and got the Output as expected.
Thanks !

Error while constructing multi-XML document (Multi Mapping)

Hi,
We are using Java mapping to split the messages and the same maping has been called in the Enchanced interface determination. The Jave mapping is executing successfully when we run in the Test tab of the interface mapping.
But we are getting error "Error while constructing multi-XML document", when we execute scenario from Runtime work bench or Test Configuration.
Could you advise whether we need to do any extra setting to execute the java mapping in the Enhanced Interface Determination.
Thanks,
Krishnaraju.
Edited by: krishnaraju Mudunuri on Jan 9, 2010 4:13 PM

refer - http://wiki.sdn.sap.com/wiki/display/Java/MultiMappingwithJavaandXSLTmappings
you need to have the messages tag.

Bursting Program errors with "Error while generating the Document"

Hello Folks
Here is my bursting control file
<?xml version="1.0" encoding="UTF-8"?>
<xapi:requestset xmlns:xapi="http://xmlns.oracle.com/oxp/xapi">
<xapi:globalData location="stream">
</xapi:globalData >
<xapi:request select="/XMLEXCEL1/LIST_G_Q0">
<xapi:delivery>
<xapi:email server="mycompany.com" port="25" from="[email protected]"
reply-to ="[email protected]">
<xapi:message id="1234" to="[email protected]"
attachment="true" content-type="html/text"
subject="Employee Report for Empno"> Dear
Please review the attached document</xapi:message>
</xapi:email>
</xapi:delivery>
<xapi:document key="123" output-type="XLS" delivery="1234"
output="XMLEXCEL1" >
<xapi:template type="RTF" location="xdo://AR.XMLEXCEL1.en.00/?getSource=true">
</xapi:template>
</xapi:document>
</xapi:request>
</xapi:requestset>
this is the output of bursting status report:
<?xml version="1.0" encoding="UTF-8"?>
<BURS_REPORT><REQUESTID>40403415</REQUESTID>
<PARENT_REQUESTID>40403339</PARENT_REQUESTID>
<REPORT_DESC>XMLEXCEL1</REPORT_DESC>
<OUTPUT_FILE>/opt/local/application/orafin/applmgr/out/outfaud/S1759.zip
</OUTPUT_FILE>
<DOCUMENT_STATUS>
<KEY>123</KEY>
<OUTPUT_TYPE>XLS</OUTPUT_TYPE>
<DELIVERY></DELIVERY>
<OUTPUT>
</OUTPUT>
<STATUS>fail</STATUS>
<LOG>Error while generating the Document...</LOG>
</DOCUMENT_STATUS>
</BURS_REPORT>
Can anyone help on this please.

can anyone help me?

Error while generating the Document... Bursting Status Report

Hey all,
I am getting some errors in a production environment when trying to burst out some invoice data.
This process has been pretty robust and out of 1000+ invoices a day, I can only find 4 that are failing regularily.
Why am I mentioning?, just to show that I am thinking this is a data issue, but just cannot see anything that stands out.
I can take the xml output and run it through my development suite on my local machine and all runs fine.
Just when it is running live through the db is when it fails.
Here is the Bursting output that shows the error....
<?xml version="1.0" encoding="UTF-8"?>
<BURS_REPORT>
<REQUESTID>27044820</REQUESTID>
<PARENT_REQUESTID>27044726</PARENT_REQUESTID>
<REPORT_DESC>Invoice Print Selected Invoices</REPORT_DESC>
<OUTPUT_FILE>[$OUT_DIR]/o27044820.zip</OUTPUT_FILE>
<DOCUMENT_STATUS>
<KEY></KEY>
<OUTPUT_TYPE>pdf</OUTPUT_TYPE>
<DELIVERY></DELIVERY>
<OUTPUT></OUTPUT>
<STATUS>fail</STATUS>
<LOG>Error while generating the Document...</LOG>
</DOCUMENT_STATUS>
</BURS_REPORT>
The problem is that this output doesn't necessarily help, nor can I find any hints in the OPP logs.
So... the question becomes...
Any ideas on where I can look to resolve this issue?+
Or where I can find any clues at, that would possible point at the issue?+
Oracle Database 10g Enterprise Edition Release 10.2.0.4.0 - 64bi
BI Publisher 5.6.3
Thanks
Hayden,

Tim,
Thanks for the suggestion, always seems to slip my mind that the Bursting Report has debug on it.
As far as what is generating the XML, it is oracle's standard, only slightly modified ... ;), invoice generating report, RAXINV_SEL.
Well RAXINV_SEL, or RAXINV_NEW, doesn't matter, same code, that is the executable.
I have turned on the debug, for both the source xml and the burst request, and unfortunately, still nothing stands out to me.
I was really expecting to see something in the burst log, pasted at the bottom...
but, it yet avoids me.
If I had to guess, I would bet the user went, in our terminology, "slashwit crazy", or example "model /w options", in some description.
But can't seem to find which field it is blowing up on, since we are catching these special characters in several places already, and slashwit is littered throughout the output.
I was also looking in the bursting control file for the special xml tags identified there, as those would require no slashes. But those are all clean.
Hayden,
XML Publisher: Version : 11.5.0
Copyright (c) 1979, 1999, Oracle Corporation. All rights reserved.
XDOBURSTREP module: XML Publisher Report Bursting Program
Current system time is 21-SEP-2009 10:43:12
XML/BI Publisher Version : 5.6.3
Request ID: 27048106
All Parameters: ReportRequestID=27044726:DebugFlag=Y
Report Req ID: 27044726
Debug Flag: Y
Updating request description
Updated description
Retrieving XML request information
Node Name:{node}
Preparing parameters
null output =/u007/app/applmgr/{instance}/out/{instance}/o27048106.out
inputfilename =/u007/app/applmgr/{instance}/out/{instance}/o27044726.out
Data XML File:/u007/app/applmgr/{instance}/out/{instance}/o27044726.out
Set Bursting parameters..
Temp. Directory:/u007/app/applmgr/{instance}/temp
[092109_104315337][][STATEMENT] Oracle XML Parser version ::: Oracle XDK Java 9.0.4.0.0 Production
[092109_104315340][][STATEMENT] setOAProperties called..
Bursting propertes.....
{burstng-source=EBS, font.Free 3 of 9.normal.normal=truetype./usr/java/jre/lib/fonts/FREE3OF9.TTF, font.Times New Roman.normal.normal=truetype./usr/java/jre/lib/fonts/TIMES.TTF, system-temp-dir=/u007/app/applmgr/{instance}/temp, font.Arial.italic.normal=truetype./usr/java/jre/lib/fonts/ARIALI.TTF, user-variable:cp:parent_request_id=27044726, user-variable:cp:application_short_name=XDO, font.Courier New.normal.bold=truetype./usr/java/jre/lib/fonts/COURBD.TTF, font.Times New Roman.normal.bold=truetype./usr/java/jre/lib/fonts/TIMESBD.TTF, user-variable:cp:request_id=27048106, font.Arial.normal.normal=truetype./usr/java/jre/lib/fonts/ARIAL.TTF, font.Courier New.normal.normal=truetype./usr/java/jre/lib/fonts/COUR.TTF, user-variable.OA_MEDIA=http://diierp.corio.com:8002/OA_MEDIA, font.Courier New.italic.bold=truetype./usr/java/jre/lib/fonts/COURBI.TTF, user-variable:cp:org_id=83, user-variable:cp:DebugFlag=Y, font.Times New Roman.italic.bold=truetype./usr/java/jre/lib/fonts/TIMESBI.TTF, user-variable:cp:responsibility=51270, font.Arial.italic.bold=truetype./usr/java/jre/lib/fonts/ARIALBI.TTF, font.Courier New.italic.normal=truetype./usr/java/jre/lib/fonts/COURI.TTF, user-variable:cp:user=HAYDEN, user-variable:cp:reportdescription=Invoice Print Selected Invoices, user-variable:cp:language=en, font.Times New Roman.italic.normal=truetype./usr/java/jre/lib/fonts/TIMESI.TTF, user-variable:cp:ReportRequestID=27044726, user-variable:cp:locale=en-US, user-variable:cp:territory=US, font.Arial.normal.bold=truetype./usr/java/jre/lib/fonts/ARIALBD.TTF}
Start bursting process..
Bursting process complete..
Generating Bursting Status Report..
Start of log messages from FND_FILE
End of log messages from FND_FILE
Executing request completion options...
------------- 1) PUBLISH -------------
Beginning post-processing of request 27048106 on node {node} at 21-SEP-2009 10:43:19.
Post-processing of request 27048106 completed at 21-SEP-2009 10:43:20.
Finished executing request completion options.
Concurrent request completed
Current system time is 21-SEP-2009 10:43:20
---------------------------------------------------------------------------

Bursting Program in error 'error while generating the document'

Hi All,
We have a requirement to place EXCEL output generated through BI XML report, in EBS path. ex: /usr/tmp
Parent Concurrent program is generating output file and program got completed normal and Bursting program got submitted.
But, Bursting program completing in error, saying 'Error While Generating Document'
Other programs which use Bursting are working normal and they are using same path (/usr/tmp)
Anyone faced similar issue ? Any sample bursting control file that sends .xls file will also be helpful.
Below is the bursting file that we created:
<xapi:requestset xmlns:xapi="http://xmlns.oracle.com/oxp/xapi" type="bursting">
<xapi:request select="/XXPREDICT/G_DATA_GROUP">
    <xapi:delivery/>
    <xapi:document output="/usr/tmp/XXYYZZ_${RUN_DATE}_${RUN_TIME}.xls" output-type="excel">
      <xapi:template type="xsl-fo" location="xdo://<APPLSHORTNAME>.<TEMPLATECODE>.en.US/?getSource=true" />
    </xapi:document>
</xapi:request>
</xapi:requestset>
P.S: When we give template type as 'rtf', then we are getting a different error i.e., "No such file or directory"
Regards,
Rupa

You should use:
<xapi:template type="rtf" location="CUSTOME_TOP_PATH/US/REPORT_RTF_NAME.rtf"/>
You need to check that there should rtf file present with the same name as you mentioned in above code. Also verify the port number.
Example:
<?xml version="1.0" encoding="US-ASCII"?>
<xapi:requestset xmlns:xapi="http://xmlns.oracle.com/oxp/xapi" type="bursting">
<xapi:request select="/DEBIT_MEMO/LIST_G_1/G_1">
<xapi:delivery>
<xapi:email id="123" server="localhost" port="1028" from="[email protected]" reply-to="[email protected]">
<xapi:message id="123" to="[email protected] ${EMAIL}" attachment="true" subject="Invoices for VENDOR_NO:${SEGMENT1} and Period ${CF_4}">
Please ignore this report.It is for Testing,For INVOICES of vendor ${VENDOR_NAME} for the Period ${CF_4}</xapi:message>
</xapi:email>
</xapi:delivery>
<xapi:document output="${SEGMENT1}||TSRL HM||${CF_4}" output-type="pdf" delivery="123">
<xapi:template type="rtf" location="/ebiz/app01/appldev/DEV/apps/apps_st/appl/xxabrl/12.0.0/reports/US/XXTSRL_DEBIT_CREDIT_MEMO_PRINT_LATEST_TSRL_HM.rtf">
</xapi:template>
</xapi:document>
</xapi:request>
</xapi:requestset>
HOP! it will help you.

"Error while parsing SOAP XML payload: no element found" received when invoking Web Service

Running PB 12.1 Build 7000. Using Easysoap. Error ""Error while parsing SOAP XML payload: no element found" received when invoking Web Service". This error does not appear to be coming from the application code. Noticed that there were some erroneous characters showing up within the header portion of the XML ("&Quot;"). Not sure where these are coming from. When I do a find within the PB code for """" it gets located within two objects, whereas they both reference a "temp_xml_letter". Not sure where or what temp_xml_letter resides???   The developer of this is no longer with us and my exposure to WSDL and Web Services is rather limited. Need to get this resolved...please.
This is the result of the search. Notice the extraneous characters ("""):
dar1main.pbl(d_as400_mq_xml)
darlettr.pbl(d_email_xml)
---------- Search: Searching Target darwin for 'temp_xml'    (9:52:41 AM)
---------- 2 Matches Found On "temp_xml":
dar1main.pbl(d_as400_mq_xml).d_as400_mq_xml: export.xml(usetemplate="temp_xml_letter" headgroups="1" includewhitespace="0" metadatatype=0 savemetadata=0 template=(comment="" encoding="UTF-8" name="temp_xml_letter" xml="<?xml version=~"1.0~" encoding=~"UTF-16LE~" standalone=~"yes~"?><EmailServiceTransaction xmlns=~"http://xml.xxnamespace.com/Utility/Email/EmailService" ~" xmlns:imc=~"http://xml.xxnamespace.com/IMC~" xmlns:xsi=~"http://www.w3.org/2001/XMLSchema-instance~" xmlns:root=~"http://xml.xxnamespace.com/RootTypes~" xmlns:email=~"http://xml.xxnamespace.com/Utility/Email~" xsi:schemaLocation=~"http://xml.xxnamespace.com/Utility/Email/EmailService http://dev.xxnamespace.com/Utility/Email/EmailService/V10-TRX-EmailService.xsd~"><EmailServiceInformation><EmailServiceDetail __pbband=~"detail~"><ApplicationIdentifier> applicationidentifier </ApplicationIdentifier><AddresseeInformation><AddresseeDetail><Number> number </Number></AddresseeDetail></AddresseeInformation><EmailMessageInformation><Ema
darlettr.pbl(d_email_xml).d_email_xml: export.xml(usetemplate="temp_xml_letter" headgroups="1" includewhitespace="0" metadatatype=0 savemetadata=0 template=(comment="" encoding="UTF-8" name="temp_xml_letter" xml="<?xml version=~"1.0~" encoding=~"UTF-16LE~" standalone=~"yes~"?><EmailServiceTransaction xmlns=~"http://xml.xxnamespace.com/Utility/Email/EmailService" ~" xmlns:imc=~"http://xml.xxnamespace.com/IMC~" xmlns:xsi=~"http://www.w3.org/2001/XMLSchema-instance~" xmlns:root=~"http://xml.xxnamespace.com/RootTypes~" xmlns:email=~"http://xml.xxnamespace.com/Utility/Email~" xsi:schemaLocation=~"http://xml.xxnamespace.com/Utility/Email/EmailService http://dev.xxnamespace.com/Utility/Email/EmailService/V10-TRX-EmailService.xsd~"><EmailServiceInformation><EmailServiceDetail __pbband=~"detail~"><ApplicationIdentifier> applicationidentifier </ApplicationIdentifier><AddresseeInformation><AddresseeDetail><Number> imcnumber </Number></AddresseeDetail></AddresseeInformation><EmailMessageInformation><Ema
---------- Done 2 Matches Found On "temp_xml":
---------- Finished Searching Target darwin for 'temp_xml'    (9:52:41 AM)

Maybe "extraneous" is an incorrect term. Apparantly, based upon the writeup within Wiki, the parser I am using does not interpret the """? How do I find which parser is being utilized and how to control it?
<<<
If the document is read by an XML parser that does not or cannot read external entities, then only the five built-in XML character entities (see above) can safely be used, although other entities may be used if they are declared in the internal DTD subset.
If the document is read by an XML parser that does read external entities, then the five built-in XML character entities can safely be used. The other 248 HTML character entities can be used as long as the XHTML DTD is accessible to the parser at the time the document is read. Other entities may also be used if they are declared in the internal DTD subset.
>>>

Error while generating an XML Document from XML Schema with JAXB

Similar Messages

Maybe you are looking for