Component Validation & Properties File

hi
I have created a simple web-page using visual web framework where I m taking FName as input string..where i want to validate that user should not enter any number or a white space character..
I want to validate it using Regular Expression i.e. java.util.Pattern
     String merit=(String) getMerit_num().getSubmittedValue();
        Pattern pattern =Pattern.compile(text_pattern);
        boolean matcher=Pattern.matches(text_pattern,merit);
        if(matcher)
            setMsg_merit(msg_merit);
        }Above code checks that whether its a digit or not but how to check a white spce charcater with this?
Is it the right way? mean is there any other better way for it?
And how to edit Messages.Properties File?
Edited by: Maltec on Aug 31, 2008 2:26 AM

Maltec wrote:
I have created a simple web-page using visual web framework where I m taking FName as input string..where i want to validate that user should not enter any number or a white space character..
I want to validate it using Regular Expression i.e. java.util.Pattern
String merit=(String) getMerit_num().getSubmittedValue();
Pattern pattern =Pattern.compile(text_pattern);
boolean matcher=Pattern.matches(text_pattern,merit);
if(matcher)
setMsg_merit(msg_merit);
}Above code checks that whether its a digit or not but how to check a white spce charcater with this?
Is it the right way? mean is there any other better way for it?I can't tell if the above code is correct, because you didn't show how text_pattern look like. If you're using Java 1.5 or newer, you could also use String#matches() instead of all those code lines. Just pass the text_pattern as parameter.
And how to edit Messages.Properties File?Just create your own, put it in the classpath and define it as <message-bundle> entry in the faces-config.xml. Specify in there any message key that you want to override from the default. If you don't specify it, then the default will be used.

Similar Messages

  • Read properties file in abstract portal component

    Hi,
    i have test.properties file, i want to read information on this file and its located in src.api/properties . if any one knows How to read this  properties file in abstract portal component please tell me.
    Regards,
    nari.

    Hi Nari,
    Follow the below steps:
    1. Store your properties files (test.properties, test_en.properties, test_xx.properties where xx is the locale ) in the folder PORTAL-INF ->Private ->classes
    2. In portalapp.xml for component-config, add this
    <property name="ResourceBundleName" value="test"/>
    3. In your abstract portal component you can use the below code to fetch the value for the key "SERVER_NAME".
        public void doContent(IPortalComponentRequest request, IPortalComponentResponse response)
             ResourceBundle resourceBundle = request.getResourceBundle();
             if(resourceBundle!=null)
                  response.write(resourceBundle.getString("SERVER_NAME"));
             else
                  response.write("Error");
    Let me know if you still face any issue.
    Thanks
    Prashant

  • URGENT!!! can I borrow a valid jserv.properties file for a JSP application ?

    Hi there !
    I'm running Oracle enterprise edition on NT with oracle http server under apache.
    I created a JSP application using jdeveloper
    and deployed it to the web server.
    Now I'm still getting getting nullPointer exceptions after I have modified the jserv.properties file according to the documentation
    Can someone give me a file that is working for her/him under the above described circumstances ?
    Many Thanaks in advance
    Tony
    null

    laredotornado wrote:
    Hi,
    This might not be a JSF question, but I thought I'd start here as I'm building a JSF application. Upon startup of my Weblogic 9.2.2 server, I see these error messages
    log4j:WARN No appenders could be found for logger (org.apache.myfaces.webapp.StartupServletContextListener).
    log4j:WARN Please initialize the log4j system properly.
    One complication, my log4j.properties file is actually called "my.properties" (bizarre company reason). Is there somewhere in my faces-config.xml file or an equivalent where I can indicate what log4j properties file I'd like to use?Your company policy is to use non-standard names so that things must be configured manually? Interesting.
    In the past people created a servlet those sole purpose was to configure log4j in the initialization sequence and then do nothing.

  • Error reading Properties file

    I have a main method which i am using to call a servlet located in the same Development Component. Until recently i had the servlet location hard coded and it was working without issues. Now i decided to make the location configurable. For this i created an sap.application.global.properties file in the EAR DC which contains the WAR of this DC.
    The contents of the above file are as follows:
    SAP application properties
    SERVLET.LOCATION=http://<server-name>/ControllerServlet/servlet/com.nike.xapps.eqptsp.swem.controller.ControllerServlet
    The code i am using in the main method to call this properties file and access the property is as follows:
    Context ctx = new InitialContext();
    ApplicationConfigHandlerFactory cfgHdlr = (ApplicationConfigHandlerFactory)ctx.lookup("ApplicationConfiguration");          
    Properties props = cfgHdlr.getApplicationProperties();
    String servlet = props.getProperty("SERVLET.LOCATION");
    contained in a try...catch block.
    On dubugging i get a NoInitialContextException repeatedly in the statement where the lookup is performed.
    These are all the additions i have made for reading this properties file. Does anyone know if there is anything more that needs to be done for this to work.
    Thanks,
    Murtaza.

    thank for the help mangst. i guess the IO approach is also applicable ^^; i changed my code to:
    configFile.load( new FileInputStream( ".\\resources\\config.properties" ) );but i had a little trouble in debugging it since it starts the file search from the main project directory. however it works fine upon deployment. ^^; thanks again.
    Edited by: xnofate on Sep 23, 2008 6:21 PM

  • $USER_HOME variable not working in Java7u55 deployment.properties file.

    I'm trying to setup a separate cache directory for an AppV Java 7u55 package. In the deployment.properties file I created the following entry:
    deployment.user.cachedir=$USER_HOME\\AppData\\LocalLow\\Sun\\Java\\Deployment\\Java7cache
    But upon initiating an application I do not see the folder created and populated with cache data. This is what I see in the Java7 control panel for the cache path after my edit:
    My question, is $USER_HOME still a valid variable for use in the deployment.properties file and if so what is the path that it points to?
    UPDATE: So I did find where at least for me this path led to on my desktop a directory called $USER_HOME was created with the rest of the above location following it. Is this correct?
    How can I my current setup deployment.user.cachedir=$USER_HOME to go to this location: C:\users\<user account>\AppData\LocalLow\Sun\Java\Deployment\Java7cache\ ???

    I don't have an answer to the problem, but I am having problems with the system level deployment.properties file and IE9 on Windows 7 32/64bit.
    Starting with version 13, the IE plugin seems to igonore the system level deployment.properties file in favor of the user level deployment.properties file. When I open the Java Control Panel, the settings are correct per the system deployment.properties file. Currently to get the Java Plugin to work reliably in IE9 I have to set the following:
    _JAVA_OPTIONS = -Djava.net.preferIPv4Stack=true
    Disable caching
    Set the proxy to Direct Connection.
    If I set the _JAVA_OPTIONS as an environment variable and the other two in the system deployment.properties file, Firefox works fine, but IE wont load either of the Java tests. If I removed the system deployment.properties files and configure the user deployment.properties file, both IE and Firefox work fine.
    I find it interesting that if I set the configuration through the control panel, then apply the system deployment.propteries file, the user deployment.properties file reverts to defaults when the system file is removed.

  • Format Text in properties File

    I have a large amount of text for an element in the properties file that I'd like to format. I'm retrieving this value and displaying it in the tip of a panelLabelAndMessage ADF component. For example, in the properties file I have the following:
    displayparagraph=This is the first paragraph.This is a second paragraph I'd like on a new line.
    I'd like this text to be broken apart onto new lines when it displays in the tip element, like this:
    This is the first paragraph.
    This is the second paragraph I'd like on a new line.
    I'm not sure how to go about doing this or if it's even possible. I've tried placing \n, \\n, \r, \r\n, etc...inbetween the "." and "This" but this doesn't appear to work.
    I'd also like to a portion of that same message be underlined as a link...not sure if that is possible either.
    I have to keep the text in the properties file for translation purposes and I can't really break up the sentences into seperate elements to ensure that translations doesn't lose the meaning of the tip.

    Hi,
    If you set the escape property to false on your output components you can put HTML code in your properties file for the components that you want to format differently.
    Not all components can do this but the key ones like OutputText do.
    regards,
    Brenden

  • How to get File Reference of a properties file from EJB

    Hi,
    I am using Sun App server 7 with Oracle 9i. I am keeping all my SQL statements in a properties file from which I am loading it while making a database operation from Stateless beans. My problem is I am not able to get the reference of the properties file. Here is the code through which I am getting the SQL statements loaded to a cache.
    String sqlFileName = "SQL.properties";
    sqlCache.load(new FileInputStream(sqlFileName));
    From the cache I am sending the SQL statement depending on the key value. But the problem is I have to keep the SQL.properties file on the App Server config directory of the instance where the server.xml file resides. Otherwise it is not able to find the properties file. But I don't want to put the properties file on the config directory of the server instance. Please help how to get the properties file from the packakge. My file is residing inside a package com.company.sql . Botht the properties file and the class accessing the file are residing in the same package. Please help how to get the reference of the file with out putting the file in the config directory.
    Thanks
    Amit Patnaik

    Just wanted to warn you of the hazards if you read a file from EJB
    So please make sure that these hazards will not affect your application. However the solution suggested to use getResourceStream() concurs with ejbSpec
    This snippet is from suns blueprint on ejb
    Why can't EJBs read and write files and directories in the filesystem? And why can't they access file descriptors?
    Enterprise beans aren't allowed to access files primarily because files are not transactional resources. Allowing EJBs to access files or directories in the filesystem, or to use file descriptors, would compromise component distributability, and would be a security hazard.
    Another reason is deployability. The EJB container can choose to place an enterprise bean in any JVM, on any machine in a cluster. Yet the contents of a filesystem are not part of a deployment, and are therefore outside of the EJB container's control. File systems, directories, files, and especially file descriptors tend to be machine-local resources. If an enterprise bean running in a JVM on a particular machine is using or holding an open file descriptor to a file in the filesystem, that enterprise bean cannot easily be moved from one JVM or machine to another, without losing its reference to the file.
    Furthermore, giving EJBs access to the filesystem is a security hazard, since the enterprise bean could potentially read and broadcast the contents of sensitive files, or even upload and overwrite the JVM runtime binary for malicious purposes.
    Files are not an appropriate mechanism for storing business data for use by components, because they tend to be unstructured, are not under the control of the server environment, and typically don't provide distributed transactional access or fine-grained locking. Business data is better managed using a persistence interface such as JDBC, whose implementations usually provide these benefits. Read-only data can, however, be stored in files in a deployment JAR, and accessed with the getResource() or getResourceAsStream() methods of java.lang.Class.
    Hope this info helps!

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

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

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

  • Properties files in a Java package not included in DC build

    We are developing a Portal Standalone DC and i have a JspDynPage component within it. and i need to do internationalization in  it. so as part of that i want to keep multiple resource bundles(properties) so that i could manage my properties files easily, For example
    MSS.properties
    MSS_es.properties
    ESS.properties
    LSO.properties
    since portal by default has no way to do this bcos it allows only one resourcebundle to specify in portalapp.xml file, i have kept the resource bundles in java package like
    com.companyname.portal.resources.
    when i export from NWDS with selection of "i want to add non java resources into jar " option from windows->preferences->enterprise portal ->application development studio, it exports all the properties files as part of the par and everything works. but when i do the DC build it ignores all my properties files and it is not working. any suggestions on how to resolve this??? does SAP provide any other way of handling multiple properties files inside a PAR?????

    We are using NWDS 2004 SP19.  and yes i have defined three default SCs as dependencies. I tested with 2004s NWDS and it seems work fine. I am able to resovle this issue by moving my properties files into another java DC and create public part in java DC and use those public parts in Portal application DC.
    So The problem of not including the properties files into Jar seems to be issue only in Portal Application DC not in Java DC. thanks everyone for the quick responses..

  • Very weird issue with server logging when using log4j.properties file

    I'm using log4j logging. In log4j.properties the root logger is set up to use the ServerLoggingAppender class so that all our application logs go to the main server logfile. In addition, there are several appenders defined for specific components, with output going to specific per-component log files. Everything is going fine until I launch the server console. At this point all of those per-component log files get wiped out (zero length) and some non-ASCII lines are written to at least one of these files, after which the logs appear to be fine. The main server log file does not appear to be affected (because the root logger is set to "warn" level, while component-specific loggers are set to trace, the contents in these files is different; however I tried disabling all the other appenders and turning the root logger up to trace, and that still did not re-create the problem in the main server log file.
    And here's the really weird part -- if I use the same configuration, but in a log4j.xml file, the problem does not happen.

    Figured it out.
    We were passing in the configuration for log4j as -Dlog4j.configuration=file:/<properties file> and this was added to the command line for both the managed and admin servers. Problem is that the console app starts its own instance of log4j, and when it reads the configuration for the appenders it initializes or rolls over the files. At some point we have two JVMs accessing the same files, so some corruption is bound to happen.
    I'm not clear why the .xml file made a difference, but earlier we had been passing the log4j configuration as a jar file placed in the domain/lib folder, so perhaps the designer reverted to that (placed the log4j.xml file in a jar in lib, and not simply changed the -Dlog4j.configuration=file:/ option.

  • Dynamic java logging properties file

    Hello,
    I am looking for a dynamic way to set a property in a java logging properties file.
    For example something like this:
    java.util.logging.FileHandler.pattern = ${log.dir}/logfile%u.log
    ..where log.dir is a system property. But this does not work. Any other way to do it?
    Thanks in advance,
    Rohnny

    This pattern doesn't work ? here is the content of my
    logging.properties file.
    java.util.logging.FileHandler.pattern = LOGFILE.log
    java.util.logging.FileHandler.limit = 50000
    java.util.logging.FileHandler.count = 1
    java.util.logging.FileHandler.formatter =
    java.util.logging.SimpleFormatter
    FIRST_LOGGER.Handler = java.util.logging.FileHandler
    FIRST_LOGGER.level = ALL
    SECOND_LOGGER.Handler =
    java.util.logging.FileHandler
    SECOND_LOGGER.level = ALLIt seems like you're not thoroughly reading the spec on this stuff.
    I don't think ".Handler" is even a valid property on a logger.
    Loggers aren't typically initialized with a complex configuration out of a configuration file...unless you write your own custom format. For instance, FileHandler is a class, so when you define java.util.logging.FileHandler.pattern in the config file, you're defining it for every default instance of FileHandler...so naturally both your loggers that use FileHandlers will write to the same file.
    I've never done this before, but here's what I came up with after reading the spec:
    1) define 1 subclass of FileHandler for each file you want to write to... let's call them FileHandlerA and FileHandlerB. All they have to do is extend FileHandler, nothing else.
    2) define the patterns for each subclass in the config file. You can also define any other properties you want for each handler, such as .level, .limit, .count, etc.
    mypackage.myhandlers.FileHandlerA.pattern = LogFile-A.log
    mypackage.myhandlers.FileHandlerB.pattern = LogFile-B.log
    // ... more config here
    3) define the loggers in the config file and specify the handlers to use on each:
    FIRST_LOGGER.handlers = mypackage.myhandlers.FileHandlerA
    SECOND_LOGGER.handlers = mypackage.myhandlers.FileHandlerB
    4) create your Loggers in your code:
    Logger firstLog = Logger.getLogger("FIRST_LOGGER");
    Logger secondLog = Logger.getLogger("SECOND_LOGGER");
    Good luck.

  • WTK 2.5.2 device properties files

    Hello,
    is there a list which contains all valid key and maybe values that can be used in the wireless toolkit device properties files (e.g DefaultColorPhone.properties)?
    And is there anywhere some documents how i can create own devices?
    Thanks
    Micha

    but with "camera.src.file" you can define a video to simulate the camera so its not needlessMakes sense. Changing "camera.src.file" probably allows that... did you try it?
    The problem is, is this ability intended by design or not? If it is, then why is it not documented? and why is it absent in QwertyDevice properties?
    If it is not (I mean if "camera.src.file" is not intended to be modified by users), then why it is present in DefaultColorPhone properties?
    In other words, is changing this property a misuse or a legal feature? WTK docs don't clarify this - that's why I call this a problem.

  • Could not find "jdbc.datasources=..." in default.properties file

    Dear sirs,
    I sucessfully install jdk1.3 ,j2ee 1.3 and 50 day's trial cloudscape5.1 , then run the Cview create a database ,now I want to rigister the database by opening %J2EE_HOME%\config\default.properties file to find the line likes
    "jdbc.datasources=..." to add my database name behind , but I could not find it ,it's content is only appeared as
    following :
    # maximum size of message driven bean instance
    # pool per mdb type
    messagebean.pool.size=3
    # maximum size of a "bulk" message bean delivery
    messagebean.max.serversessionmsgs=1
    # message-bean container resource cleanup interval
    messagebean.cleanup.interval=600
    passivation.threshold.memory=128000000
    idle.resource.threshold=600
    log.directory=logs
    log.output.file=output.log
    log.error.file=error.log
    log.event.file=event.log
    distributed.transaction.recovery=false
    transaction.timeout=0
    transaction.nonXA.optimization=true
    sessionbean.timeout=0
    # validating parser values
    # validating.perser is used when archive file are loaded by
    # any of the J2EE Reference Implementation tools.
    # deployment.validating.parser is used when deploying an
    # archive on the J2EE AppServer.
    validating.parser=false
    deployment.validating.parser=true
    What shoul I do?
    Best regard !
    zhangyu
    cosbulk

    hi zylf,
    what u are looking for is ther in the resource.properties file..
    %J2EE_HOME%\config\resource.properties
    dont rely too much on tutorials.. many are outdated.. it seems..
    try opening all the files in the j2ee dir's, read 'em and try to understand them....
    a better forum for this is the J2EE forum at this url..
    http://forum.java.sun.com/forum.jsp?forum=136
    all the best..
    -Jer

  • Formatting swing for properties file

    this relates a bit to the last post I put on here about JTextAreas.
    I have a lot of properties files that contain strings used throughout the program.
    I was wondering what the ideal way of going about the formatting of the swing components the strings are used inside in relation to the properties file.
    The problem is that the lengths of the strings vary so much (and are used the same way), that its not a "one size fits all" screen.
    The properties only has the most required of \n's in it (This is the standard, correct?), so you have to setTextWrap(true) for the JTextArea. The problem with this is you do not have a way of dedecting the height.
    We are trying to get all of the message boxes formatted the same with the same length between the end of the text and buttons at the bottom, but cannot come up with a good way of doing this. character counting with FontMetrics does not work well since there are a few \n's in it. Adding \n to the properties file doesn't seem like an accurate solution. So basically, I have two questions:
    1)Does anyone have a way of dedecting the height of this jTextArea with textwrap on?
    2)What is the standard for interaction and spacing between a properties file and swing component?

    Could you post a small example, compilable and runnable, code that can reproduce your
    problem? I reread your first post and recognized that I didn't have understood your problem
    fully and in detail.
    trying to get all of the message boxes formatted the same with the same length between
    the end of the text and buttons at the bottomThis sentence is quite hard to swallow without real code or screen shot.
    Why multiple text areas?
    Buttons? What buttons?
    etc., etc. Questions are endless.

  • JRE 6u19 - security warning   external properties file

    Hi,
    I have an applet with several jars files, all jars are signed.
    Since JRE 6u19, when launching my applet, I have the message "Java has discovered application components that could indicate a security problem".
    6u19 has a new security approach for application/applet mixing Signed and Unsigned Code.
    http://java.sun.com/javase/6/docs/technotes/guides/jweb/mixed_code.html
    Nevertheless, in my case, all jars are signed and I still have the warning message.
    I analyzed the code and noticed that the warning comes from the use of a properties file and a 'cacerts' file.
    The property file is used through the common class: java.util.Properties
    I think also that we have security warnings when using the following methods to get resources :
    this.getClass().getClassLoader().getResourceAsStream(fileName)
    or java.util.ResourceBundle.getBundle
    JRE 6u19 is supposed to verify if the jars are signed (and all my jars are signed) but I don' t understand why I have a security warning when using a properties file.
    I would appreciate to get help. thanks.
    Regards,
    Cédric

    I read your reply as: It should work to use the context classloader to load resources from unsigned jars without getting the warning. Is that correct?
    Unfortunately, I cannot attach context, so I am going to provide a small sample consisting of a handful of files, that produces a warning for me.
    To run the example:
    - Correct the codebase in the two jnlp-files
    - Compile the java-file, jar it to a jar called webstart.jar and sign the jar.
    - Jar the text file to a jar called resource.jar.
    - Run the webstart.jnlp.
    Main.java:
    package com.virtubuild;
    import java.io.*;
    import java.net.*;
    public class Main {
      public static void main(String[] args) throws IOException {
        ClassLoader contextClassLoader = Thread.currentThread().getContextClassLoader();
        URL url = contextClassLoader.getResource("resource.txt");
        if(url==null) {
          System.err.println("Could not find external resource");
          return;
        readAndPrint(url);
      private static void readAndPrint(URL url) throws IOException {
        BufferedReader in = openFile(url);
        String inputLine = null;
        while ((inputLine = in.readLine()) != null) {
          System.out.println(inputLine);
        in.close();
      public static BufferedReader openFile(URL url) throws IOException{
        InputStream input = url.openStream();
        InputStreamReader ireader = new InputStreamReader(input,"UTF8");
        return new BufferedReader(ireader);
    webstart.jnlp:
    <?xml version="1.0" encoding="UTF-8"?>
    <jnlp spec="6.0+" codebase="file:///C:/TEMP/webstart/" href="webstart.jnlp">
      <information>
        <title>Webstart</title>
      </information>
      <security>
        <all-permissions/>
      </security>
      <update check="always" policy="prompt-update"/>
      <resources>
        <java version="1.6+"/>
              <jar href="webstart.jar" main="true"/>
      </resources>
      <resources>
           <extension href="resource.jnlp"/>
      </resources>
      <application-desc/>
    </jnlp>
    resource.txt:
    Test
    Testing
    Tested
    resource.jnlp:
    <?xml version="1.0" encoding="UTF-8"?>
    <jnlp spec="6.0+" codebase="file:///C:/TEMP/webstart/" href="resource.jnlp">
      <information>
        <title>Resource</title>
      </information>
    <update check="always" policy="prompt-update"/>
    <resources>
      <jar href="resource.jar"/>
    </resources>
    <component-desc/>
    </jnlp>The better way you mention is not really an option for us right now, but we will keep it in mind if we create another product deployed through webstart.

Maybe you are looking for