Context-root="" in ant script still reports missing in mxmlc

Hi, I keep getting an error for this:
<mxmlc
file="${project.src}/main.mxml"
output="${build.debug}/main.swf"
locale="${LOCALE}"
static-rsls="false"
accessible="false"
use-network="false"
services="${flexRemotingServices}"
incremental="true"
context-root=""
>
[mxmlc] Error: The services configuration includes a channel-definition 'java-polling-amf' that has an endpoint with a context.root token but a context root has not been defined. Please specify a context-root compiler argument.

the solution is to use a space ie
context-root=" "

Similar Messages

Mail still reporting missing plugins.

After trying all the suggestions in this community and macworlds mac hints forum, I am still getting the "missing plug in" on eforwarding emails that have embedded jpeg images. The only way i have found around it is to select and copy each image, then paste into a new email. However, this approach
removes all colr from the copied image and turns it into a grey scale image. Attempting to paste into a draft forward email does not work, even if I highlight
and delete the original messages' "missing plug-in" block. I don't know if mail uses the same plug-ins as Safari, but, I did notice that there is no plug-in
listed in the Safari set for handling jpeg or jpg files. Could that be the problem? If so , where can I get such a plug-in? I am running on a Macbook Pro, with OS 10.6.8, Safari 5.0.5, Mail 4.5 (1084), and have Java JE6 installed.
Thanks for any help!

I have to admit this is an annoyance of mine too. I have plugins that no one else has where I work. If some one else has to open my files or package them for some reason they also have to do the interchange route, which is a total waste of time (and not very convenient)--especially for files that didn't even use the plugin, just were edited on a machine that had the plugin. ID definitely needs to honor the "ignore" the plugins when the user wants them ignored without having to "clean" the document through interchange. Older versions used to ask you if you wanted to open the files without the plugins, and you could purge the documents that way. Why can't it now? Seems like a pretty straightforward thing to me.

ManagedAvailability still reporting uninstalled server as missing

Hi,
during a migration I temporariliy had two Exchange 2013 CU2 servers installed. After the migration was complete, I uninstalled one Exchange 2013 CU2 using the proper procedures. Two days after the uninstall, the monitoring agent of the ManagedAvailability
is still reporting the old server as missing with the following error in the eventlog:
Machine '<old server>' has failed to heartbeat since '11-9-2013 22:30:30', as observed by machine '<new server>'. Restarting the Exchange Health Manager service did not fix the problem.
How can I correct this error?
Frank.

I have the same problem (2013 CU3), but removing all my HealthMailboxes and rebooting the system did not resolve the issue.
Can anyone think of any more tips?
Here is one that has worked for me:
Go to: HKLM\Software\Microsoft\ExchangeServer\v15\ActiveMonitoring\Subjects
and delete any old server entry if you see one and restart MSExchangeHM.
Martina Miskovic
Perfect!
I also found the old server at:
HKLM\Cluster\ExchangeActiveManager\NoteState\
HKLM\Cluster\ExchangeActiveManager\SystemState\
HKLM\Software\Microsoft\ExchangeServer\v15\WorkerTaskFramework\IdStore\MonitorDefinition\
HKLM\Software\Microsoft\ExchangeServer\v15\WorkerTaskFramework\IdStore\ProbeDefinition\
HKLM\Software\Microsoft\ExchangeServer\v15\WorkerTaskFramework\IdStore\ResponderDefinition\
I have a good feeling about this!

So what's the deal with missing context-root element in domain.xml?

I see that this issue has come up in the past:
If one hand modifies an application's web.xml file and tries to deploy using JSC, the application's corresponding web-module element's context-root gets nuked in the app server's domain.xml file. The only way I can get the server AND app to successfully run is to manually add context-root back in and manually restart the server (whether from JSC Deployment Server tree node or from the Start Menu (I'm running on XP Pro.) Trying to start either/both from the Run Project button on JSC recreates the problem. Is this a bug? Am I doing something wrong? If bug, will this be addressed soon?

Here's what I did:
1. I created a simple HelloWorld JSF project & tested that it compiled, deployed & ran fine using built-in AppServer.
2. Switched Project View to FileSystem view & opened src/web/WEB-INF/web.xml for editing
3. Inserted security-constraint
    
    <security-constraint>
          <display-name>SecurityConstraint</display-name>
          <web-resource-collection>
             <web-resource-name>WRCollection</web-resource-name>
             <url-pattern>/*</url-pattern>
          </web-resource-collection>
          <auth-constraint>
             <role-name>admin</role-name>
          </auth-constraint>
          <user-data-constraint>
             <transport-guarantee>NONE</transport-guarantee>
          </user-data-constraint>
    </security-constraint> 4. Tried to deploy & get deplyment failure messages.
5. Looking in to the %APPSERVERROOT%/domains/creator/config/domain.xml file shows that the HelloWorld webmodule line looks as follows:
<web-module enabled="true" location="c:/Documents and Settings/Jake Ochs/My Documents/Creator/Projects/HelloWorld/build" name="_helloworld" object-type="user"/>(notice how "context-root" is missing & now needs to be added manually to getthe app to run again.

How to map a url that does not match with the context root ?

does weblogic support url that does not match the context root ?
ex. the context root is AAA. the welcome page can be
retrieved using http://localhost:7001/AAA
Can it be configured to use http://localhost:7001/BBB to bring up the index.html in context root AAA ? if so, how ?

I agree with Imp68.
It still amazes me that in 2014 so many web sites are still not standards-compliant and instead insist on sniffing for the user-agent. And, in the majority of cases, I've found that the websites work fine with any modern browser.
phardell,
To be clear, Safari is not the problem, the website is! The developer of this website is still living in the 1990s and needs to move forward with the times. Imp68's suggestion will cause Safari to "pretend" to be whatever browser you wish. Try choosing "Safari 7" if that worked for you in the past and the website will likely go back to working. If that does not work then try choosing "Internet Explorer 10" from the menu and see if that works.
No matter what the result, you should look at the bottom of the page for a link to report problems with the website. Submit a comment that tells them that they need to "modernize your website to support all modern web browsers".
Good luck.

10g BPEL process upgrade to 11g hangs in Jdeveloper and Ant script

I have successfully upgraded several 10g (10.1.3.4) BPEL processes and ESB services using Jdeveloper 11g (11.1.1.6.0) migration wizard and deployed them to an 11g environment. Both 10g and 11g environments are up and running.
However, my 11g jdeveloper hangs when migrating the next BPEL process. It hangs at the message box with the title: "Migration Status". I tried the Ant script and it hangs too. It hangs after printing out:
"CompositeRefs
[upgrade] WARNING: UPGBPEL-02009: No Binding setup for : "soapCheckPrivileges"
. This will cause compilation of the upgraded project to fail. Check SOA Upgrade
documentation on manual steps necessary to bind this composite reference. If ne
cessary, upgrade and deploy any dependencies. If planning to retain 1013x nodes
in this projects dependency tree, check earlier part of this log for 1013x WSDL
URLs that can be used."
I guess it makes sense since Jdeveloper and Ant script use the same code base for migration.
One other observation is that if I kill the hanging jdeveloper process and reopen it and go through the migration wizard again, it will be successful without hanging. However, when I fix all the wsdl reference and do a build and deploy to sar. The resulting sar is defective and cannot be deployed to Weblogic even if both build and deploy to sar report success. The defective sar contains only scac.log and scac-log.xml, not even composite.xml.
One difference between this BPEL process and others I have successfully upgraded is that it depends on an ESB service (this esb service has been upgraded and deployed to 11g).
Any ideas?
Thanks,

I will answer my question. I killed the migrating Java process and the migrating wizard will report failure of migrating the .jpr file. Actually, the only thing missing in the migrated .jpr file is deployment profile which I can generate from deployment menu. And I can deploy the migrated process. This works as a workaround.

Exported ant script -- NoClassDefFound?

I've exported ant script from workshop (wls9.2 eclipse) and I was able to build the app.war (web services) ok.
However I saw message like this:
"assembly: Imput fileset contained no files, nothing to do."
And when I deployed the war to server and tried to access the webservices, it gave me NoClassDefFound error.
Also I noticed that the ".staging" directory has empty "lib" dir under it.
Does anyone know how to fix it?
Here is the generated build.xml and workspace.xml.
========================= workspace.xml==============
<?xml version="1.0" encoding="UTF-8"?>
<node name="metadata">
<node name="projects">
<node name="billingservice">
<attribute name="location" value="C:/home/rlee/projects/telepacific/billingservice"/>
</node>
</node>
<node name="library-modules">
<node name="library-module">
<attribute name="location" value="%wl.home%/common/deployable-libraries/wls-commonslogging-bridge.war"/>
</node>
<node name="library-module">
<attribute name="location" value="%wl.home%/common/deployable-libraries/weblogic-controls-1.0.war"/>
</node>
<node name="library-module">
<attribute name="location" value="%wl.home%/common/deployable-libraries/beehive-controls-1.0.war"/>
</node>
</node>
<node name="server-runtimes">
<node name="BEA WebLogic v9.2">
<attribute name="location" value="%wl.home%"/>
</node>
</node>
<node name="vm-locations">
<attribute name="defaultVM" value="C:/bea/wls922/jdk150_10"/>
<node name="org.eclipse.jdt.internal.debug.ui.launcher.StandardVMType/BEA WebLogic v9.2 JRE">
<attribute name="location" value="c:/bea/wls922/jrockit90_150_10"/>
</node>
</node>
<node name="classpath-vars">
<node name="SDKS_HOME">
<attribute name="value" value="c:/home/rlee/projects/mpower/sdks"/>
</node>
<node name="WEBLOGIC_HOME">
<attribute name="value" value="%wl.home%"/>
</node>
</node>
</node>
======================= end of workspace.xml==============
==================== exported build.xml ====================
<project default="build">
<description>
Project build script. All public targets require the "workspace" property to be
set at invocation. It can either point at the Eclipse workspace directory that
this project belongs to or an exported workspace.xml file. The wl.home property
may also need to be specified unless WL_HOME environment variable is defined.
</description>
<target name="init.env" unless="init.env.executed">
<property name="init.env.executed" value="true"/>
<property environment="env"/>
<condition property="wl.home" value="${env.WL_HOME}">
<isset property="env.WL_HOME"/>
</condition>
<fail unless="wl.home" message="The wl.home property needs to be set!"/>
</target>
<target name="init.typedefs" depends="init.env" unless="init.typedefs.executed">
<property name="init.typedefs.executed" value="true"/>
<typedef resource="com/bea/wlw/antlib/antlib.xml">
<classpath>
<fileset dir="${wl.home}">
<include name="workshop/lib/wlw-antlib.jar"/>
<include name="workshop/lib/wlw-util.jar"/>
<include name="workshop/lib/wlw-libmodules.jar"/>
<include name="workshop/lib/wlw-splitsrc.jar"/>
<include name="server/lib/ant/ant-contrib-1.0b1.jar"/>
</fileset>
</classpath>
</typedef>
</target>
<target name="init" depends="init.env,init.typedefs" unless="init.executed">
<property name="init.executed" value="true"/>
<fail unless="workspace" message="The workspace property needs to be set!"/>
<dirname property="project.dir" file="${ant.file}"/>
<property name="echo.metadata" value="false"/>
<mdimport workspace="${workspace}" pjdir="${project.dir}" echo="${echo.metadata}">
<option name="skipAnnotationProcessors" value="com.bea.wlw.webservices.core"/>
</mdimport>
<property name="archive.name" value="${project.name}.war"/>
<property name="uri" value="${archive.name}"/>
<taskdef name="xmlbean"
classname="org.apache.xmlbeans.impl.tool.XMLBean">
<classpath>
<pathelement path="${wl.home}/common/lib/apache_xbean.jar"/>
<pathelement path="${wl.home}/common/eclipse/plugins/com.bea.eclipse.common.lib.apache_xbean2/jsr173_api.jar"/>
</classpath>
</taskdef>
<property name="generated.module.root" value="${project.dir}/build/weboutput"/>
<property name="assembly.src" value="${project.dir}/build/assembly/.src"/>
</target>
<target name="build" depends="init" description=" compiles the source files; does not package the results">
<for list="0,1,2,3,4,5,6,7,8,9" param="i">
<sequential>
<if>
<and>
<isset property="xbean.src.@{i}.dir"/>
<available file="${xbean.src.@{i}.dir}"/>
</and>
<then>
<fileset id="xbean.src.paths.@{i}"
dir="${xbean.src.@{i}.dir}"
includes="${xbean.src.@{i}.include}"
excludes="${xbean.src.@{i}.exclude}"/>
</then>
<else>
<fileset id="xbean.src.paths.@{i}"
file="null_file_set"/>
</else>
</if>
</sequential>
</for>
<if>
<isset property="xbean.include-classpath-contributions"/>
<then>
<path id="xbean.classpath">
<path refid="java.classpath"/>
</path>
</then>
<else>
<path id="xbean.classpath">
<pathelement location="${wl.home}/common/lib/apache_xbean.jar"/>
</path>
</else>
</if>
<mkdir dir="${xbean.src.output.dir}"/>
<mkdir dir="${xbean.bin.output.dir}"/>
<xmlbean
javasource="${xbean.java-version}"
download="${xbean.download-network-urls}"
typesystemname="${xbean.schema-type-name}"
noupa="${xbean.unique-particle-attribution}"
nopvr="${xbean.particle-valid-restriction}"
noannotations="${xbean.skip-annotations}"
ignoreDuplicatesInNamespaces="${xbean.namespaces-to-ignore-dups}"
srcgendir="${xbean.src.output.dir}"
classgendir="${xbean.bin.output.dir}"
classpathref="xbean.classpath"
srconly="true">
<fileset refid="xbean.src.paths.0"/>
<fileset refid="xbean.src.paths.1"/>
<fileset refid="xbean.src.paths.2"/>
<fileset refid="xbean.src.paths.3"/>
<fileset refid="xbean.src.paths.4"/>
<fileset refid="xbean.src.paths.5"/>
<fileset refid="xbean.src.paths.6"/>
<fileset refid="xbean.src.paths.7"/>
<fileset refid="xbean.src.paths.8"/>
<fileset refid="xbean.src.paths.9"/>
</xmlbean>
<if>
<isreference refid="apt.factory.path"/>
<then>
<mkdir dir="${apt.src.output.dir}"/>
<for-each-java-src-path>
<if>
<available file="${.java.src.dir}"/>
<then>
<mkdir dir="${.java.src.output}"/>
<apt
sourcepath="${java.sourcepath}"
srcdir="${.java.src.dir}"
includes="${.java.src.include}"
excludes="${.java.src.exclude}"
destdir="${.java.src.output}"
preprocessdir="${apt.src.output.dir}"
classpathref="java.classpath"
factorypathref="apt.factory.path"
options="${apt.options}"
compile="false"/>
</then>
</if>
</for-each-java-src-path>
</then>
</if>
<for-each-java-src-path>
<if>
<available file="${.java.src.dir}"/>
<then>
<mkdir dir="${.java.src.output}"/>
<javac
sourcepath="${java.sourcepath}"
srcdir="${.java.src.dir}"
includes="${.java.src.include}"
excludes="${.java.src.exclude}"
destdir="${.java.src.output}"
classpathref="java.classpath"
debug="on"/>
</then>
</if>
</for-each-java-src-path>
<delete dir="${generated.module.root}"/>
<mkdir dir="${generated.module.root}"/>
<resolve-path property="user.web.xml" path="WEB-INF/web.xml"/>
<resolve-path property="user.weblogic.xml" path="WEB-INF/weblogic.xml"/>
<copy todir="${generated.module.root}/WEB-INF" file="${user.web.xml}" />
<copy todir="${generated.module.root}/WEB-INF" file="${user.weblogic.xml}" failonerror="false" />
</target>
<target name="clean" depends="init" description=" removes the files and directories generated by the build target">
<if>
<available file="${xbean.src.output.dir}"/>
<then>
<delete includeEmptyDirs="true">
<fileset dir="${xbean.src.output.dir}" includes="**/*"/>
</delete>
</then>
</if>
<if>
<available file="${xbean.bin.output.dir}"/>
<then>
<delete includeEmptyDirs="true">
<fileset dir="${xbean.bin.output.dir}" includes="**/*"/>
</delete>
</then>
</if>
<if>
<available file="${apt.src.output.dir}"/>
<then>
<delete includeEmptyDirs="true">
<fileset dir="${apt.src.output.dir}" includes="**/*"/>
</delete>
</then>
</if>
<for-each-java-src-path>
<if>
<available file="${.java.src.output}"/>
<then>
<if>
<equals arg1="${.java.src.dir}" arg2="${.java.src.output}"/>
<then>
<delete includeEmptyDirs="true">
<fileset dir="${.java.src.output}">
<or>
<filename name="**/*.class"/>
<and>
<type type="dir"/>
<depth min="0"/>
</and>
</or>
</fileset>
</delete>
</then>
<else>
<delete includeEmptyDirs="true">
<fileset dir="${.java.src.output}" includes="**/*"/>
</delete>
</else>
</if>
</then>
</if>
</for-each-java-src-path>
<delete dir="${assembly.src}"/>
<delete dir="${generated.module.root}"/>
<mkdir dir="${generated.module.root}"/>
</target>
<target name="assemble" depends="init" description=" assembles the project for iterative dev deployment; requires that the "ear.root" property is specified">
<property name="prefix" value=""/>
<for-each-resource-path>
<link ear="${ear.root}" source="${.resource.path}" target="${prefix}${uri}/${.resource.prefix}"/>
</for-each-resource-path>

<for-each-referenced-component>
<if>
<and>
<equals arg1="${.referenced.component.type}" arg2="project"/>
<equals arg1="${.referenced.component.target.path}" arg2="WEB-INF/lib"/>
</and>
<then>
<antex
antfile="${.referenced.component.handle}/build.xml"
dir="${.referenced.component.handle}"
target="assemble"
inheritUserProps="false"
inheritAll="false"
inheritRefs="false">
<property name="wl.home" value="${wl.home}"/>
<property name="patch.home" value="${patch.home}"/>
<property name="workspace" value="${workspace}"/>
<property name="init.typedefs.executed" value="true"/>
<property name="ear.root" value="${ear.root}"/>
<property name="prefix" value="${uri}/WEB-INF/lib/"/>
</antex>
</then>
</if>
</for-each-referenced-component>
<link ear="${ear.root}" source="${xbean.bin.output.dir}" target="${link.target}"/>
<link ear="${ear.root}" source="${generated.module.root}" target="${uri}"/>
<antcall target="assembly" inheritAll="true" inheritRefs="true" >
<param name="ear.root" value="${ear.root}"/>
</antcall>
<antcall target="webservice.build" inheritAll="true" inheritRefs="true" />
</target>
<target name="stage" depends="init" description=" copies all of project's resources and build artifacts into a form that's ready for archive creation; staging directory can be overridden via the "staging.dir" property">
<antcall target="assembly" inheritAll="true" inheritRefs="true" >
<param name="ear.root" value="${ear.staging.dir}"/>
</antcall>
<antcall target="webservice.build" inheritAll="true" inheritRefs="true" />
<property name="staging.dir" value="${project.dir}/.staging"/>
<delete dir="${staging.dir}" quiet="true"/>
<mkdir dir="${staging.dir}"/>
<for-each-resource-path>
<if>
<available file="${.resource.path}"/>
<then>
<if>
<isfile path="${.resource.path}"/>
<then>
<copy file="${.resource.path}" tofile="${staging.dir}/${.resource.prefix}"/>
</then>
<else>
<copy todir="${staging.dir}/${.resource.prefix}">
<fileset dir="${.resource.path}" includes="${.resource.include}" excludes="${.resource.exclude}"/>
</copy>
</else>
</if>
</then>
</if>
</for-each-resource-path>

<property name="webinflib" value="${staging.dir}/WEB-INF/lib"/>
<mkdir dir="${webinflib}"/>
<for-each-referenced-component>
<if>
<and>
<equals arg1="${.referenced.component.type}" arg2="project"/>
<equals arg1="${.referenced.component.target.path}" arg2="WEB-INF/lib"/>
</and>
<then>
<antex
antfile="${.referenced.component.handle}/build.xml"
dir="${.referenced.component.handle}"
target="archive"
inheritUserProps="false"
inheritAll="false"
inheritRefs="false">
<property name="wl.home" value="${wl.home}"/>
<property name="patch.home" value="${patch.home}"/>
<property name="workspace" value="${workspace}"/>
<property name="init.typedefs.executed" value="true"/>
<property name="archive.dir" value="${webinflib}"/>
</antex>
</then>
</if>
</for-each-referenced-component>
<copy todir="${staging.dir}/${xbean.deploy.prefix}">
<fileset dir="${xbean.bin.output.dir}"/>
</copy>
<if>
<available file="${generated.module.root}"/>
<then>
<copy todir="${staging.dir}" overwrite="true">
<fileset dir="${generated.module.root}"/>
</copy>
</then>
</if>
<taskdef name="build-manifests"
classname="weblogic.ant.taskdefs.build.AnnotationManifestTask"
onerror="fail" />
<path id="annotation.manifest.search.path">
<fileset dir="${staging.dir}">
<include name="WEB-INF/lib/*.jar"/>
</fileset>
<pathelement location="${staging.dir}/WEB-INF/classes"/>
</path>
<path id="annotation.manifest.class.path">
<path refid="annotation.manifest.search.path"/>
<path refid="java.classpath"/>
</path>
<build-manifests moduleDir="${staging.dir}"
searchClasspathRef="annotation.manifest.search.path"
classpathRef="annotation.manifest.class.path"
verbose="true"
version=""
stagingDir="${java.io.tmpdir}/.manifest"/>
</target>
<target name="archive" depends="stage" description=" creates an archive containing all projects's resources and build artifacts; archive name and location can be overridden via the "archive.path" property">
<property name="archive.dir" value="${project.dir}"/>
<mkdir dir="${archive.dir}"/>
<zip destfile="${archive.dir}/${archive.name}" encoding="UTF8" whenempty="create">
<fileset dir="${staging.dir}"/>
</zip>
</target>
<target name="stage.to.ear" depends="init">
<property name="prefix" value=""/>
<antcallex target="archive" inheritUserProps="false" inheritAll="false" inheritRefs="false">
<param name="wl.home" value="${wl.home}"/>
<param name="patch.home" value="${patch.home}"/>
<param name="workspace" value="${workspace}"/>
<param name="init.typedefs.executed" value="true"/>
<param name="archive.dir" value="${ear.staging.dir}${prefix}"/>
<param name="ear.staging.dir" value="${ear.staging.dir}"/>
</antcallex>
</target>
<target name="generated.root.init" depends="init">
<property name="generated.module.root" value="${project.dir}/build/weboutput"/>
</target>
<target name="assembly" depends="init,generated.root.init">
<taskdef name="assemble"
classname="com.bea.control.assembly.AssembleTask"
classpathref="java.classpath"
onerror="report" />
<property name="assembly.src.output" value="${java.src.0.output}"/>
<mkdir dir="${assembly.src}"/>
<path id="assembly.classpath">
<path refid="java.classpath" />
<pathelement location="${assembly.src.output}" />
<pathelement path="${java.outpath}" />
<pathelement path="${java.sourcepath}"/>
</path>
<assemble
moduleDir="${generated.module.root}"
moduleName="${project.name}"
srcOutputDir="${assembly.src}"
appRootDir="${ear.root}">
<assemblyContext factory="org.apache.beehive.controls.runtime.assembly.WebAppAssemblyContext$Factory" />
<assemblyContext factory="org.apache.beehive.controls.runtime.assembly.AppAssemblyContext$Factory" />
<classpath refid="assembly.classpath" />
<fileset dir="${project.dir}">
<include name="**/*.controls.properties" />
</fileset>
</assemble>
<apt
srcdir="${assembly.src}"
preprocessdir="${apt.src.output.dir}"
factorypathref="apt.factory.path"
options="${apt.options}"
compile="false">
<classpath refid="assembly.classpath" />
</apt>
<javac
srcdir="${assembly.src}"
destdir="${assembly.src.output}"
debug="on">
<classpath refid="assembly.classpath" />
</javac>
</target>
<target name="webservice.build" depends="init,generated.root.init">
<path id="jwsc.srcpath">
<path path="${java.sourcepath}" />
<pathelement path="build/assembly/.src" />
</path>
<taskdef name="jwsc" classname="weblogic.wsee.tools.anttasks.JwscTask" />
<property name="jwsc.module.root" value="${project.dir}/build/weboutput"/>
<property name="jwsc.contextpath" value="billingservice"/>
<property name="jwsc.srcpath.prop" refid="jwsc.srcpath"/>
<path id="jwsc.classpath">
<path refid="java.classpath" />
<pathelement path="${java.outpath}" />
</path>
<jwsc
destdir="${project.dir}/build"
classpathref="jwsc.classpath"
>
<module name="weboutput" explode="true" contextPath="${jwsc.contextpath}">
<jwsFileSet srcdir="${jwsc.srcpath.prop}">
<include name="**/*.java"/>
</jwsFileSet>
<descriptor file="${jwsc.module.root}/WEB-INF/web.xml" />
<descriptor file="${jwsc.module.root}/WEB-INF/weblogic.xml" />
</module>
</jwsc>
</target>
</project>
==================== end of exported build.xml =========
Thanks!
Edited by renqili at 08/09/2007 10:52 AM

It looks a bug to me. The exported ant script does not take care the jar files setup in the classpath in workshop/eclipes and copy them to the WEB-INFO/lib directory.

Can not get application bc4j for adding context root file

Hi all,
Can someone help me on this,
i got this this error while trying to run my web based reporting:
06/08/21 18:01:04 [SEVERE]: Error instantiating application at file:/C:/Documents and Settings/Bryan1/Desktop/Pattern Maching JSP 2006Feb/jdevstudio1013/jdev/system/oracle.j2ee.10.1.3.34.12/embedded-oc4j/applications/bc4j.ear: Unable to get ApplicationConfig for bc4j : Error creating deployment directory: IO Error: The system cannot find the path specified.
06/08/21 18:01:04 [SEVERE]: Error instantiating application at file:/C:/Documents and Settings/Bryan1/Desktop/Pattern Maching JSP May2006/jdevstudio1013/jdev/system/oracle.j2ee.10.1.3.34.12/embedded-oc4j/applications/ITS.ear: Unable to get ApplicationConfig for ITS : Error creating deployment directory: IO Error: The system cannot find the path specified.
2006-08-21 18:01:07.265 WARNING J2EE_OJR0007 Can not get application bc4j for adding context root file:/C:/Pattern Maching JSP May2006/jdevstudio1013/jdev/system/oracle.j2ee.10.1.3.34.12/embedded-oc4j/config/default-web-site.xml
Ready message received from Oc4jNotifier.
Embedded OC4J startup time: 5282 ms.
Target URL -- http://192.168.2.55:8988/Trans-Reporting-context-root/login.jsp
06/08/21 18:01:07 Oracle Containers for J2EE 10g (10.1.3.0.0) - Developer Preview initializedIF i run http://192.168.2.55:8080/Reporting/login.jsp from web browser then is ok, but cannot straight run from JDeveloper? How to set the path?
rgds,
bryan

Dear Frank,
Thanks for ur reply but i still failed to access to my login.jsp
I already select RUN from menu then clean <XXXX.jpr>, then rebuild the project and Run the project but still have the same problem.
rgds,
bryan

Deploy given EAR file having application.xml and change context-root

hi
Please consider deploying a given EAR file on WebLogic Server 10.3.5 (part of JDeveloper 11.1.1.6.0) and changing the context-root for its web-module.
For example an EAR file with only a web-module (ReviewContextRootFirstApp.ear [1]) or an EAR file with a web-module and an ejb-module (ReviewContextRootSecondApp.ear [2]).
Given documentation appendix B section "context-root" [3] saying
"... A context-root setting in application.xml takes precedence over context-root setting in weblogic.xml. ..."
and documentation section "Typical Deployment Configuration Workflows" [4] saying
"Oracle does not support using a deployment plan to change the context-root in an application.xml file. However, if an application is deployed as a library, you can either change the context-root through an weblogic-application.xml file or use the deployment plan to change the context-root in an weblogic-application.xml file. "
Some observed behaviour:
- scenario (sc1) : deploy ReviewContextRootFirstApp.ear without deployment plan, results in context-root "/rcrfaweb" (as in application.xml)
- scenario (sc2) : deploy ReviewContextRootFirstApp.ear with deployment plan fa-plan.xml (tries to configure "/rcrfaweb11"), results in context-root "/rcrfaweb" (as in application.xml)
- scenario (sc3) : deploy ReviewContextRootSecondApp.ear without deployment plan, results in context-root "/rcrsaweb" (as in application.xml)
- scenario (sc4) : deploy ReviewContextRootSecondApp.ear with deployment plan sa-plan.xml (tries to configure "/rcrsaweb21"), results in context-root "/rcrsaweb" (as in application.xml)
The blog post "Defining the context root of a web application in Oracle WebLogic server" [5] by Silviu Leahu in its section "Defining the context root in deployment plan" suggests to
"Remove the META-INF/application.xml DD from the EAR"
- scenario (sc5) : remove application.xml from ReviewContextRootFirstApp.ear (e.g. using Ant target "remove.application.xml.from.ear") and deploy with deployment plan fa-plan.xml, results in context-root "/rcrfaweb11" (as in fa-plan.xml)
- scenario (sc6) : remove application.xml from ReviewContextRootSecondApp.ear (e.g. using Ant target "remove.application.xml.from.ear") and deploy with deployment plan sa-plan.xml, results in context-root "/rcrsaweb21" (as in sa-plan.xml)
One could expect that using a deployment plan (like in scenario's (sc2) and (sc4)) would allow to configure/change the context-root, whithout having to make changes to the EAR file to make this possible. (Somewhat like "Figure 4-2 Single Deployment Plan Workflow")
Only in scenario's (sc5) and (sc6) I see something close to what I would like to achieve, but there the application.xml file has been removed from the EAR file.
So ...
- (q1) Is it impossible to change the context-root at deploy-time for a web-module in a given EAR file that includes an application.xml file, without changing the EAR file?
- (q2) Is working with EAR files that don't have an application.xml file a supported approach (to change the context-root at deploy-time)?
Seems like a simple goal, but I must be missing something that is required to achieve it.
- [1] ReviewContextRootFirstApp/deploy/ReviewContextRootFirstApp.ear in the ZIP file
at http://www.consideringred.com/files/oracle/2012/ReviewContextRootApps-v0.01.zip
- [2] ReviewContextRootSecondApp/deploy/ReviewContextRootSecondApp.ear in the (same) ZIP file
at http://www.consideringred.com/files/oracle/2012/ReviewContextRootApps-v0.01.zip
- [3] http://docs.oracle.com/cd/E21764_01/web.1111/e13712/weblogic_xml.htm#WBAPP623
- [4] http://docs.oracle.com/cd/E21764_01/web.1111/e13702/config.htm#DEPGD172
- [5] http://blog.leahu.net/it/2011/01/04/defining-the-context-root-of-a-web-application-in-oracle-weblogic-server/
many thanks
Jan Vervecken

Thanks for your reply René van Wijk.
René van Wijk wrote:
You can use deployment plans in order to change the context-root ...That is what I tried and describe in scenario's (sc2), (sc4), (sc5) and (sc6) in this forum thread.
Because the application.xml file (in the "given EAR file"), added by JDeveloper 11.1.1.6.0 when deploying to an EAR file, doesn't have id attributes on its application/module elements, I first tried a different XPath expression:
"/application/module/web[web-uri/text()="WebProject.war"]/context-root"
But, that didn't work.
Although the "given EAR file" does not have the suggested id attributes, I tried adding a deployment descriptor application.xml file that does have such id attributes [2], allowing an XPath expression like the one suggested:
"/application/module[id="WebProject"]/web/context-root"
- scenario (sc7) : deploy ReviewContextRootFirstApp.ear (in ReviewContextRootApps-v0.02.zip) with deployment plan fa-plan-application-xml-with-id.xml (tries to configure "/rcrfaweb14"), results in context-root "/rcrfaweb" (as in application.xml)
- scenario (sc8) : deploy ReviewContextRootSecondApp.ear (in ReviewContextRootApps-v0.02.zip) with deployment plan sa-plan-application-xml-with-id.xml (tries to configure "/rcrsaweb24"), results in context-root "/rcrsaweb" (as in application.xml)
So, it does not seem to work.
... you have to use a variable assignment in the right part of the deployment plan (in this case the application.xml) ...My observations I describe above (that it does not seem to work) seem to confirm the Oracle documentation [1] I referred to in this forum thread before:
"Oracle does not support using a deployment plan to change the context-root in an application.xml file. ... "
... By using an xpath expression, you can define which part of the xml has to be changed. ...The values for the deployment-plan xpath elements seem to be "peculiar".
Although it should not be a problem in an XPath expression, using single quotes (like module[id='WebProject'] ) instead of double quotes (like module[id="WebProject"] ) results in:
"java.lang.AssertionError: Attributes must be defined as name value pairs, eg, name="value" -- [id='WebProject']"
Because an XPath predicate expression would use an "@" to refer to an attribute, I also tried to replace what you suggested module[id="Web"] with something like module[@id="Web"] but that also did not make a difference.
- [1] http://docs.oracle.com/cd/E21764_01/web.1111/e13702/config.htm#DEPGD172
- [2] http://www.consideringred.com/files/oracle/2012/ReviewContextRootApps-v0.02.zip
regards
Jan Vervecken

Export OSB configuration from eclipse using ant script

I am trying to export an OSB project from eclipse using ant script
I followed the link below http://biemond.blogspot.com/2010/07/osb-11g-ant-deployment-scripts.html
It is using com.bea.alsb.core.ConfigExport to do the export. This export is always set to resource level.
I see it generates a file ExportInfo setting some properties. It has a property that set the export level as below
<imp:property name="projectLevelExport" value="false"/>*
How can I export the project in project level? basically setting projectLevelExport to true?
So that if a file does not exist in the sbconfig.jar file , then while importing the jar to OSB server it will delete the file from the server instead of skipping it?
I appreciate any help
here is the ant script snippet that gets executed to export from eclipse
<target name="exportFromWorkspace">
     <delete failonerror="false" includeemptydirs="true"
dir="${metadata.dir}"/>
               
<java dir="${eclipse.home}"
jar="${eclipse.home}/plugins/org.eclipse.equinox.launcher_1.1.0.v20100507.jar"
fork="true" failonerror="true" maxmemory="768m">
<jvmarg line="-XX:MaxPermSize=256m"/>
<arg line="-data ${workspace.dir}"/>
<arg line="-application com.bea.alsb.core.ConfigExport"/>
<arg line="-configProject ${config.project}"/>
<arg line="-configJar ${config.jar}"/>
<arg line="-configSubProjects ${config.subprojects}"/>
          <arg line="-exportLevel true"/>
<arg line="-includeDependencies ${config.includeDependencies}"/>
<sysproperty key="weblogic.home" value="${weblogic.home}"/>
<sysproperty key="osb.home" value="${osb.home}"/>
<sysproperty key="osgi.bundlefile.limit" value="500"/>
<sysproperty key="harvester.home" value="${osb.home}/harvester"/>
<sysproperty key="osgi.nl" value="en_US"/>
<sysproperty key="sun.lang.ClassLoader.allowArraySyntax" value="true"/>
</java>
</target>

yes, I specified the project name to export the whole project.
Here is few lines from my properties file
# properties for workspace export
config.project="OSB Configuration-GW"
config.jar=D:/workspace/osb/scripts/gateway/mycode2/ant_osb/dist/sbconfig.jar
config.subprojects="GatewaySecurity"
config.includeDependencies=true
workspace.dir=D:/workspace/osb/gateway-workspace
But this property does not make it to export at project level ,it export the specified project at resource level.
And while importing this jar to OSB server, if a file is missing it skips the file instead of deleting the file from the OSB server
If I unjar sbconfig.jar file, open ExportInfo file and update the line in bold below to true then it deletes the file from OSB server, if not exist in sbconfig.jar
<imp:property name="exporttime" value="Thu Dec 29 13:57:44 EST 2011"/>
<imp:property name="productname" value="Oracle Service Bus"/>
<imp:property name="productversion" value="11.1.1.4"/>
*<imp:property name="projectLevelExport" value="false"/>*
Here is few lines from Oracle API java doc
http://docs.oracle.com/cd/E13171_01/alsb/docs26/javadoc/com/bea/wli/sb/management/importexport/ALSBImportOperation.Operation.html
public static final ALSBImportOperation.Operation Delete
Indicates that the resource is deleted in the importing domain. This is the default operation when the project is exported in its entirety and the resource exists in the target domain but not in the jar file
public static final ALSBImportOperation.Operation Skip
Indicates that the resource is skipped meaning the resource is not touched in the importing domain. This is the default operation if the jar file was exported at the resource level, and a resource that exists in the target domain, does not exist in the jar file.

Error while compiling the composite through custom ant script

Hi,
I am getting the following error while compiling the composite through custom built ant scripts which are intern call the ant-sca-package.xml. And the composite is created by upgrading the 10g bpels. But the same composite is successfully compiling from Jdeveloper (11.1.1.4).
oad of wsdl "oramds:/soa/shared/workflow/NotificationService.wsdl" failed
oracle.fabric.common.FabricException: Error in getting XML input stream: oramds:/soa/shared/workflow/NotificationService.wsdl: oracle.mds.exception.MDSException: MDS-00054: The file to be loaded oramds:/soa/shared/workflow/NotificationService.wsdl does not exist.
     at oracle.fabric.common.metadata.MetadataManagerImpl.getInputStreamFromAbsoluteURL(MetadataManagerImpl.java:280)
     at oracle.integration.platform.common.MDSMetadataManagerImpl.getInputStreamFromAbsoluteURL(MDSMetadataManagerImpl.java:555)
     at oracle.fabric.common.metadata.MetadataManagerImpl.getDocumentAsInputStream(MetadataManagerImpl.java:159)
     at oracle.integration.platform.common.MDSMetadataManagerImpl.getDocumentAsInputStream(MDSMetadataManagerImpl.java:417)
     at oracle.fabric.common.wsdl.WSDLManager.loadWSDL(WSDLManager.java:241)
     at oracle.fabric.common.wsdl.WSDLManager.loadWSDL(WSDLManager.java:304)
     at oracle.soa.scac.ValidateComposite.loadWSDLs(ValidateComposite.java:934)
     at oracle.soa.scac.ValidateComposite.doValidation(ValidateComposite.java:491)
     at oracle.soa.scac.ValidateComposite.run(ValidateComposite.java:150)
     at oracle.soa.scac.ValidateComposite.main(ValidateComposite.java:135)
Caused by: java.io.IOException: oracle.mds.exception.MDSException: MDS-00054: The file to be loaded oramds:/soa/shared/workflow/NotificationService.wsdl does not exist.
     at oracle.mds.internal.net.AbstractOraMDSURLConnection.getPDocStream(AbstractOraMDSURLConnection.java:388)
     at oracle.mds.internal.net.AbstractOraMDSURLConnection.getInputStream(AbstractOraMDSURLConnection.java:176)
     at oracle.mds.internal.net.OraMDSURLConnection.getInputStream(OraMDSURLConnection.java:67)
     at java.net.URL.openStream(URL.java:1010)
     at oracle.fabric.common.metadata.MetadataManagerImpl.getInputStreamFromAbsoluteURL(MetadataManagerImpl.java:276)
     ... 9 more
Caused by: oracle.mds.exception.MDSException: MDS-00054: The file to be loaded oramds:/soa/shared/workflow/NotificationService.wsdl does not exist.
     at oracle.mds.internal.net.AbstractOraMDSURLConnection.getPDocStream(AbstractOraMDSURLConnection.java:339)
And in the following blog, its recommended to check for the adf-config.xml. But when upgrading the bpels from 10g to 11.1.1.4, I don't see any such file created by Jdeveloper.
http://orasoa.blogspot.com/2010/08/ant-and-mds-composite-compile-error.html
Not sure if I am missing some properties to add in by custom script while compiling.
Thanks
Sree
Edited by: Sree on Jul 4, 2011 7:25 AM

Hi Hussain,
Thanks for the reply.
Were you able to compile the form at the client side successfully?
1) Were you able to compile the form at the client side successfully?:
Ans: Yes, I was able to compile the form successfully at client side.
2) Are you logged in as applmgr user? Have you sourced the application env file before compiling the form?
Ans: No, I have not logged by applmgr user, i am using my own login. Yes I have sourced the application env file before compiling the form
3) What does "echo $FORMS_PATH" return?
Ans: echo $FORMS_PATH on server gives this path
/u01/app/EBS00/apps/apps_st/appl/au/12.0.0/resource:/u01/app/EBS00/apps/apps_st/appl/au/12.0.0/resource/stub
Can you please advise?
Thanks,

Disk Utility and fsck report 'missing thread records' and can't repair.

Hello,
What first made me realise there was a problem with my iMac was that when I tried to update a application it failed. I then manually download the .dmg of the update and tried replaced the app (Transmission 1.82 being that app in question). This failed, OS X claiming that it could not replace the older version (1.81). I then tried copying the file to the desktop where OS X claimed that there was already a copy of the application and so left a corrupted file on my desktop. This also happened when i attempted to move and copy a couple of pages documents and movie files around. I decided the best thing to do at this point was to reboot my computer; OS X decided it needed to install a couple of security updates at this point. This installation failed.
My iMac booted up, but only after a progress bar has appeared under the Apple logo and spinner and has done its thing (From what I've read this means that OS X is trying its best to resolve some sort of errors). This happens upon every boot.
This made me think that something must be going on with the file system of my Mac so I ran all the tests in Disk Utility. Permissions repair ran fine and fixed a few issues, but when I verified the disk this is what it reported:
"Verifying volume “Macintosh HD”
Performing live verification.
Checking Journaled HFS Plus volume.
Checking extents overflow file.
Checking catalog file.
Missing thread record (id = 2045563)
Missing thread record (id = 2096282)
Keys out of order
The volume Macintosh HD was found corrupt and needs to be repaired.
Error: This disk needs to be repaired. Start up your computer with another disk (such as your Mac OS X installation disc), and then use Disk Utility to repair this disk."
I booted up from the DVD and tried to repair; this failed. Next I tried using fsck in single user mode; this also failed. Upon rebooting again and waiting for the progress bar to fill I was able to move files around and update Transmission without issue. Disk Utility still reports the same error.
If I boot into Windows Vista everything works perfectly; as of yet I haven't got around to installing the new Boot Camp update for Windows 7 support incase that changes anything. When running the diagnostic tool on the Windows Vista DVD it reports that everything is fine for Windows.
I really am at a loss for what to do next. All my data is backed up by Time Machine onto a Time Capsule as well as manually onto a FW external. I also made a clone of the Windows partition using the free app Winclone. Does anyone know anything I can do to fix this problem?
Thanks so much,
Sam.

I have been experiencing exactly the same problem here with my MacPro. Apple replaced the hard disk because it was reporting bad sectors. However even with the replacement hard disk I'm experiencing the "missing thread" issue again. I'm guessing its either a software issue that keeps recurring or a fundamental hardware issue. Is the disk controller part of the hard disk or the motherboard? I've never had hard disk problems like this before.
Here's my Disk Utility report from earlier today:
Checking Journaled HFS Plus volume.
Checking extents overflow file.
Checking catalog file.
Missing thread record (id = 1067066)
Missing thread record (id = 1111528)
Missing thread record (id = 1196845)
Missing thread record (id = 1200621)
Missing thread record (id = 1260154)
Missing thread record (id = 1277166)
Missing thread record (id = 1285010)
Missing thread record (id = 1297257)
Missing thread record (id = 1316679)
Missing thread record (id = 1437800)
Incorrect number of thread records
Checking multi-linked files.
Checking catalog hierarchy.
Invalid volume directory count
(It should be 155085 instead of 155095)
Checking extended attributes file.
Checking volume bitmap.
Checking volume information.
Repairing volume.
Missing directory record (id = 1437800)
Missing directory record (id = 1316679)
Missing directory record (id = 1297257)
Missing directory record (id = 1285010)
Missing directory record (id = 1277166)
Missing directory record (id = 1260154)
Missing directory record (id = 1200621)
Missing directory record (id = 1196845)
Missing directory record (id = 1111528)
Missing directory record (id = 1067066)
Look for missing items in lost+found directory.
Rechecking volume.
Checking Journaled HFS Plus volume.
Checking extents overflow file.
Checking catalog file.
Checking multi-linked files.
Checking catalog hierarchy.
Checking extended attributes file.
Checking volume bitmap.
Checking volume information.
Invalid volume directory count
(It should be 155106 instead of 155096)
Repairing volume.
Rechecking volume.
Checking Journaled HFS Plus volume.
Checking extents overflow file.
Checking catalog file.
Checking multi-linked files.
Checking catalog hierarchy.
Checking extended attributes file.
Checking volume bitmap.
Checking volume information.
The volume MacHD was repaired successfully.

Mapping of Web App context root and the physical directory of the web app

I'm running Weblogic 7.0 on Windows2000.The physical directory of my web application
is D:\WL8\weblogic81\TestDeploy\build\TestWebApp and under these directory I have
my JSPS, static HTML and WEB-INF. I define the context path of this web app in
the weblogic.xml ;-
<weblogic-web-app>
<context-root>/testapp</context-root>
</weblogic-web-app>
As a result of deploying this web app in the server (or it may be created manually
also), the following entry gets inserted in the server's config.xml ,-
<Application Deployed="true" Name="TestWebApp"
Path="D:\WL8\weblogic81\TestDeploy\build" TwoPhase="true">
<WebAppComponent Name="TestWebApp" Targets="myserver" URI="TestWebApp"/>
</Application>
Now, whenever I make a request of the form "http://localhost:7001/testapp/..",
it's properly executing my web app. My question is, how does the container knows
that for any request for the web app with context path as 'testapp', it has to
server files from D:\WL8\weblogic81\TestDeploy\build\TestWebApp. In the above
process, nowhere such mapping is specified. I expected something like Tomcat's
server.xml, where in docbase we clearly specify this mapping between the context
path and the physical directory. Please help.

Let me give some more details and hopefully this will make things clearer.
Say you deploy /foo/bar/myweb.war and in myweb.war you configure a
context-root of /rob
During deployment, the server creates an ApplicationMBean with a path of
/foo/bar/. It then creates a WebAppComponent with a uri of myweb.war.
Next, deployment calls back on the web container and tells it to deploy
the WebAppComponent. The web container reads the myweb.war, parses
descriptors etc. The web container then updates its data structures to
register that myweb.war has a context path of /rob. (It has to figure
out all the other servlet mappings as well.)
When a request for /rob/foo comes in, the web container consults its
data structures to determine which webapp and servlet receives the
request. This is not a linear search of all webapps and servlets.
There's much better ways to do pattern matching.
Hope this clears things up. Let me know if you still have questions.
-- Rob
Arindam Chandra wrote:
Thanks for the answer. Still one thing is not clear. Whatever context path I declare
for my web app as the value of <context-root> element in the weblogic.xml (in
my example it's "/testapp"), it is no where mapped with the "URI" attribute (or
any other attribute, sub-element whatsoever in the <Application> element).
Application Deployed="true" Name="TestWebApp"
Path="D:\WL8\weblogic81\TestDeploy\build" TwoPhase="true">
<WebAppComponent Name="TestWebApp" Targets="myserver" URI="TestWebApp"/>
</Application>
So when a request of the form http://myweblogic.com:7001/testapp/... arrives at
the server, how does the server knows that it has to serve this request with files
from D:\WL8\weblogic81\TestDeploy\build\TestWebApp ? It should not be like the
web container iterates thru all the web application entries in config.xml and
tries to match with one context-root declaration. I repeat, I expected some mapping
similar to Tomcat's server.xml, where in the <docbase> element u clearly specify
the mapping between the context path and the physical directory
Rob Woollen <[email protected]> wrote:
Arindam Chandra wrote:
I'm running Weblogic 7.0 on Windows2000.The physical directory of myweb application
is D:\WL8\weblogic81\TestDeploy\build\TestWebApp and under these directoryI have
my JSPS, static HTML and WEB-INF. I define the context path of thisweb app in
the weblogic.xml ;-
<weblogic-web-app>
<context-root>/testapp</context-root>
</weblogic-web-app>
As a result of deploying this web app in the server (or it may be createdmanually
also), the following entry gets inserted in the server's config.xml,-
<>So the server will look for your web application at the Application Path
(D:\WL8\weblogic81\TestDeploy\build|) + the web uri (TestWebApp). So
it
maps the context-root you've specified /testapp to that path.
It's a little clearer in the case where you had a full-fledged EAR.
Then you'r application path would map to the "root" of the EAR, and the
uris would point to the various modules (eg webapps.)
-- Rob
Now, whenever I make a request of the form "http://localhost:7001/testapp/..",
it's properly executing my web app. My question is, how does the containerknows
that for any request for the web app with context path as 'testapp',it has to
server files from D:\WL8\weblogic81\TestDeploy\build\TestWebApp. Inthe above
process, nowhere such mapping is specified. I expected something likeTomcat's
server.xml, where in docbase we clearly specify this mapping betweenthe context
path and the physical directory. Please help.

How to change data source name and context root during deployment

Hi,
Env:
WLS 10.1.3
JDev 11.1.1.6
Hudson
I need to deploy two instances of my ADF application on the same development enviroment. We are using Hudson to deploy. My question is how to change data source name and application context root before second deployment.
Kuba

I don't believe there is an inbuilt facility to do this.
Previously how I've done this is when checking files out using Hudson jovs, before the build I then use an Ant extension called XmlTask (http://www.oopsconsultancy.com/software/xmltask/) to modify the required XML files.
Can I ask why you're doing this in the first place please? Multi-tenancy? 2 versions of the same app?
CM.

Problem in ant script (starting tomcat)...

Hi,
in my ant script (build.xml) I have some targets to start/stop tomcat:
    
    
    
    
    <target name="-started">
        <condition property="server.started">
            <and>
                <socket port="${tomcat.port}" server="${tomcat.server}"/>
            </and>
        </condition>
    </target>
    
    <target name="start" depends="-started" description="start tomcat server"
        unless="server.started">
        <echo message="Starting tomcat servlet engine..."/>
            <java classname="org.apache.catalina.startup.Bootstrap" fork="yes">
            <jvmarg value="-Djava.endorsed.dirs=${catalina.dir}/common/endorsed"/>
            <jvmarg value="-Dcatalina.base=${catalina.dir}"/>
            <jvmarg value="-Dcatalina.home=${catalina.dir}"/>
            <jvmarg value="-Djava.io.tmpdir=${catalina.dir}/temp"/>
            <arg value="start"/>
            <classpath>
                <pathelement location="${java.home}/../lib/tools.jar"/>
                <pathelement location="${catalina.dir}/bin/bootstrap.jar"/>
            </classpath>
        </java>
    </target>
    
    <target name="-stopped">
        <condition property="server.stopped">
            <and>
                <socket port="${tomcat.port}" server="${tomcat.server}"/>
                <not>
                    <isset property="server.started"/>
                </not>
            </and>
        </condition>
    </target>
    
    <target name="stop" depends="-stopped" description="stop tomcat server"
        if="server.stopped">
        <echo message="Stopping tomcat servlet engine..."/>
        <java classname="org.apache.catalina.startup.Bootstrap" fork="yes">
            <jvmarg value="-Djava.endorsed.dirs=${catalina.dir}/common/endorsed"/>
            <jvmarg value="-Dcatalina.base=${catalina.dir}"/>
            <jvmarg value="-Dcatalina.home=${catalina.dir}"/>
            <jvmarg value="-Djava.io.tmpdir=${catalina.dir}/temp"/>
            <arg value="stop"/>
            <classpath>
                <pathelement location="${java.home}/../lib/tools.jar"/>
                <pathelement location="${catalina.dir}/bin/bootstrap.jar"/>
            </classpath>
        </java>
    </target>The problem I have is, when using another target which depends on the tomcat start target, for example my list target:
    <target name="list" depends="start" description="list installed web applications">
        <list url="${url}" username="${username}"
            password="${password}"/>
    </target>When executing the list target, tomcat starts up correctly but the list target is not executed.
Any help would be greatly appreciated.
Best regards
- Stephan

No, I don't think that's the problem.
In my opinion, the problem has something to do with
fork="yes"in the start target.
But how can I tell ant to first execute another target (the target that starts tomcat) and then execute for example the list target (which lists all the installed web apps)? When using the depends attribute it doesn't work:
<target name="list" depends="start">
    <list url=.../>
</target>When executing the list target, tomcat starts automatically (start target) but the list target is not executed after that :-(
Any ideas?
Best regards
- Stephan

Context-root="" in ant script still reports missing in mxmlc

Similar Messages

Maybe you are looking for