Build.xml classpath ref to be used in another build XML file
Hi,
I have ant build.xml with a target as
<target name="build_project">
<ant antfile="C:/projects/antbuild/build.xml" inheritAll="true">
<target name="clean" />
</ant>
</target>
in report1.xml.
This build.xml inturn have the classpath defined in it with the JARS added to the classpath.
In the report2.xml,
Can I use the classpathref in build.xml which is defined in report2.xml? Where report2.xml is imported in report1.xml as
<import file="report2.xml" />
If I can do so I don't have to create duplicate class path ref again adding all the JARS in report2.xml?
Please clarify.
Thanks.
I've used quite a bit of ANT in the past, but I don't really know what to answer to your question that is in any way helpful to you. I remember that ANT has some form of build file inheritance built in, I've played around with it in years ago to try and crank out somewhat standardized build files with reusable elements. What I can recall is that I had to read a book on advanced ANT usage to be able to work it out, the online manual wasn't nearly enough.
Similar Messages
-
Calling XML Publisher Report from OAF using the conc programs xml output
Hi all
I am trying to call a report from oa Framework. I have developed the Template in the Ms-Word and for Generating the xml data i used the view object defined in OAF, this approach is working for me...i used the following code to do this in the AM as mentioned in many places...
public XMLNode getEmpDataXML()
OAViewObject vo = (OAViewObject)findViewObject("EmpVO1");
XMLNode xmlNode = (XMLNode) vo.writeXML(4, XMLInterface.XML_OPT_ALL_ROWS);
return xmlNode;
now i want that instead of the view object i should use the xml generated by the report which is registered as concurrnet program with output as xml.
I am submitting the concurrent program and able to get the request id ...
Now from here what should i do.. please suggest...Hi,
I am thinking of doing something very similar. What i was planning on doing is submitting the request, and then redirecting the user to the concurrent request page. They can then use the standard functionality to view output and get the xml to use the appropriate template.
i would be interested in how you get the concurrent request id from the submitted job.
Many thanks
Rupesh -
Problem with use utf8 words in xml
hi . today many components like Drop down menus and galleries and ... use dynamic data importin ( xml ) files ...
after i edit xml and put some utf8 words an save , when i test my swf i see nothing show in rows that i replace english data with other langauge ...
on some others i see unknown characters !!
whats the problem ?
the Xml file have :
<?xml version="1.0" encoding="UTF-8"?>
in header so why Flash cant act like Dreamweaver or webpage and ...
what setting i must change in my xml or Flash to enable use type unicode characters and langauges in xml files ?
thanks ...thanks for replay ...
what do you mean exactly ? copy my xml code here ? or use copy paste for xml ?!
For example this is one of my Xml :
<?xml version="1.0" encoding="utf-8"?>
<menu>
<menuItem title="منوی 1">
<subItem title="منو 2 " />
<subItem title="sub 2" >
<subSubItem title="sub sub 1" file="flv.flv" type="video"/>
<subSubItem title="sub sub 2" />
<subSubItem title="sub sub 3" />
</subItem>
<subItem title="sub 3" />
</menuItem>
<menuItem title="درباره ما">
<subItem title="Sub 1" >
<subSubItem title="sub sub 1" file="flv.flv" type="video"/>
<subSubItem title="sub sub 2" />
<subSubItem title="sub sub 3" />
</subItem>
<subItem title="sub 2" >
<subSubItem title="sub sub 1" file="flv.flv" type="video"/>
<subSubItem title="sub sub 2" />
<subSubItem title="sub sub 3" />
</subItem>
<subItem title="sub 3" />
</menuItem>
<menuItem title="Menu 3">
<subItem title="Sub 1" >
<subSubItem title="sub sub 1" file="flv.flv" type="video"/>
<subSubItem title="sub sub 2" />
<subSubItem title="sub sub 3" />
</subItem>
<subItem title="sub 2" >
<subSubItem title="sub sub 1" file="flv.flv" type="video"/>
<subSubItem title="sub sub 2" />
<subSubItem title="sub sub 3" />
</subItem>
<subItem title="sub 3">
<subSubItem title="sub sub 1" file="flv.flv" type="video"/>
<subSubItem title="sub sub 2" />
<subSubItem title="sub sub 3" />
</subItem>
</menuItem>
</menu>
for first and secound menu i can only see the numbers after save xml file -
What tools do you use for automating builds?
Hi all Build Engineers,
what systems do you use for automating builds - do you use your own tools, or some opensource project?
If it is something public, which one it is, and what were the reasons to chose it?
We are thinking about using the Hudson system (http://hudson.dev.java.net/) for our developers, but would like to hear from other RE groups about their experiences too.
Thanks,
KarelTinderbox is another build monitoring tool. It does not show detailed steps of a build cycle. It only shows the final result : success or failed. But it can display build output for multiple platforms on the same page.
This is how the tinderbox build grid will look --> http://tinderbox.mozilla.org/showbuilds.cgi?tree=SeaMonkey
Detail Info -->
http://www.mozilla.org/tinderbox.html
Tinderbox can be connected to Bonsai -->
It is a tool that shows you who checked in what, lets you perform queries on the contents of a CVS archive; get a list of checkins, see what checkins have been made by a whom, or on a given CVS branch, or in a particular time period.
Detail Info -->
http://www.mozilla.org/bonsai.html -
Using taglib in web.xml in WLS 9.2
I am trying to build a web application in which the JSPs refer to a JSF taglib at the following URI(http://java.sun.com/jsf/core). When i deploy the application in WLS 9.2 and attempt to load this JSP, WLS says that it is unable to resolve this taglib. I added the following to web.xml to help the application find the taglibs.
<taglib>
<taglib-uri>http://java.sun.com/jsf/core</taglib-uri>
<taglib-location>
/WEB-INF/jsf_core.tld
</taglib-location>
</taglib>
But now when i attempt to startup WLS, it looks like the appserver does not recognize the <taglib> as a valid element. It gives the following exception:
Expected elements 'description@http://java.sun.com/xml/ns/j2ee display-name@http://java.sun.com/xml/ns/j2ee
instead of 'taglib@http://java.sun.com/xml/ns/j2ee' here in element web-app@http://java.sun.com/xml/ns/j2ee
..." VALIDATION PROBLEMS WERE FOUND"
Any clues as to what i am doing wrong here since I have seen documentation which shows using taglib elements in web.xml.
Thanks
RamdasI figured out looking at one of the webapp samples that is packaged as part of WLS9.2 that the taglib element needs to be part of the jsp-config element.
-Ramdas -
How can I use a 3rd party XML parser such as xerces with OC4J ?
Hi all tech experts,
I am using Oracle Application Server 10g Release 2 (10.1.2) and i have
installed Portal and Wireless and OracleAS Infrastructure on the same
computer.
i tried all the solutions on this thread
Use of Xerces Parser in out application with Oracle App Server 9.0.4
but still fighting.
I have also posted this query on OTN on following thread
How can I use a 3rd party XML parser such as xerces with OC4J?
but no reply....
Please help me on this issue.
Since OC4J is preconfigured to use the Oracle XML parser which is xmlparserv2.jar.
i have read the following article which states that
OC4J is preconfigured to use the Oracle XML parser. The Oracle XML parser is fully JAXP 1.1 compatible and will serve the needs of applications which require JAXP functionality. This approach does not require the download, installation, and configuration of additional XML parsers.
The Oracle XML parser (xmlparserv2.jar) is configured to load as a system level library of OC4J through it's inclusion as an entry in the Class-Path entry of the oc4j.jar Manifest.mf file. This results in the Oracle XML parser being used for all common deployment and packaging situations. You are not permitted to modify the Manifest.mf file of oc4j.jar.
It must be noted that configuring OC4J to run with any additional XML parser or JDBC library is not a supported configuration. We do know customers who have managed to successfully replace the system level XML parser and the Oracle JDBC drivers that ship with the product, but we do not support this type of configuration due to the possibility of unexpected system behavior and system errors that might occur from replacing the tested and certified libraries.
If you absolutely must use an additional XML parser such as xerces, then you have to start OC4J such that the xerces.jar file is loaded at a level above the OC4J system classpath. This can be accomplished using the -Xbootclasspath flag of the JRE.
i have also run the following command
java -Xbootclasspath/a:d:\xerces\xerces.jar -jar oc4j.jar
but no success.
How could i utilize my jar's like xerces.jar and xalan.jar for parsing instead of OC4J in-built parser ?
All reply will be highly appreciated.
Thnx in advance to all.
Neeraj Sidhaye
try_catch_finally @ Y !Hi Neeraj Sidhaye,
I am trying to deploy a sample xform application to the Oracle Application Server (10.1.3). However, I encountered the class loader issue that is similar to your stuation. I tried all the three solutions but the application is still use the Oracle xml paser class. I am wondering if you have any insight about this?
Thanks for your help.
Xingsheng Qian
iPass Inc.
Here is the error message I got.
Message:
java.lang.ClassCastException: oracle.xml.parser.v2.XMLElement
Stack Trace:
org.chiba.xml.xforms.exception.XFormsException: java.lang.ClassCastException: oracle.xml.parser.v2.XMLElement
at org.chiba.xml.xforms.Container.dispatch(Unknown Source)
at org.chiba.xml.xforms.Container.dispatch(Unknown Source)
at org.chiba.xml.xforms.Container.initModels(Unknown Source)
at org.chiba.xml.xforms.Container.init(Unknown Source)
at org.chiba.xml.xforms.ChibaBean.init(Unknown Source)
at org.chiba.adapter.servlet.ServletAdapter.init(ServletAdapter.java:153)
at org.chiba.adapter.servlet.ChibaServlet.doGet(ChibaServlet.java:303)
at javax.servlet.http.HttpServlet.service(HttpServlet.java:743)
at javax.servlet.http.HttpServlet.service(HttpServlet.java:856)
at com.evermind.server.http.ServletRequestDispatcher.invoke(ServletRequestDispatcher.java:719)
at com.evermind.server.http.ServletRequestDispatcher.forwardInternal(ServletRequestDispatcher.java:376)
at com.evermind.server.http.HttpRequestHandler.doProcessRequest(HttpRequestHandler.java:870)
at com.evermind.server.http.HttpRequestHandler.processRequest(HttpRequestHandler.java:451)
at com.evermind.server.http.AJPRequestHandler.run(AJPRequestHandler.java:299)
at com.evermind.server.http.AJPRequestHandler.run(AJPRequestHandler.java:187)
at oracle.oc4j.network.ServerSocketReadHandler$SafeRunnable.run(ServerSocketReadHandler.java:260)
at com.evermind.util.ReleasableResourcePooledExecutor$MyWorker.run(ReleasableResourcePooledExecutor.java:303)
at java.lang.Thread.run(Thread.java:595)
Caused by: java.lang.ClassCastException: oracle.xml.parser.v2.XMLElement
at org.chiba.xml.xforms.Instance.iterateModelItems(Unknown Source)
at org.chiba.xml.xforms.Bind.initializeModelItems(Unknown Source)
at org.chiba.xml.xforms.Bind.init(Unknown Source)
at org.chiba.xml.xforms.Initializer.initializeBindElements(Unknown Source)
at org.chiba.xml.xforms.Model.modelConstruct(Unknown Source)
at org.chiba.xml.xforms.Model.performDefault(Unknown Source)
at org.chiba.xml.xforms.XFormsDocument.performDefault(Unknown Source)
at org.chiba.xml.xforms.XFormsDocument.dispatchEvent(Unknown Source)
at org.apache.xerces.dom.NodeImpl.dispatchEvent(Unknown Source)
... 18 more -
How to Build a DC project that makes use of other Projects??
Hi all,
I am trying to build a DC project that makes use of two other projects in my workspace, one is a java class project, the other one is a EJB project where it takes care of database access.
if i right click on the Application and use "Deploy new Archive and Run" it deploys and runs ok.
but if i right click on the DC project and use "Development Component -> Build", it gives me a lot of errors like below, as if it doesn't know where my reference projects are, but i have set them into my java build path.
Can anyone give me some advice?
Thanks.
Here comes the error msg:
008-11-26 14:52:42 /userOut/Development Component (com.sap.ide.eclipse.component.provider.listener.DevConfListener) [Thread[ModalContext,5,main]] ERROR: test2: Build failed for ecenta.com/test2(MyComponents) in variant "default": The Build terminated with errors
------------------------------------- Build log ------------------------------------------------------
Development Component Build (2008-11-26 14:52:40)
Component name: test2
Component vendor: ecenta.com
SC compartment: MyComponents
Configuration: LocalDevelopment
Location: local
Source code location: ecenta03@LENOVO-73231993
DC root folder: C:\Documents and Settings\ecenta03\.dtc\LocalDevelopment\DCs\ecenta.com\test2\_comp\
DC type: Web Dynpro
Host: LENOVO-73231993
DC Model check:
All used DCs are available locally
validating dependency to build plugin "sap.com/tc/bi/bp/webDynpro"
validating dependency to public part "default" of DC "sap.com/tc/cmi"
validating dependency to public part "default" of DC "sap.com/tc/ddic/ddicruntime"
validating dependency to public part "default" of DC "sap.com/tc/ddic/metamodel/content"
validating dependency to public part "default" of DC "sap.com/tc/wd/webdynpro"
validating dependency to public part "default" of DC "sap.com/tc/logging"
validating dependency to public part "default" of DC "sap.com/tc/wdp/metamodel/content"
validating dependency to public part "default" of DC "sap.com/com.sap.aii.proxy.framework"
validating dependency to public part "default" of DC "sap.com/com.sap.aii.util.misc"
validating dependency to public part "default" of DC "sap.com/com.sap.exception"
validating dependency to public part "default" of DC "sap.com/com.sap.mw.jco"
validating dependency to used DC "sap.com/com.sap.security.api.sda"
validating dependency to public part "JxlLibAssembly" of DC "ecenta.com/jxl/jar"
validating dependency to public part "JxlLibCompilation" of DC "ecenta.com/jxl/jar"
DC model check OK
Start build plugin:
using build plugin: sap.com/tc/bi/bp/webDynpro
starting build plugin from : D:\Program Files\SAP\IDE\IDE70\eclipse\plugins\com.sap.tc.ap_2.0.0\comp\SAP_BUILDT\DCs\sap.com\tc\bi\bp\webDynpro\_comp\gen\default\public\webDynpro\
Build Plugin 'WebdynproPlugin', Version 7.00 SP 14 (645_VAL_REL, built on 2007-11-10 18:28:29 CET, CL76041)
development component: test2 (ecenta.com)
software component: MyComponents (demo.sap.com)
location: local
type: Web Dynpro
build variant: default
output location: C:\Documents and Settings\ecenta03\.dtc\LocalDevelopment\DCs\ecenta.com\test2\_comp\gen\default
generation folder: C:\Documents and Settings\ecenta03\.dtc\LocalDevelopment\t\0EAFE51A1CEEAA916A875CFE652599FE
plugin start time: 2008-11-26 14:52:40 GMT+08:00 (CST)
Java VM: Java HotSpot(TM) Client VM, 1.4.2_18-b06 (Sun Microsystems Inc.)
General options:
convert *.xlf to *.properties: yes
include sources for debugging: yes
Warning: Source folder "META-INF" exists but is empty and will be ignored.
Checking path lengths for sources
Path length checks finished in 0.016 seconds
Preparing data context..
No public part descriptor found for component "tc/cmi" (vendor "sap.com"), public part "default", using legacy mode.
No public part descriptor found for component "tc/ddic/ddicruntime" (vendor "sap.com"), public part "default", using legacy mode.
No public part descriptor found for component "tc/ddic/metamodel/content" (vendor "sap.com"), public part "default", using legacy mode.
No public part descriptor found for component "tc/wd/webdynpro" (vendor "sap.com"), public part "default", using legacy mode.
No public part descriptor found for component "tc/logging" (vendor "sap.com"), public part "default", using legacy mode.
No public part descriptor found for component "tc/wdp/metamodel/content" (vendor "sap.com"), public part "default", using legacy mode.
No public part descriptor found for component "com.sap.aii.proxy.framework" (vendor "sap.com"), public part "default", using legacy mode.
No public part descriptor found for component "com.sap.aii.util.misc" (vendor "sap.com"), public part "default", using legacy mode.
No public part descriptor found for component "com.sap.exception" (vendor "sap.com"), public part "default", using legacy mode.
No public part descriptor found for component "com.sap.mw.jco" (vendor "sap.com"), public part "default", using legacy mode.
No public part descriptor found for component "com.sap.security.api.sda" (vendor "sap.com"), public part "default", using legacy mode.
No 'default' JDK defined, will use running VM.
Data context preparation finished in 0.078 seconds
Creating Ant build file..
Creating output file: C:\Documents and Settings\ecenta03\.dtc\LocalDevelopment\DCs\ecenta.com\test2\_comp\gen\default\logs\build.xml
Using macro file: D:\Program Files\SAP\IDE\IDE70\eclipse\plugins\com.sap.tc.ap_2.0.0\comp\SAP_BUILDT\DCs\sap.com\tc\bi\bp\webDynpro\_comp\gen\default\public\webDynpro\macros\build.vm
Build file creation finished in 0.109 seconds
Starting Ant..
Using build file: C:\Documents and Settings\ecenta03\.dtc\LocalDevelopment\DCs\ecenta.com\test2\_comp\gen\default\logs\build.xml
Using build target: build
Using Ant version: 1.6.2
compile:
[echo] Starting dictionary generator
[ddgen]
[ddgen] [Info] Property deployment is true: Deployment information is provided!
[ddgen] [Info] Property sourcepath: C:\Documents and Settings\ecenta03\.dtc\LocalDevelopment\DCs\ecenta.com\test2\_comp\src\packages
[ddgen] [Info] Property targetpath: C:\Documents and Settings\ecenta03\.dtc\LocalDevelopment\t\0EAFE51A1CEEAA916A875CFE652599FE\gen_ddic
[ddgen] [Info] Property archivename: ecenta.com~test2
[ddgen] [Info] Property vendor: ecenta.com
[ddgen] [Info] Property dcname: test2
[ddgen] [Info] Property projectlanguage: zh_CN
[ddgen] [Info] Property language: Available languages are automatically determined!
[ddgen] [Info] Property addpaths ...
[ddgen] [Info] SapMetamodelWebdynproContent.zip - D:/Program Files/SAP/IDE/IDE70/eclipse/plugins/com.sap.tc.ap_2.0.0/comp/SAP_BUILDT/DCs/sap.com/tc/bi/extwd/_comp/gen/default/public/def/lib/model
[ddgen] [Info] SapMetamodelDictionaryContent.zip - D:/Program Files/SAP/IDE/IDE70/eclipse/plugins/com.sap.tc.ap_2.0.0/comp/SAP_BUILDT/DCs/sap.com/tc/bi/extddic/_comp/gen/default/public/def/lib/model
[ddgen] [Info] aii_util_misc.jar - D:/Program Files/SAP/IDE/IDE70/eclipse/plugins/com.sap.tc.ap_2.0.0/comp/SAP_JTECHS/DCs/sap.com/com.sap.aii.util.misc/_comp/gen/default/public/default/lib/java
[ddgen] [Info] _cmi_api.jar - D:/Program Files/SAP/IDE/IDE70/eclipse/plugins/com.sap.tc.ap_2.0.0/comp/SAP_JTECHS/DCs/sap.com/tc/cmi/_comp/gen/default/public/default/lib/java
[ddgen] [Info] exception.jar - D:/Program Files/SAP/IDE/IDE70/eclipse/plugins/com.sap.tc.ap_2.0.0/comp/SAP-JEE/DCs/sap.com/com.sap.exception/_comp/gen/default/public/default/lib/java
[ddgen] [Info] SapMetamodelWebdynproContent.zip - D:/Program Files/SAP/IDE/IDE70/eclipse/plugins/com.sap.tc.ap_2.0.0/comp/SAP_JTECHS/DCs/sap.com/tc/wdp/metamodel/content/_comp/gen/default/public/default/lib/java
[ddgen] [Info] logging.jar - D:/Program Files/SAP/IDE/IDE70/eclipse/plugins/com.sap.tc.ap_2.0.0/comp/SAP-JEE/DCs/sap.com/tc/logging/_comp/gen/default/public/default/lib/java
[ddgen] [Info] logging.perf.jar - D:/Program Files/SAP/IDE/IDE70/eclipse/plugins/com.sap.tc.ap_2.0.0/comp/SAP-JEE/DCs/sap.com/tc/logging/_comp/gen/default/public/default/lib/java
[ddgen] [Info] _webdynpro_admin.jar - D:/Program Files/SAP/IDE/IDE70/eclipse/plugins/com.sap.tc.ap_2.0.0/comp/SAP-JEE/DCs/sap.com/tc/wd/webdynpro/_comp/gen/default/public/default/lib/java
[ddgen] [Info] _webdynpro_basesrvc.jar - D:/Program Files/SAP/IDE/IDE70/eclipse/plugins/com.sap.tc.ap_2.0.0/comp/SAP-JEE/DCs/sap.com/tc/wd/webdynpro/_comp/gen/default/public/default/lib/java
[ddgen] [Info] _webdynpro_runtime_repository.jar - D:/Program Files/SAP/IDE/IDE70/eclipse/plugins/com.sap.tc.ap_2.0.0/comp/SAP-JEE/DCs/sap.com/tc/wd/webdynpro/_comp/gen/default/public/default/lib/java
[ddgen] [Info] _webdynpro_runtime_repository_pmr.jar - D:/Program Files/SAP/IDE/IDE70/eclipse/plugins/com.sap.tc.ap_2.0.0/comp/SAP-JEE/DCs/sap.com/tc/wd/webdynpro/_comp/gen/default/public/default/lib/java
[ddgen] [Info] _webdynpro_services.jar - D:/Program Files/SAP/IDE/IDE70/eclipse/plugins/com.sap.tc.ap_2.0.0/comp/SAP-JEE/DCs/sap.com/tc/wd/webdynpro/_comp/gen/default/public/default/lib/java
[ddgen] [Info] _webdynpro_clientserver.jar - D:/Program Files/SAP/IDE/IDE70/eclipse/plugins/com.sap.tc.ap_2.0.0/comp/SAP-JEE/DCs/sap.com/tc/wd/webdynpro/_comp/gen/default/public/default/lib/java
[ddgen] [Info] _webdynpro_model_dynamicrfc.jar - D:/Program Files/SAP/IDE/IDE70/eclipse/plugins/com.sap.tc.ap_2.0.0/comp/SAP-JEE/DCs/sap.com/tc/wd/webdynpro/_comp/gen/default/public/default/lib/java
[ddgen] [Info] _webdynpro_modelimpl.jar - D:/Program Files/SAP/IDE/IDE70/eclipse/plugins/com.sap.tc.ap_2.0.0/comp/SAP-JEE/DCs/sap.com/tc/wd/webdynpro/_comp/gen/default/public/default/lib/java
[ddgen] [Info] _webdynpro_pdfobject.jar - D:/Program Files/SAP/IDE/IDE70/eclipse/plugins/com.sap.tc.ap_2.0.0/comp/SAP-JEE/DCs/sap.com/tc/wd/webdynpro/_comp/gen/default/public/default/lib/java
[ddgen] [Info] _webdynpro_portal.jar - D:/Program Files/SAP/IDE/IDE70/eclipse/plugins/com.sap.tc.ap_2.0.0/comp/SAP-JEE/DCs/sap.com/tc/wd/webdynpro/_comp/gen/default/public/default/lib/java
[ddgen] [Info] _webdynpro_progmodel.jar - D:/Program Files/SAP/IDE/IDE70/eclipse/plugins/com.sap.tc.ap_2.0.0/comp/SAP-JEE/DCs/sap.com/tc/wd/webdynpro/_comp/gen/default/public/default/lib/java
[ddgen] [Info] _webdynpro_runtime_designtime_coupling.jar - D:/Program Files/SAP/IDE/IDE70/eclipse/plugins/com.sap.tc.ap_2.0.0/comp/SAP-JEE/DCs/sap.com/tc/wd/webdynpro/_comp/gen/default/public/default/lib/java
[ddgen] [Info] _webdynpro_runtime_designtime_coupling_api.jar - D:/Program Files/SAP/IDE/IDE70/eclipse/plugins/com.sap.tc.ap_2.0.0/comp/SAP-JEE/DCs/sap.com/tc/wd/webdynpro/_comp/gen/default/public/default/lib/java
[ddgen] [Info] SapMetamodelDictionaryContent.zip - D:/Program Files/SAP/IDE/IDE70/eclipse/plugins/com.sap.tc.ap_2.0.0/comp/SAP_JTECHS/DCs/sap.com/tc/ddic/metamodel/content/_comp/gen/default/public/default/lib/java
[ddgen] [Info] jdsr.jar - D:/Program Files/SAP/IDE/IDE70/eclipse/plugins/com.sap.tc.ap_2.0.0/comp/SAP-JEE/DCs/sap.com/com.sap.mw.jco/_comp/gen/default/public/default/lib/java
[ddgen] [Info] jrfc.jar - D:/Program Files/SAP/IDE/IDE70/eclipse/plugins/com.sap.tc.ap_2.0.0/comp/SAP-JEE/DCs/sap.com/com.sap.mw.jco/_comp/gen/default/public/default/lib/java
[ddgen] [Info] SapDictionaryTypeServices.jar - D:/Program Files/SAP/IDE/IDE70/eclipse/plugins/com.sap.tc.ap_2.0.0/comp/SAP_JTECHS/DCs/sap.com/tc/ddic/ddicruntime/_comp/gen/default/public/default/lib/java
[ddgen] [Info] SapDictionaryTypesRuntime.jar - D:/Program Files/SAP/IDE/IDE70/eclipse/plugins/com.sap.tc.ap_2.0.0/comp/SAP_JTECHS/DCs/sap.com/tc/ddic/ddicruntime/_comp/gen/default/public/default/lib/java
[ddgen] [Info] aii_proxy_rt.jar - D:/Program Files/SAP/IDE/IDE70/eclipse/plugins/com.sap.tc.ap_2.0.0/comp/SAP_JTECHS/DCs/sap.com/com.sap.aii.proxy.framework/_comp/gen/default/public/default/lib/java
[ddgen] [Info] jxl.jar - C:/Documents and Settings/ecenta03/.dtc/LocalDevelopment/DCs/ecenta.com/jxl/jar/_comp/gen/default/public/JxlLibCompilation/lib/java
[ddgen] [Info] com.sap.security.api.jar - D:/Program Files/SAP/IDE/IDE70/eclipse/plugins/com.sap.tc.ap_2.0.0/comp/SAP-JEE/DCs/sap.com/com.sap.security.api.sda/_comp/gen/default/public/default/lib/java
[ddgen] [Info] com.sap.security.api.perm.jar - D:/Program Files/SAP/IDE/IDE70/eclipse/plugins/com.sap.tc.ap_2.0.0/comp/SAP-JEE/DCs/sap.com/com.sap.security.api.sda/_comp/gen/default/public/default/lib/java
[ddgen] [Info] Initialize generation templates from configuration jar:file:/D:/Program Files/SAP/IDE/IDE70/eclipse/plugins/com.sap.tc.ap_2.0.0/comp/SAP_BUILDT/DCs/sap.com/tc/bi/extddic/_comp/gen/default/public/def/lib/java/SapDictionaryGenerationCore.jar!/DictionaryGenerationConfigurationCompiled.xml
[ddgen] [Info] Generating dbtables/sdmDeployDd.xml
[ddgen] [Info] Generation finished (0 seconds)
[ddgen]
[timer] Dictionary generator finished in 0.469 seconds
[mkdir] Created dir: C:\Documents and Settings\ecenta03\.dtc\LocalDevelopment\t\0EAFE51A1CEEAA916A875CFE652599FE\gen_ddic\datatypes
[echo] Starting WebDynpro generator
[wdgen]
[wdgen] [Info] Property deployment is true: Deployment information is provided!
[wdgen] [Info] Property sourcepath: C:\Documents and Settings\ecenta03\.dtc\LocalDevelopment\DCs\ecenta.com\test2\_comp\src\packages
[wdgen] [Info] Property targetpath: C:\Documents and Settings\ecenta03\.dtc\LocalDevelopment\t\0EAFE51A1CEEAA916A875CFE652599FE\gen_wdp
[wdgen] [Info] Property archivename: ecenta.com~test2
[wdgen] [Info] Property vendor: ecenta.com
[wdgen] [Info] Property dcname: test2
[wdgen] [Info] Property projectlanguage: zh_CN
[wdgen] [Info] Property language: Available languages are automatically determined!
[wdgen] [Info] Property addpaths ...
[wdgen] [Info] SapMetamodelWebdynproContent.zip - D:/Program Files/SAP/IDE/IDE70/eclipse/plugins/com.sap.tc.ap_2.0.0/comp/SAP_BUILDT/DCs/sap.com/tc/bi/extwd/_comp/gen/default/public/def/lib/model
[wdgen] [Info] SapMetamodelDictionaryContent.zip - D:/Program Files/SAP/IDE/IDE70/eclipse/plugins/com.sap.tc.ap_2.0.0/comp/SAP_BUILDT/DCs/sap.com/tc/bi/extddic/_comp/gen/default/public/def/lib/model
[wdgen] [Info] aii_util_misc.jar - D:/Program Files/SAP/IDE/IDE70/eclipse/plugins/com.sap.tc.ap_2.0.0/comp/SAP_JTECHS/DCs/sap.com/com.sap.aii.util.misc/_comp/gen/default/public/default/lib/java
[wdgen] [Info] _cmi_api.jar - D:/Program Files/SAP/IDE/IDE70/eclipse/plugins/com.sap.tc.ap_2.0.0/comp/SAP_JTECHS/DCs/sap.com/tc/cmi/_comp/gen/default/public/default/lib/java
[wdgen] [Info] exception.jar - D:/Program Files/SAP/IDE/IDE70/eclipse/plugins/com.sap.tc.ap_2.0.0/comp/SAP-JEE/DCs/sap.com/com.sap.exception/_comp/gen/default/public/default/lib/java
[wdgen] [Info] SapMetamodelWebdynproContent.zip - D:/Program Files/SAP/IDE/IDE70/eclipse/plugins/com.sap.tc.ap_2.0.0/comp/SAP_JTECHS/DCs/sap.com/tc/wdp/metamodel/content/_comp/gen/default/public/default/lib/java
[wdgen] [Info] logging.jar - D:/Program Files/SAP/IDE/IDE70/eclipse/plugins/com.sap.tc.ap_2.0.0/comp/SAP-JEE/DCs/sap.com/tc/logging/_comp/gen/default/public/default/lib/java
[wdgen] [Info] logging.perf.jar - D:/Program Files/SAP/IDE/IDE70/eclipse/plugins/com.sap.tc.ap_2.0.0/comp/SAP-JEE/DCs/sap.com/tc/logging/_comp/gen/default/public/default/lib/java
[wdgen] [Info] _webdynpro_admin.jar - D:/Program Files/SAP/IDE/IDE70/eclipse/plugins/com.sap.tc.ap_2.0.0/comp/SAP-JEE/DCs/sap.com/tc/wd/webdynpro/_comp/gen/default/public/default/lib/java
[wdgen] [Info] _webdynpro_basesrvc.jar - D:/Program Files/SAP/IDE/IDE70/eclipse/plugins/com.sap.tc.ap_2.0.0/comp/SAP-JEE/DCs/sap.com/tc/wd/webdynpro/_comp/gen/default/public/default/lib/java
[wdgen] [Info] _webdynpro_runtime_repository.jar - D:/Program Files/SAP/IDE/IDE70/eclipse/plugins/com.sap.tc.ap_2.0.0/comp/SAP-JEE/DCs/sap.com/tc/wd/webdynpro/_comp/gen/default/public/default/lib/java
[wdgen] [Info] _webdynpro_runtime_repository_pmr.jar - D:/Program Files/SAP/IDE/IDE70/eclipse/plugins/com.sap.tc.ap_2.0.0/comp/SAP-JEE/DCs/sap.com/tc/wd/webdynpro/_comp/gen/default/public/default/lib/java
[wdgen] [Info] _webdynpro_services.jar - D:/Program Files/SAP/IDE/IDE70/eclipse/plugins/com.sap.tc.ap_2.0.0/comp/SAP-JEE/DCs/sap.com/tc/wd/webdynpro/_comp/gen/default/public/default/lib/java
[wdgen] [Info] _webdynpro_clientserver.jar - D:/Program Files/SAP/IDE/IDE70/eclipse/plugins/com.sap.tc.ap_2.0.0/comp/SAP-JEE/DCs/sap.com/tc/wd/webdynpro/_comp/gen/default/public/default/lib/java
[wdgen] [Info] _webdynpro_model_dynamicrfc.jar - D:/Program Files/SAP/IDE/IDE70/eclipse/plugins/com.sap.tc.ap_2.0.0/comp/SAP-JEE/DCs/sap.com/tc/wd/webdynpro/_comp/gen/default/public/default/lib/java
[wdgen] [Info] _webdynpro_modelimpl.jar - D:/Program Files/SAP/IDE/IDE70/eclipse/plugins/com.sap.tc.ap_2.0.0/comp/SAP-JEE/DCs/sap.com/tc/wd/webdynpro/_comp/gen/default/public/default/lib/java
[wdgen] [Info] _webdynpro_pdfobject.jar - D:/Program Files/SAP/IDE/IDE70/eclipse/plugins/com.sap.tc.ap_2.0.0/comp/SAP-JEE/DCs/sap.com/tc/wd/webdynpro/_comp/gen/default/public/default/lib/java
[wdgen] [Info] _webdynpro_portal.jar - D:/Program Files/SAP/IDE/IDE70/eclipse/plugins/com.sap.tc.ap_2.0.0/comp/SAP-JEE/DCs/sap.com/tc/wd/webdynpro/_comp/gen/default/public/default/lib/java
[wdgen] [Info] _webdynpro_progmodel.jar - D:/Program Files/SAP/IDE/IDE70/eclipse/plugins/com.sap.tc.ap_2.0.0/comp/SAP-JEE/DCs/sap.com/tc/wd/webdynpro/_comp/gen/default/public/default/lib/java
[wdgen] [Info] _webdynpro_runtime_designtime_coupling.jar - D:/Program Files/SAP/IDE/IDE70/eclipse/plugins/com.sap.tc.ap_2.0.0/comp/SAP-JEE/DCs/sap.com/tc/wd/webdynpro/_comp/gen/default/public/default/lib/java
[wdgen] [Info] _webdynpro_runtime_designtime_coupling_api.jar - D:/Program Files/SAP/IDE/IDE70/eclipse/plugins/com.sap.tc.ap_2.0.0/comp/SAP-JEE/DCs/sap.com/tc/wd/webdynpro/_comp/gen/default/public/default/lib/java
[wdgen] [Info] SapMetamodelDictionaryContent.zip - D:/Program Files/SAP/IDE/IDE70/eclipse/plugins/com.sap.tc.ap_2.0.0/comp/SAP_JTECHS/DCs/sap.com/tc/ddic/metamodel/content/_comp/gen/default/public/default/lib/java
[wdgen] [Info] jdsr.jar - D:/Program Files/SAP/IDE/IDE70/eclipse/plugins/com.sap.tc.ap_2.0.0/comp/SAP-JEE/DCs/sap.com/com.sap.mw.jco/_comp/gen/default/public/default/lib/java
[wdgen] [Info] jrfc.jar - D:/Program Files/SAP/IDE/IDE70/eclipse/plugins/com.sap.tc.ap_2.0.0/comp/SAP-JEE/DCs/sap.com/com.sap.mw.jco/_comp/gen/default/public/default/lib/java
[wdgen] [Info] SapDictionaryTypeServices.jar - D:/Program Files/SAP/IDE/IDE70/eclipse/plugins/com.sap.tc.ap_2.0.0/comp/SAP_JTECHS/DCs/sap.com/tc/ddic/ddicruntime/_comp/gen/default/public/default/lib/java
[wdgen] [Info] SapDictionaryTypesRuntime.jar - D:/Program Files/SAP/IDE/IDE70/eclipse/plugins/com.sap.tc.ap_2.0.0/comp/SAP_JTECHS/DCs/sap.com/tc/ddic/ddicruntime/_comp/gen/default/public/default/lib/java
[wdgen] [Info] aii_proxy_rt.jar - D:/Program Files/SAP/IDE/IDE70/eclipse/plugins/com.sap.tc.ap_2.0.0/comp/SAP_JTECHS/DCs/sap.com/com.sap.aii.proxy.framework/_comp/gen/default/public/default/lib/java
[wdgen] [Info] jxl.jar - C:/Documents and Settings/ecenta03/.dtc/LocalDevelopment/DCs/ecenta.com/jxl/jar/_comp/gen/default/public/JxlLibCompilation/lib/java
[wdgen] [Info] com.sap.security.api.jar - D:/Program Files/SAP/IDE/IDE70/eclipse/plugins/com.sap.tc.ap_2.0.0/comp/SAP-JEE/DCs/sap.com/com.sap.security.api.sda/_comp/gen/default/public/default/lib/java
[wdgen] [Info] com.sap.security.api.perm.jar - D:/Program Files/SAP/IDE/IDE70/eclipse/plugins/com.sap.tc.ap_2.0.0/comp/SAP-JEE/DCs/sap.com/com.sap.security.api.sda/_comp/gen/default/public/default/lib/java
[wdgen] [Info] Initialize generation templates from configuration jar:file:/D:/Program Files/SAP/IDE/IDE70/eclipse/plugins/com.sap.tc.ap_2.0.0/comp/SAP_BUILDT/DCs/sap.com/tc/bi/extwd/_comp/gen/default/public/def/lib/java/SapWebDynproGenerationCore.jar!/WebDynproGenerationConfigurationCompiled.xml
[wdgen] [Info] cn.ykjt.dbtest1.DBtest1View --> TextView DefaultTextView: UIElement does not have a label
[wdgen] [Info] Generating packages/cn/ykjt/dbtest1/wdp/IPrivateDBtest1View.java
[wdgen] [Info] Generating packages/cn/ykjt/dbtest1/DBtest1View.java
[wdgen] [Info] Generating packages/cn/ykjt/dbtest1/wdp/InternalDBtest1View.java
[wdgen] [Info] Generating packages/cn/ykjt/dbtest1/wdp/IPublicDBtest1.java
[wdgen] [Info] Generating packages/cn/ykjt/dbtest1/wdp/IPrivateDBtest1.java
[wdgen] [Info] Generating packages/cn/ykjt/dbtest1/DBtest1.java
[wdgen] [Info] Generating packages/cn/ykjt/dbtest1/wdp/InternalDBtest1.java
[wdgen] [Info] Generating packages/cn/ykjt/dbtest1/wdp/IPublicDBtest1Interface.java
[wdgen] [Info] Generating packages/cn/ykjt/dbtest1/wdp/IExternalDBtest1Interface.java
[wdgen] [Info] Generating packages/cn/ykjt/dbtest1/wdp/IPrivateDBtest1Interface.java
[wdgen] [Info] Generating packages/cn/ykjt/dbtest1/DBtest1Interface.java
[wdgen] [Info] Generating packages/cn/ykjt/dbtest1/wdp/InternalDBtest1Interface.java
[wdgen] [Info] Generating packages/cn/ykjt/dbtest1/DBtest1Interface.wdcontroller
[wdgen] [Info] Generating packages/cn/ykjt/dbtest1/wdp/IPublicDBtest1InterfaceCfg.java
[wdgen] [Info] Generating packages/cn/ykjt/dbtest1/wdp/IExternalDBtest1InterfaceCfg.java
[wdgen] [Info] Generating packages/cn/ykjt/dbtest1/wdp/IPrivateDBtest1InterfaceCfg.java
[wdgen] [Info] Generating packages/cn/ykjt/dbtest1/DBtest1InterfaceCfg.java
[wdgen] [Info] Generating packages/cn/ykjt/dbtest1/wdp/InternalDBtest1InterfaceCfg.java
[wdgen] [Info] Generating packages/cn/ykjt/dbtest1/DBtest1InterfaceCfg.wdcontroller
[wdgen] [Info] Generating packages/cn/ykjt/dbtest1/wdp/IPublicDBtest1InterfaceView.java
[wdgen] [Info] Generating packages/cn/ykjt/dbtest1/wdp/IPrivateDBtest1InterfaceView.java
[wdgen] [Info] Generating packages/cn/ykjt/dbtest1/DBtest1InterfaceView.java
[wdgen] [Info] Generating packages/cn/ykjt/dbtest1/wdp/InternalDBtest1InterfaceView.java
[wdgen] [Info] Generating packages/cn/ykjt/dbtest1/wdp/IMessageDBtest1.java
[wdgen] [Info] Generating configuration/Components/cn.ykjt.dbtest1.DBtest1/DBtest1.xml
[wdgen] [Info] Generating packages/cn/ykjt/dbtest1/wdp/ResourceDBtest1.properties
[wdgen] [Info] Generating packages/cn/ykjt/dbtest1/wdp/ResourceDBtest1_zh_CN.properties
[wdgen] [Info] Generating portalapp.xml
[wdgen] [Info] Generating wd.xml
[wdgen] [Info] Generating application.xml
[wdgen] [Info] Generating application-j2ee-engine.xml
[wdgen] [Info] Generating PublicPartFileList.properties
[wdgen] [Info] Generating PublicPartFileList.xml
[wdgen] [Info] Generation finished (0 seconds)
[wdgen]
[timer] WebDynpro generator finished in 0.734 seconds
[echo] Starting Java compiler
[echo] Settings:
[echo] debug: on
[echo] optimize: off
[echo] deprecation: default
[echo] verbose: default
[echo] encoding: UTF8
[echo] source: default
[echo] target: default
[echo] source paths:
[echo] C:\Documents and Settings\ecenta03\.dtc\LocalDevelopment\DCs\ecenta.com\test2\_comp\src\packages
[echo] C:\Documents and Settings\ecenta03\.dtc\LocalDevelopment\t\0EAFE51A1CEEAA916A875CFE652599FE\gen_ddic\datatypes
[echo] C:\Documents and Settings\ecenta03\.dtc\LocalDevelopment\t\0EAFE51A1CEEAA916A875CFE652599FE\gen_wdp\packages
[echo] class path:
[echo] D:\Program Files\SAP\IDE\IDE70\eclipse\plugins\com.sap.tc.ap_2.0.0\comp\SAP_JTECHS\DCs\sap.com\com.sap.aii.util.misc\_comp\gen\default\public\default\lib\java\aii_util_misc.jar
[echo] D:\Program Files\SAP\IDE\IDE70\eclipse\plugins\com.sap.tc.ap_2.0.0\comp\SAP_JTECHS\DCs\sap.com\tc\cmi\_comp\gen\default\public\default\lib\java\_cmi_api.jar
[echo] D:\Program Files\SAP\IDE\IDE70\eclipse\plugins\com.sap.tc.ap_2.0.0\comp\SAP-JEE\DCs\sap.com\com.sap.exception\_comp\gen\default\public\default\lib\java\exception.jar
[echo] D:\Program Files\SAP\IDE\IDE70\eclipse\plugins\com.sap.tc.ap_2.0.0\comp\SAP_JTECHS\DCs\sap.com\tc\wdp\metamodel\content\_comp\gen\default\public\default\lib\java\SapMetamodelWebdynproContent.zip
[echo] D:\Program Files\SAP\IDE\IDE70\eclipse\plugins\com.sap.tc.ap_2.0.0\comp\SAP-JEE\DCs\sap.com\tc\logging\_comp\gen\default\public\default\lib\java\logging.jar
[echo] D:\Program Files\SAP\IDE\IDE70\eclipse\plugins\com.sap.tc.ap_2.0.0\comp\SAP-JEE\DCs\sap.com\tc\logging\_comp\gen\default\public\default\lib\java\logging.perf.jar
[echo] D:\Program Files\SAP\IDE\IDE70\eclipse\plugins\com.sap.tc.ap_2.0.0\comp\SAP-JEE\DCs\sap.com\tc\wd\webdynpro\_comp\gen\default\public\default\lib\java\_webdynpro_admin.jar
[echo] D:\Program Files\SAP\IDE\IDE70\eclipse\plugins\com.sap.tc.ap_2.0.0\comp\SAP-JEE\DCs\sap.com\tc\wd\webdynpro\_comp\gen\default\public\default\lib\java\_webdynpro_basesrvc.jar
[echo] D:\Program Files\SAP\IDE\IDE70\eclipse\plugins\com.sap.tc.ap_2.0.0\comp\SAP-JEE\DCs\sap.com\tc\wd\webdynpro\_comp\gen\default\public\default\lib\java\_webdynpro_runtime_repository.jar
[echo] D:\Program Files\SAP\IDE\IDE70\eclipse\plugins\com.sap.tc.ap_2.0.0\comp\SAP-JEE\DCs\sap.com\tc\wd\webdynpro\_comp\gen\default\public\default\lib\java\_webdynpro_runtime_repository_pmr.jar
[echo] D:\Program Files\SAP\IDE\IDE70\eclipse\plugins\com.sap.tc.ap_2.0.0\comp\SAP-JEE\DCs\sap.com\tc\wd\webdynpro\_comp\gen\default\public\default\lib\java\_webdynpro_services.jar
[echo] D:\Program Files\SAP\IDE\IDE70\eclipse\plugins\com.sap.tc.ap_2.0.0\comp\SAP-JEE\DCs\sap.com\tc\wd\webdynpro\_comp\gen\default\public\default\lib\java\_webdynpro_clientserver.jar
[echo] D:\Program Files\SAP\IDE\IDE70\eclipse\plugins\com.sap.tc.ap_2.0.0\comp\SAP-JEE\DCs\sap.com\tc\wd\webdynpro\_comp\gen\default\public\default\lib\java\_webdynpro_model_dynamicrfc.jar
[echo] D:\Program Files\SAP\IDE\IDE70\eclipse\plugins\com.sap.tc.ap_2.0.0\comp\SAP-JEE\DCs\sap.com\tc\wd\webdynpro\_comp\gen\default\public\default\lib\java\_webdynpro_modelimpl.jar
[echo] D:\Program Files\SAP\IDE\IDE70\eclipse\plugins\com.sap.tc.ap_2.0.0\comp\SAP-JEE\DCs\sap.com\tc\wd\webdynpro\_comp\gen\default\public\default\lib\java\_webdynpro_pdfobject.jar
[echo] D:\Program Files\SAP\IDE\IDE70\eclipse\plugins\com.sap.tc.ap_2.0.0\comp\SAP-JEE\DCs\sap.com\tc\wd\webdynpro\_comp\gen\default\public\default\lib\java\_webdynpro_portal.jar
[echo] D:\Program Files\SAP\IDE\IDE70\eclipse\plugins\com.sap.tc.ap_2.0.0\comp\SAP-JEE\DCs\sap.com\tc\wd\webdynpro\_comp\gen\default\public\default\lib\java\_webdynpro_progmodel.jar
[echo] D:\Program Files\SAP\IDE\IDE70\eclipse\plugins\com.sap.tc.ap_2.0.0\comp\SAP-JEE\DCs\sap.com\tc\wd\webdynpro\_comp\gen\default\public\default\lib\java\_webdynpro_runtime_designtime_coupling.jar
[echo] D:\Program Files\SAP\IDE\IDE70\eclipse\plugins\com.sap.tc.ap_2.0.0\comp\SAP-JEE\DCs\sap.com\tc\wd\webdynpro\_comp\gen\default\public\default\lib\java\_webdynpro_runtime_designtime_coupling_api.jar
[echo] D:\Program Files\SAP\IDE\IDE70\eclipse\plugins\com.sap.tc.ap_2.0.0\comp\SAP_JTECHS\DCs\sap.com\tc\ddic\metamodel\content\_comp\gen\default\public\default\lib\java\SapMetamodelDictionaryContent.zip
[echo] D:\Program Files\SAP\IDE\IDE70\eclipse\plugins\com.sap.tc.ap_2.0.0\comp\SAP-JEE\DCs\sap.com\com.sap.mw.jco\_comp\gen\default\public\default\lib\java\jdsr.jar
[echo] D:\Program Files\SAP\IDE\IDE70\eclipse\plugins\com.sap.tc.ap_2.0.0\comp\SAP-JEE\DCs\sap.com\com.sap.mw.jco\_comp\gen\default\public\default\lib\java\jrfc.jar
[echo] D:\Program Files\SAP\IDE\IDE70\eclipse\plugins\com.sap.tc.ap_2.0.0\comp\SAP_JTECHS\DCs\sap.com\tc\ddic\ddicruntime\_comp\gen\default\public\default\lib\java\SapDictionaryTypeServices.jar
[echo] D:\Program Files\SAP\IDE\IDE70\eclipse\plugins\com.sap.tc.ap_2.0.0\comp\SAP_JTECHS\DCs\sap.com\tc\ddic\ddicruntime\_comp\gen\default\public\default\lib\java\SapDictionaryTypesRuntime.jar
[echo] D:\Program Files\SAP\IDE\IDE70\eclipse\plugins\com.sap.tc.ap_2.0.0\comp\SAP_JTECHS\DCs\sap.com\com.sap.aii.proxy.framework\_comp\gen\default\public\default\lib\java\aii_proxy_rt.jar
[echo] C:\Documents and Settings\ecenta03\.dtc\LocalDevelopment\DCs\ecenta.com\jxl\jar\_comp\gen\default\public\JxlLibCompilation\lib\java\jxl.jar
[echo] D:\Program Files\SAP\IDE\IDE70\eclipse\plugins\com.sap.tc.ap_2.0.0\comp\SAP-JEE\DCs\sap.com\com.sap.security.api.sda\_comp\gen\default\public\default\lib\java\com.sap.security.api.jar
[echo] D:\Program Files\SAP\IDE\IDE70\eclipse\plugins\com.sap.tc.ap_2.0.0\comp\SAP-JEE\DCs\sap.com\com.sap.security.api.sda\_comp\gen\default\public\default\lib\java\com.sap.security.api.perm.jar
[echo] output dir: C:\Documents and Settings\ecenta03\.dtc\LocalDevelopment\t\0EAFE51A1CEEAA916A875CFE652599FE\classes
[javac] Compiling 22 source files to C:\Documents and Settings\ecenta03\.dtc\LocalDevelopment\t\0EAFE51A1CEEAA916A875CFE652599FE\classes
[javac] ERROR: C:\Documents and Settings\ecenta03\.dtc\LocalDevelopment\t\0EAFE51A1CEEAA916A875CFE652599FE\gen_wdp\packages\cn\ykjt\dbtest1\DBtest1View.java:22: package com.ecenta.materialplan does not exist
[javac] ERROR: import com.ecenta.materialplan.MaterialPlanProcessor;
[javac] ERROR: ^
[javac] ERROR: C:\Documents and Settings\ecenta03\.dtc\LocalDevelopment\t\0EAFE51A1CEEAA916A875CFE652599FE\gen_wdp\packages\cn\ykjt\dbtest1\DBtest1View.java:23: package com.ecenta.materialplan does not exist
[javac] ERROR: import com.ecenta.materialplan.MaterialPlanProcessorHome;
[javac] ERROR: ^
[javac] ERROR: C:\Documents and Settings\ecenta03\.dtc\LocalDevelopment\t\0EAFE51A1CEEAA916A875CFE652599FE\gen_wdp\packages\cn\ykjt\dbtest1\DBtest1View.java:105: cannot resolve symbol
[javac] ERROR: symbol : class MaterialPlanProcessorHome
[javac] ERROR: location: class cn.ykjt.dbtest1.DBtest1View
[javac] ERROR: MaterialPlanProcessorHome materialPlanHome = (MaterialPlanProcessorHome) ctx.lookup("MaterialPlanJNDI");
[javac] ERROR: ^
[javac] ERROR: C:\Documents and Settings\ecenta03\.dtc\LocalDevelopment\t\0EAFE51A1CEEAA916A875CFE652599FE\gen_wdp\packages\cn\ykjt\dbtest1\DBtest1View.java:105: cannot resolve symbol
[javac] ERROR: symbol : class MaterialPlanProcessorHome
[javac] ERROR: location: class cn.ykjt.dbtest1.DBtest1View
[javac] ERROR: MaterialPlanProcessorHome materialPlanHome = (MaterialPlanProcessorHome) ctx.lookup("MaterialPlanJNDI");
[javac] ERROR: ^
[javac] ERROR: C:\Documents and Settings\ecenta03\.dtc\LocalDevelopment\t\0EAFE51A1CEEAA916A875CFE652599FE\gen_wdp\packages\cn\ykjt\dbtest1\DBtest1View.java:106: cannot resolve symbol
[javac] ERROR: symbol : class MaterialPlanProcessor
[javac] ERROR: location: class cn.ykjt.dbtest1.DBtest1View
[javac] ERROR: MaterialPlanProcessor proc = materialPlanHome.create();
[javac] ERROR: ^
[javac] 5 errors
Error: C:\Documents and Settings\ecenta03\.dtc\LocalDevelopment\DCs\ecenta.com\test2\_comp\gen\default\logs\build.xml:154: Compile failed; see the compiler error output for details.
at org.apache.tools.ant.taskdefs.Javac.compile(Javac.java:938)
at org.apache.tools.ant.taskdefs.Javac.execute(Javac.java:758)
at org.apache.tools.ant.UnknownElement.execute(UnknownElement.java:275)
at org.apache.tools.ant.Task.perform(Task.java:364)
at org.apache.tools.ant.Target.execute(Target.java:341)
at org.apache.tools.ant.Target.performTasks(Target.java:369)
at org.apache.tools.ant.Project.executeTarget(Project.java:1214)
at com.sap.tc.buildplugin.techdev.ant.util.AntRunner.run(AntRunner.java:116)
at com.sap.tc.buildplugin.DefaultAntBuildAction.execute(DefaultAntBuildAction.java:58)
at com.sap.tc.buildplugin.DefaultPlugin.handleBuildStepSequence(DefaultPlugin.java:196)
at com.sap.tc.buildplugin.DefaultPlugin.performBuild(DefaultPlugin.java:168)
at com.sap.tc.buildplugin.DefaultPluginV3Delegate$BuildRequestHandler.handle(DefaultPluginV3Delegate.java:66)
at com.sap.tc.buildplugin.DefaultPluginV3Delegate.requestV3(DefaultPluginV3Delegate.java:48)
at sun.reflect.GeneratedMethodAccessor608.invoke(Unknown Source)
at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25)
at java.lang.reflect.Method.invoke(Method.java:324)
at com.sap.tc.buildtool.v2.impl.PluginHandler2.maybeInvoke(PluginHandler2.java:350)
at com.sap.tc.buildtool.v2.impl.PluginHandler2.request(PluginHandler2.java:99)
at com.sap.tc.buildtool.v2.impl.PluginHandler2.build(PluginHandler2.java:73)
at com.sap.tc.buildtool.PluginHandler2Wrapper.execute(PluginHandler2Wrapper.java:59)
at com.sap.tc.devconf.impl.DCProxy.make(DCProxy.java:1750)
at com.sap.tc.devconf.impl.DCProxy.make(DCProxy.java:6004)
at com.sap.ide.eclipse.component.provider.actions.dcproject.BuildAction.buildDCsForDevConfig(BuildAction.java:307)
at com.sap.ide.eclipse.component.provider.actions.dcproject.BuildAction.access$200(BuildAction.java:58)
at com.sap.ide.eclipse.component.provider.actions.dcproject.BuildAction$1.run(BuildAction.java:212)
at org.eclipse.jface.operation.ModalContext$ModalContextThread.run(ModalContext.java:101)
Ant runtime 1.578 seconds
Ant build finished with ERRORS
Compile failed; see the compiler error output for details.
Error: Build stopped due to an error: Compile failed; see the compiler error output for details.
Build plugin finished at 2008-11-26 14:52:42 GMT+08:00 (CST)
Total build plugin runtime: 1.984 seconds
Build finished with ERRORThanks for the reply, i think i m getting close.
by making my EJB project a DC project and put the public parts into my Used DC, i reduce the build errors down to 2 (from more than 10).
maybe i m not making my EJB project into DC properly
the error msg itself is related to the EJB project:
[javac] Compiling 22 source files to C:\Documents and Settings\Administrator\.dtc\LocalDevelopment\t\587CAFC00F9128BE9AF538F893A3FFFB\classes
[javac] ERROR: C:\Documents and Settings\Administrator\.dtc\LocalDevelopment\t\587CAFC00F9128BE9AF538F893A3FFFB\gen_wdp\packages\com\ecenta\excelimport\ExcelImport.java:595: cannot access javax.ejb.EJBHome
[javac] ERROR: file javax\ejb\EJBHome.class not found
[javac] ERROR: MaterialPlanProcessor proc = materialPlanHome.create();
[javac] ERROR: ^
[javac] ERROR: C:\Documents and Settings\Administrator\.dtc\LocalDevelopment\t\587CAFC00F9128BE9AF538F893A3FFFB\gen_wdp\packages\com\ecenta\excelimport\ExcelImport.java:602: cannot access javax.ejb.EJBObject
[javac] ERROR: file javax\ejb\EJBObject.class not found
[javac] ERROR: materialPlanModel = proc.newMaterialPlan(""+materialNo,quantity,mDesc,mPrice,mName,factory,site,cc,wbs,requestor,traxNo,ps,mobileType,creationDate,requestDate,status,creator,unit);
[javac] ERROR: ^
[javac] 2 errors -
Using HAL to generate XML files
Greetings,<BR>I'd like to use HAL to build XML files and feeding certain variables while these files are generated. When the XML file is done being created, it will contain the variables passed. There are over 500 XML required to be build and for each of these files, only 2 or 3 variables must be passed to them. A template of the xml file was created using the Batch scheduler from Hyperion Reports, and this is the file I'd like to use as a template and build a HAL adapter based on that file.<BR><BR>Does any one have a sample of the XML adapter (via screen shot) that I can use a starting guide?<BR><BR>Many thanks in advance for your time.
Hi,
I'm running into the same problem deploying the classes generated by the class generator. Code works fine from JDeveloper, but had to put my DTD in the directory where my classes are. Deploying the classes with Apache's JServ gives me a NullPointer exception on the first addNode method. I guess it can't find the DTD. I tried to put the DTD in many locations but this didn't fix the problem. Any suggestions?
Steve,
Did you fix this problem? Thanx!
null -
? - Is there a way to validate 1 XML record at a time, using the SAX or oth
Hello!
Before running into space problems, i generated an XML file from a 'pipe delimited' file and and then processed that XML file thru a SAXParser 'validator' and the data was correctly validated, using the RELAXNG Schema patterns as the validation criteria!
But as feared, the XML file was huge! (12 billion XML recs. generated from 1 billion 'pipe' recs.) and i am now trying to find a way to process 1 'pipe' record at a time, (ie) read 1 record from the 'pipe delimited' file, convert that rec. to an XML rec. and then send that 1 XML rec. thru the SAXParser 'validator', avoiding the build of a huge temporary XML file!
After testing this approach, its looks like the SAXParser 'validator' (sp.parse) is expecting only (1) StringBufferInputStream as input,and after opening, reading and closing just (1) of the returned StringBufferInputStream objects, the validator wants to close up operations!
Where i have the "<<<<<" you can see where i'm calling the the object.method that creates the 'pipe>XML' records 'sb.createxml' and will be returning many occurances of the StringBufferInputStream object, where (1) StringBufferInputStream object represents (1) 'pipe>XML' record!
So what i'm wondering, is if there is a form of 'inputStream' class that can be loaded and processed at the same time! ie instead of requiring that the 'inputStream' object be loaded in it's entirety, before going to validation?
Or if there is another XML 'validator' that can validate 1 XML record at a time, without requiring that the entire XML file be built first?
1. ---------------------------------class: (SX2) ---------------------------------------------------------------------------------------------------------
import ............
public class SX2
public static void main(String[] args) throws Exception
MyDefaultHandler dh = new MyDefaultHandler();
SX1 sx = new SX1();
SAXParser sp = sx.getParser(args[0]);
stbuf1 sb = new stbuf1();
sp.parse(sb.createxml(args[1]),dh); <<<<<< createxml( ) see <<<<<<< below
class MyDefaultHandler extends DefaultHandler {
public int errcnt;
"SX2.java" 87 lines, 2563 characters
2. ----------------------------------class: (stbuf1) method: (createxml) ----------------------------------------------------------------------------
public stbuf1 () { }
public StringBufferInputStream createxml( String inputFile ) <<<<<< createxml(
BufferedReader textReader = null;
if ( (inputFile == null) || (inputFile.length() <= 1) )
{ throw new NullPointerException("Delimiter Input File does not exist");
String ele = new String();
try {
ele = new String();
textReader = new BufferedReader(new FileReader(inputFile));
String line = null; String SEPARATOR = "\\|"; String sToken = null;
String hdr1=("<?xml version=#1.0# encoding=#UTF-8#?>"); hdr1=hdr1.replace('#','"');
String hdr2=("<hlp_data>");
String hdr3=("</hlp_data>");
String hdr4=("<"+TABLE_NAME+">");
String hdr5=("</"+TABLE_NAME+">");
while ( (line = textReader.readLine()) != null )
String[] sa = line.split(SEPARATOR);
String elel = new String();
for (int i = 0; i < NUM_COLS; i++)
if (i>(sa.length-1)) { sToken = new String(); } else { sToken = sa; }
elel="<"+_columnNames[i]+">"+sToken+"</"+_columnNames[i]+">";
if (i==0) {
ele=ele.concat(hdr1);ele=ele.concat(hdr2);ele=ele.concat(hdr4);ele=ele.concat(elel);
else
if (i==NUM_COLS - 1) {
ele=ele.concat(elel);ele=ele.concat(hdr5);ele=ele.concat(hdr3);
else {
ele=ele.concat(elel);
textReader.close();
catch (IOException e) {
return (new StringBufferInputStream(ele));
public static void main( String args[] ) {
stbuf1 genxml_obj = new stbuf1 ();
String ptxt=new String(args[0]);
genxml_obj.createxml(ptxt); }}Well,i think you can use the streaming API for xml processing provided by weblogic.It is pull model,not push model like SAX.with it,you can select the events you want without having to react to every event,and you can filter the events out.
Sun also provide such streaming API for xml processing,and i got an very simple introduction about it on the Chinese Sun developer site.but i couldn't find any other infomation about it elsewhere! If you have such materials,please send to my email:[email protected],and if I have it,i will be sure to post the links here.hope it helps more or less:)
@smile@ -
/* Style Definitions */
table.MsoNormalTable
{mso-style-name:"Table Normal";
mso-tstyle-rowband-size:0;
mso-tstyle-colband-size:0;
mso-style-noshow:yes;
mso-style-priority:99;
mso-style-qformat:yes;
mso-style-parent:"";
mso-padding-alt:0in 5.4pt 0in 5.4pt;
mso-para-margin:0in;
mso-para-margin-bottom:.0001pt;
mso-pagination:widow-orphan;
font-size:11.0pt;
font-family:"Calibri","sans-serif";
mso-ascii-font-family:Calibri;
mso-ascii-theme-font:minor-latin;
mso-fareast-font-family:"Times New Roman";
mso-fareast-theme-font:minor-fareast;
mso-hansi-font-family:Calibri;
mso-hansi-theme-font:minor-latin;
mso-bidi-font-family:"Times New Roman";
mso-bidi-theme-font:minor-bidi;}
For the last 5 years (and in IPCC3.x/4.x,UCCX/5.x/7.x) I've used the same basic subflow to read a XML document that contains holiday dates where the queue should be closed. I've re-used this script on 20+ client installs and it's always worked. The structure of the script allows you to pass the path and filename of the XML document as parameters to the subflow. (The document is in the repository)
I loaded this script in UCCX 8.0.2 recently and it crashed with a Java.IO error. It looked like it was trying to read the file system directly and not the repository. (In the Linux appliance model this kind of makes sense but why is the step trying to read the file system directly?)
So I open a TAC case (SR# 615243125) and TAC tells me that the method of using the Create File Document step is not supported anymore and that I should specify the filename directly in the Create XML Document step
The problem that I see (aside from having to edit all my scripts that use XML files) is that the Create XML Document step is looking for the input to be a type DOCUMENT and not a type STRING. This seems to imply that I have to hardcode the document in each script that I deploy for a customer. When it was a string it was easy to construct the full file path from parameters and pass to the subflow.
Questions to the group
#1 Am I missing something here?
#2 Do you assume that you'll be able to load a script that worked fine in UCCX 7 into UCCX 8 and that it should completely function when you're doing everything according to the step reference documentation.
#3 Cisco didn’t document this in any way that I can find.
#4 How can you use the Create XML Document step in a fashion that would let you construct the path of the file and the filename previously in the script so you could pass it to a subflow ? It would seem this functionality has been killed in UCCX 8
/* Style Definitions */
table.MsoNormalTable
{mso-style-name:"Table Normal";
mso-tstyle-rowband-size:0;
mso-tstyle-colband-size:0;
mso-style-noshow:yes;
mso-style-priority:99;
mso-style-qformat:yes;
mso-style-parent:"";
mso-padding-alt:0in 5.4pt 0in 5.4pt;
mso-para-margin:0in;
mso-para-margin-bottom:.0001pt;
mso-pagination:widow-orphan;
font-size:11.0pt;
font-family:"Calibri","sans-serif";
mso-ascii-font-family:Calibri;
mso-ascii-theme-font:minor-latin;
mso-fareast-font-family:"Times New Roman";
mso-fareast-theme-font:minor-fareast;
mso-hansi-font-family:Calibri;
mso-hansi-theme-font:minor-latin;
mso-bidi-font-family:"Times New Roman";
mso-bidi-theme-font:minor-bidi;}
(Background)
Create File Document Step
The input filename is a STRING, could be an explicit path and filename in the repository or a variable that represents that path and string
The output of this step is a DOCUMENT to be used in the Create XML Document step
The string FILE_FullPathHolidayFiles references en_us\folderName\documentName.xml
The document was properly uploaded into the repository only, NOT trying to directly read c:\foo\blah…
/* Style Definitions */
table.MsoNormalTable
{mso-style-name:"Table Normal";
mso-tstyle-rowband-size:0;
mso-tstyle-colband-size:0;
mso-style-noshow:yes;
mso-style-priority:99;
mso-style-qformat:yes;
mso-style-parent:"";
mso-padding-alt:0in 5.4pt 0in 5.4pt;
mso-para-margin:0in;
mso-para-margin-bottom:.0001pt;
mso-pagination:widow-orphan;
font-size:11.0pt;
font-family:"Calibri","sans-serif";
mso-ascii-font-family:Calibri;
mso-ascii-theme-font:minor-latin;
mso-fareast-font-family:"Times New Roman";
mso-fareast-theme-font:minor-fareast;
mso-hansi-font-family:Calibri;
mso-hansi-theme-font:minor-latin;
mso-bidi-font-family:"Times New Roman";
mso-bidi-theme-font:minor-bidi;}
The create XML document input can only be a type DOCUMENT#1 Am I missing something here?
You are mixing two different issues together here.
The Create File Document step is indeed not needed or supported for creating an XML document. That is why there is a unique step; to trigger XML parsing within the MIVR subsystem.
Accessing the file system is restricted to a single folder within the VOS model (i.e. 8.0+). This folder is not backed up, replicated, or cleaned up automatically. It was intended to give developers some FS access as a temporary swap location only.
#2 Do you assume that you'll be able to load a script that
worked fine in UCCX 7 into UCCX 8 and that it should completely
function when you're doing everything according to the step reference
documentation.
Assume nothing; read the documentation and attend one of the dozens of partner training sessions that CCBU put on advising of the upcoming changes.
#3 Cisco didn’t document this in any way that I can find.
You're right, I guess, on the Create File vs. XML Document step. AFAIK Cisco never wrote a notice into the Step Reference Guide explicitly stating that you cannot use the Create File Document although the documentation seemed pretty clear to me without it. File system restrictions are documented in the 8.0 release notes.
Scripting and Development Series: Volume 2, Editor Step ReferenceUse the Create XML Document step to create a logical document that maps a document to another document variable (where the document has already been pre-parsed as an XML document and is ready to be accessed by the Get XML Document Data step).Use this step before the Get XML Document Data step to obtain data from a document formatted using the Extensible Markup Language (XML).
#4 How can you use the Create XML Document step in a fashion that would
let you construct the path of the file and the filename previously in
the script so you could pass it to a subflow ? It would seem this functionality has been killed in UCCX 8
No it hasn't; just concatinate a string to build the Source Document parameter the step needs. Example: "DOC[" + myFilePath + "]" -
Data transfer using ALE/IDOC into XML.
Dear All,
I have to transfer FI document data (FB01) from the sap system ,convert it into XML and dump it in 1 of the file servers.I want to do this using ALE/IDOC.Is it possible to do the same and how.Similarly i want to do the same for Vendor and Customer master i.e sending the data in XML format.
Kindly Suggest how do i go about doin the same..Its very urgent.Please help.
Thanks & Regards,
Lailu Philip.In continuation:
Example Purchasing & Selling scenario
We will develop a custom IDoc to carry the billing number from the Service Receivers system to the Service Providers system. We will populate the IDoc in a user exit on the sending side and we will process the transaction on the receiving side using a custom function module and a BDC transaction call.
No rule conversion, segment filtering or version conversion will be implemented in the model as described in Figure 1.
Requirements
Working ALE environment - See ALE Basis Configuration Guide;
ALE scenario design together with the business requirement;
Development access; and
ALE configuration access.
NOTES:
1. All IMG references to transactions are located in the transaction SALE which is the ALE portion of the IMG
2. This is one way of developing a scenario where no message control exists. If message control exist (EG. On purchase orders) then NAST can be used to call an outbound function module that would create the required IDocs.
3. Extensive knowledge of IDocs and ALE basis configuration is required in order to understand this guide.
2. OUTBOUND PROCESSING
2.1. Create IDoc type (WE30) Client independent
The IDoc type refers to the IDoc structure that you will require for your development. In our case the IDoc type is called ZINVRV01. This IDoc type will have 1 segment called Z1INVRV with 2 fields, LIFNR & XBLNR, in this segment. If you require many segments or nested segments then they are also created using the same procedure.
We will create the IDoc of the following structure:
ZINVRV01
Purchasing and Selling - Invoice receipt reversal
Z1INVRV P&S - Segment 1
Segment fields
LIFNR Vendor account number
XBLNR Reference document number
Figure 3: IDoc type ZINVRV01
To create the IDoc type, follow these next few steps:
Enter transaction WE30 (ALE -> Extensions -> IDoc types -> Maintain IDoc type)
Type in ZINVRV01 and click on Basic IDoc type, click the Create icon
Click on Create new (we are creating an IDoc from scratch but you may want to copy another IDoc if it is similar to your requirements) and enter a description, and press enter
Click on ZINVRV01 and then on the Create icon
Enter Z1INVRV as the segment type (must start with Z1), check mandatory if the segment must exist (in this case check it), enter 1 in minimum number and 1 as maximum number. (Make the maximum number 9999999999 if there are going to be many of these segments in each IDoc. IE. When line items are passed via IDocs), click on Segment editor
Enter a description for your segment type and create
Enter a description for your segment, enter each field required in your IDoc, in our case type LIFNR across for Field name, DE structure and DE documentation, repeat for XBLNR and press enter to validate.
Save and generate, press back
To release the segment choose Goto, Release from the menu
Check the box on the line of your new segment
Save, back and enter
Your IDoc type structure should be displayed with your new segment
Save and back
To release the IDoc type choose Extras, Release type from the menu and Yes
Your IDoc is now ready for use. If you need to add fields or segments to your IDoc type, you will need to cancel the release of the IDoc type as well as the segment release using a similar procedure followed above (except now you uncheck the release box for the segment and you choose cancel release for the IDoc type).
2.2. Create message type (WE81) Client independent
To create a new message type, follow these next few steps:
Enter transaction WE81 (ALE -> Extensions -> IDoc types -> Maintain message type for intermed. Structure -> Create logical message type)
Choose Create logical message type by double clicking on it
Click on change icon to enter change mode
Click on New entries to add a new type
Enter the required message type, in our case it is ZINVRV and an appropriate description
Save and exit.
Your message type has now been created. The next step will be to link it to the IDoc.
2.2.1. Link message to IDoc type (WE82 & BD69) Client independent
To link the message type to the IDoc type follow these next few steps:
Enter transaction WE82 (ALE -> Extensions -> IDoc types -> Maintain message type for intermed. Structure -> EDI: Message Types and Assignment to IDoc Types)
Click on change icon to enter change mode
Click on New entries to create the link
Enter the message type ZINVRV and the BasicIDoc type as ZINVRV01
Save and exit
Enter transaction BD69 (ALE -> Extensions -> IDoc types -> Maintain message type for intermed. Structure -> Assign message type to IDoc for ALE)
Click on change icon to enter change mode
Click on New entries to create the link
Enter the message type ZINVRV and the BasicIDoc type as ZINVRV01
Save and exit
Your IDoc is now linked to your message type. We still need to link object types and add the message to the model before we can use the message.
2.2.2. Maintain object type for message type (BD59) Client independent
The ALE objects are used to create links between IDocs and applications objects, to control the serialisation, to filter messages in the customer model and to use listings.
For our own message type and IDoc you must maintain object types for the links.
If you want to check the serialisation for the message type, then you must maintain object types for the serialisation. If no serialisation object has been maintained for a given message type, then the serialisation will not be checked for this message type.
To add an object type to our message type, follow these next few steps:
Enter transaction BD59 (ALE -> Extensions -> ALE object maintenance -> Maintain object types)
Type in your message type ZINVRV and press enter
Click on New entries
Enter your object type, LIFNR (We need to use the vendor as a filter object), the segment name where LIFNR resides, Z1INVRV, a number 1 for the sequence followed by the actual field name LIFNR
Save and exit.
You have now created an object that well use as a filter object in the customer model to direct the flow of messages to the various logical systems based on the vendors in the filter of the message type ZINVRV.
We now need to add our new message type to the distribution model.
2.3. Configuring the Distribution Model
This task is performed on your ALE reference client.
2.3.1. Manual Configuration (BD64) Client dependent
To manually configure the customer distribution model, read the ALE configuration procedure, and follow these steps:
Perform the Maintain customer distribution model directly function. (ALE -> Distribution customer model -> Maintain customer distribution model directly)
Specify the customer model you want to maintain and the logical system that is to be the sender of the messages OR create a new model. (Create model ALE with logical system ALELS1C400)
Choose the receiving systems to which the sending system must forward message type ZINVRV to.
For each receiving logical system allocate the message type necessary for communication to the receiving systems as per ALE configuration procedure.
Create filter objects (in our case LIFNR as the object type with the associated vendor number, 0000018001 with leading zeros, in the object area) for the message types.
Save the entries.
NOTES:
You cannot maintain a message type between the same sender and receiver in more than one customer distribution model.
Only the owner is authorised to modify the model.
To change the owner of a model, choose the 'Maintain ownership of customer distribution model' function. Make sure that all changes will be distributed to all systems that know the corresponding model. To do so, you can use the correction and transport system.
To transport the customer distribution model you should use the Distribute customer model function of the IMG as described below.
2.3.2. Distribute customer model (BD71) Client dependent
After the customer model has been created centrally, it must be distributed to the other remote systems. This entails first of all setting up the communication for the distributed systems and then sending the model.
2.3.2.1. Distribute Model (BD71) Client dependent
This task is performed on your ALE reference client. To distribute the customer distribution model, read the ALE configuration procedure and follow these steps:
Make the settings for the communication with the other decentral systems, you have not set them yet.
Define the RFC destination for R/3 connections whose names correspond to the name of the corresponding logical system.
Create the output partner profile.
Distribute the customer model
Specify the name of the customer model.
You must specify the target system to which you want to distribute the customer model.
You must repeat this function for every distributed logical system.
2.3.2.2. Maintain sending system partner profile (WE20) Client dependent
With this function, you define the partner profiles for all outbound and inbound messages on the basis of the customer distribution model.
After you have defined and distributed the customer model, you will have to maintain the partner profiles locally. To do this read the ALE configuration procedure.
Enter the output mode (background, immediately) and the package size for outbound processing.
Requirements
The customer model must be maintained.
RFC destinations must be maintained.
The customer model must be distributed.
To ensure that the appropriate persons in charge are informed if a processing error occurs, you must make settings in: Error processing Maintain organisational units.
2.4. Populate & distribute IDoc using ABAP
An IDoc consists of a control record with structure edidc and one or more data records with structure edidd. The control record contains the sender and recipient of the IDoc, as well as information on the type of message.
To be able to pass an IDoc to the ALE layer, you must set up a field string with structure edidc and an internal table with structure edidd. They are used to call function module master_idoc_distribute, which performs the save to the database and triggers the dispatch if necessary.
2.4.1. Example code
The code displayed below does the following:
populates our IDoc segment Z1INVR with the 2 fields XBLNR and LIFNR, populates the segment name and appends this to an internal table used to store the IDoc data;
populates the control record info with the message type and IDoc type; and
calls the MASTER_IDOC_DISTRIBUTE function module which distributes the IDoc as configured in the customer distribution model.
Data declaration statements
DATA: C_INVREV_SEGNAME(7) TYPE C VALUE 'Z1INVRV',
C_INVREV_MESTYPE(6) TYPE C VALUE 'ZINVRV',
C_INVREV_IDOC_TYPE(8) TYPE C VALUE 'ZINVRV01',
Z1INVRV LIKE Z1INVRV,
C_INVREV_DOCTYPE LIKE BKPF-BLART VALUE 'YY',
IDOC_CONTROL LIKE EDIDC,
T_COMM_CONTROL LIKE EDIDC OCCURS 0 WITH HEADER LINE,
IDOC_DATA LIKE EDIDD OCCURS 0 WITH HEADER LINE.
Move the document header into a structure
LOOP AT DOC_HEAD_TAB INTO DOC_HEAD.
ENDLOOP.
Move the document item data into a structure
LOOP AT DOC_ITEM_TAB INTO DOC_ITEM WHERE NOT ( LIFNR IS INITIAL ).
ENDLOOP.
Populate the IDoc segments field with the required data
CLEAR Z1INVRV.
Z1INVRV-LIFNR = DOC_ITEM-LIFNR. Store vendor number for filter
Z1INVRV-XBLNR = DOC_HEAD-XBLNR. Billing number
IDOC_DATA-SEGNAM = C_INVREV_SEGNAME. Segment name
IDOC_DATA-SDATA = Z1INVRV. Segment data
APPEND IDOC_DATA. Populate IDoc internal table
Move the control data info required for the distribution
IDOC_CONTROL-MESTYP = C_INVREV_MESTYPE.
IDOC_CONTROL-DOCTYP = C_INVREV_IDOC_TYPE.
Call the distribute function with the required parameters
CALL FUNCTION 'MASTER_IDOC_DISTRIBUTE' IN UPDATE TASK
EXPORTING
MASTER_IDOC_CONTROL = IDOC_CONTROL
TABLES
COMMUNICATION_IDOC_CONTROL = T_COMM_CONTROL
MASTER_IDOC_DATA = IDOC_DATA
EXCEPTIONS
ERROR_IN_IDOC_CONTROL = 1
ERROR_WRITING_IDOC_STATUS = 2
ERROR_IN_IDOC_DATA = 3
SENDING_LOGICAL_SYSTEM_UNKNOWN = 4
OTHERS = 5.
Figure 4: Outbound processing example code
NOTE:
For debugging purposes, use transaction WE05 (IDoc overview) to see check your IDoc status, or to see whether an IDoc was created/
3. INBOUND PROCESSING
3.1. Create Function Module
This function module is called when a message type, of type ZINVRV, comes into the receiving system. This needs to be configured and is dealt with later in this section. The function module is passed the IDoc as a parameter.
Example parameters
Import parameters Reference field Opt Y/N
INPUT_METHOD BDWFAP_PAR-INPUTMETHD N
MASS_PROCESSING BDWFAP_PAR-MASS_PROC N
Export Parameters Reference field Opt Y/N
WORKFLOW_RESULT BDWFAP_PAR-RESULT N
APPLICATION_VARIABLE BDWFAP_PAR-APPL_VAR N
IN_UPDATE_TASK BDWFAP_PAR-UPDATETASK N
CALL_TRANSACTION_DONE BDWFAP_PAR-CALLTRANS N
Table Parameters Reference field Optional Y/N
IDOC_CONTRL EDIDC
IDOC_DATA EDIDD
IDOC_STATUS BDIDOCSTAT
RETURN_VARIABLES BDWFRETVAR
SERIALIZATION_INFO BDI_SER
Exceptions
WRONG_FUNCTION_CALLED
Example code
The code displayed below does the following:
populates a BDC table with the IDoc info;
calls the transaction via a BDC call; and
updates the IDoc status according to the BDC error status.
EXTRACT FROM: Z_IDOC_INPUT_ZINVRV
Declaration of local variables
DATA: C_SEGNAM(10) TYPE C VALUE 'Z1INVRV'.
*-Loop through the IDOCs
LOOP AT IDOC_CONTRL.
*---Loop through the data for the IDOC
LOOP AT IDOC_DATA WHERE DOCNUM = IDOC_CONTRL-DOCNUM.
CASE IDOC_DATA-SEGNAM.
WHEN C_SEGNAM.
Here we get the info from the idoc table
IT_Z1INVRV = IDOC_DATA-SDATA.
ENDCASE.
PERFORM REV_INV.
ENDLOOP.
PERFORM UPDATE_IDOC_STATUS.
ENDLOOP.
FORM REV_INV "Reverse invoice form
Local variables & constants
DATA: C_TCODE LIKE BKPF-TCODE VALUE 'VF11'. "BDC transaction code
Now we can build the bdc table to call the reversal transaction start of screen 109
CLEAR BDC_TAB.
BDC_TAB-PROGRAM = 'SAPMV60A'.
BDC_TAB-DYNPRO = '109'.
BDC_TAB-DYNBEGIN = 'X'.
APPEND BDC_TAB.
Document number
CLEAR BDC_TAB.
BDC_TAB-FNAM = 'KOMFK-VBELN(01)'.
BDC_TAB-FVAL = IT_Z1INVRV-XBLNR. "Billing document number
APPEND BDC_TAB.
OK Code for screen 109
CLEAR BDC_TAB.
BDC_TAB-FNAM = 'BDC_OKCODE'.
BDC_TAB-FVAL = 'SICH'.
APPEND BDC_TAB.
Now we can call transaction 'VF11' with the populated bdc table. The transaction is called inside the idoc-contrl loop, so a transaction will be called for every idoc (journal). the transaction is called in no-display mode ('N') because this code runs in background as it is called by ale. The update is specified to be synchronous ('S') because we have to wait for the result to update the idoc status correctly.
CALL TRANSACTION C_TCODE USING BDC_TAB MODE 'N' UPDATE 'S'.
Store the return code for use in another form (status update)
RETURN_CODE = SY-SUBRC.
Here we check the return code, if there was an error, we put the transaction in a bdc session for the user to review and correct.
IF SY-SUBRC NE 0.
CALL FUNCTION 'BDC_OPEN_GROUP'
EXPORTING
CLIENT = SY-MANDT
GROUP = 'ZINVRV'
USER = C_ALE_USER
KEEP = 'X'.
CALL FUNCTION 'BDC_INSERT'
EXPORTING
TCODE = C_TCODE
TABLES
DYNPROTAB = BDC_TAB.
CALL FUNCTION 'BDC_CLOSE_GROUP'
EXCEPTIONS
NOT_OPEN = 1
QUEUE_ERROR = 2
OTHERS = 3.
ELSE. "No problems
C_EXISTS = 'N'.
Select from the billing document table to get sales doc number
SELECT * FROM VBRP WHERE VBELN = IT_Z1INVRV-XBLNR.
Select from the sales document table to get user status number
SELECT SINGLE * FROM VBAP WHERE VBELN = VBRP-AUBEL AND
POSNR = VBRP-AUPOS.
Select from the status table to change the user status to pending
SELECT * FROM JEST WHERE OBJNR = VBAP-OBJNR AND
STAT LIKE C_USER_STATUS.
IF JEST-STAT = C_US_PENDING. "User status is pending
JEST-INACT = C_UNCHECKED. "Make pending the active status
UPDATE JEST.
C_EXISTS = 'Y'. "I.E. An entry is already in table
ELSEIF JEST-INACT = C_UNCHECKED AND JEST-STAT NE C_US_PENDING.
JEST-INACT = C_CHECKED. "Make everything else inactive
UPDATE JEST.
ENDIF.
ENDSELECT.
IF C_EXISTS = 'N'. "I.E. Pending has never been a status before
JEST-OBJNR = VBAP-OBJNR.
JEST-STAT = C_US_PENDING.
JEST-INACT = C_UNCHECKED. "Make pending the active status
INSERT JEST.
ENDIF.
ENDSELECT. "Select from VBRP (Billing document table)
ENDIF.
ENDFORM. " REV_INV
FORM UPDATE_IDOC_STATUS.
Now we check the CALL TRANSACTION return code and set IDOC status
CLEAR IDOC_STATUS.
IF RETURN_CODE = 0.
WORKFLOW_RESULT = '0'.
IDOC_STATUS-DOCNUM = IDOC_CONTRL-DOCNUM.
IDOC_STATUS-STATUS = '53'.
IDOC_STATUS-UNAME = SY-UNAME.
IDOC_STATUS-REPID = SY-REPID.
IDOC_STATUS-MSGTY = SY-MSGTY.
IDOC_STATUS-MSGID = SY-MSGID.
IDOC_STATUS-MSGNO = SY-MSGNO.
IDOC_STATUS-MSGV1 = SY-MSGV1.
IDOC_STATUS-MSGV2 = SY-MSGV2.
IDOC_STATUS-MSGV3 = SY-MSGV3.
IDOC_STATUS-MSGV4 = SY-MSGV4.
RETURN_VARIABLES-WF_PARAM = 'Processed_IDOCs'.
RETURN_VARIABLES-DOC_NUMBER = IDOC_CONTRL-DOCNUM.
APPEND RETURN_VARIABLES.
ELSE.
WORKFLOW_RESULT = '99999'.
IDOC_STATUS-DOCNUM = IDOC_CONTRL-DOCNUM.
IDOC_STATUS-STATUS = '51'.
IDOC_STATUS-UNAME = SY-UNAME.
IDOC_STATUS-REPID = SY-REPID.
IDOC_STATUS-MSGTY = SY-MSGTY.
IDOC_STATUS-MSGID = SY-MSGID.
IDOC_STATUS-MSGNO = SY-MSGNO.
IDOC_STATUS-MSGV1 = SY-MSGV1.
IDOC_STATUS-MSGV2 = SY-MSGV2.
IDOC_STATUS-MSGV3 = SY-MSGV3.
IDOC_STATUS-MSGV4 = SY-MSGV4.
RETURN_VARIABLES-WF_PARAM = 'ERROR_IDOCS'.
RETURN_VARIABLES-DOC_NUMBER = IDOC_CONTRL-DOCNUM.
APPEND RETURN_VARIABLES.
ENDIF.
APPEND IDOC_STATUS.
ENDFORM. " UPDATE_IDOC_STATUS
Figure 5: Inbound processing example code
3.1.1. Debugging inbound FM
Use transaction WE19 to test inbound function module in debugging mode. Also use WE05 to view the IDocs and their statuses.
3.2. Maintain ALE attributes
The inbound function module needs to be linked to the message type and the message type needs to be linked to the appropriate inbound process code at the partner profile level before the scenario is enabled. These steps are described below in detail.
3.2.1. Link Message Type to Function Module (WE57) Client independent
To link a message (ZINVRV) type to a function module (Z_IDOC_INPUT_ZINVRV) follow these steps:
Enter transaction WE57 (ALE -> Extensions -> Inbound -> Allocate function module to logical message)
Select an entry (EG. IDOC_INPUT_ORDERS) and copy
Type in module name Z_IDOC_INPUT_ZINVRV
Type in basic IDoc type as ZINVRV01
Type in message type as ZINVRV
Type object type as IDOCINVOIC (Invoice document) - Used for workflow
Direction should be set to 2 for inbound
Enter and save
3.2.2. Define FM settings (BD51) Client independent
Enter transaction BD51 (ALE -> Extensions -> Inbound -> Define settings for input modules)
Click on New entries
Type in the name of the new function module Z_IDOC_INPUT_ZINVRV
Enter 0 for mass processing in the output column
Save and Exit
3.2.3. Maintain process codes (WE42) Client dependent
A process code needs to be maintained on each client. It then needs to be linked to the message via the partner profiles on each client. This allows the various clients to use a unique function module for the same message type.
To maintain the process code follow these steps:
Log on to the appropriate receiving system client
Execute WE42 (ALE -> Extensions -> Inbound -> Maintaining process codes inbound)
Choose Inbound with ALE service
Choose Processing with function module
Click on Processing with function module and choose create icon
Click on New Entries
Type in process code ZINR and give it a description and save
Now you are asked to Please maintain codes added in ALE entry methods, enter and choose Z_IDOC_INPUT_FIRVSL and copy it. You should choose a FM similar to your one.
Enter your process code ZINR
Enter your function module Z_IDOC_INPUT_ZINVRV
NOTE: The next 6 steps are used in workflow error handling.
Enter IDPKFIDCMT in object type
Enter MASSINPUTFINISHED in End event
Enter IDOCINVOIC in IDoc object type
Enter INPUTERROROCCURREDFI in IDoc start event
Enter INPUTFINISHEDFI in IDoc End event
Enter IDOCINVOIC in Application object type
You will need to determine the task associated with object IDOCINVOIC, and then assign the appropriate position to it. This position will then receive the application error messages via workflow.
To set up the workflow area please consult the Workflow config guide.
3.3. Create inbound partner profile
For each message type you need to maintain the inbound partner profiles.
3.3.1. Maintain receiving system partner profile (WE20) Client dependent
To maintain inbound partner profiles read the document ALE configuration procedure:
Add the message type ZINVRV with process code ZINR.
Enter the output mode (background, immediately) for inbound processing and NO message code.
Enter the position S and choose the ALE administrator 50000085. This position will then receive all the technical ALE errors via workflow.
3.4. Test
Once the inbound function module has been debugged the scenario should be ready to test in its entirety. If problems occur, read through the relevant areas of this document to check your configuration or code.
Hope this will help you,
If you want me to explain more, you can give me your email id.
Reward with points incase you are satisfied.
Regards,
Sushama -
Xslt conversion not working: nosuchmethoderror:org.apache.xml.dtm.ref.sax2d
hi all, iam trying to convert xml file to html using xslt.
for that iam using xalan implementation 2.6. this was working fine when i checked it from the application, no iam using servet which instantiates a object of the class and calls the method...and it not working now.
it is giving this errror
java.lang.NoSuchMethodError: org.apache.xml.dtm.ref.sax2dtm.SAX2DTM.(Lorg/apache/xml/dtm/DTMManager;Ljavax/xml/transform/Source;ILorg/apache/xml/dtm/DTMWSFilter;Lorg/apache/xml/utils/XMLStringFactory;ZIZZ)V
at org.apache.xml.dtm.ref.sax2dtm.SAX2DTM2.(SAX2DTM2.java:1901)
at org.apache.xalan.xsltc.dom.SAXImpl.(SAXImpl.java:767)
at org.apache.xalan.xsltc.dom.XSLTCDTMManager.getDTM(XSLTCDTMManager.java:390)
at org.apache.xalan.xsltc.dom.XSLTCDTMManager.getDTM(XSLTCDTMManager.java:267)
at org.apache.xalan.xsltc.trax.TransformerImpl.getDOM(TransformerImpl.java:477)
at org.apache.xalan.xsltc.trax.TransformerImpl.transform(TransformerImpl.java:637)
at org.apache.xalan.xsltc.trax.TransformerImpl.transform(TransformerImpl.java:317)
...can anyone tell me what the problem is? iam setting the system property at runtime like,
java -Djavax.xml.transformer.TransformerFactory=org.apache.xalan.processor.TransformerFactoryImpl GetTestiam using the standard way of instantiating the trnaformer like
TransformerFacotry fac= transformerFactory.newinstance() etc.etc.
is it beaucse iam not specifiying the imlementation in the application???if so how can i do that.
thankyou.found the answer !!!
i was using a buggy implementation of xalan. on loading the good xalan.jar and xercesImpl.jar files it started working.
found that there was a memory leak in 2 places. not sure what that meant but some how the virtual machine wasnt getting the right values for the transformer.
cheers. -
Using XLST in the XML output returned.
I have written a SQL (using 10G) which creates an XML document using the XML syntax and the output
is as follows:
<?xml version="1.0" encoding="UTF-8"?>
<FIXML xmlns="http://www.fixprotocol.org/FIXML-4-4"><Order Acct="1" Px="480.25"
SettlDt="2009-12-01" SettlTyp="0" Side="1" StopPx="480.25" Typ="2">
<TrdSes SesID="0"/><Instrmt CpnRt="5.1" EncIssrLen="2" ID="3134865" Issr="Barclays"
MMY="200903" Mult="1.0" OptAt="L" SecTyp="BA" Sfx="P" Src="2" />
</Order></FIXML>I need to use XSLT to convert the above XML in the format attached below.
- <i:Interest >
<i:OrderAct>1</i:OrderAct>
<i:StopPx>480.25</i:StopPx>
<i:Issr>Barclays</i:Issr>
<i:Ref />
</i:Interest>i know that this is not the forum to ask XSLT,but as I am using 10G with SQL,can anyone
just send in a small XSLT script which I can use as a template and create XSLT.
This is the first time I am using XSLT.
Again,no offence meant if this is not the correct forum but help really appreciated.
Thanks,What's wrong with Sundars answer in this Writing a Procedure to return back XML. Please help.?
-
It is easy to transfer data between a simple input/output dll build with LV and an external code like C++, but when data are available inside a loop running in the dll(in fact thread running in LV); How can I read them or receive an handle pointer to the calling C++ application when new data are ready.
If you're using LabVIEW 7, you can use the PostLVUserEvent function to fire an event for an event structure in LV. Refer to the Using External Code in LV manual.
Or you could use datasocket for this. The datasocket activex dll is nids.dll. You could have the class wizard generate wrappers for you or if you have Measurement Studio, you could use the custom wrappers it provides to communicate between the VI and dll.
I hope this helps
Bilal Durrani
NI
Bilal Durrani
NI -
Create XML element without closing tag using Visual C++
I know how to create xml element with closing tag (using WriteStartElement and WriteEndElement methods)
<tag id="1234">
</tag>
but is there a way in Visual C++ to produce xml element like this
<tag id="1234"/>
i.e. without closing tag?Hi adamay,
Please refer to this thread.
http://stackoverflow.com/questions/8182245/create-xml-element-without-closing-tag-using-xslt
I think you could try the way of write your own class derived from XmlWriter.
We are trying to better understand customer views on social support experience, so your participation in this interview project would be greatly appreciated if you have time. Thanks for helping make community forums a great place.
Click
HERE to participate the survey.
Maybe you are looking for
-
How do i get safari off my mac?
I don't like safari, I don't use it, and I want the updates to stop! How can I get my mac to recognise g-mail as my primary e-mail?
-
I received an email from Apple about fifteen minutes ago saying that "per your request" I had downgraded to a free account for iCloud. But I had made no such request! In fact, I had expected Apple to charge me $20.00 for a full 15 GB of storage. A
-
I just got a Nano 3rd gen from someone and it's not doing as I wish. When I connect it to a computer, sometimes it will be recognised and sometimes it won't. When it's not recognised, the Apple logo will just flash on and off for hours. I kept it plu
-
Airport Express 1st gen A1264 can't be seen in Airport Utility 6.3.2 in OS X 10.10.2
I have acquired a 1st gen 802.11n airport express base station and I am trying to set it up through Airport utility but no matter what I try It won't recognize the device. I am using a 2014 MBP w retina display, 2.8 GHz Intel Core i7, won't be get pi
-
Project Online report templates
Hi I, being a novice, have managed to mess up all the out of box reports that come with Project Online. Is there anyway that I can have these reports reinstated to a pre-messed up state. I promise not to edit the templates again. Thanks Alex