Deployment of Portal Standalone Application DC

Hi All,
I've created a DC of type 'Portal Application Standalone'. I also created a DC of type 'External Library' for use by the former DC. Upon building the former DC, I see that the sda file is created with the par file within it.
Under Development configuration tab in NWDS, I checked in both the above-mentioned DCs and activated them.Shouldn't this have deployed the DC to the Dev server? I've verified that there are runtime systems configured in NWDI with deploy option checked.
I tried to locate my application from System Administration ->Support>Portal Runtime>Browse Deployment/Admin Console etc..but don't see it there.
Do I have to release the activity for it to deploy?
Also, I tried to right click and deploy the DC myself from the Dev Config perspective in NWDS. but i got an error saying 'sdm host is empty'. I've already set the host under Windows>Preferences>SAP EP. The port i set here is not the sdm port, but 500xx where xx is the instance no.
I was able to create a portal app and deploy it using the 'deploy par' option with the above settings. Am I missing any additional config  configuration for DC deployment (am sure we hv to set the sdm port etc somewhere).
I'll appreciate if someone can help guide me on this.
Thanks!

Hi,
To use NWDI,
Check the below paramaters configured or not?
1) Window -> Preferences -> Java Development Infrastructure -> Development Configurations
enter the URL of your NWDI.
2) Window -> Preferences -> sap Enterprise Portal -> sap j2ee engine  and then enter message server name and port details
To deploy the developed dc into nwdi , you need to checkout and release the activity.
Koti Reddy

Similar Messages

  • Desesperatly trying to deploy a simple standalone application...

    Hi,
    i've been trying to deploy a simple application but i have a problem when using the command line "java -jar myarchive.jar"...i have a "java.lang.NoClassDefFoundError" !
    I make the archive via Jdev, by using "Making a simple Jar archive", i let the default arguments but i don't really know what to put in the field "Main class".
    I only have a class which is in a package :
    My class is in c:\jdev\mywork\myproject\classes\mypackage1
    I try different things in the "Main class" field :
    1) c:\jdev\mywork\myproject\classes\mypackage\myclass
    2)c:\jdev\mywork\myproject\classes\mypackage.myclass
    but it does not work...
    thanks you for helping me...

    If you've taken the defaults and have something like Class1.java in the package mypackage1. Then the value you put in the Main Class field of the deployment profile is: (without the quotes) "mypackage1.Class1"
    Note:
    The case of the package and class names must be correct
    There is no .class extension mentioned

  • Deploying standalone applications

    I'm a beginning programmer interested in learning how to deploy client-side standalone applications in Java. I'm using the Metrowerks CodeWarrior IDE, and I am writing some simple GUI applications. Under 'Java Output', my IDE lets me select either Jar file or application. When 'application' is selected, two files are generated: a Windows application (JavaApplication.exe) that transparently runs the program, and JavaApplication.zip (which presumably holds the .class files). Would it be possible to FTP these files to a server for others to download and run (under Windows only, of course)? Or is it better to simply upload the .jar file? On a related note, I don't understand why the "executable" .jar files output in my projects can't run when I double click on them, even though I have the JVM on my computer.
    I realize that any compiling destroys the "write once, run anywhere" capability that is Java's hallmark, but for now my main concern is just to get some practice deploying my programs.
    any help with these questions would be greatly appreciated,
    thanks,
    Eric

    Good help you if you are using Metrowerks, one of the CRAPPIEST IDE every. Anyway, all it is doing is putting a wrapper around your main Java app class when you create a exe. As for download, either will do, put both up and let user decide. The jar is good for all, were the exe is OK, as many window user will find it more familiar to deal with. As to the VM problem, the solution is here on the forum, go search, I gave you 2 of the 3 answers, do now you can also get some search practice to go with your deploy practice.

  • Avitek Sample Portal fails to deploy to any Standalone WLS

    Hi
    The Avitek Sample Portal is a custom portal built using Oracle WebCenter 11g Release 1 and WebCenter Web 2.0 Services. to find out more see link below
    http://www.oracle.com/technetwork/middleware/webcenter/avitek-sample-portal-086834.html
    I have successfully been able to deploy the Avitek Sample Portal to a JDeveloper 11.1.1.3.0 Integrated WebLogic Server follow the suggestions/workaround given in the thread below:
    Error Avitek sample deployment
    However the sample application fails to be deployed to any standalone Weblogic server. I have tried to deploy it to an Oracle Webcenter 11.1.1.3.0 instance sitting on standalone WebLogic Server 10.3.3.0 container.
    I have tried to deploy it using both WLST and from JDeveloper 11.1.1.3.0. either way the error is the same.
    the stack trace is below
    [2010-12-05T19:55:33.125+00:00] [DefaultServer] [ERROR] [] [oracle.adf.share.config.ADFMDSConfig] [tid: [STANDBY].ExecuteThread: '5' for queue: 'weblogic.kernel.Default (self-tuning)'] [ecid: 0000Ims6aLaFk3WFLzVK8A1CyymG000005,0] [APP: application1#V2.0] [dcid: a853d41d80ebc7cd:35a3bb73:12cb8147939:-8000-000000000000003b] MDSConfigurationException encountered in parseADFConfigurationMDS-00170: The MDS instance is not usable because metadata deployment failed with status "ERROR". [[
    MDS-01325: unable to load type definition "<classpath>/oracle/webcenter/avitek/sitemodel/node.xsd<classpath>" oracle.mds.config.MDSConfigurationException: MDS-00170: The MDS instance is not usable because metadata deployment failed with status "ERROR".
    MDS-01325: unable to load type definition "<classpath>/oracle/webcenter/avitek/sitemodel/node.xsd<classpath>"
         at oracle.mds.core.MDSInstance.checkMDSDeployStatus(MDSInstance.java:1005)
         at oracle.mds.core.MDSInstance.<init>(MDSInstance.java:1695)
         at oracle.mds.core.MDSInstance.<init>(MDSInstance.java:1667)
         at oracle.mds.core.MDSInstance.createMDSInstanceWithCustomizedConfig(MDSInstance.java:1179)
         at oracle.mds.core.MDSInstance.getOrCreateInstance(MDSInstance.java:571)
         at oracle.adf.share.config.ADFMDSConfig.parseADFConfiguration(ADFMDSConfig.java:137)
         at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
         at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:39)
         at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25)
         at java.lang.reflect.Method.invoke(Method.java:597)
         at oracle.adf.share.config.ADFConfigImpl.getResultFromComponent(ADFConfigImpl.java:443)
         at oracle.adf.share.config.ADFConfigImpl.getConfigObject(ADFConfigImpl.java:508)
         at oracle.adf.share.config.ADFConfigImpl.getConfigObject(ADFConfigImpl.java:491)
         at oracle.adf.share.config.ADFConfigImpl.getMDSInstance(ADFConfigImpl.java:547)
         at oracle.adf.share.config.ADFConfigImpl.getMDSInstance(ADFConfigImpl.java:542)
         at oracle.adf.share.config.ADFContextMDSConfigHelperImpl.getMDSInstance(ADFContextMDSConfigHelperImpl.java:274)
         at oracle.adf.share.ADFContext.getMDSInstanceAsObject(ADFContext.java:1210)
         at oracle.adf.share.http.ServletADFContext.initialize(ServletADFContext.java:420)
         at oracle.adf.share.http.ServletADFContext.initThreadContext(ServletADFContext.java:352)
         at oracle.adf.share.http.ServletADFContext.initThreadContextIfNeeded(ServletADFContext.java:285)
         at oracle.webcenter.collab.forum.internal.view.ForumGatewayInitializer.contextDestroyed(ForumGatewayInitializer.java:103)
         at weblogic.servlet.internal.EventsManager$FireContextListenerAction.run(EventsManager.java:482)
         at weblogic.security.acl.internal.AuthenticatedSubject.doAs(AuthenticatedSubject.java:321)
         at weblogic.security.service.SecurityManager.runAs(SecurityManager.java:121)
         at weblogic.servlet.internal.EventsManager.notifyContextDestroyedEvent(EventsManager.java:200)
         at weblogic.servlet.internal.WebAppServletContext.destroy(WebAppServletContext.java:3197)
         at weblogic.servlet.internal.ServletContextManager.destroyContext(ServletContextManager.java:241)
         at weblogic.servlet.internal.HttpServer.unloadWebApp(HttpServer.java:461)
         at weblogic.servlet.internal.WebAppModule.destroyContexts(WebAppModule.java:1540)
         at weblogic.servlet.internal.WebAppModule.deactivate(WebAppModule.java:513)
         at weblogic.application.internal.flow.ModuleStateDriver$2.previous(ModuleStateDriver.java:389)
         at weblogic.application.utils.StateMachineDriver.previousState(StateMachineDriver.java:167)
         at weblogic.application.utils.StateMachineDriver.previousState(StateMachineDriver.java:160)
         at weblogic.application.internal.flow.ModuleStateDriver.deactivate(ModuleStateDriver.java:141)
         at weblogic.application.internal.flow.ScopedModuleDriver.deactivate(ScopedModuleDriver.java:207)
         at weblogic.application.internal.flow.ModuleListenerInvoker.deactivate(ModuleListenerInvoker.java:261)
         at weblogic.application.internal.flow.DeploymentCallbackFlow$2.previous(DeploymentCallbackFlow.java:538)
         at weblogic.application.utils.StateMachineDriver.previousState(StateMachineDriver.java:167)
         at weblogic.application.utils.StateMachineDriver.previousState(StateMachineDriver.java:160)
         at weblogic.application.internal.flow.DeploymentCallbackFlow.deactivate(DeploymentCallbackFlow.java:182)
         at weblogic.application.internal.flow.DeploymentCallbackFlow.deactivate(DeploymentCallbackFlow.java:175)
         at weblogic.application.internal.BaseDeployment$2.previous(BaseDeployment.java:1281)
         at weblogic.application.utils.StateMachineDriver.previousState(StateMachineDriver.java:167)
         at weblogic.application.utils.StateMachineDriver.nextState(StateMachineDriver.java:50)
         at weblogic.application.internal.BaseDeployment.activate(BaseDeployment.java:409)
         at weblogic.application.internal.EarDeployment.activate(EarDeployment.java:58)
         at weblogic.application.internal.DeploymentStateChecker.activate(DeploymentStateChecker.java:161)
         at weblogic.deploy.internal.targetserver.AppContainerInvoker.activate(AppContainerInvoker.java:79)
         at weblogic.deploy.internal.targetserver.operations.AbstractOperation.activate(AbstractOperation.java:569)
         at weblogic.deploy.internal.targetserver.operations.ActivateOperation.activateDeployment(ActivateOperation.java:150)
         at weblogic.deploy.internal.targetserver.operations.ActivateOperation.doCommit(ActivateOperation.java:116)
         at weblogic.deploy.internal.targetserver.operations.AbstractOperation.commit(AbstractOperation.java:323)
         at weblogic.deploy.internal.targetserver.DeploymentManager.handleDeploymentCommit(DeploymentManager.java:844)
         at weblogic.deploy.internal.targetserver.DeploymentManager.activateDeploymentList(DeploymentManager.java:1253)
         at weblogic.deploy.internal.targetserver.DeploymentManager.handleCommit(DeploymentManager.java:440)
         at weblogic.deploy.internal.targetserver.DeploymentServiceDispatcher.commit(DeploymentServiceDispatcher.java:164)
         at weblogic.deploy.service.internal.targetserver.DeploymentReceiverCallbackDeliverer.doCommitCallback(DeploymentReceiverCallbackDeliverer.java:195)
         at weblogic.deploy.service.internal.targetserver.DeploymentReceiverCallbackDeliverer.access$100(DeploymentReceiverCallbackDeliverer.java:13)
         at weblogic.deploy.service.internal.targetserver.DeploymentReceiverCallbackDeliverer$2.run(DeploymentReceiverCallbackDeliverer.java:69)
         at weblogic.work.SelfTuningWorkManagerImpl$WorkAdapterImpl.run(SelfTuningWorkManagerImpl.java:528)
         at weblogic.work.ExecuteThread.execute(ExecuteThread.java:201)
         at weblogic.work.ExecuteThread.run(ExecuteThread.java:173)
    Caused by: oracle.mds.config.MDSConfigurationException: MDS-01325: unable to load type definition "<classpath>/oracle/webcenter/avitek/sitemodel/node.xsd<classpath>"
         at oracle.mds.internal.config.DefaultTypeDefURLResolver.resolve(DefaultTypeDefURLResolver.java:69)
         at oracle.mds.internal.config.ConfigurationUtils.getURLs(ConfigurationUtils.java:349)
         at oracle.mds.config.TypeConfig.loadFromBean(TypeConfig.java:428)
         at oracle.mds.config.TypeConfig.<init>(TypeConfig.java:214)
         at oracle.mds.internal.lcm.MDSLCMManager.getTypeConfig(MDSLCMManager.java:2114)
         at oracle.mds.internal.lcm.deploy.DeployManager.deploy(DeployManager.java:419)
         at oracle.mds.internal.lcm.deploy.DeployManager.startDeployment(DeployManager.java:168)
         at oracle.mds.internal.lcm.MDSLifecycleListenerImpl.start(MDSLifecycleListenerImpl.java:160)
         at oracle.mds.lcm.weblogic.WLLifecycleListener.preStart(WLLifecycleListener.java:188)
         at weblogic.application.internal.flow.BaseLifecycleFlow$PreStartAction.run(BaseLifecycleFlow.java:282)
         at weblogic.security.acl.internal.AuthenticatedSubject.doAs(AuthenticatedSubject.java:321)
         at weblogic.security.service.SecurityManager.runAs(SecurityManager.java:121)
         at weblogic.application.internal.flow.BaseLifecycleFlow$LifecycleListenerAction.invoke(BaseLifecycleFlow.java:199)
         at weblogic.application.internal.flow.BaseLifecycleFlow.preStart(BaseLifecycleFlow.java:62)
         at weblogic.application.internal.flow.HeadLifecycleFlow.prepare(HeadLifecycleFlow.java:284)
         at weblogic.application.internal.BaseDeployment$1.next(BaseDeployment.java:1223)
         at weblogic.application.utils.StateMachineDriver.nextState(StateMachineDriver.java:41)
         at weblogic.application.internal.BaseDeployment.prepare(BaseDeployment.java:367)
         at weblogic.application.internal.EarDeployment.prepare(EarDeployment.java:58)
         at weblogic.application.internal.DeploymentStateChecker.prepare(DeploymentStateChecker.java:154)
         at weblogic.deploy.internal.targetserver.AppContainerInvoker.prepare(AppContainerInvoker.java:60)
         at weblogic.deploy.internal.targetserver.operations.ActivateOperation.createAndPrepareContainer(ActivateOperation.java:208)
         at weblogic.deploy.internal.targetserver.operations.ActivateOperation.doPrepare(ActivateOperation.java:98)
         at weblogic.deploy.internal.targetserver.operations.AbstractOperation.prepare(AbstractOperation.java:217)
         at weblogic.deploy.internal.targetserver.DeploymentManager.handleDeploymentPrepare(DeploymentManager.java:749)
         at weblogic.deploy.internal.targetserver.DeploymentManager.prepareDeploymentList(DeploymentManager.java:1216)
         at weblogic.deploy.internal.targetserver.DeploymentManager.handlePrepare(DeploymentManager.java:250)
         at weblogic.deploy.internal.targetserver.DeploymentServiceDispatcher.prepare(DeploymentServiceDispatcher.java:160)
         at weblogic.deploy.service.internal.targetserver.DeploymentReceiverCallbackDeliverer.doPrepareCallback(DeploymentReceiverCallbackDeliverer.java:171)
         at weblogic.deploy.service.internal.targetserver.DeploymentReceiverCallbackDeliverer.access$000(DeploymentReceiverCallbackDeliverer.java:13)
         at weblogic.deploy.service.internal.targetserver.DeploymentReceiverCallbackDeliverer$1.run(DeploymentReceiverCallbackDeliverer.java:47)
         ... 3 more
    Any help would be much appreciated.
    Edited by: user9177929 on Dec 5, 2010 12:20 PM
    Edited by: user9177929 on Dec 5, 2010 12:30 PM

    Rajat,
       Thanks for replying.
       Unfortunately, the problem persists after we restart the SAP Services on both the DTR and CBS servers.  Clearing out memory, etc... doesnt seem to do the trick anymore.  Oncec the CBS comes back up, and we initiate a build on the DC, changes still are not reflected in the portal runtime.
       Are there any cache settings on the Portal itself that handle caching of JSPs, settings that handle when JSPs get recompiled, or any other settings you can think of?
    Thanks.
    ~Greg

  • How to deploy the custom java application for self regaistration in portal?

    hi,
    I have created a custom java application in NWDS for Self Registration of new users.I am working on EP 7.02 and the standard self registration application is a Web dynpro java application.
    How can i deploy my custom java application built as a par file in place of the Web dynpro java application?
    Thanks,

    Hi Amarys,
    If you have developed the PAR file in NWDS then you can deploy the PAR in the server with NWDS ( [Check Required Settings |NWDS 7.0 does not deploy PAR;) or in server directly (system administrator > support >> portal runtime >> administration console)
    Best Regards
    Arun Jaiswal

  • How to deploy the  webdynpro ABAP application  in Portal

    Hi,
        Can someone provide me, all the steps involved to deploy the  webdynpro ABAP application  in Portal.
    Thanks,
    Kundan

    Hi Kundan,
    First create a WD abap component and then you have to integrate in the portal.
    Refer this article [Integrate a Web Dynpro Application into the SAP Enterprise Portal|http://www.sdn.sap.com/irj/scn/index?rid=/library/uuid/7bfea990-0201-0010-44a7-84a74971b795&overridelayout=true].
    I hope it helps.
    Regards
    Arjun
    Edited by: Arjun Thakur on Sep 22, 2009 2:20 PM

  • Creating a user in EP using a java standalone application

    Hi,
      I am trying to create a java application to create a user in Enterprise Portal.
      I am getting the following error:
    com.sap.security.api.UMRuntimeException: Cannot lookup ManageConnectionFactory "jdbc/sapep". Possible reasons: 1) The connector in which ManagedConnectionFactory "jdbc/sapep" is defined is not deployed or not started, 2) Cannot deserialize object due to a naming exception.
    ume.db.connection_pool_type=jdbc/sapep
    ume.db.connection_pool.j2ee.xatransactions_used=false
    ume.db.connection_pool.j2ee.is_unicode=true
    ume.db.connection_pool.j2ee.oracle_native_driver_used=false: Cannot lookup ManageConnectionFactory "jdbc/sapep". Possible reasons: 1) The connector in which ManagedConnectionFactory "jdbc/sapep" is defined is not deployed or not started, 2) Cannot deserialize object due to a naming exception.
      Q1. Is it possible to create user from java standalone application.
      Q2. Pls. help to resolve the error or give any sample code if you have
      Thanks in advance.
    Regards,
      Pratik

    Hi Ravi,
    How about something like this:
    IUserMaint user = UMFactory.getUserFactory().newUser("myNewUser");
    user.setFirstName("1st Name");
    user.setLastName("2nd Name");
    user.setEmail("[email protected]");
    user.save();
    user.commit();
    IUserAccount uacc = UMFactory.getUserAccountFactory().newUserAccount("myNewUser", user.getUniqueID());
    uacc.setPassword("initial");
    uacc.setPasswordChangeRequired(false);
    uacc.save();
    uacc.commit();
    Hope this helps.
    Daniel

  • Deployment of JavaFX Web application on client machine(Windows OS.)

    Problem Statement:
    Deployment of JavaFX Web application on client machine(Windows OS.)
    Error: unable to load the native libarary(JNI Windows dll) i.e. throws java.lang.UnsatisfiedLinkError exception.
    Problem Description:
    I have create the JavaFX application which have dependency on Native library written in Java Native Interface(JNI).
    When the application is deployed on Apache 6.0 Tomcat Server(Copied .html file *.jnlp file and .jar file) and when client machine hit the html page in internet explorer version 8.0 its throws the following error(java.lang.UnsatisfiedLinkError: no JNIHelloWorld in java.library.path)
    Note:
    I have created the jar file which have my "JNIHelloWorld' native library dll in root directory. I have signed the jar with same signature which i have used for signing for my application Jar file.
    I have mentioned the native library jar in JNLP file resource keyword as follows:
    <resources os=Windows>
    <nativelib href="JNIHelloWorld.jar" download="eager" />
    </resources>
    The complete jnlp file content is in "JavaFXApplication.jnlp file:" section below.
    The description of error is as follows:
    Match: beginTraversal
    Match: digest selected JREDesc: JREDesc[version 1.6+, heap=-1--1, args=null, href=http://java.sun.com/products/autodl/j2se, sel=false, null, null], JREInfo: JREInfo for index 0:
    platform is: 1.7
    product is: 1.7.0_07
    location is: http://java.sun.com/products/autodl/j2se
    path is: C:\Program Files\Java\jre7\bin\javaw.exe
    args is: null
    native platform is: Windows, x86 [ x86, 32bit ]
    JavaFX runtime is: JavaFX 2.2.1 found at C:\Program Files\Java\jre7\
    enabled is: true
    registered is: true
    system is: true
         Match: ignoring maxHeap: -1
         Match: ignoring InitHeap: -1
         Match: digesting vmargs: null
         Match: digested vmargs: [JVMParameters: isSecure: true, args: ]
         Match: JVM args after accumulation: [JVMParameters: isSecure: true, args: ]
         Match: digest LaunchDesc: http://10.187.143.68:8282/KPIT/JavaFXApplication20.jnlp
         Match: digest properties: []
         Match: JVM args: [JVMParameters: isSecure: true, args: ]
         Match: endTraversal ..
         Match: JVM args final:
         Match: Running JREInfo Version match: 1.7.0.07 == 1.7.0.07
         *Match: Running JVM args match: have:<> satisfy want:<>*
    *java.lang.UnsatisfiedLinkError: no JNIHelloWorld in java.library.path*
    *     at java.lang.ClassLoader.loadLibrary(Unknown Source)*
    *     at java.lang.Runtime.loadLibrary0(Unknown Source)*
    *     at java.lang.System.loadLibrary(Unknown Source)*     at javafxapplication20.JavaFXApplication20.<clinit>(JavaFXApplication20.java:41)
         at sun.reflect.NativeConstructorAccessorImpl.newInstance0(Native Method)
         at sun.reflect.NativeConstructorAccessorImpl.newInstance(Unknown Source)
         at sun.reflect.DelegatingConstructorAccessorImpl.newInstance(Unknown Source)
         at java.lang.reflect.Constructor.newInstance(Unknown Source)
         at java.lang.Class.newInstance0(Unknown Source)
         at java.lang.Class.newInstance(Unknown Source)
         at com.sun.javafx.applet.FXApplet2.init(FXApplet2.java:63)
         at com.sun.deploy.uitoolkit.impl.fx.FXApplet2Adapter.init(FXApplet2Adapter.java:207)
         at sun.plugin2.applet.Plugin2Manager$AppletExecutionRunnable.run(Unknown Source)
         at java.lang.Thread.run(Unknown Source)
    Java Plug-in 10.7.2.11
    Using JRE version 1.7.0_07-b11 Java HotSpot(TM) Client VM
    User home directory = C:\Users\io839
    Please find my native library code and JavaFX application code:
    Native library JNI Code:
    JavaFXApplication.java:
    JNIEXPORT jstring JNICALL Java_javafxapplication_SampleController_printString(JNIEnv *env, jobject envObject)
         string str = "hello JNI";
         jstring jniStr = env->NewStringUTF(str.c_str());
         return jniStr;
    JavaFX Application code:
    JavaFXApplication.java:
    package javafxapplication;
    import javafx.application.Application;
    import javafx.fxml.FXMLLoader;
    import javafx.scene.Parent;
    import javafx.scene.Scene;
    import javafx.stage.Stage;
    public class JavaFXApplication extends Application {
    @Override
    public void start(Stage stage) throws Exception {
    Parent root = FXMLLoader.load(getClass().getResource("Sample.fxml"));
    Scene scene = new Scene(root);
    stage.setScene(scene);
    stage.show();
    * The main() method is ignored in correctly deployed JavaFX application.
    * main() serves only as fallback in case the application can not be
    * launched through deployment artifacts, e.g., in IDEs with limited FX
    * support. NetBeans ignores main().
    * @param args the command line arguments
    public static void main(String[] args) {
    launch(args);
    static{
    System.loadLibrary("JNIHelloWorld");
    SampleController.java file:
    package javafxapplication;
    import java.net.URL;
    import java.util.ResourceBundle;
    import javafx.event.ActionEvent;
    import javafx.fxml.FXML;
    import javafx.fxml.Initializable;
    import javafx.scene.control.Label;
    public class SampleController implements Initializable {
    @FXML
    private Label label;
    private native String printString();
    @FXML
    private void handleButtonAction(ActionEvent event) {
    System.out.println("You clicked me!");
    String str = printString();
    label.setText(str);
    @Override
    public void initialize(URL url, ResourceBundle rb) {
    // TODO
    //String str = printString();
    JavaFXApplication.jnlp file:
    <?xml version="1.0" encoding="utf-8"?>
    <jnlp spec="1.0" xmlns:jfx="http://javafx.com" href="JavaFXApplication.jnlp">
    <information>
    <title>JavaFXApplication20</title>
    <vendor>io839</vendor>
    <description>Sample JavaFX 2.0 application.</description>
    <offline-allowed/>
    </information>
    <resources>
    <jfx:javafx-runtime version="2.2+" href="http://javadl.sun.com/webapps/download/GetFile/javafx-latest/windows-i586/javafx2.jnlp"/>
    </resources>
    <resources>
    <j2se version="1.6+" href="http://java.sun.com/products/autodl/j2se"/>
    <jar href="JavaFXApplication.jar" size="20918" download="eager" />
    </resources>
    <resources os=Windows>
    <nativelib href="JNIHelloWorld.jar" download="eager" />
    </resources>
    <security>
    <all-permissions/>
    </security>
    <applet-desc width="800" height="600" main-class="com.javafx.main.NoJavaFXFallback" name="JavaFXApplication" >
    <param name="requiredFXVersion" value="2.2+"/>
    </applet-desc>
    <jfx:javafx-desc width="800" height="600" main-class="javafxapplication.JavaFXApplication" name="JavaFXApplication" />
    <update check="always"/>
    </jnlp>

    No problem.
    Make sure your resources are set at the proper location. Could be that tje jni.jar is under a 'lib' folder?
    Normally you don't have to worry about deployment a lot if you are using like Netbeans 7.2 or higher.
    When you press 'Clean and build' it creates your deployed files in the 'dist' folder.
    You can change specification by adapting the build.xml file.
    Of course lot of different possibilities are available for deployment!
    You can find lot of info here:
    [http://docs.oracle.com/javafx/2/deployment/jfxpub-deployment.htm|http://docs.oracle.com/javafx/2/deployment/jfxpub-deployment.htm]
    Important to know is if you want to work with
    - a standalone application (self-contained or not)
    - with webstart
    - or with applets
    (In my case I'm using webstart, but also Self-Contained Application Packaging (jre is also installed!)

  • PCUI GP Deployment ERROR on Standalone Java Stack

    We are in the midst of deploying the PCUI archive via SDM (also tried JSPM)
    Got the following error
    Aborted: development component 'pcui_gp/isr/cfg'/'sap.com'/'MAIN_ERP05VAL_C'/'2515722'/'0', grouped by software component 'SAPPCUI_GP'/'sap.com'/'MAIN_ERP05VAL_C'/'1000.600.0.13.0.20080516101947''/'0':Caught exception during application deployment from SAP J2EE Engine's deploy service:java.rmi.RemoteException: Error occurred while deploying ear file ./temp/deploy/work/deploying/pcui_gp_isr_cfg.ear. Reason: None of the available containers recognized the components of application sap.com/pcui_gpisrcfg; it is not possible to make deploy. (message ID: com.sap.sdm.serverext.servertype.inqmy.extern.EngineApplOnlineDeployerImpl.performAction(DeploymentActionTypes).REMEXC)
    Deployment of pcui_gp/isr/cfg finished with Error (Duration 12495 ms)
    Starting Deployment of SAPPCUI_GP
    Aborted: software component 'SAPPCUI_GP'/'sap.com'/'MAIN_ERP05VAL_C'/'1000.600.0.13.0.20080516101947''/'0':Failed deployment of SDAs:development component 'pcui_gp/isr/cfg'/'sap.com'/'MAIN_ERP05VAL_C'/'2515722'/'0' : abortedPlease, look at error logs above for more information!
    Deployment of SAPPCUI_GP finished with Error (Duration 6525 ms)
    PCUI Patch level is SP13 (highest). and Java stack is 15
    Even tried starting from PCUI SP1
    This is a Standalone Java Stack. Not Add-In
    HAs anyone had experience deploying PCUI on Standalone Java Stack.
    Any help/pointers appreciated.

    Hi ,
    Please check :
    https://wiki.sdn.sap.com/wiki/display/WDJava/Clusterwideexception-FailedtodeployWebDynprocontentforapplication
    Regards,
    Nibu Antony
    Edited by: Nibu Antony on Dec 13, 2010 2:52 PM

  • Servlets Vs Standalone Application?

    Servlets Vs Standalone Application?
    I know this is an extremely broad subject, but put very simply can anyone give me a basic list of pros & cons in writing an application on a network with either of the two mentioned technologies?!?
    We will need security, efficiency, speed etc as well as an intuitive interface!!
    Not much to ask i know!
    cheers now!

    Servlets:
    +Easier to deploy
    +Upgrading easier (Just upgrade one instance)
    -Interface somewhat limited
    +Security is centralized
    Standalone
    -You have to deploy to every client
    -Upgrading is cumbersome, especially when the new version is not backwards compatible, and you need a big bang upgrade.
    +Highly interactive interfaces (Swing)
    -Security can be a problem (e.g. clients can be forged), when it is not centralized.
    The speed of the application is dependent on the kind of application. It depends on the complexity of the UI, whether data is on a central server or local, etc.
    --Arnout                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                               

  • Is webdynpro a standalone application

    Hi SDN's,
    Can we run a webdynpro allication as a standalone application?
    If so how to use this application as a stand alone application
    Thanks,
    Krishnam Raju.

    Hi,
    See the link below.It may help you in the understanding of
    web dynpro.
    https://www.sdn.sap.com/irj/sdn/go/portal/prtroot/docs/library/uuid/a048387a-0901-0010-13ac-87f9eb649381
    Hope this helps you.
    Regards,
    Sumangala

  • Deploying BEA Portal App in Managed Server problems....

    Hello,
    I have a BEA portal application (exploded EAR) that I want to deploy in a managed server. I first created a regular portal domain (8.1 SP4). I then created a managed server via the console. When I went to deploy my portal application (in the console), I received an error indicating that the application was a Split Development Directory and that I would have to run the wlpackage Ant task against the application first. I ran the wlpackage ant task and it seemingly worked.
    I then used the wldeploy Ant task to deploy it in the managed server but got an error indicating that it could not find a JNDI name from one of the data sources. I went back to the console and targeted/deployed all of the default Connection Pools & Data Sources to the managed server thinking that was the reason the deploy failed.
    When I ran the wldeploy again I got the following error:
    Module: content.jar Error: Exception activating module: EJBModule(content.jar, status=PREPARED)
    Unable to deploy EJB: ValueBean from content.jar
    java.sql.SQLException: javax.naming.NameNotFoundException: While trying to lookup 'portalFrameworkPool; contentDataSource;weblogic.jdbc.jts.commercialPool' didn't find subcontext 'portalFrameworkPool;contentDataSource;weblogic' Resolved ; remaining name 'portalFrameworkPool;contentDataSource;weblogic/jdbc/jts/commercialPool'
    Has anyone run into this? Am I not suppose to deploy a portal application in a managed server?
    Any help would be greatly appreciated.
    Thanks - Peter Len

    Problem solved.......
    After targeting all the data sources and poolers to the managed server, I restarted the main domain but did not restart the managed server. After restarting the managed server all was well.
    Thanks - Peter

  • How to create datasource for standalone application using JPA

    In the persistence.xml configuration file, we have data source got it from web server configuration file, and created by server like Jboss or tomcat.
    I just wonder how to create this same data source via Java stand-alone application?
    I have Java standalone application embedded Jetty server running with JPA module. Question is how to setup or create data source from my Java application just like web server; which called by persistence.xml?
    Thanks,

    Hello,
    Sharepoint deployment is completely different. I don't think you can deploy any solution as wizard in prod so you have to first identify what you want to deploy.
    If you just want to deploy only web application then backup/restore process is available in sharepoint. you can use STSADM or powershell to deploy your web app.
    http://technet.microsoft.com/en-us/library/ee748618%28v=office.14%29.aspx
    If there is any custom code or .NET code then create a WSP package and deploy it on prod. If you have multiple WSP's then create a batch file (as exe package) then run this package on prod.
    http://www.ironspeed.com/Designer/9.1.1/WebHelp/Part_VI/SharePoint_Solution_Package_WSP_Deployment.htm
    Let us know in case any doubt
    Hemendra:Yesterday is just a memory,Tomorrow we may never see
    Please remember to mark the replies as answers if they help and unmark them if they provide no help

  • Deploying Java stand alone application in Weblogic server

    Hi All,
    We have an java stand alone application which our client uses. Suddenly they came up with a requirement of using this application from web logic server.We have following directory structure for our application
    myapp
    - config -> contains all configuration files
    - logs -> contains log files
    - ssl -> ssl related files
    - samples ->contians stub's
    - myapp.jar
    How to deploy our standalone application in to weblogic server?.
    We tried putting whole myapp folder in WEB-INF folder , and from the servlet we are able to invoke an method in an class file( in myapp.jar say Test.getInstance()) but it couldnt find configuration files (in config folder ) and it is throwing an error. We have a class called Test in myapp.jar and when we call getInstance of the class it loads all config files - config file location is hardcoded as /config/myconfig.xml , and we are facing problem here because it couldnt find myconfig.xml.
    We also tried packaging whole myapp folder in to jar , but with that also we faced the same problem
    Please let us know are we proceeding in the right way and how to deploy our application in weblogic server.We dont prefer making changes to our code at this point of time.
    Any info on this will be very helpful to us.
    Regards,
    Suresh

    Hi René van Wijk,
    Thanks for quick reply. Link you mentioned gave a basic idea of application structure , but still i couldnt get deployment process.
    Am very much new to weblogic.Can you please let me know how to deploy our standalone application in to weblogic, with out making any changes to the code.
    Below is folder structure of my java stand alone application *( not webapplication)*
    myapp
    - config -> contains all configuration files , for ex:- myconfig.xml
    - logs -> contains log files
    - ssl -> ssl related files
    - samples ->contians stub's
    - myapp.jar
    We have logic to load configuration file (config/myconfig.xml) , in an class and we are not allowed to make any changes to this code, so we cant use Thread.currentThread().getContextClassLoader().getResource(...) .
    Regards,
    Suresh

  • Error Deploying Sample Portal from Development Guide

    I am going through creating a New Portal from WebLogic Portal 7 Development
    Guide and I am running into the following problem.
    After completing Step 2: Create the New Portal, when I try to Hot Deploy the
    application, I get the following error.
    Hot deploy failed with the following message:
    Unable to add module: NewPortalWebApp to application descriptor for:
    portalApp.
    The log has the following information..
    Adding file:
    C:\bea\user_projects\myNewdomain\beaApps\portalApp-project\application-sync\
    portlets\Portlet1.portlet to sync list.
    Adding file:
    C:\bea\user_projects\myNewdomain\beaApps\portalApp-project\application-sync\
    webapps\PortalWebApp\tools.wf to sync list.
    Adding file:
    C:\bea\user_projects\myNewdomain\beaApps\portalApp-project\application-sync\
    webapps\PortalWebApp\webflow-extensions.wfx to sync list.
    Adding file:
    C:\bea\user_projects\myNewdomain\beaApps\portalApp-project\application-sync\
    webapps\PortalWebApp\user_account.wf to sync list.
    Adding file:
    C:\bea\user_projects\myNewdomain\beaApps\portalApp-project\application-sync\
    webapps\PortalWebApp\portal.wf to sync list.
    Adding file:
    C:\bea\user_projects\myNewdomain\beaApps\portalApp-project\application-sync\
    webapps\PortalWebApp\security.wf to sync list.
    Adding file:
    C:\bea\user_projects\myNewdomain\beaApps\portalApp-project\application-sync\
    webapps\PortalWebApp\NewPortal.portal to sync list.
    Attempting sync...
    Sync complete.
    Searching for portalApp application descriptor...
    Found it.
    Error - please check log for details.

    That's great, Mike, you're welcome. I'm glad it's working for you. Thanks for letting me know.
    -Scott
    Mike Friesen wrote:
    I'm sorry you were right.. I tried it and everything works... thanks..
    Mike
    "Scott Ellis" <[email protected]> wrote in message
    news:[email protected]...
    Hi Mike,
    I hear what you are saying and I believe you. But the error you describedis the known issue related to Internet access
    (down to the exact line numbers in the stack trace). Is it possible yourconnection was down last time you attempted
    hot-deploy?
    If you are sure your Internet connection is up, I would recommend tryinghot-deploy again. If it still does not work,
    something very strange is going on. At that point I would recommendtrying the workaround anyway or escalating the issue
    to BEA Support.
    Now my curiosity is piqued so I hope you'll let me know either way.
    Best Regards,
    Scott Ellis
    BEA Systems
    Mike Friesen wrote:
    yes..
    "Scott Ellis" <[email protected]> wrote in message
    news:[email protected]...
    Can you please try something for me? Paste the following URL into abrowser:
    http://java.sun.com/dtd/application_1_3.dtd
    Does it come up?
    Thanks,
    Scott
    Mike Friesen wrote:
    Actually, my computer does have internet access, so I don't think that
    is
    the problem.
    Mike
    "Scott Ellis" <[email protected]> wrote in message
    news:[email protected]...
    Hi Mike,
    I would bet that you are working on a machine that doesn't have
    Internet
    access, correct?
    The problem is that the EBCC is trying and failing to access the J2EEapplication descriptor
    dtd from Sun's website.
    If you can't get Internet access, here is the workaround:
    - save the attached file to your harddrive (just save it to c:\)
    - edit the application.xml file for your project as follows:
    - first copy the entire DOCTYPE declaration and save it somewhere
    in
    a
    separate text file (in case want to revert back to it later)
    - edit the DOCTYPE declaration so that it looks like this:
    <!DOCTYPE application PUBLIC '-//Sun Microsystems, Inc.//DTD J2EEApplication 1.3//EN' 'file:///application_1_3.dtd'>
    ( notice that the java.sun.com web address is replaced with the URI
    to
    the file on your harddrive)
    - save your changes and hotdeploy will work with or without Internetaccess
    Thanks,
    Scott Ellis
    BEA Systems
    Mike Friesen wrote:
    I am going through creating a New Portal from WebLogic Portal 7
    Development
    Guide and I am running into the following problem.
    After completing Step 2: Create the New Portal, when I try to Hot
    Deploy
    the
    application, I get the following error.
    Hot deploy failed with the following message:
    Unable to add module: NewPortalWebApp to application descriptor for:
    portalApp.
    The log has the following information..
    Adding file:
    C:\bea\user_projects\myNewdomain\beaApps\portalApp-project\application-sync\
    portlets\Portlet1.portlet to sync list.
    Adding file:
    C:\bea\user_projects\myNewdomain\beaApps\portalApp-project\application-sync\
    webapps\PortalWebApp\tools.wf to sync list.
    Adding file:
    C:\bea\user_projects\myNewdomain\beaApps\portalApp-project\application-sync\
    webapps\PortalWebApp\webflow-extensions.wfx to sync list.
    Adding file:
    C:\bea\user_projects\myNewdomain\beaApps\portalApp-project\application-sync\
    webapps\PortalWebApp\user_account.wf to sync list.
    Adding file:
    C:\bea\user_projects\myNewdomain\beaApps\portalApp-project\application-sync\
    webapps\PortalWebApp\portal.wf to sync list.
    Adding file:
    C:\bea\user_projects\myNewdomain\beaApps\portalApp-project\application-sync\
    webapps\PortalWebApp\security.wf to sync list.
    Adding file:
    C:\bea\user_projects\myNewdomain\beaApps\portalApp-project\application-sync\
    webapps\PortalWebApp\NewPortal.portal to sync list.
    Attempting sync...
    Sync complete.
    Searching for portalApp application descriptor...
    Found it.
    Error - please check log for details.
    <!--
    Copyright (c) 2000 Sun Microsystems, Inc.,
    901 San Antonio Road,
    Palo Alto, California 94303, U.S.A.
    All rights reserved.
    Sun Microsystems, Inc. has intellectual property rights relating to
    technology embodied in the product that is described in this document.
    In particular, and without limitation, these intellectual property
    rights may include one or more of the U.S. patents listed at
    http://www.sun.com/patents and one or more additional patents or
    pending patent applications in the U.S. and in other countries.
    This document and the product to which it pertains are distributed
    under licenses restricting their use, copying, distribution, and
    decompilation. This document may be reproduced and distributed but
    may
    not be changed without prior written authorization of Sun and its
    licensors, if any.
    Third-party software, including font technology, is copyrighted and
    licensed from Sun suppliers.
    Sun, Sun Microsystems, the Sun logo, Java, JavaServer Pages, Java
    Naming and Directory Interface, JDBC, JDK, JavaMail and and
    Enterprise JavaBeans are trademarks or registered trademarks of Sun
    Microsystems, Inc. in the U.S. and other countries.
    Federal Acquisitions: Commercial Software - Government Users Subjectto
    Standard License Terms and Conditions.
    DOCUMENTATION IS PROVIDED "AS IS" AND ALL EXPRESS OR IMPLIED
    CONDITIONS, REPRESENTATIONS AND WARRANTIES, INCLUDING ANY IMPLIED
    WARRANTY OF MERCHANTABILITY, FITNESS FOR FOR A PARTICULAR PURPOSE OR
    NON-INFRINGEMENT, ARE DISCLAIMED, EXCEPT TO THE EXTENT THAT SUCH
    DISCLAIMERS ARE HELD TO BE LEGALLY INVALID.
    Copyright (c) 2000 Sun Microsystems, Inc.,
    901 San Antonio Road,
    Palo Alto, California 94303, E'tats-Unis.
    Tous droits re'serve's.
    Sun Microsystems, Inc. a les droits de proprie'te' intellectuels
    relatants a` la technologie incorpore'e dans le produit qui est
    de'crit
    dans ce document. En particulier, et sans la limitation, ces droits de
    proprie'te' intellectuels peuvent inclure un ou plus des brevets
    ame'ricains e'nume're's a` http://www.sun.com/patents et un ou les
    brevets plus supple'mentaires ou les applications de brevet en attente
    dans les E'tats-Unis et dans les autres pays.
    Ce produit ou document est prote'ge' par un copyright et distribue'
    avec des licences qui en restreignent l'utilisation, la copie, la
    distribution, et la de'compilation. Ce documention associe n peut
    e^tre reproduite et distribuer, par quelque moyen que ce soit, sans
    l'autorisation pre'alable et e'crite de Sun et de ses bailleurs de
    licence, le cas e'che'ant.
    Le logiciel de'tenu par des tiers, et qui comprend la technologie
    relative aux polices de caracte`res, est prote'ge' par un copyright et
    licencie' par des fournisseurs de Sun.
    Sun, Sun Microsystems, le logo Sun, Java, JavaServer Pages, Java
    Naming and Directory Interface, JDBC, JDK, JavaMail et and
    Enterprise JavaBeans sont des marques de fabrique ou des marques
    de'pose'es de Sun Microsystems, Inc. aux E'tats-Unis et dans d'autres
    pays.
    LA DOCUMENTATION EST FOURNIE "EN L'E'TAT" ET TOUTES AUTRES CONDITIONS,
    DECLARATIONS ET GARANTIES EXPRESSES OU TACITES SONT FORMELLEMENT
    EXCLUES, DANS LA MESURE AUTORISEE PAR LA LOI APPLICABLE, Y COMPRIS
    NOTAMMENT TOUTE GARANTIE IMPLICITE RELATIVE A LA QUALITE MARCHANDE, A
    L'APTITUDE A UNE UTILISATION PARTICULIERE OU A L'ABSENCE DE
    CONTREFAC,ON.
    -->
    <!--
    This is the XML DTD for the J2EE 1.3 application deployment
    descriptor. All J2EE 1.3 application deployment descriptors
    must include a DOCTYPE of the following form:
    <!DOCTYPE application PUBLIC
    "-//Sun Microsystems, Inc.//DTD J2EE Application 1.3//EN"
    "http://java.sun.com/dtd/application_1_3.dtd">
    -->
    <!--
    The following conventions apply to all J2EE deployment descriptor
    elements unless indicated otherwise.
    - In elements that contain PCDATA, leading and trailing whitespace
    in the data may be ignored.
    - In elements whose value is an "enumerated type", the value is
    case sensitive.
    - In elements that specify a pathname to a file within the same
    JAR file, relative filenames (i.e., those not starting with "/")
    are considered relative to the root of the JAR file's namespace.
    Absolute filenames (i.e., those starting with "/") also specify
    names in the root of the JAR file's namespace. In general, relative
    names are preferred. The exception is .war files where absolute
    names are preferred for consistency with the servlet API.
    -->
    <!--
    The application element is the root element of a J2EE application
    deployment descriptor.
    -->
    <!ELEMENT application (icon?, display-name, description?, module+,
    security-role*)>
    <!--
    The alt-dd element specifies an optional URI to the post-assembly
    version of the deployment descriptor file for a particular J2EEmodule.
    The URI must specify the full pathname of the deployment descriptor
    file relative to the application's root directory. If alt-dd is not
    specified, the deployer must read the deployment descriptor from the
    default location and file name required by the respective component
    specification.
    Used in: module
    -->
    <!ELEMENT alt-dd (#PCDATA)>
    <!--
    The connector element specifies the URI of a resource adapter archive
    file, relative to the top level of the application package.
    Used in: module
    -->
    <!ELEMENT connector (#PCDATA)>
    <!--
    The context-root element specifies the context root of a web
    application.
    Used in: web
    -->
    <!ELEMENT context-root (#PCDATA)>
    <!--
    The description element is used to provide text describing the parent
    element. The description element should include any information that
    the application ear file producer wants to provide to the consumer of
    the application ear file (i.e., to the Deployer). Typically, the tools
    used by the application ear file consumer will display the description
    when processing the parent element that contains the description.
    Used in: application, security-role
    -->
    <!ELEMENT description (#PCDATA)>
    <!--
    The display-name element contains a short name that is intended to be
    displayed by tools. The display name need not be unique.
    Used in: application
    Example:
    <display-name>Employee Self Service</display-name>
    -->
    <!ELEMENT display-name (#PCDATA)>
    <!--
    The ejb element specifies the URI of an ejb-jar, relative to the top
    level of the application package.
    Used in: module
    -->
    <!ELEMENT ejb (#PCDATA)>
    <!--
    The icon element contains small-icon and large-icon elements that
    specify the file names for small and a large GIF or JPEG icon images
    used to represent the parent element in a GUI tool.
    Used in: application
    -->
    <!ELEMENT icon (small-icon?, large-icon?)>
    <!--
    The java element specifies the URI of a java application clientmodule,
    relative to the top level of the application package.
    Used in: module
    -->
    <!ELEMENT java (#PCDATA)>
    <!--
    The large-icon element contains the name of a file
    containing a large (32 x 32) icon image. The file
    name is a relative path within the application's
    ear file.
    The image may be either in the JPEG or GIF format.
    The icon can be used by tools.
    Used in: icon
    Example:
    <large-icon>employee-service-icon32x32.jpg</large-icon>
    -->
    <!ELEMENT large-icon (#PCDATA)>
    <!--
    The module element represents a single J2EE module and contains a
    connector, ejb, java, or web element, which indicates the module type
    and contains a path to the module file, and an optional alt-ddelement,
    which specifies an optional URI to the post-assembly version of the
    deployment descriptor.
    The application deployment descriptor must have one module element for
    each J2EE module in the application package.
    Used in: application
    -->
    <!ELEMENT module ((connector | ejb | java | web), alt-dd?)>
    <!--
    The role-name element contains the name of a security role.
    The name must conform to the lexical rules for an NMTOKEN.
    Used in: security-role
    -->
    <!ELEMENT role-name (#PCDATA)>
    <!--
    The security-role element contains the definition of a security
    role. The definition consists of an optional description of the
    security role, and the security role name.
    Used in: application
    Example:
    <security-role>
    <description>
    This role includes all employees who are authorized
    to access the employee service application.
    </description>
    <role-name>employee</role-name>
    </security-role>
    -->
    <!ELEMENT security-role (description?, role-name)>
    <!--
    The small-icon element contains the name of a file
    containing a small (16 x 16) icon image. The file
    name is a relative path within the application's
    ear file.
    The image may be either in the JPEG or GIF format.
    The icon can be used by tools.
    Used in: icon
    Example:
    <small-icon>employee-service-icon16x16.jpg</small-icon>
    -->
    <!ELEMENT small-icon (#PCDATA)>
    <!--
    The web element contains the web-uri and context-root of a web
    application module.
    Used in: module
    -->
    <!ELEMENT web (web-uri, context-root)>
    <!--
    The web-uri element specifies the URI of a web application file,
    relative to the top level of the application package.
    Used in: web
    -->
    <!ELEMENT web-uri (#PCDATA)>
    <!--
    The ID mechanism is to allow tools that produce additional deployment
    information (i.e., information beyond the standard deployment
    descriptor information) to store the non-standard information in a
    separate file, and easily refer from these tool-specific files to the
    information in the standard deployment descriptor.
    Tools are not allowed to add the non-standard information into the
    standard deployment descriptor.
    -->
    <!ATTLIST alt-dd id ID #IMPLIED>
    <!ATTLIST application id ID #IMPLIED>
    <!ATTLIST connector id ID #IMPLIED>
    <!ATTLIST context-root id ID #IMPLIED>
    <!ATTLIST description id ID #IMPLIED>
    <!ATTLIST display-name id ID #IMPLIED>
    <!ATTLIST ejb id ID #IMPLIED>
    <!ATTLIST icon id ID #IMPLIED>
    <!ATTLIST java id ID #IMPLIED>
    <!ATTLIST large-icon id ID #IMPLIED>
    <!ATTLIST module id ID #IMPLIED>
    <!ATTLIST role-name id ID #IMPLIED>
    <!ATTLIST security-role id ID #IMPLIED>
    <!ATTLIST small-icon id ID #IMPLIED>
    <!ATTLIST web id ID #IMPLIED>
    <!ATTLIST web-uri id ID #IMPLIED>

Maybe you are looking for

  • Safari is Constantly Crashing - NEW CASE? Help!

    Dear Fellow MAC Users, I need your help for solving my problem about Safari. It constantly crashes and I don't have any idea what could be causing the problem (I posted the report below). I came across the problem posted by LeonardoGolden that has be

  • Is it possible to reset password for any user using abap program

    Hi friends, Is it possible to reset password for any user using abap program by specifying client number and user id. in selection screen. if any code for that to reset password please mail me. Thanks & Regards, Yogesh

  • Two emails, not one reply.

    Hello everybody, I emailed Verizon last Thursday with a question (which I will talk about in a second). After writing the email and filling out all the fields (since I was not going to be able to really check email over the weekend), I clicked the "s

  • Phone is reported stolen every time i do an apple update.

    For the last three time that apple has had an update i run the update hours later my phone stops working i call verizon and they tell me my account was suspended due to the phone being reported lost or stolen.  I purchased my phone direclty from veri

  • VZW ... truly more bars in more places

    This can put tears in your eyes, if you have suffered from abysmal AT&T coverage for years: What a relief ...