Application.xml and servicegen

Hi
Our web services each have an admin web application that goes with them. This enables us to change configuration settings at runtime.
We want to try to build an ear file that includes both the service and the admin web app.
The problem is that we need to add the web app as a module to application.xml. The Servicegen ant task does not seem to allow us to do this. Ideally, we would have our web app entries in a file that servicegen merges with its generated application.xml.
Clearly we can manually edit the generated application file and repackage the ear file, put this is messy and prone to error.
Any ideas?
Thanks
Andrew Bamford

Found the solution.
We created an application.xml with just the web application in it and added the overwrite="false" attribute to the servicegen task.
The ant script was changed to copy our application.xml file to the appropriate place in the build area (/build/META-INF). Servicegen now adds to this, rather than overwriting it.
Andrew Bamford:-)

Similar Messages

  • Using ADL when Application.xml and Content.swf are not in the BIN directory

    Hello, I am trying to use the air debug launcher (ADL) to
    launch a simple air app. My issue is I am trying to have ADL launch
    this app from outside of the bin directory of the SDK. Whenever I
    try to pass adl the full path to the Applicaiton.xml file it says
    "application descriptor not found" Does anyone know how to get
    around this? How can I run an AIR app that is outside of the bin?
    My situation C:\AIR has the Applicaiton.xml and Content.swf
    files, then a directory way below C:\Program Files\....\..... has
    the bin directory. I can run adl using its full path C:\Program
    Files\....\bin\adl, but when I pass it the full path for
    Application.xml it fails.
    By the way when I put everything in the bin, or below the bin
    it works just fine.

    If you're receiving this error message then the full path
    you're specifying for application.xml must be incorrect.

  • Content-type: application/xml and Application server 9

    I have a web service running on Application server 9, implemented using netbeans and JAX-WS.
    When a client sends a request to it with:
    Content-type: application/xml
    the request is rejected because the server does not recognise the mime type.
    Specifically, the response is:
    HTTP/1.1 415 Unsupported Media Type
    X-Powered-By: Servlet/2.5
    Content-Type: text/plain; charset=iso-8859-1
    Date: Fri, 01 Sep 2006 14:49:04 GMT
    Server: Sun Java System Application Server Platform Edition 9.0
    Connection: close
    Everything works fine when the request has:
    Content-type: text/xml
    Is there a way to make my web service accept content type of 'application/xml'?
    -Tony Beaumont
    Aston University
    beaumoaj

    I have fixed this for myself, i.e. decompile, replace in jar.
    My problem was that most tools define the encoding but code was simply testing
    if( contentType.equalsIgnoreCase( "text/xml" ) )
    so sending xml from other tools that send contentType
    "text/xml;encoding=UTF-8" or some such, like soap tools, would mean no XML was seen.
    Is the proper source available for XSQL?

  • Weblogic-application.xml and prefer-application-packages tag issue.

    Hi All,
    To solve one of the issue I have mentioned already in
    http://forums.bea.com/bea/thread.jspa?threadID=300000394 post.
    I am planning to use prefer-application-packages tag in weblogic-application.xml but it says XML is invalid and shows following error in workshop 9.2.1.
    Severity     Description     Resource     In Folder     Location     Creation Time     Id
    2     cvc-complex-type.2.4.a: Invalid content was found starting with element 'wls:prefer-application-packages'. One of '{"http://www.bea.com/ns/weblogic/90":library-ref, "http://www.bea.com/ns/weblogic/90":fair-share-request, "http://www.bea.com/ns/weblogic/90":response-time-request, "http://www.bea.com/ns/weblogic/90":context-request, "http://www.bea.com/ns/weblogic/90":max-threads-constraint, "http://www.bea.com/ns/weblogic/90":min-threads-constraint, "http://www.bea.com/ns/weblogic/90":capacity, "http://www.bea.com/ns/weblogic/90":work-manager, "http://www.bea.com/ns/weblogic/90":application-admin-mode-trigger, "http://www.bea.com/ns/weblogic/90":session-descriptor, "http://www.bea.com/ns/weblogic/90":library-context-root-override}' is expected.     weblogic-application.xml     wivApp/EarContent/META-INF     line 22     June 13, 2007 9:12:51 AM     191
    This is my weblogic-application.xml
    <?xml version="1.0" encoding="UTF-8"?>
    <wls:weblogic-application xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance" xmlns:wls="http://www.bea.com/ns/weblogic/90" xsi:schemaLocation="http://java.sun.com/xml/ns/j2ee http://java.sun.com/xml/ns/j2ee/j2ee_1_4.xsd http://www.bea.com/ns/weblogic/90 http://www.bea.com/ns/weblogic/90/weblogic-application.xsd">
    <wls:application-param>
    <wls:param-name>webapp.encoding.default</wls:param-name>
    <wls:param-value>UTF-8</wls:param-value>
    </wls:application-param>
    <wls:library-ref>
    <wls:library-name>beehive-controls-1.0</wls:library-name>
    <wls:specification-version>1.0</wls:specification-version>
    <wls:implementation-version>1.0</wls:implementation-version>
    </wls:library-ref>
    <wls:library-ref>
    <wls:library-name>wls-commonslogging-bridge</wls:library-name>
    <wls:specification-version>1.0</wls:specification-version>
    <wls:implementation-version>1.0</wls:implementation-version>
    </wls:library-ref>
    <wls:library-ref>
    <wls:library-name>weblogic-controls-1.0</wls:library-name>
    <wls:specification-version>1.0</wls:specification-version>
    <wls:implementation-version>1.0</wls:implementation-version>
    </wls:library-ref>
    <wls:prefer-application-packages>
         <wls:package-name>org.apache.log4j.*</wls:package-name>
    </wls:prefer-application-packages>
    </wls:weblogic-application>

    Hi Hitesh,
    Got the same problem.
    What I did to fix it was to switch both declarations :
    Before :
    http://www.bea.com/ns/weblogic/90
    http://www.bea.com/ns/weblogic/90/weblogic-application.xsd
    After :
    http://www.bea.com/ns/weblogic/90/weblogic-application.xsd http://www.bea.com/ns/weblogic/90
    And the Workshop error's gone.
    Note that I don't think it would have prevented your filtering class loader from working.
    Regards

  • 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

  • Override JNDI names in persistence.xml and @resource annotation

    I have a Java EE 7 application that I am developing for use with both GlassFish and WildFly, but I have discovered that both application servers use a slightly different format for specifying JNDI names.
    In GlassFish the persistence.xml file references the data source jdbc/myDataSouce, but in WildFly the data source needs to be java:/jdbc/myDataSource.The same is also true for classes that are annotated with @Resource. In GlassFish the annotation for a class using JavaMail would be @Resource(name = "mail/myMailSession"), but to deploy onto WildFly this would need to be @Resource(name = "java:mail/myMailSession").
    The only solution I've got at present is using Maven to create two different releases of the EAR file, with one EAR file containing a persistence.xml file with the data source jdbc/myDataSouce for use with GlassFish, and the second EAR file containing a persistence.xml file with the data source java:/jdbc/myDataSource for use with WildFly. Unfortunately, I haven't found a solution for the @Resource annotation.
    I've taken a look at the documentation for glassfish-application.xml and glassfish-ejb-jar.xml and have tried using resource-ref to override the JNDI names but the application fails to deploy due to an error in the name.
    My question is does GlassFish provide any capability to override the JNDI names specified in the persistence.xml file and classes with the @resource annotation?
    Many Thanks
    Paul

    Have you been able to solve this? I'm attempting to understand what Web Server 7 can do with regard to Java Persistence and what elements of it require Glassfish.
    I've also spent great amounts of time in WS6.1 trying to figure out why a JNDI resource couldn't be found. The rules of thumb I've learned are:
    - Try dropping the *'java:/comp/env/* prefix; just use jdbc/pact part
    - Make sure all referrences (in web.xml and sun-web.xml) are identical with regard to that name.
    I'm hoping you're not still dealing with this (it's been two months!) but if anybody else stumbles on this, maybe it'll help them.
    Dave

  • SOAP Adapter without SOAP envelope sets contenttype to application/xml

    Hi,
    I wrote a adaptermodul for the SOAP adapter to create a SOAP:HEADER.
    I disable the SOAP envelope in the communication channel.
    Now I get a error from the WebService Provider because the SOAP Adapter sends with Content-Type application/xml and not text/xml. I set the content-type in the adapter module but it seens to not work.
    How can I correct this ?
    Regards,
    Gerald

    Hi
    Simple answer is NO, it is not possible (without party/channel/ service etc to process the request)
    but it is worth a try to check if the URL encoding works.. though I have not tried..
    for example sending the hex value of the "?" -   %3F%
    URL is a generic topic, you can search that to get more information
    (ex  :  http://www.blooberry.com/indexdot/html/topics/urlencoding.htm)
    Regards
    Vishnu

  • Orion-application.xml

    I am packaging an application for deployment. Using JDeveloper, I created an orion-application.xml and it was placed in src/META-INF. When I deploy to an ear file, I see that my orion-application.xml is packaged. However, when I deploy it to my stand-alone OC4J instance, a new, default orion-applicaiton.xml is created and mine is nowhere to be found. I see no errors reported in any of the logs about any possible syntax errors with mine. Anyone know what I may have done wrong? Thanks!

    Did you check how the EAR was formed by your JDeveloper? There should be an orion-application.xml file with in META-INF dir starting from the root of your ear file check for this.
    Any how when it you deploy to standalone oc4j, it modifies your packaged orion-application.xml file a little bit i.e it addes the items to it and then deployes.
    The items that gets added to orion-application.xml before it gets deployed is as follows.
    <namespace-access>
              <read-access>
                   <namespace-resource root="">
                        <security-role-mapping>
                             <group name="jazn.com/administrators"/>
                        </security-role-mapping>
                   </namespace-resource>
              </read-access>
              <write-access>
                   <namespace-resource root="">
                        <security-role-mapping>
                             <group name="jazn.com/administrators"/>
                        </security-role-mapping>
                   </namespace-resource>
              </write-access>
         </namespace-access>
    </orion-application>
    -Mallik

  • StorageDir in Application.xml

    We store all of our flv files on a network storage device.
    I've setup a VirtualDirectory in vhosts.xml that maps a virtual
    path to the network drive.
    I have noted the StorageDir in application.xml and tried
    changing this to the network drive. It was not successful.
    My question is what is the difference between these two
    settings (other than the ability to add the virtual path part of
    the Virtual Directory).
    We plan on having only a few applications and passing the
    different rtmp paths via xml or html to the player. Should we use
    the StorageDir (and if so how to make it a network path) or should
    we continue to just add /{dirname} to the rtmp and let it map to
    the network drive.
    thanks,
    sds

    I think you need to use <VirtualDirectory> settings rather than <StorageDir> setting. Please refer this page for more info:http://help.adobe.com/en_US/FlashMediaServer/3.5_AdminGuide/WS5b3ccc516d4fbf351e63e3d119f2 925e64-7fc7.html

  • Orion-application.xml gets overwriten when deploying with admin_client.jar

    Hi,
    I am trying to deploy an ear in OC4J 10.1.3.3.0. The ear contains a META-INF folder with a application.xml and a orion-application.xml files.
    When running the admin-client command line, the deployment overwrittes the orion-application.xml file.
    I really don't know how to solve this problem.
    What else could I do?

    Greetings,
    The file orion-application.xml is an oc4j-specific file. If you do not create this yourself it will be created during deployment of your application.
    Reference for additional information:
    "OCA Oracle Application Server 10g Administrator Exam Guide"
    This is an Oracle Press book and treats the topic very thoroughly.
    -Michael

  • Newbie: orion-application.xml in both deployment and applications dirs

    Okay,
    I am using OAS 10.1.2.2 and have deployed an OC4J instance with a web application. The web application that I deployed (from a .war file) was installed normally but for some reason I have an orion-application.xml file in both the +/application-deployments/webappname/+ and the +/applications/webappname/META-INF/+ directories. They look almost identical with the differences noted below:
    applications directory version:
    This file has a complete definition for the jazn provider but is missing a reference to the principals.xml file.
    jazn section looks like this:
         <jazn provider="LDAP" location="ldap://ldap.server.edu:389">
              <property name="ldap.user" value="cn=username" />
              <property name="ldap.password" value="!password" />
              <property name="ldap.cache.session.enable" value="false"/>
              <property name="ldap.cache.realm.enable" value="false"/>
              <property name="ldap.cache.policy.enable" value="false"/>
              <property name="jaas.username.simple" value="true" />
              <jazn-web-app auth-method="SSO"/>
         </jazn>
    application-deployments directory version:
    It points to a principals.xml file and gives a generic definition for the jazn provider (specifies provider="LDAP" and a default-realm but no location attribute in the jazn tag).
    jazn section looks like this:
         <jazn provider="LDAP" default-realm="whidbey1">
              <jazn-web-app auth-method="SSO"/>
              <property name="jaas.username.simple" value="true" />
         </jazn>
    I assume the one defined in the +/applications/webappname/META-INF+ is the proper one since it has all the detailed OID connection information. However, are both needed? If so, why? If not, which one is being used and why would there be two of them?
    I've checked all the documentation and have found several references to it being installed in one or the other place but not both.
    Any help you can provide would be much appreciated.

    Hi,
    The difference between these files is this:
    The one in the applications/ tree is the one that comes packaged in your ear file. This is a way to package your deployment preferences. At deployment time, enterprise manager extracts this file to configure your deployment.
    The one in the application-deployments directory is the one that is actually in use.
    LDAP connection from OC4J containers is specified on the container level, because this is container-level security. This means that using the enterprise manager, you configure your container to connect to the LDAP (enterprise manager, tab administration, item Identity Management). In the orion-application.xml, you no longer need the details because they are stored on container level. So these are removed when deploying your application, leaving only what you see.
    The configuration parameters you specify can be added as container startup parameters using -Dparam=value.
    Regards,
    Jeroen van Veldhuizen

  • Can I unzip the .ipa file and edit the application.xml file

    I want to modify the below info to also have an additional string value of 2, which somewhere along the line tells something somewhere that the app can run on the ipad. Is there some info in the compiled application that will error out if I modify this document?
    <InfoAdditions>
    - <![CDATA[ <key>UIDeviceFamily</key><array><string>1</string></array> ]]>
    </InfoAdditions>
    into this
    <InfoAdditions>
    - <![CDATA[ <key>UIDeviceFamily</key><array><string>1</string><string>2</string></array> ]]>
    </InfoAdditions>

    you can change the file extension to zip, unzip it, find the application.xml file in one of the subdirectories, edit it, rezip the files, change the file extension to ipa and install.

  • Installing BDB XML and including it into a java application

    Hi there :)
    I'm new to BDB XML and I've got some questions about it :
    1/ The documentation says about BDB XML that it is based on BDB. Does it mean that I need to install the standard BDB first to use BDB XML ? (I'm pretty sure I don't have to but I would like a confirmation =))
    2/ I want to developp a web application which will use BDB XML. The documentation says I need to add some jars into my project to use it but do I need to install it on my computer (Windows XP) first ? (with the .msi file ?)
    3/ Where will the xml files be physically stored after I add them into the database ? (what is the default database folder on the hard disk ?)
    Thank you for you help :)
    Regards,
    Gary

    Hi Gary,
    1) You need to install only DB XML. BDB is bundled with DB XML, so you don't have to worry.
    2) Yes, you need to add two jars: db.jar and dbxml.jar. But these jars depend on native DB XML libraries, so you will have to install DB XML anyway: only jars wouldn't be sufficient. Moreover, I would recommend to install DB XML from sources providing the --enable-java+ flag to the buildall.sh script
    3) All XML files will be stored in a container or containers (depending on how many of those you will decide to utilize in your application). It is up to you where you are going to reside DB XML environment/containers -- DB XML is quite low-level XML-database.
    Hope this helps,
    Vyacheslav

  • OC4J orion-application.xml - elements and attributes

    Hi. i read in oracle docs sentense like this: "Each property maps to an element attribute in the orion-application.xml descriptor." These properties are from deployment plan and i need to know what is the name of the element in orion-application.xml wich is mapped to webSiteBinding property (from deployment plan).

    I just did a quick test of this, and it seems to work for me.
    I used the following XML:
    <?xml version="1.0" encoding="iso-8859-1"?>
    <Employees xmlns="
    http://www.foo.com/Employees">
    <Employee Id="001">
    <LastName>Davis</LastName>
    <FirstName>Kirk</FirstName>
    </Employee>
    <Employee Id="002">
    <LastName></LastName>
    <FirstName>James</FirstName>
    </Employee>
    <Employee Id="003">
    <FirstName>Anthony</FirstName>
    </Employee>
    <Employee>
    </Employee>
    </Employees>
    With the XPath "/Employees/Employee" I got rows in the data
    set and things displayed fine in my page. Changing it to
    "/employees/employee" caused the data set to have no rows which I
    would expect since things should be case sensitive.
    Can you provide me with some sample XML and XPath that
    doesn't work?
    Thanks!
    --== Kin ==--

  • Urgent : Generation of file "application".xml fails and deploys aborted

    Hi,
    I recently took over an application (called RDAS) and downloaded if from DTR. But this didnt work well (all sources files have been downloaded, but lots of models and custom controllers were missing in the webdynpro perspective). This has been fixed well by modifying manually file Rdas.wdcomponent
    I just found out that in my component, a window and it's view are also missing (no links with any other windows or views of my application). This window just contains a view and acts as a popup (no navigation link or so with the rest of my component). I modified files Rdas.wdcomponent and RdasInterface.wdcomponentinterface and it builds well. No errors. I can now find my missing window and view in the webdynpro perspective.
    But since then I can not deploy anymore. I get the following errors:
    Web Dynpro Generation: com.sap.tc.webdynpro.repository.RepositoryRuntimeException: Failed to parse XML document containing VMO=com.alstom.power.rdas.wd.Rdas., D:/Workspace_JDI/0/DCs/power.alstom.com/rdaswd/_comp/gen_wdp/configuration/Applications/com.alstom.power.rdas.wd.Rdas/Rdas.xml
    And when I check in the generated files, the xml file associated to the application is not genetared anymore.
    Any ideas?
    Points rewarded for any help
    Thanks
    Yann

    Hi,
    Finally I figured out what was wrong.
    An entry was missing in file RDAS.wdcomponent (views have to be inserted in the views list and also in the components list).
    Do I deserve points?
    I think so

Maybe you are looking for