Set database dictionary in Mappingtool Ant Task

Hi,
I'm sure I'm not the only person that uses the MappingTool Ant task to
create SQL DDL, so why isn't there a way to tell it to use the correct
database
dictionary? When I run the ant task, the SQL producted is incorrect for my
database type.
I've checked the MappingTookTask.java file and I can that
JDBCConfiguration has a setter method to set the dictionary, but I can't
see how I would add this as a parameter to my Ant Task.
I've added
kodo.jdbc.DBDictionary=postgres
to my kodo.properties file but this doesn't seem to be used by the ant
task.
So for the momement I'm falling back on a sed script to correct the SQL
(i.e. int8(8) to int8, etc), but this is hardly ideal.
Thanks,
Andy.

Abe White wrote:
Could it be that Kodo is in fact using the right dictionary, but is just
issuing bad SQL? What version of Kodo are you using? And what exactly
are the symptoms of the problem? The use of type names like int8(8)?
Is that generated for an existing database column, or a new one Kodo is
creating?Something strange is happening because my other Ant tasks, including a
mapping tool task that creates the database tables works fine.
Here is how I call the task that creates the schema file -
<pre>
<mappingToolTask action="refresh" sqlfile="${sql.schema.file}"
schemaaction="build">
<fileset dir="${project.src.dir}">
<include name="**/*.jdo" />
</fileset>
</mappingToolTask>
</pre>
Here is how I call the task that creates the database tables -
<pre>
<mappingToolTask action="${param.action}">
<fileset dir="${project.src.dir}">
<include name="**/*.jdo" />
</fileset>
</mappingToolTask>
</pre>
As you can see only only differnce between the two tasks is the sqlfile
and schemaaction properties - it is as if the code that writes the schema
file does use the same dictionary logic as when the database tables are
created.
Th error manifests itself as incorrect data types (for PostgreSQL). I get
int(8) instead of int8, etc. Currently I correct this as follows -
line = line.replaceAll("int8\\(8\\)","int8");
line = line.replaceAll("int4\\(4\\)","int4");
line = line.replaceAll("timestamp\\(8\\)","timestamp");
line = line.replaceAll("bigserial\\(8\\)","bigserial");
line = line.replaceAll("bool\\(1\\)","boolean");
line = line.replaceAll("text\\(-1\\)","text");
line = line.replaceAll("float8\\(8\\)","float8");
I'm using 3.3.4.
Andy.

Similar Messages

  • Mappingtool Ant task classpath errors

    Hello,
         I'm trying to use the mappingtool in my build file, but I'm getting a
    ClassNotFoundException:
    [mappingtool] java.lang.ClassNotFoundException:
    edu.uiuc.cs427.domain.BreakState
    [mappingtool] at java.net.URLClassLoader$1.run(URLClassLoader.java:199)
    [mappingtool] at java.security.AccessController.doPrivileged(Native
    Method)
    [mappingtool] at
    java.net.URLClassLoader.findClass(URLClassLoader.java:187)
    [mappingtool] at java.lang.ClassLoader.loadClass(ClassLoader.java:289)
    [mappingtool] at
    sun.misc.Launcher$AppClassLoader.loadClass(Launcher.java:274)
    [mappingtool] at java.lang.ClassLoader.loadClass(ClassLoader.java:235)
    [mappingtool] at
    org.apache.tools.ant.AntClassLoader.findBaseClass(AntClassLoader.java:1104)
    [mappingtool] at
    org.apache.tools.ant.AntClassLoader.loadClass(AntClassLoader.java:938)
    [mappingtool] at java.lang.ClassLoader.loadClass(ClassLoader.java:235)
    [mappingtool] at
    java.lang.ClassLoader.loadClassInternal(ClassLoader.java:302)
    [mappingtool] at java.lang.Class.forName0(Native Method)
    [mappingtool] at java.lang.Class.forName(Class.java:219)
    [mappingtool] at serp.util.Strings.toClass(Strings.java:149)
    [mappingtool] at
    com.solarmetric.meta.ClassArgParser.parseClasses(ClassArgParser.java:77)
    [mappingtool] at kodo.jdbc.meta.MappingTool.run(MappingTool.java:837)
    [mappingtool] at
    kodo.jdbc.ant.MappingToolTask.executeOn(MappingToolTask.java:169)
    [mappingtool] at com.solarmetric.ant.TaskBase.execute(TaskBase.java:105)
    [mappingtool] at
    org.apache.tools.ant.UnknownElement.execute(UnknownElement.java:193)
    When I set kodo.properties to db MappingFactory, I do not get this
    error. However, when I set kodo.properties to file MappingFactory, I get
    this error. Nothing else is different.
    I've checked several times to make sure the class path setting is correct:
    <!-- run mappingtool -->
    <mappingtool action="refresh">
         <classpath>
              <path refid="jdo.classpath"/>
              <pathelement location="${build.classes.dir}"/>
         </classpath>
         <fileset dir="${build.classes.dir}" includes="package.jdo"/>
         <config propertiesFile="${kodo.home}/kodo.properties"/>
    </mappingtool>
    and my file is in ${build.classes.dir}
    Also note that the jdoc task works fine with this same classpath, so
    this seems like an issue with mappingtool.
    See my other mappingtool post for similar errors, maybe related.

    Abe White wrote:
    Could it be that Kodo is in fact using the right dictionary, but is just
    issuing bad SQL? What version of Kodo are you using? And what exactly
    are the symptoms of the problem? The use of type names like int8(8)?
    Is that generated for an existing database column, or a new one Kodo is
    creating?Something strange is happening because my other Ant tasks, including a
    mapping tool task that creates the database tables works fine.
    Here is how I call the task that creates the schema file -
    <pre>
    <mappingToolTask action="refresh" sqlfile="${sql.schema.file}"
    schemaaction="build">
    <fileset dir="${project.src.dir}">
    <include name="**/*.jdo" />
    </fileset>
    </mappingToolTask>
    </pre>
    Here is how I call the task that creates the database tables -
    <pre>
    <mappingToolTask action="${param.action}">
    <fileset dir="${project.src.dir}">
    <include name="**/*.jdo" />
    </fileset>
    </mappingToolTask>
    </pre>
    As you can see only only differnce between the two tasks is the sqlfile
    and schemaaction properties - it is as if the code that writes the schema
    file does use the same dictionary logic as when the database tables are
    created.
    Th error manifests itself as incorrect data types (for PostgreSQL). I get
    int(8) instead of int8, etc. Currently I correct this as follows -
    line = line.replaceAll("int8\\(8\\)","int8");
    line = line.replaceAll("int4\\(4\\)","int4");
    line = line.replaceAll("timestamp\\(8\\)","timestamp");
    line = line.replaceAll("bigserial\\(8\\)","bigserial");
    line = line.replaceAll("bool\\(1\\)","boolean");
    line = line.replaceAll("text\\(-1\\)","text");
    line = line.replaceAll("float8\\(8\\)","float8");
    I'm using 3.3.4.
    Andy.

  • 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>

  • Class generated by genInterface ant task does not compile

    I am trying to build a web service from existing wsdl using genInterface and topDownAssemble ant tasks.
    The wsdl contains following type definition. Java class generated from this type (see below) does not compile. The problem is that there are two class members named
    'value'. Is this an issue with Web Services Assembly tool or there is some way to get
    around it?
    <s:simpleType name="quantityType">
    <s:restriction base="s:string">
    <s:enumeration value="summation"/>
    <s:enumeration value="demand"/>
    <s:enumeration value="value"/>
    <s:enumeration value="consumption"/>
    </s:restriction>
    </s:simpleType>
    // Version = Oracle WebServices (10.1.3.3.0, build 070610.1800.23513)
    public class QuantityType implements java.io.Serializable {
    private java.lang.String value;
    private static final String _summationString = "summation";
    private static final String _demandString = "demand";
    private static final String _valueString = "value";
    private static final String _consumptionString = "consumption";
    public static final java.lang.String summation = new java.lang.String(summationString);
    public static final java.lang.String demand = new java.lang.String(demandString);
    public static final java.lang.String value = new java.lang.String(valueString);
    public static final java.lang.String consumption = new java.lang.String(consumptionString);
    public static final QuantityType summation = new QuantityType(_summation);
    public static final QuantityType demand = new QuantityType(_demand);
    public static final QuantityType value = new QuantityType(_value);
    public static final QuantityType consumption = new QuantityType(_consumption);
    Andrei

    Pls set debug attribute of JWSC ant task to true or on, e.g.
    <jwsc srcdir="." destdir="${output.dir}" debug="on" keepGenerated="true">
              </jwsc>

  • Line numbers in JWS classfile generated by jwsc Ant task

    Does anyone know how to get the jswc ant task to add line number attributes to JWS class file that it generates. When I try to use Eclipse to set a breakpoint in the service code I get a pop up that states
    +"Unable to install breakpoint in.....due to missing line number attributes. Modify compiler option to generate line number attributes"+
    I looked at the documentation for jswc and I dont see any options that can be passed to the java compiler.
    Karl

    Pls set debug attribute of JWSC ant task to true or on, e.g.
    <jwsc srcdir="." destdir="${output.dir}" debug="on" keepGenerated="true">
              </jwsc>

  • Setting UseXADataSourceInterface to false using wlconfig ant task

    Is there any way, I can set the UseXADataSourceInterface property to false within the wlconfig ant task.? I am aware that this property can be set using the admin console. But I would like to set this in an ant task. Any pointers?
    Thanks in advance,
    Jacob

    According to document:
    Warning: In particular, the wlconfig Ant task uses the deprecated BEA
    proprietary API weblogic.management.MBeanHome to access WebLogic MBeans, the
    same as it did in Version 8.1 of WebLogic Server. The Ant task does not use
    the standard JMX interface (javax.management.MBeanServerConnection) to
    discover MBeans.
    Warning: This means that the only MBeans that you can access using wlconfig
    are those listed under the Deprecated MBeans category in the WebLogic Server
    MBean Reference.
    Since UseXADataSourceInterface is defined in JDBCDriverParamsBean which is
    introduced in WLS 9.0, so I feel this should be impossible.
    Maybe you can try WLST, which also can be used in Ant.
    <Jacob Marcus> wrote in message news:[email protected]..
    Is there any way, I can set the UseXADataSourceInterface property to false
    within the wlconfig ant task.? I am aware that this property can be set
    using the admin console. But I would like to set this in an >ant task. Any
    pointers?
    Thanks in advance,
    Jacob

  • Maven Ant Tasks

    I have a build file as shown below (AFTER THE ERROR).
    When I try to run it I get the following error:
    Buildfile: build.xml
    BUILD FAILED
    /Users/abder-rahmanali/Desktop/Hibernate/build.xml:13: The following error occurred while executing this line:
    jar:file:/System/Library/Java/Extensions/maven-ant-tasks-2.0.9.jar!/org/apache/maven/artifact/ant/antlib.xml:4: taskdef A class needed by class org.apache.maven.artifact.ant.DependenciesTask cannot be found: org/apache/tools/ant/Task
    <?xml version="1.0"?>
    <project name="Harnessing Hibernate 3 (Developer's Notebook Second Edition)"
    default="db" basedir="."
    xmlns:artifact="antlibrg.apache.maven.artifact.ant">
    <!-- Set up properties containing important project directories -->
    <property name="source.root" value="src"/>
    <property name="class.root" value="classes"/>
    <property name="data.dir" value="data"/>
    <artifact:dependencies pathId="dependency.classpath">
    <dependency groupId="hsqldb" artifactId="hsqldb" version="1.8.0.7"/>
    <dependency groupId="hibernate" artifactId="hibernate"
    version="3.2.6.ga">
    <exclusion groupId="javax.transaction" artifactId="jta"/>
    </dependency>
    <dependency groupId="org.hibernate" artifactId="hibernate-tools"
    version="3.2.3.ga"/>
    <dependency groupId="org.apache.geronimo.specs"
    artifactId="geronimo-jta_1.1_spec" version="1.1.1"/>
    <dependency groupId="log4j" artifactId="log4j" version="1.2.15"/>
    </artifact:dependencies>
    <!-- Set up the class path for compilation and execution -->
    <path id="project.class.path">
    <!-- Include our own classes, of course -->
    <pathelement location="${class.root}" />
    <!-- Add the dependencies classpath -->
    <path refid="dependency.classpath"/>
    </path>
    <target name="db" description="Runs HSQLDB database management UI
    against the database file--use when application is not running">
    <java classname="org.hsqldb.util.DatabaseManager"
    fork="yes">
    <classpath refid="project.class.path"/>
    <arg value="-driver"/>
    <arg value="org.hsqldb.jdbcDriver"/>
    <arg value="-url"/>
    <arg value="jdbc:hsqldb:${data.dir}/music"/>
    <arg value="-user"/>
    <arg value="sa"/>
    </java>
    </target>
    </project>
    How can I deal with this error?
    Thanks.

    Please don't post the same topic more than once. You already have a thread on this subject: [http://forums.sun.com/thread.jspa?threadID=5365961]

  • Ant tasks

    Hi all,
    I'm using 2.3.3 on linux and ant 1.5.1, against the latest MS Sql JDBC
    drivers.
    With ant target below, i get the following error:
    file:build.xml:285: javax.jdo.JDOFatalDataStoreException: An error occurred
    while connecting to the data store for user "xx" at URL
    "jdbc:microsoft:sqlserver://192.168.10.102;DatabaseName=TestObjects;SelectMe
    thod=cursor".
    NestedThrowables:
    java.sql.SQLException: No suitable driver
    the driver does exist in the given classpath (see the echo message). and
    i've tried putting the jdbc drivers in the taskdef, with no luck (but a
    ClassNotFoundException is thrown instead).
    as a side note, why does schema tool try to connect if i give it an
    "outputFile" value??
    <target name="kodo-schema">
    <property file="kodo/kodo.properties"/>
    <available property="driver.exists" classname="${jdbc.driverclass}"
    classpathref="classpath.msjdbc"/>
    <echo message="driver: ${jdbc.driverclass} exists: ${driver.exists}"/>
    <taskdef name="schematool"
    classname="com.solarmetric.modules.integration.ant.SchemaToolTask">
    <classpath>
    <path refid="classpath.kodo"/>
    <!-- <path refid="classpath.msjdbc"/>-->
    <!-- <path refid="classpath.runtime.server"/>-->
    </classpath>
    </taskdef>
    <schematool action="refresh" ignoreErrors="false"
    outputFile="kodo/kodo_test.ddl">
    <config connectionUsername="${jdbc.user}"
    connectionPassword="${jdbc.password}"
    licenseKey="${com.solarmetric.kodo.LicenseKey}"
    connectionUrl="${jdbc.url}"
    connectionDriverName="${jdbc.driverclass}" />
    <fileset dir="kodo/mapping">
    <include name="**/*.jdo"/>
    </fileset>
    <classpath>
    <path refid="classpath.msjdbc"/>
    <path refid="classpath.kodo"/>
    <path refid="classpath.runtime.server"/>
    </classpath>
    </schematool>
    </target>
    Stack trace:
    [schematool] NestedThrowables:
    [schematool] java.sql.SQLException: No suitable driver
    [schematool] at
    com.solarmetric.kodo.impl.jdbc.schema.SchemaTool.<init>(SchemaTool.java:78)
    [schematool] at
    com.solarmetric.kodo.impl.jdbc.schema.SchemaTool.main(SchemaTool.java:1234)
    [schematool] at
    com.solarmetric.modules.integration.ant.SchemaToolTask.executeOn(SchemaToolT
    ask.java:46)
    [schematool] at
    com.solarmetric.modules.integration.ant.TaskBase.execute(TaskBase.java:115)
    [schematool] at
    org.apache.tools.ant.UnknownElement.execute(UnknownElement.java:166)
    [schematool] at org.apache.tools.ant.Task.perform(Task.java:319)
    [schematool] at org.apache.tools.ant.Target.execute(Target.java:309)
    [schematool] at org.apache.tools.ant.Target.performTasks(Target.java:336)
    [schematool] at
    org.apache.tools.ant.Project.executeTarget(Project.java:1306)
    [schematool] at
    org.apache.tools.ant.Project.executeTargets(Project.java:1250)
    [schematool] at org.apache.tools.ant.Main.runBuild(Main.java:610)
    [schematool] at org.apache.tools.ant.Main.start(Main.java:196)
    [schematool] at org.apache.tools.ant.Main.main(Main.java:235)
    [schematool] NestedThrowablesStackTrace:
    [schematool] java.sql.SQLException: No suitable driver
    [schematool] at
    java.sql.DriverManager.getConnection(DriverManager.java:532)
    [schematool] at
    java.sql.DriverManager.getConnection(DriverManager.java:171)
    [schematool] at
    com.solarmetric.kodo.impl.jdbc.datasource.ConnectionImpl.connect(ConnectionI
    mpl.java:222)
    [schematool] at
    com.solarmetric.kodo.impl.jdbc.datasource.ConnectionImpl.<init>(ConnectionIm
    pl.java:56)
    [schematool] at
    com.solarmetric.kodo.impl.jdbc.datasource.ConnectionImpl.<init>(ConnectionIm
    pl.java:45)
    [schematool] at
    com.solarmetric.kodo.impl.jdbc.schema.SchemaTool.<init>(SchemaTool.java:68)
    [schematool] at
    com.solarmetric.kodo.impl.jdbc.schema.SchemaTool.main(SchemaTool.java:1234)
    [schematool] at
    com.solarmetric.modules.integration.ant.SchemaToolTask.executeOn(SchemaToolT
    ask.java:46)
    [schematool] at
    com.solarmetric.modules.integration.ant.TaskBase.execute(TaskBase.java:115)
    [schematool] at
    org.apache.tools.ant.UnknownElement.execute(UnknownElement.java:166)
    [schematool] at org.apache.tools.ant.Task.perform(Task.java:319)
    [schematool] at org.apache.tools.ant.Target.execute(Target.java:309)
    [schematool] at org.apache.tools.ant.Target.performTasks(Target.java:336)
    [schematool] at
    org.apache.tools.ant.Project.executeTarget(Project.java:1306)
    [schematool] at
    org.apache.tools.ant.Project.executeTargets(Project.java:1250)
    [schematool] at org.apache.tools.ant.Main.runBuild(Main.java:610)
    [schematool] at org.apache.tools.ant.Main.start(Main.java:196)
    [schematool] at org.apache.tools.ant.Main.main(Main.java:235)

    fyi, the ant target below connects fine.. (so it seems)
    <target name="kodo-schema2">
    <property file="kodo/kodo.properties"/>
    <java classname="com.solarmetric.kodo.impl.jdbc.schema.SchemaTool"
    fork="true">
    <classpath>
    <path refid="classpath.kodo"/>
    <path refid="classpath.msjdbc"/>
    <path refid="classpath.runtime.server"/>
    </classpath>
    <jvmarg
    value="-Dcom.solarmetric.kodo.LicenseKey=${com.solarmetric.kodo.LicenseKey}"
    />
    <jvmarg
    value="-Djavax.jdo.option.ConnectionDriverName=${jdbc.driverclass}"/>
    <jvmarg value="-Djavax.jdo.option.ConnectionURL=${jdbc.url}"/>
    <jvmarg value="-Djavax.jdo.option.ConnectionUserName=${jdbc.user}"/>
    <jvmarg
    value="-Djavax.jdo.option.ConnectionPassword=${jdbc.password}"/>
    <arg line="-ignoreErrors false -action refresh -outfile
    kodo/kodo_test.ddl kodo/mapping/test.jdo"/>
    </java>
    </target>
    "Chris K. Wensel" <[email protected]> wrote in message
    news:[email protected]...
    it includes all the jar files (*.jar). the exact same path definition is
    used for hibernate, toplink, and others. i'm simply adding kodo support to
    my framework that already supports those listed peristence tools.
    "Marc Prudhommeaux" <[email protected]> wrote in message
    news:[email protected]...
    Chris-
    What is the "classpath.msjdbc" path set to? Note that the MS JDBC driver
    (the last one I used, at least) required multiple jar files to function
    (the driver itself, and another one with a utility jar).
    as a side note, why does schema tool try to connect if i give it an
    "outputFile" value??The schematool still needs to analyze the database to determine the
    database's and JDBC driver's capabilities, as well as see which tables
    already exist (when refreshing the schema).
    In article <[email protected]>, Chris K. Wensel wrote:
    Hi all,
    I'm using 2.3.3 on linux and ant 1.5.1, against the latest MS Sql JDBC
    drivers.
    With ant target below, i get the following error:
    file:build.xml:285: javax.jdo.JDOFatalDataStoreException: An error
    occurred
    while connecting to the data store for user "xx" at URL
    "jdbc:microsoft:sqlserver://192.168.10.102;DatabaseName=TestObjects;SelectMe
    thod=cursor".
    NestedThrowables:
    java.sql.SQLException: No suitable driver
    the driver does exist in the given classpath (see the echo message).and
    i've tried putting the jdbc drivers in the taskdef, with no luck (buta
    ClassNotFoundException is thrown instead).
    as a side note, why does schema tool try to connect if i give it an
    "outputFile" value??
    <target name="kodo-schema">
    <property file="kodo/kodo.properties"/>
    <available property="driver.exists"classname="${jdbc.driverclass}"
    classpathref="classpath.msjdbc"/>
    <echo message="driver: ${jdbc.driverclass} exists:${driver.exists}"/>
    <taskdef name="schematool"
    classname="com.solarmetric.modules.integration.ant.SchemaToolTask">
    <classpath>
    <path refid="classpath.kodo"/>
    <!-- <path refid="classpath.msjdbc"/>-->
    <!-- <path refid="classpath.runtime.server"/>-->
    </classpath>
    </taskdef>
    <schematool action="refresh" ignoreErrors="false"
    outputFile="kodo/kodo_test.ddl">
    <config connectionUsername="${jdbc.user}"
    connectionPassword="${jdbc.password}"
    licenseKey="${com.solarmetric.kodo.LicenseKey}"
    connectionUrl="${jdbc.url}"
    connectionDriverName="${jdbc.driverclass}" />
    <fileset dir="kodo/mapping">
    <include name="**/*.jdo"/>
    </fileset>
    <classpath>
    <path refid="classpath.msjdbc"/>
    <path refid="classpath.kodo"/>
    <path refid="classpath.runtime.server"/>
    </classpath>
    </schematool>
    </target>
    Stack trace:
    [schematool] NestedThrowables:
    [schematool] java.sql.SQLException: No suitable driver
    [schematool] at
    com.solarmetric.kodo.impl.jdbc.schema.SchemaTool.<init>(SchemaTool.java:78)
    [schematool] at
    com.solarmetric.kodo.impl.jdbc.schema.SchemaTool.main(SchemaTool.java:1234)
    [schematool] at
    com.solarmetric.modules.integration.ant.SchemaToolTask.executeOn(SchemaToolT
    ask.java:46)
    [schematool] at
    com.solarmetric.modules.integration.ant.TaskBase.execute(TaskBase.java:115)
    [schematool] at
    org.apache.tools.ant.UnknownElement.execute(UnknownElement.java:166)
    [schematool] at org.apache.tools.ant.Task.perform(Task.java:319)
    [schematool] atorg.apache.tools.ant.Target.execute(Target.java:309)
    [schematool] atorg.apache.tools.ant.Target.performTasks(Target.java:336)
    [schematool] at
    org.apache.tools.ant.Project.executeTarget(Project.java:1306)
    [schematool] at
    org.apache.tools.ant.Project.executeTargets(Project.java:1250)
    [schematool] at org.apache.tools.ant.Main.runBuild(Main.java:610)
    [schematool] at org.apache.tools.ant.Main.start(Main.java:196)
    [schematool] at org.apache.tools.ant.Main.main(Main.java:235)
    [schematool] NestedThrowablesStackTrace:
    [schematool] java.sql.SQLException: No suitable driver
    [schematool] at
    java.sql.DriverManager.getConnection(DriverManager.java:532)
    [schematool] at
    java.sql.DriverManager.getConnection(DriverManager.java:171)
    [schematool] at
    com.solarmetric.kodo.impl.jdbc.datasource.ConnectionImpl.connect(ConnectionI
    mpl.java:222)
    [schematool] at
    com.solarmetric.kodo.impl.jdbc.datasource.ConnectionImpl.<init>(ConnectionIm
    pl.java:56)
    [schematool] at
    com.solarmetric.kodo.impl.jdbc.datasource.ConnectionImpl.<init>(ConnectionIm
    pl.java:45)
    [schematool] at
    com.solarmetric.kodo.impl.jdbc.schema.SchemaTool.<init>(SchemaTool.java:68)
    [schematool] at
    com.solarmetric.kodo.impl.jdbc.schema.SchemaTool.main(SchemaTool.java:1234)
    [schematool] at
    com.solarmetric.modules.integration.ant.SchemaToolTask.executeOn(SchemaToolT
    ask.java:46)
    [schematool] at
    com.solarmetric.modules.integration.ant.TaskBase.execute(TaskBase.java:115)
    [schematool] at
    org.apache.tools.ant.UnknownElement.execute(UnknownElement.java:166)
    [schematool] at org.apache.tools.ant.Task.perform(Task.java:319)
    [schematool] atorg.apache.tools.ant.Target.execute(Target.java:309)
    [schematool] atorg.apache.tools.ant.Target.performTasks(Target.java:336)
    [schematool] at
    org.apache.tools.ant.Project.executeTarget(Project.java:1306)
    [schematool] at
    org.apache.tools.ant.Project.executeTargets(Project.java:1250)
    [schematool] at org.apache.tools.ant.Main.runBuild(Main.java:610)
    [schematool] at org.apache.tools.ant.Main.start(Main.java:196)
    [schematool] at org.apache.tools.ant.Main.main(Main.java:235)
    Marc Prud'hommeaux [email protected]
    SolarMetric Inc. http://www.solarmetric.com
    Kodo Java Data Objects Full featured JDO: eliminate the SQL from yourcode

  • Built-in wlst ant task does not work in weblogic 10.3.1

    Hi,
    We have an installer script that deploys an ear file to a weblogic managed server. The script also invokes the build-tin wlst ant task to bounce the managed server. However, in version 10.3.1 the wlst task seems to be broken. I get this error:
    [echo] [wlst] sys-package-mgr: can't create package cache dir, '/u00/webadmin/product/10.3.1/WLS/wlserver_10.3/server/lib/weblogic.jar/./java
    tmp/wlstTemp/packages'
    [echo] [wlst] java.io.IOException: No such file or directory
    [echo] [wlst] at java.io.UnixFileSystem.createFileExclusively(Native Method)
    [echo] [wlst] at java.io.File.checkAndCreate(File.java:1704)
    [echo] [wlst] at java.io.File.createTempFile(File.java:1792)
    [echo] [wlst] at java.io.File.createTempFile(File.java:1828)
    [echo] [wlst] at com.bea.plateng.domain.script.jython.WLST_offline.getWLSTOfflineInitFilePath(WLST_offline.java:240)
    [echo] [wlst] at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
    [echo] [wlst] at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:39)
    [echo] [wlst] at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25)
    [echo] [wlst] at java.lang.reflect.Method.invoke(Method.java:597)
    [echo] [wlst] at weblogic.management.scripting.utils.WLSTUtil.getOfflineWLSTScriptPath(WLSTUtil.java:63)
    [echo] [wlst] at weblogic.management.scripting.utils.WLSTUtil.setupOffline(WLSTUtil.java:214)
    [echo] [wlst] at weblogic.management.scripting.utils.WLSTInterpreter.<init>(WLSTInterpreter.java:133)
    [echo] [wlst] at weblogic.management.scripting.utils.WLSTInterpreter.<init>(WLSTInterpreter.java:75)
    [echo] [wlst] at weblogic.ant.taskdefs.management.WLSTTask.execute(WLSTTask.java:103)
    [echo] [wlst] at org.apache.tools.ant.UnknownElement.execute(UnknownElement.java:288)
    Obviously that is not a valid directory...so I am wondering what it is trying to do, and why. The wlst task worked perfectly in 10.3.0. No changes were made when attempting to run the script against 10.3.0 and 10.3.1, which tells me that something is different with the 10.3.1 setup. Here is the ant code I am running:
    <target name="init-taskdefs">
    <taskdef resource="net/sf/antcontrib/antcontrib.properties">
    <classpath>
    <pathelement location="ant-ext/ant-contrib.jar" />
    </classpath>
    </taskdef>
    <taskdef name="wldeploy" classname="weblogic.ant.taskdefs.management.WLDeploy" />
    <taskdef name="wlst" classname="weblogic.ant.taskdefs.management.WLSTTask" />
    </target>
    <macrodef name="wlShutdownServer">
    <attribute name="adminUser" default="${deploy.admin.username}" />
    <attribute name="adminPassword" default="${deploy.admin.password}" />
    <attribute name="adminUrl" default="${deploy.admin.url}" />
    <attribute name="serverTarget" />
    <sequential>
    <trycatch property="server.error">
    <try>
    <wlst failonerror="true"
    arguments="@{adminUser} @{adminPassword} @{adminUrl} @{serverTarget}">
    <script>
    adminUser=sys.argv[0]
    adminPassword=sys.argv[1]
    adminUrl=sys.argv[2]
    serverTarget=sys.argv[3]
    connect(adminUser,adminPassword,adminUrl)
    target=getMBean("/Servers/"+serverTarget)
    if target == None:
    target=getMBean("/Clusters/"+serverTarget)
    type="Cluster"
    else:
    type="Server"
    print 'Shutting down '+serverTarget+'...'
    shutdown(serverTarget,type,'true',15,force='true')
    print serverTarget+' was shut down successfully.'
    </script>
    </wlst>
    <!-- setDomainEnv.sh must have been called to set DOMAIN_HOME. Remove all leftover .lok files to allow server
    to start back up again. -->
    <echo message="Deleting any lok files that have not been removed..." />
    <delete failonerror="false">
    <fileset dir="${env.DOMAIN_HOME}/servers/@{serverTarget}" includes="**/*.lok"/>
    </delete>
    </try>
    <catch>
    <fail message="@{serverTarget} shutdown failed. ${server.error}" />
    </catch>
    <finally/>
    </trycatch>
    </sequential>
    </macrodef>
    Any help would be appreciated. Thanks!

    Well, it looks like passing something like "-Djava.io.tmpdir=/var/tmp/javatmp/`date +%Y%m%d`" to ant did the trick. I had to make sure that directory existed first, otherwise it threw a java ioexception.
    I still don't understand what changes between 10.3.0 and 10.3.1 to necessitate this change.

  • Error in writing an Ant task for creating a new connection pool.

    I have written the following ant task to create a new connection pool in weblogic 10.3.
    <target name="pool.dev">
         <wlconfig url="http://localhost:7001/" username="weblogic" password="weblogic">
         <query domain="C:/weblogic/rtg-L0" name="myserver"/>
         <create type="JDBCConnectionPool" name="OneSourceConnectionPool">
         <set attribute="DriverName"
         value="oracle.jdbc.OracleDriver"/>
         <set attribute="InitialCapacity" value="1"/>
         <set attribute="MaxCapacity" value="5"/>
         <set attribute="Password" value="rating"/>
         <set attribute="Properties" value="user=rating"/>
         <set attribute="RefreshMinutes" value="0"/>
         <set attribute="ShrinkPeriodMinutes" value="15"/>
         <set attribute="ShrinkingEnabled" value="true"/>
         <set attribute="TestConnectionsOnRelease" value="true"/>
         <set attribute="TestConnectionsOnReserve" value="true"/>
         <set attribute="TestConnectionsOnCreate" value="true"/>
         <set attribute="TestTableName" value="SQL SELECT 1 FROM DUAL"/>
         <set attribute="URL"
         value="jdbc:oracle:thin:@xyz.com:1522:oradvl"/>
         <set attribute="Targets" value="myserver"/>
         </create>
         </wlconfig>
    </target>
    When I run it, I see the following error:
    BUILD FAILED
    C:\ganymede\eclipse\workspace1\RtgSvr\build.xml:286: Failed to connect to the server: javax.naming.CommunicationException [Root exception is java.rmi.ConnectIOException: error during JRMP connection establishment; nested exception is:
         java.io.EOFException]
    Can anybody please help me regarding this...
    Thank you,
    Sowmya

    Hi everybody,
    Thank you very much for your replies....actually I added weblogic.jar to the classpath of the target. So, now I dont see that error. But, I have another problem which is as follows:
    <target name="initJDBC">
    <wlconfig url="t3://${host}:${port}" username="${username}" password="${password}">
         <query domain="domain.name" type="Server" name="${target.server}" property="${target.server}"/>
         <create type="JDBCConnectionPool" name="TestConnectionPool">
         <set attribute="DriverName" value="oracle.jdbc.OracleDriver"/>
         <set attribute="Password" value="welcome"/>
         <set attribute="Properties" value="user=welcome"/>
         <set attribute="URL" value="jdbc:oracle:thin:@test.com:1522:oradvl"/>
              <set attribute="Targets" value=""/>
         <set attribute="TestTableName" value="SQL SELECT 1 FROM DUAL"/>
         <set attribute="TestConnectionsOnRelease" value="false"/>
         <set attribute="TestConnectionsOnReserve" value="true"/>
         </create>
         <create type="JDBCDataSource" name="TestDataSource">
              <set attribute="JNDIName" value="TestDataSource"/>
              <set attribute="PoolName" value="TestConnectionPool"/>
              <set attribute="Targets" value=""/>
              </create>
         </wlconfig>
         </target>
    I am not knowing what to give in the value field of <set attribute="Targets" value=""/>. The following is my build.properties file:
    target.server=myserver
    host=127.0.0.1
    port=7001
    username=weblogic
    password=weblogic
    domain.name=testDomain
    If I give <set attribute="Targets" value="${myserver}"/>, I get the following error:
    BUILD FAILED
    C:\ganymede\eclipse\workspace1\TestSvr\build.xml:290: Property not set: ${myserver}
    When I set myserver=myserver in build.properties, I get the following error:
    BUILD FAILED
    C:\ganymede\eclipse\workspace1\TestSvr\build.xml:290: Error invoking MBean command: java.lang.IllegalArgumentException: Property Name and value not valid for the MBean. Value myserver for parameter[Targets].java.lang.IllegalArgumentException: Unable to convert the argument valuemyserver to class javax.management.ObjectName.java.lang.reflect.InvocationTargetException
    Can someone plzz help me in this regard.
    Thank you,
    Sowmya

  • 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

  • Can i reference external flex-config in flexunit ant task?

    flexunit gurus,
    i'm trying to figure out how to best specify the compiler arguments for the flexunit ant task in flexunit 4.1 beta 1.  from the documentation i see this sample flexunit usage:
    <flexunit workingDir="${bin.loc}" toDir="${report.loc}"
    haltonfailure="false" verbose="true" localTrusted="true">
    <testSource dir="${main.src.loc}" />
    <testSource dir="${test.src.loc}">
    <include name="**/*Test.as" />
    </testSource>
    <library dir="${lib.loc}" />
    </flexunit>
    in this example, the source and library paths are explicitly listed.  in this simple example all the needed libraries reside within a single directory.
    when i build my application, i use a custom flex-config.xml file, as the following snippet shows:
            <mxmlc file="${application.file}" output="${swf.debug.file}" debug="true" headless-server="${headless.server}">
                <load-config filename="${flex.config.file}" />
            </mxmlc>
    in that custom flex-config.xml file i list all the build options (e.g. source dirs, library paths, theme, etc.) appropriate for building the application.  the libraries i reference are in a number of different directories (in general each 3rd party library is in a different directory).
    in the flexunit task, i could individually reference all the same libraries that are in the flex-config.xml, but that'd be a pain to keep them in sync.  i suppose i also could parse the flex-config.xml to extract the library information and use that to populate the library argument.  really what i want to say in the flexunit task is "build all source and tests as indicated in flex-config.xml, then run the tests", perhaps with a syntax like the following:
    <flexunit workingDir="${bin.loc}"  toDir="${report.loc}"
    haltonfailure="false" verbose="true" localTrusted="true">
                <load-config filename="${flex.config.file}" />
    <testSource dir="${test.src.loc}">
    <include name="**/*Test.as" />
    </testSource>
    <library dir="${flexunit.lib}" />
    </flexunit>
    i'd rather keep the flex-config.xml file free of any test specific information, so ideally i'd specify the path to the flexunit swc's and the test path in the flexunit task (as in the above example).
    is there support for such usage currently or planned for in the future?  recommendations on how best to accomplish my goal of not duplicating library information already present in a custom flex-config.xml?
    thanks.
    -mike

    hi brian,
    thanks for your response.
    i understand the desire to avoid re-implementing the flex sdk ant tasks.  i'm not sure that can reasonably be accomplished wihen the TestRunner is dynamically generated from within the flexunit task.  in addition to the source path and library path, the theme setting and namespaces settings can affect successful compilation, and the runtime-shared-library-path setting can affect whether the produced swf runs correctly.
    perhaps there's an alternative.  what if we separate the creation of the TestRunner.mxml from the compilation and the execution of the tests.  if flexunit offers an ant task that can produce (but not run) a TestRunner.mxml, i can write the mxmlc task that compiles it properly, and then i can invoke the old style flexunit specifying the swf argument.  this would still accomplish my primary goal of not needing to manually enumerate every test file in a TestRunner.mxml that i have to maintain (and which neither Flash Builder nor maven builds require).  to compile the TestRunner.mxml, i'd load in my custom flex-config.xml, then append to the source path and library path to include my test directory and flexunit libraries.
    maybe something like the following to create the TestRunner:
    <generatetestrunner output="${bin.loc}/TestRunner.mxml">
              <testSource dir="${test.dir}">
                 <include name="**/*Test.as" />
              </testSource>
    </generatetestrunner>
    thoughts?
    one other thing i noticed about the current library argument to flexunit is that it assumes a directory even if you provide an explicit path to an swc (i tried switching <library dir...> to <library file...> but that didn't seem to make a difference).  in my case, there are specific swc's i need in the library path, and the task assuming i mean a directory when i specify an explicit swc is problematic.  the directory my swc libraries are contained in sometimes contain multiple and conflicting versions of a library (each library directory contains various snapshot builds of the library).  i need a way to explicitly indicate which library to use.
    finally, could you point me to the java source for the flexunit ant tasks?  i've found the flexunit action script source ok but haven't found where the java ant task is defined.
    thanks.
    -mike

  • FU Ant task failure: java.util.concurrent.ExecutionException: could not close client/server socket

    We sometimes see this failure intermitently when using the FlexUnit Ant task to run tests in a CI environment. The Ant task throws this exception:
    java.util.concurrent.ExecutionException: could not close client/server socket
    I have seen this for a while now, and still see it with the latest 4.1 RC versions.
    Here is the console output seen along with the above exception:
    FlexUnit player target: flash
    Validating task attributes ...
    Generating default values ...
    Using default working dir [C:\DJTE\commons.formatter_swc\d3flxcmn32\extracted\Source\Flex]
    Using the following settings for the test run:
    FLEX_HOME: [C:\dev\vert-d3flxcmn32\302100.41.0.20110323122739_d3flxcmn32]
    haltonfailure: [false]
    headless: [false]
    display: [99]
    localTrusted: [true]
    player: [flash]
    port: [1024]
    swf: [C:\DJTE\commons.formatter_swc\d3flxcmn32\extracted\build\commons.formatter.tests.unit.sw f]
    timeout: [1800000ms]
    toDir: [C:\DJTE\commons.formatter_swc\d3flxcmn32\reports\xml]
    Setting up server process ...
    Entry  [C:\DJTE\commons.formatter_swc\d3flxcmn32\extracted\build] already  available in local trust file at  [C:\Users\user\AppData\Roaming\Macromedia\Flash  Player\#Security\FlashPlayerTrust\flexUnit.cfg].
    Executing 'rundll32' with arguments:
    'url.dll,FileProtocolHandler'
    'C:\DJTE\commons.formatter_swc\d3flxcmn32\extracted\build\commons.formatter.tests.unit.swf '
    The ' characters around the executable and arguments are
    not part of the command.
    Starting server ...
    Opening server socket on port [1024].
    Waiting for client connection ...
    Client connected.
    Setting inbound buffer size to [262144] bytes.
    Receiving data ...
    Sending acknowledgement to player to start sending test data ...
    Stopping server ...
    End of test data reached, sending acknowledgement to player ...
    When the problem occurs, it is not always during the running of any particular test (that I am aware of). Recent runs where this failure was seen had the following number of tests executed (note: the total number that should be run is 45677): 18021, 18, 229.
    Here is a "good" run when the problem does not occur:
    Setting inbound buffer size to [262144] bytes.
    Receiving data ...
    Sending acknowledgement to player to start sending test data ...
    Stopping server ...
    End of test data reached, sending acknowledgement to player ...
    Closing client connection ...
    Closing server on port [1024] ...
    Analyzing reports ...
    Suite: com.formatters.help.TestGeographicSiteUrls
    Tests run: 5, Failures: 0, Errors: 0, Skipped: 0, Time elapsed: 0.008 sec
    Suite: com.formatters.functionalUnitTest.testCases.TestNumericUDF
    Tests run: 13, Failures: 0, Errors: 0, Skipped: 0, Time elapsed: 0.071 sec
    Results :
    Tests run: 45,677, Failures: 0, Errors: 0, Skipped: 0, Time elapsed: 201.186 sec
    Has anyone else ran across this problem?
    Thanks,
    Trevor

    I am not sure if this information will help everyone, but here goes...
    For us, these problems with FlexUnit tests crashing the Flash Player appear to be related to couple of factors. Recently, we moved up from Flex 3.2 to Flex 4.1 as our development baseline.  Many people complained that their development environment (Flash Builder, etc.) was much more unstable.  Apparently, 4.1 produces SWFs that require more memory to run than 3.2 does?  Anyway, we still had Flash Player 10.1 as our runtime baseline.  Apparently, that version of the player was not as capable of running larger FlexUnit test SWFs, and would crash (as I posted months earlier).  I upgraded to the latest 10.3 standalone player versions, and the crashes have now ceased.  It would be nice to know exactly what was causing the crashes, but memory management (or lack of) is my best guess.
    So, if you are seeing these issues, try upgrading to the latest Flash Player version.
    Regards,
    Trevor

  • Deploying bpm 11g project sar file using ant task

    I am trying to deploy the bpm project using ant task file. The status I get is [deployComposite] ---->Deploying composite success. However when I check the deployments, they are not there. If I try to deploy this using Jdeveloper it works correctly. I need to get this to work for production deployments. Any suggestions?
    C:\Oracle\Middleware\Oracle_SOA1\bin>ant -f ant-sca-deploy.xml -DserverURL=http:
    //10.140.183.71:7001 -DsarLocation=N:\RuleBasedProjectInitiate\deploy\RequestPro
    ject.ear -Doverwrite=true -Duser=weblogic
    Buildfile: C:\Oracle\Middleware\Oracle_SOA1\bin\ant-sca-deploy.xml
    [echo] oracle.home = C:\Oracle\Middleware\Oracle_SOA1\bin/..
    deploy:
    [input] skipping input as property serverURL has already been set.
    [input] skipping input as property sarLocation has already been set.
    [deployComposite] created temp dir =C:\DOCUME~1\azeltov\LOCALS~1\Temp\deploy_cli
    ent_1279894885343
    [deployComposite] Creating HTTP connection to host:10.140.183.71, port:7001
    [deployComposite] Enter username and password for realm 'default' on host 10.140
    .183.71:7001
    [deployComposite] Authentication Scheme: Basic
    [deployComposite] Username:
    weblogic
    [deployComposite] Password:
    [deployComposite] Received HTTP response from the server, response code=200
    [deployComposite] clean up temp dir: C:\DOCUME~1\azeltov\LOCALS~1\Temp\deploy_cl
    ient_1279894885343
    [deployComposite] ---->Deploying composite success.
    BUILD SUCCESSFUL
    Total time: 4 seconds
    C:\Oracle\Middleware\Oracle_SOA1\bin>

    You can always deploy the ADF web apps from the Application (top menu) deploy option. Just make sure you're deploying the EAR profile for the project. Deploying the web projects from the composite deployment wizard can be convenient. But I think it's often the case that you deploy them (the composite and forms) separately (e.g. you make a series of changes to the composite without needed to redeploy the UI projects).
    Bottom line is you don't have to delete the projects to be able to modify/deploy them.

  • Compc ant task and external framework

    I'm writing an ant task to compile a couple of libraries into
    SWCs and then a shell app (that uses the libraries) into a SWF for
    deployment. If I compile the libraries by hand then run just the
    'mxmlc' part of my ant script it compiles fine. However when I try
    and first compile a library into a SWC with 'compc' it compiles but
    then the shell app complains that the classes from the library are
    missing. One thing that may be causing the problem is my library
    path (through flex builder) has it's framework.swc set to 'Link
    Type: External' and I'm not sure how to define that with 'compc'.
    The weird thing is the flex builder compiled and 'compc' compiled
    SWCs are the same size. Here's my target for 'compc':

        <mxmlc
             file="${project.name}/src/Test.mxml"
             output="${build.mxmlc.dir}/Test.swf"
             static-link-runtime-shared-libraries="true"
        >
              <load-config filename="${air.config}"/>
              <source-path path-element="${project.name}/src" />
             <runtime-shared-library-path path-element="${flex.frameworks.dir}/libs/framework.swc">
                    <url rsl-url="${rsl.dir}/framework_3.2.0.3958.swz"/>
                    <url rsl-url="${rsl.dir}/framework_3.2.0.3958.swf"/>
             </runtime-shared-library-path>
             <runtime-shared-library-path path-element="${flex.frameworks.dir}/libs/datavisualization.swc">
                    <url rsl-url="${rsl.dir}/datavisualization_3.2.0.3958.swf"/>
             </runtime-shared-library-path>
        </mxmlc>
    This also seems to work. AIR libraries are included in my output SWF. It all happens right when I have static-link-runtime-shared-libraries="true" . Why? Why does that not work when i have static-link-runtime-shared-libraries="false"  ??

Maybe you are looking for