Why wlappc ANT task forces aways the generation of the EJB classes ?

I've got a problem with the ANT task "wlappc" witch interfaces Weblogic compilator.
In fact, I would like to execute the ebj compilation only when needed (if the deployment descriptor or a class changed for example).
It seems that this is the default behavior and the 'forcegeneration' option of the wlappc Ant task can change it (the doc is below).
forceGeneration :
Forces generation of EJB and JSP classes. Without this flag, the classes will not be regenerated unless a checksum indicates that it is necessary.
So I wrote :
<wlappc source="${descriptors}/CommandeEntities" output="${build}/CommandsEntities.jar" keepgenerated="true" verbose="true" forcegeneration="false">
     <classpath refid="ejb.classpath"/>
</wlappc>
but I got the folowing result :
ejbjar:
[wlappc] Warning, output location exists H:\devWv2\wv2\build\CommandesEntities.jar
[wlappc] Created working directory: C:\DOCUME~1\vdoneva\LOCALS~1\Temp\appcgen_1221729775921_CommandesEntities
[wlappc] 18 sept. 2008 11:22:59 weblogic.diagnostics.debug.DebugLogger debug
[wlappc] FIN: [VersionHelper] Recompiling because no previous hashes found
[wlappc] 18 sept. 2008 11:22:59 weblogic.diagnostics.debug.DebugLogger debug
[wlappc] FIN: [EJBCompiler] Compliance Checker said bean was compliant
[wlappc] 18 sept. 2008 11:22:59 weblogic.diagnostics.debug.DebugLogger debug
[wlappc] FIN: [EJBCompiler] Generating Bean Sources
[wlappc] 18 sept. 2008 11:22:59 weblogic.diagnostics.debug.DebugLogger debug
[wlappc] FIN: [EJBCompiler] Generating source for ejb WCritereListeMulticritere
[wlappc] 18 sept. 2008 11:22:59 weblogic.diagnostics.debug.DebugLogger debug
[wlappc] FIN: [EJBCompiler] Generated the following sources for this EJB: [C:\DOCUME~1\vdoneva\LOCALS~1\Temp\appcgen_1221729775921_CommandesEntities\com\experian\wv2\db\WCritereListeMulticritere_u6449c_LocalHomeImpl.java, C:\DOCUME~1\vdoneva\LOCALS~1\Temp\appcgen_1221729775921_CommandesEntities\com\experian\wv2\db\WCritereListeMulticritere_u6449c_ELOImpl.java]
[wlappc] 18 sept. 2008 11:22:59 weblogic.diagnostics.debug.DebugLogger debug
[wlappc] FIN: [EJBCompiler] Generating Persistence Sources
[wlappc] 18 sept. 2008 11:22:59 weblogic.diagnostics.debug.DebugLogger debug
[wlappc] FIN: [EJBCompiler] Generating Bean Sources
[wlappc] 18 sept. 2008 11:22:59 weblogic.diagnostics.debug.DebugLogger debug
[wlappc] FIN: [EJBCompiler] Generating source for ejb Document
[wlappc] 18 sept. 2008 11:23:00 weblogic.diagnostics.debug.DebugLogger debug
[wlappc] FIN: [EJBCompiler] Generated the following sources for this EJB: [C:\DOCUME~1\vdoneva\LOCALS~1\Temp\appcgen_1221729775921_CommandesEntities\com\experian\wv2\db\Document_6vm6yi_LocalHomeImpl.java, C:\DOCUME~1\vdoneva\LOCALS~1\Temp\appcgen_1221729775921_CommandesEntities\com\experian\wv2\db\Document_6vm6yi_ELOImpl.java]
[wlappc] 18 sept. 2008 11:23:02 weblogic.diagnostics.debug.DebugLogger debug
[wlappc] FIN: [EJBCompiler] Generating Persistence Sources
[wlappc] 18 sept. 2008 11:23:02 weblogic.diagnostics.debug.DebugLogger debug
[wlappc] FIN: [EJBCompiler] Compiling EJB sources
[wlappc] Note: Some input files use unchecked or unsafe operations.
[wlappc] Note: Recompile with -Xlint:unchecked for details.
[wlappc] 18 sept. 2008 11:23:10 weblogic.diagnostics.debug.DebugLogger debug
[wlappc] FIN: [EJBCompiler] Recompilation completed
[wlappc] 18 sept. 2008 11:23:10 weblogic.diagnostics.debug.DebugLogger debug
[wlappc] FIN: [EJBCompiler] Rmic completed
[wlappc] Compilation completed successfully.
[jar] Updating jar: H:\devWv2\wv2\build\CommandesEntities.jar
BUILD SUCCESSFUL
All the classes witch hasn't changed has been checked and regenerated. The compliler says "Recompiling because no previous hashes found".
But why ? It could be besause it creates a different working directory each time I execute this ant task ? Is this working directory configurable ?
Would you have any idea of what's happening ?
Thanks.

You can find this in the 'org\apache\tools\ant\taskdefs\defaults.properties'
file of %wl-home%\server\lib\ant\ant.jar
--Sathish
<Michael Lee> wrote in message news:[email protected]..
I mean the definition of "wlappc" not the help for wlappc???thx.
i.e.
where can i find the sentence list below:
<taskdef name="wlappc" classname="weblogic.ant.taskdefs.j2ee.Appc"/>
I mean which files this "taskdef" is being in .

Similar Messages

  • Properties file not found by classloader when using wlappc ant task

    I have encountered a problem with the WebLogic Ant task "wlappc". When this task compiles a webmodule that uses the struts 1.1 framework I get the below error. This struts based web module deploys and runs fine on BEA Weblogic 8.1 SP2 as an exploded EAR structure. But when I attempt to precompile all the J2EE modules the struts web module will not compile with wlappc. The project is strutured correctly in a split directory structure. The problem area seems to be that we are using the struts-el (struts-el.jar) classes which need the properties files located in the struts.jar. The classloader seems to space out when running via the wlappc ant task. I tried adjusting the classpath via the "classpath" wlappc ant task attribute - but no success. Has anyone had this or a similiar problem?
    Any suggestions would be greatly appreciated!
    Thanks in advance,
    Scott
    Error from ant task is as such:
    compile:
    [javac] Compiling 256 source files to C:\My Builds\WWL\build\wwlentityejb
    [javac] Compiling 4 source files to C:\My Builds\WWL\build\wwlsessejb
    [javac] Compiling 91 source files to C:\My Builds\WWL\build\wwlweb\WEB-INF\classes
    appc:
    [wlappc] [appc] Compiling EAR module 'wwltestweb'
    [wlappc] [JspcInvoker]Checking web app for compliance.
    [wlappc] <Jul 28, 2004 4:38:47 PM GMT-05:00> <Info> <HTTP> <BEA-101047> <[ComplianceChecker] Validating the servlet element with servlet-name named "JUnitEETestServlet".>
    [wlappc] <Jul 28, 2004 4:38:48 PM GMT-05:00> <Info> <HTTP> <BEA-101047> <[ComplianceChecker] Checking servlet-mapping for servlet name : "JUnitEETestServlet".>
    [wlappc] [appc] Compiling EAR module 'wwlweb'
    [wlappc] [JspcInvoker]Checking web app for compliance.
    [wlappc] <Jul 28, 2004 4:38:48 PM GMT-05:00> <Info> <HTTP> <BEA-101047> <[ComplianceChecker] Validating the servlet element with servlet-name named "wwlActionServlet".>
    [wlappc] <Jul 28, 2004 4:38:48 PM GMT-05:00> <Info> <HTTP> <BEA-101047> <[ComplianceChecker] Checking servlet-mapping for servlet name : "wwlActionServlet".>
    [wlappc] <Jul 28, 2004 4:38:48 PM GMT-05:00> <Info> <HTTP> <BEA-101047> <[ComplianceChecker] Checking filter-mapping with filter-name "I18NFilter".>
    [wlappc] <Jul 28, 2004 4:38:48 PM GMT-05:00> <Info> <HTTP> <BEA-101047> <[ComplianceChecker] Checking filter-mapping with filter-name "Security Filter".>
    [wlappc] [jspc] parsing /admin/jsps/menu.jsp:
    [wlappc] Jul 28, 2004 4:38:50 PM org.apache.struts.util.MessageResourcesFactory createFactory
    [wlappc] SEVERE: MessageResourcesFactory.createFactory
    [wlappc] java.lang.ClassNotFoundException: org.apache.struts.util.PropertyMessageResourcesFactory
    [wlappc] at java.net.URLClassLoader$1.run(URLClassLoader.java:198)
    [wlappc] at java.security.AccessController.doPrivileged(Native Method)
    [wlappc] at java.net.URLClassLoader.findClass(URLClassLoader.java:186)
    [wlappc] at java.lang.ClassLoader.loadClass(ClassLoader.java:299)
    [wlappc] at sun.misc.Launcher$AppClassLoader.loadClass(Launcher.java:272)
    [wlappc] at java.lang.ClassLoader.loadClass(ClassLoader.java:255)
    [wlappc] at org.apache.struts.util.RequestUtils.applicationClass(RequestUtils.java:207)
    [wlappc] at org.apache.struts.util.MessageResourcesFactory.createFactory(MessageResourcesFactory.java:192)
    [wlappc] at org.apache.struts.util.MessageResources.getMessageResources(MessageResources.java:576)
    [wlappc] at org.apache.struts.util.RequestUtils.<clinit>(RequestUtils.java:134)
    [wlappc] at org.apache.struts.util.MessageResourcesFactory.createFactory(MessageResourcesFactory.java:192)
    [wlappc] at org.apache.struts.util.MessageResources.getMessageResources(MessageResources.java:576)
    [wlappc] at org.apache.struts.taglib.html.BaseTag.<clinit>(BaseTag.java:94)
    [wlappc] at java.lang.Class.forName0(Native Method)
    [wlappc] at java.lang.Class.forName(Class.java:140)
    [wlappc] at org.apache.strutsel.taglib.html.ELBaseTagBeanInfo.class$(ELBaseTagBeanInfo.java:81)
    [wlappc] at org.apache.strutsel.taglib.html.ELBaseTagBeanInfo.getPropertyDescriptors(ELBaseTagBeanInfo.java:81)
    [wlappc] at java.beans.Introspector.getTargetPropertyInfo(Introspector.java:436)
    [wlappc] at java.beans.Introspector.getBeanInfo(Introspector.java:372)
    [wlappc] at java.beans.Introspector.getBeanInfo(Introspector.java:207)
    [wlappc] at java.beans.Introspector.getBeanInfo(Introspector.java:193)
    [wlappc] at weblogic.servlet.jsp.StandardTagLib.parseTagDD(StandardTagLib.java:1323)
    [wlappc] at weblogic.servlet.jsp.StandardTagLib.parseDD(StandardTagLib.java:1261)
    [wlappc] at weblogic.servlet.jsp.StandardTagLib.<init>(StandardTagLib.java:292)
    [wlappc] at weblogic.servlet.jsp.TagLibHelper.loadTagLib(TagLibHelper.java:314)
    [wlappc] at weblogic.servlet.jsp.JspLexer.loadTagLib(JspLexer.java:145)
    [wlappc] at weblogic.servlet.jsp.JspLexer.mTAGLIB_DIRECTIVE_BODY(JspLexer.java:5015)
    [wlappc] at weblogic.servlet.jsp.JspLexer.mTAGLIB_DIRECTIVE(JspLexer.java:4853)
    [wlappc] at weblogic.servlet.jsp.JspLexer.mDIRECTIVE(JspLexer.java:4699)
    [wlappc] at weblogic.servlet.jsp.JspLexer.mSTANDARD_THING(JspLexer.java:2094)
    [wlappc] at weblogic.servlet.jsp.JspLexer.mTOKEN(JspLexer.java:1880)
    [wlappc] at weblogic.servlet.jsp.JspLexer.nextToken(JspLexer.java:1753)
    [wlappc] at weblogic.servlet.jsp.JspLexer.parse(JspLexer.java:963)
    [wlappc] at weblogic.servlet.jsp.JspParser.doit(JspParser.java:106)
    [wlappc] at weblogic.servlet.jsp.JspParser.parse(JspParser.java:230)
    [wlappc] at weblogic.servlet.jsp.Jsp2Java.outputs(Jsp2Java.java:125)
    [wlappc] at weblogic.utils.compiler.CodeGenerator.generate(CodeGenerator.java:258)
    [wlappc] at weblogic.jspc.runJspc(jspc.java:550)
    [wlappc] at weblogic.jspc.runJspc(jspc.java:437)
    [wlappc] at weblogic.servlet.jsp.JspcInvoker.compile(JspcInvoker.java:163)
    [wlappc] at weblogic.appc.compileWAR(appc.java:859)
    [wlappc] at weblogic.appc.compileModules(appc.java:650)
    [wlappc] at weblogic.appc.compileEAR(appc.java:733)
    [wlappc] at weblogic.appc.compileInput(appc.java:458)
    [wlappc] at weblogic.appc.runBody(appc.java:184)
    [wlappc] at weblogic.utils.compiler.Tool.run(Tool.java:146)
    [wlappc] at weblogic.utils.compiler.Tool.run(Tool.java:103)
    [wlappc] at weblogic.appc.main(appc.java:1028)
    [wlappc] at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
    [wlappc] at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:39)
    [wlappc] at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25)
    [wlappc] at java.lang.reflect.Method.invoke(Method.java:324)
    [wlappc] at weblogic.ant.taskdefs.j2ee.CompilerTask.invokeMain(CompilerTask.java:278)
    [wlappc] at weblogic.ant.taskdefs.j2ee.Appc.execute(Appc.java:179)
    [wlappc] at org.apache.tools.ant.Task.perform(Task.java:341)
    [wlappc] at org.apache.tools.ant.Target.execute(Target.java:309)
    [wlappc] at org.apache.tools.ant.Target.performTasks(Target.java:336)
    [wlappc] at org.apache.tools.ant.Project.executeTarget(Project.java:1339)
    [wlappc] at org.apache.tools.ant.Project.executeTargets(Project.java:1255)
    [wlappc] at org.apache.tools.ant.Main.runBuild(Main.java:609)
    [wlappc] at org.apache.tools.ant.Main.start(Main.java:196)
    [wlappc] at org.apache.tools.ant.Main.main(Main.java:235)
    [wlappc] Jul 28, 2004 4:38:50 PM org.apache.struts.util.MessageResourcesFactory createFactory
    [wlappc] SEVERE: MessageResourcesFactory.createFactory
    [wlappc] java.lang.ExceptionInInitializerError
    [wlappc] at org.apache.struts.util.MessageResourcesFactory.createFactory(MessageResourcesFactory.java:192)
    [wlappc] at org.apache.struts.util.MessageResources.getMessageResources(MessageResources.java:576)
    [wlappc] at org.apache.struts.taglib.html.BaseTag.<clinit>(BaseTag.java:94)
    [wlappc] at java.lang.Class.forName0(Native Method)
    [wlappc] at java.lang.Class.forName(Class.java:140)
    [wlappc] at org.apache.strutsel.taglib.html.ELBaseTagBeanInfo.class$(ELBaseTagBeanInfo.java:81)
    [wlappc] at org.apache.strutsel.taglib.html.ELBaseTagBeanInfo.getPropertyDescriptors(ELBaseTagBeanInfo.java:81)
    [wlappc] at java.beans.Introspector.getTargetPropertyInfo(Introspector.java:436)
    [wlappc] at java.beans.Introspector.getBeanInfo(Introspector.java:372)
    [wlappc] at java.beans.Introspector.getBeanInfo(Introspector.java:207)
    [wlappc] at java.beans.Introspector.getBeanInfo(Introspector.java:193)
    [wlappc] at weblogic.servlet.jsp.StandardTagLib.parseTagDD(StandardTagLib.java:1323)
    [wlappc] at weblogic.servlet.jsp.StandardTagLib.parseDD(StandardTagLib.java:1261)
    [wlappc] at weblogic.servlet.jsp.StandardTagLib.<init>(StandardTagLib.java:292)
    [wlappc] at weblogic.servlet.jsp.TagLibHelper.loadTagLib(TagLibHelper.java:314)
    [wlappc] at weblogic.servlet.jsp.JspLexer.loadTagLib(JspLexer.java:145)
    [wlappc] at weblogic.servlet.jsp.JspLexer.mTAGLIB_DIRECTIVE_BODY(JspLexer.java:5015)
    [wlappc] at weblogic.servlet.jsp.JspLexer.mTAGLIB_DIRECTIVE(JspLexer.java:4853)
    [wlappc] at weblogic.servlet.jsp.JspLexer.mDIRECTIVE(JspLexer.java:4699)
    [wlappc] at weblogic.servlet.jsp.JspLexer.mSTANDARD_THING(JspLexer.java:2094)
    [wlappc] at weblogic.servlet.jsp.JspLexer.mTOKEN(JspLexer.java:1880)
    [wlappc] at weblogic.servlet.jsp.JspLexer.nextToken(JspLexer.java:1753)
    [wlappc] at weblogic.servlet.jsp.JspLexer.parse(JspLexer.java:963)
    [wlappc] at weblogic.servlet.jsp.JspParser.doit(JspParser.java:106)
    [wlappc] at weblogic.servlet.jsp.JspParser.parse(JspParser.java:230)
    [wlappc] at weblogic.servlet.jsp.Jsp2Java.outputs(Jsp2Java.java:125)
    [wlappc] at weblogic.utils.compiler.CodeGenerator.generate(CodeGenerator.java:258)
    [wlappc] at weblogic.jspc.runJspc(jspc.java:550)
    [wlappc] at weblogic.jspc.runJspc(jspc.java:437)
    [wlappc] at weblogic.servlet.jsp.JspcInvoker.compile(JspcInvoker.java:163)
    [wlappc] at weblogic.appc.compileWAR(appc.java:859)
    [wlappc] at weblogic.appc.compileModules(appc.java:650)
    [wlappc] at weblogic.appc.compileEAR(appc.java:733)
    [wlappc] at weblogic.appc.compileInput(appc.java:458)
    [wlappc] at weblogic.appc.runBody(appc.java:184)
    [wlappc] at weblogic.utils.compiler.Tool.run(Tool.java:146)
    [wlappc] at weblogic.utils.compiler.Tool.run(Tool.java:103)
    [wlappc] at weblogic.appc.main(appc.java:1028)
    [wlappc] at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
    [wlappc] at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:39)
    [wlappc] at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25)
    [wlappc] at java.lang.reflect.Method.invoke(Method.java:324)
    [wlappc] at weblogic.ant.taskdefs.j2ee.CompilerTask.invokeMain(CompilerTask.java:278)
    [wlappc] at weblogic.ant.taskdefs.j2ee.Appc.execute(Appc.java:179)
    [wlappc] at org.apache.tools.ant.Task.perform(Task.java:341)
    [wlappc] at org.apache.tools.ant.Target.execute(Target.java:309)
    [wlappc] at org.apache.tools.ant.Target.performTasks(Target.java:336)
    [wlappc] at org.apache.tools.ant.Project.executeTarget(Project.java:1339)
    [wlappc] at org.apache.tools.ant.Project.executeTargets(Project.java:1255)
    [wlappc] at org.apache.tools.ant.Main.runBuild(Main.java:609)
    [wlappc] at org.apache.tools.ant.Main.start(Main.java:196)
    [wlappc] at org.apache.tools.ant.Main.main(Main.java:235)
    [wlappc] Caused by: java.lang.NullPointerException
    [wlappc] at org.apache.struts.util.MessageResources.getMessageResources(MessageResources.java:577)
    [wlappc] at org.apache.struts.util.RequestUtils.<clinit>(RequestUtils.java:134)
    [wlappc] ... 52 more
    BUILD FAILED
    file:C:/My Sources/WWLEar/wwlear/build.xml:128: weblogic.utils.compiler.ToolFailureException: [J2EE:160119]Appc is unable to process the file 'C:\My Builds\WWL\build'. The following error occurred:
    java.lang.ExceptionInInitializerError
    at java.lang.Class.forName0(Native Method)
    at java.lang.Class.forName(Class.java:140)
    at org.apache.strutsel.taglib.html.ELBaseTagBeanInfo.class$(ELBaseTagBeanInfo.java:81)
    at org.apache.strutsel.taglib.html.ELBaseTagBeanInfo.getPropertyDescriptors(ELBaseTagBeanInfo.java:81)
    at java.beans.Introspector.getTargetPropertyInfo(Introspector.java:436)
    at java.beans.Introspector.getBeanInfo(Introspector.java:372)
    at java.beans.Introspector.getBeanInfo(Introspector.java:207)
    at java.beans.Introspector.getBeanInfo(Introspector.java:193)
    at weblogic.servlet.jsp.StandardTagLib.parseTagDD(StandardTagLib.java:1323)
    at weblogic.servlet.jsp.StandardTagLib.parseDD(StandardTagLib.java:1261)
    at weblogic.servlet.jsp.StandardTagLib.<init>(StandardTagLib.java:292)
    at weblogic.servlet.jsp.TagLibHelper.loadTagLib(TagLibHelper.java:314)
    at weblogic.servlet.jsp.JspLexer.loadTagLib(JspLexer.java:145)
    at weblogic.servlet.jsp.JspLexer.mTAGLIB_DIRECTIVE_BODY(JspLexer.java:5015)
    at weblogic.servlet.jsp.JspLexer.mTAGLIB_DIRECTIVE(JspLexer.java:4853)
    at weblogic.servlet.jsp.JspLexer.mDIRECTIVE(JspLexer.java:4699)
    at weblogic.servlet.jsp.JspLexer.mSTANDARD_THING(JspLexer.java:2094)
    at weblogic.servlet.jsp.JspLexer.mTOKEN(JspLexer.java:1880)
    at weblogic.servlet.jsp.JspLexer.nextToken(JspLexer.java:1753)
    at weblogic.servlet.jsp.JspLexer.parse(JspLexer.java:963)
    at weblogic.servlet.jsp.JspParser.doit(JspParser.java:106)
    at weblogic.servlet.jsp.JspParser.parse(JspParser.java:230)
    at weblogic.servlet.jsp.Jsp2Java.outputs(Jsp2Java.java:125)
    at weblogic.utils.compiler.CodeGenerator.generate(CodeGenerator.java:258)
    at weblogic.jspc.runJspc(jspc.java:550)
    at weblogic.jspc.runJspc(jspc.java:437)
    at weblogic.servlet.jsp.JspcInvoker.compile(JspcInvoker.java:163)
    at weblogic.appc.compileWAR(appc.java:859)
    at weblogic.appc.compileModules(appc.java:650)
    at weblogic.appc.compileEAR(appc.java:733)
    at weblogic.appc.compileInput(appc.java:458)
    at weblogic.appc.runBody(appc.java:184)
    at weblogic.utils.compiler.Tool.run(Tool.java:146)
    at weblogic.utils.compiler.Tool.run(Tool.java:103)
    at weblogic.appc.main(appc.java:1028)
    at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
    at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:39)
    at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25)
    at java.lang.reflect.Method.invoke(Method.java:324)
    at weblogic.ant.taskdefs.j2ee.CompilerTask.invokeMain(CompilerTask.java:278)
    at weblogic.ant.taskdefs.j2ee.Appc.execute(Appc.java:179)
    at org.apache.tools.ant.Task.perform(Task.java:341)
    at org.apache.tools.ant.Target.execute(Target.java:309)
    at org.apache.tools.ant.Target.performTasks(Target.java:336)
    at org.apache.tools.ant.Project.executeTarget(Project.java:1339)
    at org.apache.tools.ant.Project.executeTargets(Project.java:1255)
    at org.apache.tools.ant.Main.runBuild(Main.java:609)
    at org.apache.tools.ant.Main.start(Main.java:196)
    at org.apache.tools.ant.Main.main(Main.java:235)
    Caused by: java.lang.NullPointerException
    at org.apache.struts.util.MessageResources.getMessageResources(MessageResources.java:577)
    at org.apache.struts.taglib.html.BaseTag.<clinit>(BaseTag.java:94)
    ... 49 more
    - with nested exception:
    [java.lang.ExceptionInInitializerError]
    Total time: 42 seconds

    Hi Rob,
    I also gets this error when I deploy my application using struts 1.2.2 with struts-el.jar also.
    The error is thrown when the server comile the jsp's :
    <BEA-101047>[ServletContext(id=20164970,name=tracer,context-path=/tracer)] classfile up-to-date for JSP /webdatagrid/layouts/default/customize.jsp>
    ####<Sep 2, 2004 2:05:26 PM EDT> <Info> <HTTP> <nyeqshu2> <sit1tracerweb> <ExecuteThread: '3' for queue: 'weblogic.kernel.System'> <<WLS Kernel>> <>
    <BEA-101047> <[ServletContext(id=20164970,name=tracer,context-path=/tracer)] checking /webdatagrid/layouts/default/exceldownload.jsp:>
    ####<Sep 2, 2004 2:05:30 PM EDT> <Error> <Deployer> <nyeqshu2> <sit1tracerweb> <ExecuteThread: '3' for queue: 'weblogic.kernel.System'> <<WLS Kernel>>
    <>
    <BEA-149201> <Failed to complete the deployment task with ID 0 for the application tracer-webapp-application-uncontrolled.
    java.lang.NullPointerException
    at org.apache.struts.util.MessageResources.getMessageResources(MessageResources.java:577)
    at org.apache.struts.taglib.html.BaseTag.<clinit>(BaseTag.java:94)
    at java.lang.Class.forName0(Native Method)
    at java.lang.Class.forName(Class.java:140)
    at org.apache.strutsel.taglib.html.ELBaseTagBeanInfo.class$(ELBaseTagBeanInfo.java:81)
    at org.apache.strutsel.taglib.html.ELBaseTagBeanInfo.getPropertyDescriptors(ELBaseTagBeanInfo.java:81)
    at java.beans.Introspector.getTargetPropertyInfo(Introspector.java:436)
    at java.beans.Introspector.getBeanInfo(Introspector.java:372)
    at java.beans.Introspector.getBeanInfo(Introspector.java:207)
    at java.beans.Introspector.getBeanInfo(Introspector.java:193)
    at weblogic.servlet.jsp.StandardTagLib.parseTagDD(StandardTagLib.java:1323)
    at weblogic.servlet.jsp.StandardTagLib.parseDD(StandardTagLib.java:1261)
    at weblogic.servlet.jsp.StandardTagLib.<init>(StandardTagLib.java:292)
    at weblogic.servlet.jsp.TagLibHelper.loadTagLib(TagLibHelper.java:314)
    at weblogic.servlet.jsp.JspLexer.loadTagLib(JspLexer.java:145)
    at weblogic.servlet.jsp.JspLexer.mTAGLIB_DIRECTIVE_BODY(JspLexer.java:5015)
    at weblogic.servlet.jsp.JspLexer.mTAGLIB_DIRECTIVE(JspLexer.java:4853)
    at weblogic.servlet.jsp.JspLexer.mDIRECTIVE(JspLexer.java:4699)
    at weblogic.servlet.jsp.JspLexer.mSTANDARD_THING(JspLexer.java:2094)
    at weblogic.servlet.jsp.JspLexer.mTOKEN(JspLexer.java:1880)
    at weblogic.servlet.jsp.JspLexer.nextToken(JspLexer.java:1753)
    at weblogic.servlet.jsp.JspLexer.parse(JspLexer.java:963)
    at weblogic.servlet.jsp.JspParser.doit(JspParser.java:106)
    at weblogic.servlet.jsp.JspParser.parse(JspParser.java:230)
    at weblogic.servlet.jsp.Jsp2Java.outputs(Jsp2Java.java:125)
    at weblogic.utils.compiler.CodeGenerator.generate(CodeGenerator.java:258)
    at weblogic.servlet.jsp.Precompiler.compileOne(Precompiler.java:191)
    at weblogic.servlet.jsp.Precompiler.compile(Precompiler.java:71)
    at weblogic.servlet.jsp.Precompiler.compile(Precompiler.java:82)
    at weblogic.servlet.internal.WebAppServletContext.precompileJSPs(WebAppServletContext.java:4908)
    at weblogic.servlet.internal.WebAppServletContext.precompileJSPs(WebAppServletContext.java:4886)
    at weblogic.servlet.internal.WebAppServletContext.prepareFromDescriptors(WebAppServletContext.java:2342)
    at weblogic.servlet.internal.WebAppServletContext.init(WebAppServletContext.java:565)
    at weblogic.servlet.internal.WebAppServletContext.<init>(WebAppServletContext.java:493)
    at weblogic.servlet.internal.HttpServer.loadWebApp(HttpServer.java:628)
    at weblogic.servlet.internal.WebAppModule.prepare(WebAppModule.java:626)
    at weblogic.j2ee.J2EEApplicationContainer.prepareWebModule(J2EEApplicationContainer.java:3011)
    at weblogic.j2ee.J2EEApplicationContainer.prepareModules(J2EEApplicationContainer.java:1532)
    at weblogic.j2ee.J2EEApplicationContainer.prepare(J2EEApplicationContainer.java:1188)
    at weblogic.j2ee.J2EEApplicationContainer.prepare(J2EEApplicationContainer.java:1031)
    at weblogic.management.deploy.slave.SlaveDeployer$ComponentActivateTask.prepareContainer(SlaveDeployer.java:2602)
    at weblogic.management.deploy.slave.SlaveDeployer$ActivateTask.createContainer(SlaveDeployer.java:2552)
    at weblogic.management.deploy.slave.SlaveDeployer$ActivateTask.prepare(SlaveDeployer.java:2474)
    at weblogic.management.deploy.slave.SlaveDeployer.processPrepareTask(SlaveDeployer.java:798)
    at weblogic.management.deploy.slave.SlaveDeployer.prepareDelta(SlaveDeployer.java:507)
    at weblogic.management.deploy.slave.SlaveDeployer.prepareUpdate(SlaveDeployer.java:465)
    at weblogic.drs.internal.SlaveCallbackHandler$1.execute(SlaveCallbackHandler.java:25)
    at weblogic.kernel.ExecuteThread.execute(ExecuteThread.java:197)
    at weblogic.kernel.ExecuteThread.run(ExecuteThread.java:170)
    --------------- nested within: ------------------
    weblogic.management.ManagementException: - with nested exception:
    [java.lang.NullPointerException]
    at weblogic.management.deploy.slave.SlaveDeployer$ActivateTask.prepare(SlaveDeployer.java:2491)
    at weblogic.management.deploy.slave.SlaveDeployer.processPrepareTask(SlaveDeployer.java:798)
    at weblogic.management.deploy.slave.SlaveDeployer.prepareDelta(SlaveDeployer.java:507)
    at weblogic.management.deploy.slave.SlaveDeployer.prepareUpdate(SlaveDeployer.java:465)
    at weblogic.drs.internal.SlaveCallbackHandler$1.execute(SlaveCallbackHandler.java:25)
    at weblogic.kernel.ExecuteThread.execute(ExecuteThread.java:197)
    at weblogic.kernel.ExecuteThread.run(ExecuteThread.java:170)
    >
    ####<Sep 2, 2004 2:37:29 PM EDT> <Info> <Deployer> <nyeqshu2> <sit1tracerweb> <ExecuteThread: '2' for queue: 'weblogic.kernel.System'> <<WLS Kernel>>
    <>
    <BEA-149059> <Module tracer of application tracer-webapp-application-1_6_3_510 is transitioning from unprepared to prepared on server sit1tracerweb
    .>
    ####<Sep 2, 2004 2:37:39 PM EDT> <Debug> <HTTP> <nyeqshu2> <sit1tracerweb> <ExecuteThread: '2' for queue: 'weblogic.kernel.System'> <<WLS Kernel>> <>
    ####<Sep 2, 2004 2:37:39 PM EDT> <Debug> <HTTP> <nyeqshu2> <sit1tracerweb> <ExecuteThread: '2' for queue: 'weblogic.kernel.System'> <<WLS Kernel>> <>
    <BEA-101211> <tracer-webapp-application-1_6_3_510:tracer Precompiling JSPs at startup with JSP config [JspConfig: verbose=true,packagePrefix=jsp_servl
    et,-compiler=javac,compileFlags=,workingDir=./applications/tracer/WEB-INF/classes,pageCheckSeconds=5,superclass=weblogic.servlet.jsp.JspBase,keepgener
    ated=true,precompileContinue=false,compilerSupportsEncoding=true,encoding=null,defaultfilename=index.jsp,compilerclass=null,noTryBlocks=true,debugEnab
    led=false,printNulls=true,jspServlet=null].>
    I've looked at the source code ant it is actually using the current thread's classloader.
    The fact is that it works fine when deployed to tomcat 4.1.30, but it fails when deploying on our weblogic managed servers.
    Thanks
    Julien De Santis
    CGI Group

  • Wlappc ANT task "runtimeFlags" attribute doesn't take effect

    I am intermittently counter "java.lang.OutOfMemoryError" error while I am running wlappc ANT task to compile jsp pages. I have lots of jsp files (about 500). According to weblogic's document, I set runtimeFlags="-J-ms512m -J-mx1024m". So my ant task looks like this:
              <wlappc source="${websrc}" output="${output}" runtimeFlags="-J-ms1024m -J-mx1024m">
              </wlappc>
              But it doesn't work. It still complains out of memory error. I tried various approach including "-J-Xms1024m -J-Xmx1024m". But not helpful at all.
              So I gave up and ended up using weblogic.appc class to build my jsp pages. So I have fully control of jvm options. I set up -Xms1024m -Xmx1024m as JVM parameters and works well.
              It looks to me that wlappc ANT task ignore runtimeFlags at all. It doesn't take any effect.
              Is it a known bug? anyone succeeded solving OutOfMemoryError by setting runtimeFlags attribute of wlappc ANT task?

    I was having the same issue.
              Try using the maxmemory argument for the standard java ant task and calling weblogic.appc:
              <java classname="weblogic.appc" fork="yes" failonerror="true" maxmemory="256m">
              <classpath>
              <fileset dir="${weblogic.home}/server/lib" includes="weblogic.jar,webservices.jar" />
              </classpath>
              <arg value="${ear.dir}" />
              <arg value="-verbose" />
              </java>

  • How to stop the generation of the trace files relate to the particular user

    Dear All,
    Please advice:
    Is it possible to stop the trace file created by a user for a particular job (sql/exp)
    For example :
    Trace files create whenever the user run the sql/exp command from his application server.
    This will created a huge files and caused the file system getting full (not in bdump but it is generation in application user home directory).
    Is there any method to stop the generation of the trace files relate to the particular user base on that job.
    thanks,
    Shanoj

    Dear SHANOJ
    This trigger will created for that specific user by dba or person who have sysdba privs. it will triggered at the login time of that user and alter the sqltrace.
    for example we have write one trigger in our database for every ddl operation in database.
    CREATE OR REPLACE TRIGGER "SYS"."SYS$DDLTRIG" after DDL on database
    declare
    v_machinename VARCHAR2(100);
    v_osuser VARCHAR2(100);
    v_dbuser VARCHAR2(100);
    v_host VARCHAR2(100);
    v_program VARCHAR2(100);
    v_instance VARCHAR2(100);
    v_date VARCHAR2(100);
    begin
    select to_char(sysdate, 'mm-dd-yyyy HH24:MI:SS'),user,sys_context('userenv','OS_
    USER'),sys_context('userenv','HOST'), (select instance_name from v$instance),(se
    lect program from v$session where sid = (select distinct sid from v$mystat)),(se
    lect machine from v$session where sid = (select distinct sid from v$mystat)) int
    o v_date,v_dbuser,v_osuser,v_host,v_instance,v_program,v_machinename from dual;
    IF ora_sysevent = 'DROP' or ora_sysevent = 'REVOKE' or ora_sysevent = 'GRANT' or
    ora_sysevent = 'CREATE' or ora_sysevent = 'TRUNCATE' or ora_sysevent = 'ALTER'
    Then
    insert into ddl_log_new(v_date,v_dbuser,v_osuser,v_host,v_instance,v_program,v_m
    achinename,V_EVENT,V_OBJECT_NAME,V_OBJECT_TYPE,V_OBJECT_OWNER) values (v_date,v_
    dbuser,v_osuser,v_host,v_instance,v_program,v_machinename,ora_sysevent,ora_dict_
    obj_name,ora_dict_obj_type,ora_dict_obj_owner);
    END IF;
    END;
    i hope above example will helpful for u,
    Regards
    Ambrish
    Edited by: ambrishr24 on Dec 5, 2012 5:02 PM
    Edited by: ambrishr24 on Dec 5, 2012 5:05 PM
    Edited by: ambrishr24 on Dec 5, 2012 5:20 PM

  • Does compiling an advanced datagrid using flex ant task require additional config other than the license property?

    Hi,
        I am trying to build my Flex app which uses the Advanced Data Grid in a couple of locations. Originally, when I built the app using the flex ant tasks, I noticed the Visualization Trial watermark show up on the screen. I then added the license tag with the serial number to my flex-config.xml and re-ran my ant build. The watermark goes away, but then when I look at the advanced datagrid, the datagrid shows up with the hierarchy, but the data does not display in the grid (only the group by nodes are visible, not the data for the leaf elements). This works fine when I build the app using my Flex Builder. Is there something I am missing or need to add to my flex ant task to make this work?
    Any help or guidance is much appreciated.
    The following is the ant task to build the module that uses the ADG:
        <target name="compile-modules" depends="compile-shared">
            <!-- Module 1 -->
            <echo>Compiling module 1...</echo>
            <mxmlc file="${modulesrc.dir}\ui\modules\mod1\Module1.mxml"
                    output="${dist.dir}\modules\mod1\Module1.swf"
                    actionscript-file-encoding="UTF-8"
                    incremental="true"
                    default-background-color="0xFFFFFF"
                    use-network="false"
                    load-externs="${extern-report-xml}">
                <load-config filename="${FLEX_HOME}/frameworks/flex-config.xml" />
                <source-path path-element="${FLEX_HOME}/frameworks"/>
                <!-- source paths -->
                <compiler.source-path path-element="${modulesrc.dir}"/>
                <!-- add external libraries -->
                <compiler.library-path dir="${main.dir}" append="true">
                    <include name="${lib.dir}"/>
                </compiler.library-path>
                <compiler.library-path dir="${FLEX_HOME}/frameworks" append="true">
                    <include name="libs" />
                    <include name="locale/{locale}" />
                </compiler.library-path>
                <compiler.debug>true</compiler.debug>
            </mxmlc>
        </target>
    And here is the ant task for the main application:
        <target name="compile-ui" depends="compile-modules">
            <mxmlc file="${src.dir}/MainApp.mxml" output="${dist.dir}/MainApp.swf"
                    actionscript-file-encoding="UTF-8" keep-generated-actionscript="false"
                    fork="true" maxmemory="1024m">
                <jvmarg value="-XX:MaxPermSize=256m"/>
                <load-config filename="${FLEX_HOME}/frameworks/flex-config.xml"/>
                <source-path path-element="${FLEX_HOME}/frameworks"/>
                <source-path path-element="${src.dir}"/>
                <source-path path-element="${main.dir}/locale/{locale}"/>
                <!-- List of SWC files or directories that contain SWC files. -->
                <!--<compiler.library-path dir="${FLEX_HOME}/frameworks" append="true">
                    <include name="libs" />
                    <include name="locale/{locale}" />
                </compiler.library-path>-->
                <compiler.library-path dir="${FLEX_HOME}/frameworks" append="true">
                    <include name="libs/datavisualization.swc" />
                    <include name="libs/flex.swc" />
                    <include name="libs/framework.swc" />
                    <include name="libs/rpc.swc" />
                    <include name="libs/utilities.swc" />
                    <include name="locale/{locale}" />
                </compiler.library-path>
                <compiler.library-path dir="${main.dir}" append="true">
                    <include name="${lib.dir}"/>
                </compiler.library-path>
                <runtime-shared-library-path path-element="${FLEX_FRAMEWORK}/framework.swc">
                    <url rsl-url="framework_3.2.0.3958.swf"/>
                    <url rsl-url="framework_3.2.0.3958.swz"/>
                </runtime-shared-library-path>
                <compiler.debug>true</compiler.debug>
            </mxmlc>
        </target>
    Regards,
    Purush

    to remove watermark i have added license key in WEB-INF\flex\license.properties file as key = value

  • Out of memory issue when executing wlappc ant task

    I am using weblogic 8.1 sp1 and doing a compilation for a little bit large EAR file using ant task. But it always throws out of memory error when the wlappc invoked the compiler to compile the jsp files.
    According to BEA's documentation<CR104610>, I put the runtimeflags with "-J-ms256m -J-mx512m" option into the wlappc tag and Ant seems recognizing this option but it didn't work. I tried every possible memory size to get rid of this problem, but the process still failed with the error message:
    The system is out of resources.
    Consult the following stack trace for details.
    java.lang.OutOfMemoryError
    - with nested exception:
    [Compilation errors : ]
    My computer has 1G memory, so it shouldn't be the hardware problem.
    Does anyone have an idea on this?
    Thanks in advance,
    Jacky

    Hi,
    Ant seems to use its own JVM and thus in the javac options during runtime,try specifying ANT java options for setting the memory parameters.
    ANT options would be memoryInitialSize and memoryMaximumSize.
    http://ant.apache.org/manual/index.html
    Hope this helps.

  • Wsdlc Ant Task - Problem creating java files in the correct package

    In eclipse, for weblogic 9.2
    Using the wsdlc WebLogic Web Services Ant Task, I am trying to auto-generate the java files for the web service based on the WSDL. I have specified the packageName as one of the parameters. However the java files are being created and packaged based on the TargetNameSpace of the WSDL rather then under the package name specified. Following is part of my build.xml
    autogen.src.dir=../code/java/beaAutoGen
    base.dest=../../../var/build/wsmToPlmWS
    bea.build.dir=beaBuild
         <target name="generate-from-wsdl" depends="prepare">
              <delete dir="${src.dir}" includeemptydirs="true" />
              <delete dir="${autogen.src.dir}" includeemptydirs="true" />
              <wsdlc srcWsdl="../config/sourceWSDL/MRPBindingPort.wsdl"
                   destJwsDir="${base.dest}/${bea.build.dir}/compiledWsdl" destImplDir="${base.dest}/${bea.build.dir}/impl"
                   packageName="com.lmco.iplm.webservices.wsmtoplm" debug="on"
                   srcServiceName="WSPlmMto_Service"
                   debugLevel="DEBUG" autoDetectWrapped="true" jaxRPCWrappedArrayStyle="true"
                   verbose="on" classpathref="bea-classpath" />
    <!-- unjar to get the all the details so we can tokenize -->
              <unjar dest="${autogen.src.dir}"
                   src="${base.dest}/${bea.build.dir}/compiledWsdl/MRPBindingPort_wsdl.jar" />
    <!-- copy over the impl file -->
              <copy todir="../code/java/src">
                   <fileset dir="${base.dest}/${bea.build.dir}/impl" />
              </copy>
         </target>

    In eclipse, for weblogic 9.2
    Using the wsdlc WebLogic Web Services Ant Task, I am trying to auto-generate the java files for the web service based on the WSDL. I have specified the packageName as one of the parameters. However the java files are being created and packaged based on the TargetNameSpace of the WSDL rather then under the package name specified. Following is part of my build.xml
    autogen.src.dir=../code/java/beaAutoGen
    base.dest=../../../var/build/wsmToPlmWS
    bea.build.dir=beaBuild
         <target name="generate-from-wsdl" depends="prepare">
              <delete dir="${src.dir}" includeemptydirs="true" />
              <delete dir="${autogen.src.dir}" includeemptydirs="true" />
              <wsdlc srcWsdl="../config/sourceWSDL/MRPBindingPort.wsdl"
                   destJwsDir="${base.dest}/${bea.build.dir}/compiledWsdl" destImplDir="${base.dest}/${bea.build.dir}/impl"
                   packageName="com.lmco.iplm.webservices.wsmtoplm" debug="on"
                   srcServiceName="WSPlmMto_Service"
                   debugLevel="DEBUG" autoDetectWrapped="true" jaxRPCWrappedArrayStyle="true"
                   verbose="on" classpathref="bea-classpath" />
    <!-- unjar to get the all the details so we can tokenize -->
              <unjar dest="${autogen.src.dir}"
                   src="${base.dest}/${bea.build.dir}/compiledWsdl/MRPBindingPort_wsdl.jar" />
    <!-- copy over the impl file -->
              <copy todir="../code/java/src">
                   <fileset dir="${base.dest}/${bea.build.dir}/impl" />
              </copy>
         </target>

  • Apt ant task suceeded but did not generate wrapper java/classes

    Hi,
    This is the first time I use apt task. Could someone help me out here.
    Thanks.
    Ant build suceeded but did not generate wrapper java/classes. Warning message I got is
    [apt] warning: Bad annotation processor factory: java.lang.ClassCastException: com.sun.istack.ws.AnnotationProcessorFactoryImpl cannot be cast to com.sun.mirror.apt.AnnotationProcessorFactory
    [apt] warning: Bad annotation processor factory: java.lang.ClassCastException: com.sun.istack.internal.ws.AnnotationProcessorFactoryImpl cannot be cast to com.sun.mirror.apt.AnnotationProcessorFactory
    [apt] warning: Annotation types without processors: [javax.jws.WebService]
    [apt] [total 725ms]
    [apt] 3 warnings
    I turned on verbose="true" and cut the command line apt -d .. -s ..
    from the ant build output.
    I executed that command line. Command suceeded, java/classes generated correctly. No warning
    <target name="run_apt" depends = "build_config_classes">
    <apt
         debug="true"
         verbose="true"
         destdir="${build_classes}"
    sourcedestdir="${apt.generated.dir}"
    sourcepath="${config.src}">
         <classpath refid="apt.classpath"/>
         <source dir="${config.src}">
         <include name="${config.pkg}/Configuration.java"/>
         </source>
    </apt>
    </target>

    try adding fork=true to apt task

  • Regarding the generation of the change log request

    Hi,
    While going through the BW310 document,i came across the below notes..
    The user can choose whether the changes called up from the different load requests are to be combined in a change log request, or whether a change log request is to be generated for each loaded request.
    How can i make the above settings.Where should i go inorder to get the screen where i can mention 'A change log request is to be generated for each loaded request'.By default the setting is like that.But i would like to know where to make these settings.
    Please help me.
    Regards,
    Rajesh janardanan

    Hi rajesh,
    If you select do not condense request into one request when activation takes places, ur generating one change log request for each loaded request. i.e while activation, each request is activated seperately and for each activation, one change log request is created. The advantage of this is you can delete individual request at the time of deletion from the ODS ( if at all u want to ). Suppose you club request and activate, and in the one request u want to delete later, then ull endup deleting all the request which are activated together.
    Process request serially when activation takes place has nothing to do with the change log requests. It sees to it that the activation process is serial instead pf parellel.
    Please post for more
    Sriram

  • Are the WLS 9.1 Web Service Ant Tasks ready for prime time?

    I am trying to create a Proof of Concept (POC) for Enterprise and B2B Services at Wendy's Int'l, Inc.
    As part of this POC, I created a WSDL for an in-house service and then used the wsdlc and jwsc Ant Tasks to translate this WSDL to Java classes and ultimately (I hoped) a deployable services.
    In this document, I describe the issues I encountered setting up what I consider to be a simple POC.
    I'll try to attach my WSDL file and build.xml so you can follow along.
    I'll also try to attach my CSS file so you can compare how the generated WSDL appears in the Browser to the way I want it to appear.
    If attachments are not allowed on these forums, then I will wait and see if there is interest in those documents before I paste them under this topic.
    Some preliminary information about my environment.
    Environment:
         Windows XP Pro SP2
         WebLogic 9.1
         Java 1.5.0_04
    Service Name:
         AppRelease
    Note: If I modify my WSDL (perhaps to add a new Operation or to change the definition of an element) and run wsdlc again, the AppReleaseSOAPPortImpl.java file is overwritten For this reason, I implemented my service logic in a class called AppReleaseServiceImple.java.
    Now, for the issues.
    1.     Bug:
    In the WSDL generated by wsdlc, the wsdl:part child of the wsdl:message tag is erroneously prefixed with a colon.
    This occurs whether or not I specify a prefix for the http://schemas.xmlsoap.org/wsdl/ namespace.
    Work around: Extract the wsdl from the jar file, fix it and add it back into the jar.
    2.     Bug:
    In the WSDL generated by wsdlc, the wsdl:input and wsdl:output children of the wsdl:operation child of wsdl:portType tag are erroneously prefixed with a colon. Like 1 above, this occurs whether or not I specify a prefix for the http://schemas.xmlsoap.org/wsdl/ namespace.
    Work around: Extract the wsdl from the jar file, fix it and add it back into the jar.
    The error message generated by Bugs 1 and 2 is not helpful in diagnosing the problem:
    [jwsc] Error at line:46 col:7 ':' expected [?! -- [CDATA[ ]
    3.     Bug:
    In the WSDL generated by wsdlc, the documentation elements have all of my html elements stripped out, as well as my xhtml and wsdl namespace references. This completely negates one of the best features of the documentation tag, being able to present the WSDL in a browser as a nicely formatted, human friendly document which is also the underlying WSDL that can be viewed when the person views the source document.
    I label this as a bug because it greatly reduces the functionality of the resulting WSDL.
    4.     Annoyance:
    The WSDL generated by wsdlc has all of my comments stripped out, except the comments in the xsd:schema section of the wsdl:types element. I would prefer that all my comments be left in the WSDL, but if comments must be stripped out then I think all of the comments should be stripped out.
    5.     Annoyance:
    The WSDL generated by wsdlc has my CSS specification stripped.
    Work around: I don’t know if adding the CSS back will do any good because I have not yet created a deployable service (see the last issue below).
    6.     Annoyance:
    The WSDL generated by wsdlc has different namespace prefixes than the ones I specified for my application's namespace and for the http://schemas.xmlsoap.org/wsdl/soap/ namespace.
    Work around: Perform a find/replace on namespace prefixes "s0" and "s1" to return them to my prefered values.
    Another thing I can do at this point is simply replace the generated WSDL in the jar file with my original WSDL. This would address issues 1 thru 6 above.
    7.     Annoyance:
    The java source files created by wsdlc are put into a jar file. This makes it annoying when working within a traditional IDE like Eclipse because there is no way to reference the source files within the jar as working source.
    Work around: Extract the source files from the jar and identify the resulting directory structure as part of the source structure of the project.
    8.     Bug:
    The jwsc task complains if the same parameter name is used in multiple operations. I received the following Errors from jwsc:
    [jwsc] C:\IDE\workspace\Acre-WL9.1\AppReleaseSOAPPort.java 0:0
    [jwsc] [ERROR] - Parameter element "{http://acre.services.wendys.com/AppRelease/}garRequest" is not unique across document/literal bare WebService.
    Since the operation names are unique, I see no reason to also require uniqueness in the parameter names used by those operations.
    Work around: Use unique element names for the input parameters of the services operations.
    9.     Bug:
    Once items 1, 2 and 8 above are taken care of, jwsc fails with the following error:
    java.lang.AssertionError: java.lang.ClassNotFoundException: weblogic.j2ee.descriptor.ApplicationBeanImpl
    This seems to be due to the weblogic.jar file not being in the System Classpath.
    However, I should note that when I set verbose="on" and debug="on" in the jwsc ant task, there was a message from the task which stated "[jwsc] [search path for class files: [big freakin’ jar list]". In the big freakin’ jar list, I did find weblogic.jar and weblogic.jar has the required ApplicationBeanImpl. This indicates to me that the jwsc task does not fully honor either its classpathref attribute, nor an embedded classpath element.
    Work around: Make sure the weblogic.jar is in the System Classpath.
    10.     Bug:
    I fixed bug #9 by running a setDomainEnv script and then ran my ant task. This time I received the following output:
    ant build-serviceBuildfile: build.xml
    build-service:
    [jwsc] 1 JWS files will be processed.
    [jwsc] Processing JWS: C:\IDE\workspace\Acre-WL9.1\src\com\wendys\services\acre\AppReleaseServiceImpl.java
    [jwsc] JWS: C:\IDE\workspace\Acre-WL9.1\src\com\wendys\services\acre\AppReleaseServiceImpl.java Validated.
    [AntUtil.deleteDir] Deleting directory <some temporary directory>
    BUILD FAILED
    java.lang.ExceptionInInitializerError
    At this point, I am completely stymied about how to proceed.
    I wonder what new issues await once this 10th issue is addressed.
    Really, is this tool set ready for prime time?

    <i>Sorry to hear you are having so many issues with using the WLS 9.1 web service Ant tasks, inside of Eclipse.
    I generally create a User Library for the couple weblogic jars needed, and use it (the User Library) in my Eclipse projects that I create JWSes in.</i><br>
    I also have a separate WebLogic Library in Eclipse (actually 2 libraries since I work with WL 8.1 and now WL 9.1). As you may know, one of the long-standing issues with the Ant integration within Eclipse is the fact that Ant, being an External Tool, does not receive the Project-specific Paths/Libraries. However, since most Java-relevant Ant tasks can take classpath and classpathref attributes, this is usually not an issue. In the case of the BEA-supplied wsdlc Ant task, it is apparent from the verbose/debug console output that wsdlc can see the jars in its classpathref, but it ignores those references when resolving class references and instead only uses the system classpath.
    <p>
    <i>I've only needed the weblogic.jar and xbean.jar, not all the ones you mentioned in an earlier thread of this post.</i><br>
    I have not tried to winnow down exactly which jars are required. I simply included all the jars that exist and were added to the system classpath by the setDomainEnv.bat file created by WebLogic 9.1.
    <p>
    <i>Afterwards, I create an Ant Builder to build the JWS Web Service EAR, as opposed to fiddlin' with Eclipse.</i><br>
    I too use Ant to build my deployable archives. Eclipse is simply my IDE of choice. I validated that all the issues I listed occurred when running Ant from the command line.
    <p>
    <i>If you are interested in how I do it, send me an e-mail (to [email protected]), and I'll send you a zip of one of these JWS projects. The build.xml script for the project, takes care of a lot of the "annoyances" you mentioned, one of which I think is not accurate. I have never had a situation where the wsdlc Ant task "overwrote" my XXXImpl.java file..</i><br>
    Since I'm doing a POC to determine how we want to proceed with developing Web Services and an SOA in general, I tried to perform the same tasks using Axis 2 1.0, the WebLogic 9.1 tools, and XFire 1.1. Overwriting the Impl class is a common failing in the tools which take a WSDL and create Java source files for all three frameworks.
    <p>
    Try my scenario. Add another operation to an existing WSDL, and run the wsdlc Ant Task. The old IMPL class will be over-written.
    <p>
    Because of this, I have a separate Impl class and I make sure that all its methods and annotations match the methods and annotations in the Skeleton Impl class created by wsdlc.
    <p>
    <i>Maybe that's because I use the <exec> Ant task with jar.exe (the xvf options) in my build.xml, to only get what I need out of the .jar/.zip the wsdlc generates. I'm typically only interest in the interface class that my XXXImpl.java file needs to implements, because I use XMLBeans for the input args (and return values) of my web service operations.</i><br>
    Perhaps. I am not using XMLBeans in any of the three frameworks because the resulting service seems to be lighter-weight in all three frameworks if XMLBeans is not used. I'm sure there will be scenarios where XMLBeans is preferred, but I have not encountered that case in this POC.
    <p>
    <i>Regards,
    Mike Wooten</i>
    Thanks for the follow-up.
    Mike McAngus

  • Meta migration ant task throw exception

    Hi,
    I am trying the migration from kodo 2 to 3.
    I successfully migrated the properties file using the integrated ant
    task; but run into some problem with the meta data migration (the *.jdo
    files). following is the ant task I am using:
    <target name="migrate-meta" depends="init, prepare-jdo-meta, compile" >
    <!-- define the kodo2migrator task; this can be done at the top
    of -->
    <!-- the build.xml file, so it will be available for all
    targets -->
    <taskdef name="kodo2migrator"
    classname="kodo.jdbc.ant.Kodo2MigratorTask">
    <classpath>
    <pathelement
    path="${java.class.path}:${project.classpath}:${project.build.jdometa.dtd}"/>
    </classpath>
    </taskdef>
    <!-- invoke migrator on all .jdo files below the src directory -->
    <kodo2migrator>
    <classpath>
    <pathelement
    path="${java.class.path}:${project.classpath}:${project.build.jdometa.dtd}"/>
    </classpath>
    <fileset dir="${project.kodo.src}">
    <include name="**/*.jdo" />
    </fileset>
    <config properties="${jdo.properties}" />
    </kodo2migrator>
    </target>
    the exception it is throwning is :
    [kodo2migrator] kodo.jdbc.migration.kodo2.util.FatalUserException: The
    specified driver class "null" is neither a java.sql.Driver nor a
    javax.sql.DataSource. Please specify a valid driver in the
    javax.jdo.option.ConnectionDriverName property.
    [kodo2migrator] at
    kodo.jdbc.migration.kodo2.schema.ConfigurationConnector.createConnectionFactory(ConfigurationConnector.java:108)
    [kodo2migrator] at
    kodo.jdbc.migration.kodo2.schema.ConfigurationConnector.<init>(ConfigurationConnector.java:65)
    [kodo2migrator] at
    kodo.jdbc.migration.kodo2.schema.ConfigurationConnector.<init>(ConfigurationConnector.java:57)
    [kodo2migrator] at
    kodo.jdbc.migration.kodo2.schema.ConfigurationConnector.<init>(ConfigurationConnector.java:37)
    [kodo2migrator] at
    kodo.jdbc.migration.kodo2.Kodo2Migrator.migrate(Kodo2Migrator.java:161)
    [kodo2migrator] at
    kodo.jdbc.migration.kodo2.Kodo2Migrator.run(Kodo2Migrator.java:1141)
    [kodo2migrator] at
    kodo.jdbc.ant.Kodo2MigratorTask.executeOn(Kodo2MigratorTask.java:53)
    [kodo2migrator] at
    com.solarmetric.ant.TaskBase.execute(TaskBase.java:105)
    [kodo2migrator] at
    org.apache.tools.ant.UnknownElement.execute(UnknownElement.java:193)
    [kodo2migrator] at org.apache.tools.ant.Task.perform(Task.java:341)
    [kodo2migrator] at
    org.apache.tools.ant.Target.execute(Target.java:309)
    [kodo2migrator] at
    org.apache.tools.ant.Target.performTasks(Target.java:336)
    [kodo2migrator] at
    org.apache.tools.ant.Project.executeTarget(Project.java:1339)
    [kodo2migrator] at
    org.apache.tools.ant.Project.executeTargets(Project.java:1255)
    [kodo2migrator] at org.apache.tools.ant.Main.runBuild(Main.java:609)
    [kodo2migrator] at org.apache.tools.ant.Main.start(Main.java:196)
    [kodo2migrator] at org.apache.tools.ant.Main.main(Main.java:235)
    BUILD FAILED
    file:/home/tyang/eclipse/workspace/UMA/build.xml:208:
    kodo.jdbc.migration.kodo2.util.FatalUserException: The specified driver
    class "null" is neither a java.sql.Driver nor a javax.sql.DataSource.
    Please specify a valid driver in the
    javax.jdo.option.ConnectionDriverName property.
    the properties file I am using is like this: (just a snipet)
    javax.jdo.PersistenceManagerFactoryClass:
    kodo.jdbc.runtime.JDBCPersistenceManagerFactory
    javax.jdo.option.ConnectionDriverName: org.postgresql.Driver
    javax.jdo.option.ConnectionURL: jdbc:postgresql://127.0.0.1/cwdevdb
    javax.jdo.option.ConnectionUserName: cwdev
    javax.jdo.option.ConnectionPassword:
    javax.jdo.option.DefaultFetchBatchSize: 10
    javax.jdo.option.DefaultFetchThreshold: 30
    javax.jdo.option.IgnoreCache: true
    javax.jdo.option.NontransactionalRead: true
    javax.jdo.option.NontransactionalWrite: false
    javax.jdo.option.Optimistic: true
    javax.jdo.option.RestoreValues: false
    javax.jdo.option.RetainValues: false
    kodo.ConnectionFactoryProperties: MaxActive=20, MaxWait=5000
    kodo.ConnectionRetainMode: persistence-manager
    kodo.DataCache: true(CacheSize=10000)
    kodo.LicenseKey: xxxx-xxxx-xxxx-xxxx-xxxx
    kodo.ManagedRuntime: TransactionManagerName=java:/TransactionManager
    kodo.PersistenceManagerImpl: CloseOnManagedCommit=true
    kodo.QueryCache: true
    kodo.RemoteCommitProvider: sjvm(Topic=topic/KodoCacheTopic)
    kodo.jdbc.DBDictionary: postgres(StoreCharsAsNumbers=false)
    kodo.jdbc.SequenceFactory: PrimaryKeyColumn=PKX,
    SequenceColumn=SEQUENCEX, TableName=JDO_SEQUENCEX
    To make sure this IS the one it is using, not only I echo out the
    "${jdo.properties}" value, but also I tried to comment out the
    licenseKey line, then it threw "license key invalid" exception. so I am
    sure this is the properties file I am using in that ant task.
    Also I tried using the command line on one of our classes, it does not
    run into this problem.
    Any clue what I am missing?
    Thanks a lot,
    Tao

    The 3.0.0 migrator task has a couple of bugs. These will be ironed out
    in 3.0.1, which is due for release any day now. But if you must work
    around the bugs immediately, you'll have to:
    1. Run the task using your old properties file. Actually this will be a
    requirement even in 3.0.1; that's why in the migration chapter of the
    docs we say to migrate your metadata before your properties. The
    migration tool needs to access 2.5 properties to map your classes properly.
    2. Add the the following property to your old properties file:
    kodo.LicenseKey: <your license key>
    3. Name the properties file "kodo.properties" and place it in one of the
    directories listed in the ant task's CLASSPATH. If that doesn't work,
    place it in a directory in your system CLASSPATH. The 3.0.0 task has
    some classpath problems, and also the <config> task element doesn't work.
    Or, you could just set your system CLASSPATH and run the kodo2migrator
    tool from the command line.
    I hope this helps. As I said, 3.0.1 resolves these ant problems, and
    will be released very shortly.

  • Autotype ant task and java source file having method which  returns hashmap

    Hi Friends,
    I am using autotype ant task to generate types.xml and supporting java classes.
    The task is defined as follows .
    <target name="std">
    <source2wsdd javaSource="HelloWorld.java"
    typesInfo="types.xml"
    ddFile="ddfiles/web-services.xml"
    serviceURI="/HelloWorldService"/>
    </target>
    In my java source i have method which is returning an HashMap. In this scenario I am getting error when i run the task. The error is as follows
    C:\test-ws\javaclass>ant auto
    Buildfile: build.xml
    auto:
    [autotype] Autotyping for javaTypes TestBean
    [autotype] weblogic.xml.schema.binding.BindingException: Invalid class received
    : interface java.util.Map loaded from file:/C:/bea/jdk142_05/jre/lib/rt.jar!/jav
    a/util/Map.class. All classes that will be serialized or deserialized must be n
    on-interface, non-abstract classes that provide a public default constructor
    [autotype] at weblogic.xml.schema.binding.internal.codegen.JavaInspector.en
    sureValidClass(JavaInspector.java:1050)
    [autotype] at weblogic.xml.schema.binding.internal.codegen.JavaInspector.fi
    llDescriptor(JavaInspector.java:174)
    [autotype] at weblogic.xml.schema.binding.internal.codegen.JavaInspector.ge
    tDescriptor(JavaInspector.java:139)
    [autotype] at weblogic.xml.schema.binding.internal.codegen.JavaInspector.cr
    eateBeanProperty(JavaInspector.java:927)
    [autotype] at weblogic.xml.schema.binding.internal.codegen.JavaInspector.cr
    eateBeanProperty(JavaInspector.java:905)
    [autotype] at weblogic.xml.schema.binding.internal.codegen.JavaInspector.ad
    dPropertiesToScalar(JavaInspector.java:834)
    [autotype] at weblogic.xml.schema.binding.internal.codegen.JavaInspector.fi
    llDescriptor(JavaInspector.java:209)
    [autotype] at weblogic.xml.schema.binding.internal.codegen.JavaInspector.ge
    tDescriptor(JavaInspector.java:139)
    [autotype] at weblogic.xml.schema.binding.internal.codegen.JavaInspector.cr
    eateDescriptorForClass(JavaInspector.java:106)
    [autotype] at weblogic.xml.schema.binding.internal.codegen.Compiler.compile
    (Compiler.java:106)
    [autotype] at weblogic.xml.schema.binding.internal.XSDTypeMappingBuilder.ma
    pClass(XSDTypeMappingBuilder.java:89)
    [autotype] at weblogic.xml.schema.binding.internal.XSDTypeMappingBuilder.ma
    pClass(XSDTypeMappingBuilder.java:102)
    [autotype] at weblogic.xml.schema.binding.internal.TypeMappingBuilderBase.a
    ddMapping(TypeMappingBuilderBase.java:180)
    [autotype] at weblogic.webservice.tools.build.internal.Java2SchemaImpl.doTy
    peMapping(Java2SchemaImpl.java:267)
    [autotype] at weblogic.webservice.tools.build.internal.Java2SchemaImpl.run(
    Java2SchemaImpl.java:167)
    [autotype] at weblogic.ant.taskdefs.webservices.javaschema.JavaSchema.doJav
    a2Schema(JavaSchema.java:302)
    [autotype] at weblogic.ant.taskdefs.webservices.javaschema.JavaSchema.execu
    te(JavaSchema.java:184)
    [autotype] at org.apache.tools.ant.Task.perform(Task.java:341)
    [autotype] at org.apache.tools.ant.Target.execute(Target.java:309)
    [autotype] at org.apache.tools.ant.Target.performTasks(Target.java:336)
    [autotype] at org.apache.tools.ant.Project.executeTarget(Project.java:1339)
    [autotype] at org.apache.tools.ant.Project.executeTargets(Project.java:1255
    [autotype] at org.apache.tools.ant.Main.runBuild(Main.java:609)
    [autotype] at org.apache.tools.ant.Main.start(Main.java:196)
    [autotype] at org.apache.tools.ant.Main.main(Main.java:235)
    BUILD FAILED
    file:C:/test-ws/javaclass/build.xml:62: weblogic.webservice.tools.build.WSBuildE
    xception: Failed to do type mapping - with nested exception:
    [weblogic.xml.schema.binding.BindingException: Invalid class received: interface
    java.util.Map loaded from file:/C:/bea/jdk142_05/jre/lib/rt.jar!/java/util/Map.
    class.  All classes that will be serialized or deserialized must be non-interfac
    e, non-abstract classes that provide a public default constructor]
    Can any one provide the solution for this
    Thanks
    Anantha

    Hi Friends,
    I am using autotype ant task to generate types.xml and supporting java classes.
    The task is defined as follows .
    <target name="std">
    <source2wsdd javaSource="HelloWorld.java"
    typesInfo="types.xml"
    ddFile="ddfiles/web-services.xml"
    serviceURI="/HelloWorldService"/>
    </target>
    In my java source i have method which is returning an HashMap. In this scenario I am getting error when i run the task. The error is as follows
    C:\test-ws\javaclass>ant auto
    Buildfile: build.xml
    auto:
    [autotype] Autotyping for javaTypes TestBean
    [autotype] weblogic.xml.schema.binding.BindingException: Invalid class received
    : interface java.util.Map loaded from file:/C:/bea/jdk142_05/jre/lib/rt.jar!/jav
    a/util/Map.class. All classes that will be serialized or deserialized must be n
    on-interface, non-abstract classes that provide a public default constructor
    [autotype] at weblogic.xml.schema.binding.internal.codegen.JavaInspector.en
    sureValidClass(JavaInspector.java:1050)
    [autotype] at weblogic.xml.schema.binding.internal.codegen.JavaInspector.fi
    llDescriptor(JavaInspector.java:174)
    [autotype] at weblogic.xml.schema.binding.internal.codegen.JavaInspector.ge
    tDescriptor(JavaInspector.java:139)
    [autotype] at weblogic.xml.schema.binding.internal.codegen.JavaInspector.cr
    eateBeanProperty(JavaInspector.java:927)
    [autotype] at weblogic.xml.schema.binding.internal.codegen.JavaInspector.cr
    eateBeanProperty(JavaInspector.java:905)
    [autotype] at weblogic.xml.schema.binding.internal.codegen.JavaInspector.ad
    dPropertiesToScalar(JavaInspector.java:834)
    [autotype] at weblogic.xml.schema.binding.internal.codegen.JavaInspector.fi
    llDescriptor(JavaInspector.java:209)
    [autotype] at weblogic.xml.schema.binding.internal.codegen.JavaInspector.ge
    tDescriptor(JavaInspector.java:139)
    [autotype] at weblogic.xml.schema.binding.internal.codegen.JavaInspector.cr
    eateDescriptorForClass(JavaInspector.java:106)
    [autotype] at weblogic.xml.schema.binding.internal.codegen.Compiler.compile
    (Compiler.java:106)
    [autotype] at weblogic.xml.schema.binding.internal.XSDTypeMappingBuilder.ma
    pClass(XSDTypeMappingBuilder.java:89)
    [autotype] at weblogic.xml.schema.binding.internal.XSDTypeMappingBuilder.ma
    pClass(XSDTypeMappingBuilder.java:102)
    [autotype] at weblogic.xml.schema.binding.internal.TypeMappingBuilderBase.a
    ddMapping(TypeMappingBuilderBase.java:180)
    [autotype] at weblogic.webservice.tools.build.internal.Java2SchemaImpl.doTy
    peMapping(Java2SchemaImpl.java:267)
    [autotype] at weblogic.webservice.tools.build.internal.Java2SchemaImpl.run(
    Java2SchemaImpl.java:167)
    [autotype] at weblogic.ant.taskdefs.webservices.javaschema.JavaSchema.doJav
    a2Schema(JavaSchema.java:302)
    [autotype] at weblogic.ant.taskdefs.webservices.javaschema.JavaSchema.execu
    te(JavaSchema.java:184)
    [autotype] at org.apache.tools.ant.Task.perform(Task.java:341)
    [autotype] at org.apache.tools.ant.Target.execute(Target.java:309)
    [autotype] at org.apache.tools.ant.Target.performTasks(Target.java:336)
    [autotype] at org.apache.tools.ant.Project.executeTarget(Project.java:1339)
    [autotype] at org.apache.tools.ant.Project.executeTargets(Project.java:1255
    [autotype] at org.apache.tools.ant.Main.runBuild(Main.java:609)
    [autotype] at org.apache.tools.ant.Main.start(Main.java:196)
    [autotype] at org.apache.tools.ant.Main.main(Main.java:235)
    BUILD FAILED
    file:C:/test-ws/javaclass/build.xml:62: weblogic.webservice.tools.build.WSBuildE
    xception: Failed to do type mapping - with nested exception:
    [weblogic.xml.schema.binding.BindingException: Invalid class received: interface
    java.util.Map loaded from file:/C:/bea/jdk142_05/jre/lib/rt.jar!/java/util/Map.
    class.  All classes that will be serialized or deserialized must be non-interfac
    e, non-abstract classes that provide a public default constructor]
    Can any one provide the solution for this
    Thanks
    Anantha

  • Servicegen ant task in weblogic 10.3

    Hi,
    Could you please let me know , the werbservice related ant tasks from weblogic 8.1 (say servicegen)
    are supported in weblogic 10.3 ?
    I am in a process of migrating application from 8.1 to 10.3. For building the application I am using 'ant'.
    Thanks,
    Sajan CR

    Apparently the ant tasks are no longer described on the oracle doc pages as they were on the bea pages.
    http://download.oracle.com/docs/cd/E12840_01/wls/docs103/programming/overview.html#using_ant
    "To view the documentation for a specific version of Ant, such as the version included with WebLogic Server, download the Ant zip file from http://archive.apache.org/dist/ant/binaries/ and extract the documentation."

  • How do I get Ant task deploy to fail on error within an ojdeploy-build ?

    I am calling ojdeploy on an xml file with several <deploy> tasks within the <ojdeploy-build> task.
    FYI this dramatically increases performance when doing several deployments.
    I want to find a way to have the script stop with an error as soon as one of the <deploy> tasks fails with an error (such as a compile error). It does not currently do this.
    Is there a way to get the script to stop as soon as a <deploy> task fails within the outer <ojdeploy-build> task?
    (eg. could I somehow check the return code for each deploy explicitly and do an exit if the deploy fails)
    My Ant book claims that Ant tasks normally fail on error, and when one task fails the Ant script stops at that point. Some Ant tasks (such as exec) have an explicit failonerror attribute which can change this behavior to ignore a non-zero return code from the task and continue executing the Ant script.
    It seems to me that the <ojdeploy-build> task has a serious bug where it (probably using java try-catch) ignores the error from <deploy> and keeps going to the next <deploy>, violating a basic design principle of a proper Ant task.
    Where can I find the java code for <ojdeploy-build> to confirm my suspicion and then report the bug officially?
    Meanwhile, I am very interested in finding some workaround for this bug that preserves having several <deploy> in one script. If I put just one <deploy> in each <ojdeploy-build>, the huge performance improvement is lost.

    I played with it some more and it seems that failonerror and resultproperty actually work in JDev 11.1.1.4.0 They are inherited from the [url http://ant.apache.org/manual/Tasks/exec.html]Ant Exec task and work, you just have to set failonerror="true", e.g.
    <ora:ojdeploy xmlns:ora="oraclelib:OJDeployAntTask"
                      executable="${oracle.jdeveloper.ojdeploy.executable}"
                      failonerror="true"
                      resultproperty="ojdeploy.exit.code"
                      ora:buildscript="${oracle.jdeveloper.deploy.dir}/ojdeploy-build.xml"
                      ora:statuslog="${oracle.jdeveloper.deploy.dir}/ojdeploy-statuslog.xml">
    ...Note that resultproperty is useful only if failonerror="false", use one or the other.

  • Building from flex builder vs ant task

    I have a flex application written using flex builder. When I
    build it and run it using flex builder, or create an air file from
    flex builder and run that, then my application works just fine.
    However, I would like people without copies of flexBuilder
    installed to be able to build my application, so I am using the
    flex ant task (flex-mxmlc) to build my application. As far as I can
    tell I have the same configuration, and the same libraries included
    in the ant task. However, when I run the air file generated by the
    ant task nothing happens. If you look in the task manager, you can
    see that the application is running, but the main window for the
    application never appears.
    I tried running the swf through a debug version of flash to
    get some log output, and I am getting a bunch of exceptions, the
    first of which is:
    VerifyError: Error #1014: Class flash.display::NativeWindow
    could not be found.
    at flash.display::MovieClip/nextFrame()
    at mx.managers::SystemManager/deferredNextFrame()
    at
    mx.managers::SystemManager/preloader_initProgressHandler()
    at flash.events::EventDispatcher/dispatchEventFunction()
    at flash.events::EventDispatcher/dispatchEvent()
    at mx.preloaders::Preloader/timerHandler()
    at flash.utils::Timer/_timerDispatch()
    at flash.utils::Timer/tick()
    It seems like it might not be finding the main flex library
    (flexlib.swc), is that where that class would be? In my ant task I
    have an include-libraries tag that points to that file.
    Anyone have any ideas?

    I experienced a similar problem (although the class that
    could not be found was different for me). Googling around I found
    someone who had a similar problem and claimed that using the
    flexlib.swc library was the culprit.
    The root of the problem is that the Flex SDK that comes
    bundled with the Flex Builder has libraries (under frameworks/libs)
    that are NOT included in plain free Flex SDK that you and I are
    presumably using on our build machines.
    When flexlib.swc is linked in, it causes certain classes to
    be required at runtime. Apparently when you compile these classes
    are linked in if available, but when they are not the compilation
    still succeeds. Only you get a VerifyError when you run the thing.
    What worked for me was to copy all the additional .swc files
    found in my Flex Builder SDK's frameworks/libs directory to the
    same directory on my build machine. Also you will need to copy the
    additional files under frameworks/locale/en_US.
    Rebuild and clear your browser's cache and it should then
    work.

Maybe you are looking for

  • How do I reset airport extreme A1408 to use on different network after buying new Extreme?

    I have just bought and set up new Airport ExtremeA1521 and want to take my old one and set up at son's.  It is A1408.  Will doing a reset do all I need to do?  And then I want to hook up an Express to it to extend his network. Thanks.

  • Best format for video, etc.

    I have downloaded videos from my camcorder and have them on the hard drive for editing. I want to make a DVD with them but I also want to have an electronic version of the movie as well to keep on my hard drive, but in a format that is 1) popular (no

  • Anyone know how to hook up two computers to High Speed DSL using one modem?

    any insight is appreciated

  • Question about analytic function

    I have a table (t1) that contains text (source_ip) and a corresponding number column (attack_count). I'm trying to group source_ip, sum attack_count per unique source ip, and then provide a percentage for unique source_ip attack count to the total su

  • Error in SLd Configuration

    hi , I am trying to add a new technical system ( Web As Abap) in my SLD.. My setting gives me the below error when i move to application server window ie when i click on the next button of the central servers screen... Error: java.lang.IllegalArgumen