JSP Requirements

Hi, I'm developing an j2me application with natural interaction.
My application needs to use jsp pages with xml to adquire parameters and that way read them to the user.
If I only use xml it works ok, but when I embed java code on xml it doesn't work.
I'm using IIS, what do I need to install on my server to run jsp pages properly?
Do I need to install the jre or I need an application or web server?
Thanks a lot, I'm very new to this technology.
Nuria.

JSP are translated to servlets , so you need a servlet engine. E.g. Tomcat has one, or Bea WebLogic, or J2EE.

Similar Messages

  • Studio Enterprise 8 EA - JSPs require redeployment

    Hi,
    the subject says it all... any changes within JSPs, addings JSPs, etc. require redeployment. I'm using the Sun Java App Server included in the installation...
    I've checked the domains folder, changes on JSPs are not reflected (on the AppServer) in the folder:
    domains\<domainname>\applications\j2ee-modules\<modulename>
    ... but only in the projects folder.
    Consequence: the AppServer doesn't know about any changes.
    Pressing F9 (Compile) doesn't help either.
    How can I get around that? Re-Deployment kills sessions and takes up-to 30 seconds here.
    Thanks!

    Perhaps this is of any interest for someone...
    This does NOT happen in newly created webmodules, but in this case I've important an "existing webapplication with sources".

  • Problem converting a JSP to html file

    Hi,
    I want to save my jsp page as a html file so that I can later send it as email body. This jsp page is a dynamic page.
    I am giving a few code lines below that i'm using.
    url = new URL("http://localhost:9080/ndw/jobsum/execdisplay.do?id=" bean.getId().toString()";jsessionid=" +id );
    in = new BufferedInputStream( url.openStream() );
    try {
    file = new File("C:/myfile.html");
    out = new BufferedOutputStream ( new FileOutputStream ( file ));
    } catch ( FileNotFoundException e ) {
    System.out.println( "Invalid save file requested: " +
    e.getMessage() );
    try {
    bytesRead = in.read( bytes, 0,
    bytes.length );
    while ( bytesRead != -1 ){
    out.write( bytes, 0, bytesRead );
    bytesRead = in.read( bytes, 0,
    bytes.length );
    in.close();
    out.close();
    } catch ( IOException e ){
    System.out.println( "Error saving to "
    +"file: " + e.getMessage() );
    This should save the JSP given by URL as html file.
    A html file by name "myfile.html" is indeed being created in C drive but the html is of loginpage of my application and not the html file of the JSP required.
    I guess this is happening because server is not convinced that i hv logged in before accessing tht JSP. Is there any servlet API which would bypass the access control mechanisms.
    Folks, please help me in this.Its quite urgent.
    Thanks in advance

    This has nothing to do with JavaMail. You'll probably get a better
    answer from the JSP support forum.
    You might have to convince the server that you've logged in before
    you can access the JSP page. That could be fairly complicated.
    Alternatively, you might be able to access the page using one of
    the servlet APIs, which would bypass the access control mechanisms.

  • WAR or JSP to serve HTML in JAR file?

    Hi,
    I want to keep a few hundred static help files in a JAR when I install my appliation on the server to ease installation and management. But what is the best way to serve them up? What litle I know about WARs seems to imply I can have HTML files in one and, with the server set up correctly, redirect a URI to find HTML files in there. Is that so? Is there an exmple out there?!
    cheers,
    Chuck

    Hi,
    Thanks, but to be clear, I want to ONLY have HTML files in this WAR. The rest of the appliation's servlets will not be part of this.
    I am simply looking for an easy way to access the HTML files if I JAR them up. Using a WAR, there is no servlet/jsp required to redirect a URL request to an HTML file in the archive, right? What would the web.xml look like, or is it even needed, when there is no JSP associated with the WAR?
    thanks,
    Chuck

  • JSP cannot be found Error when trying to Priview an Iview made of a PAR fil

    We created a project using the Netweaver Developer Studio including our code (the jsps, required libraries with it).We then created our PAR file and deployed it on the Portal using the PDK. After this we created a Iview using the PAR which we had deployed. When we tried to priview the IView it gave us an error saying the JSP could not be found . We have checked the PCD (Portal Content Directory ) and found the Jsp deployed at the right place . It could be a problem with the Path Configuration . Does anyone have any idea about how to go about resolving this issue?
    (I am also attaching the error message from the server log file.)
    D:
    usr
    sap
    P66
    JC00
    j2ee
    cluster
    server0
    apps
    sap.com
    irj
    servlet_jsp
    irj
    root
    WEB-INF
    portal
    portalapps
    com.sap.portal.admin.templateselectionwizard
    private
    lib
    com.sap.portal.admin.templateselectionwizardcore.jar
    #1.5#0007E904947000490000016B00000A680003ED5CE8B5DA9D#1105408227143#/System/Server#sap.com/irj#com.sap.portal.portal#Administrator#266##LABTEST01_P66_4818350#Administrator#d6becb70637211d9b2bb0007e9049470#SAPEngine_Application_Thread[impl:3]_3##0#0#Error#1#com.sap.portal.portal#Java###Exception ID:05:50_10/01/05_0004_4818350
    [EXCEPTION]
    #1#com.sapportals.portal.prt.component.PortalComponentException: Error in service call of Resource
    Component : pcd:portal_content/HistPerf
    Component class : com.maxager.pct.profitanalysis.HistoricalPerformance
    User : Administrator
         at com.sapportals.portal.prt.core.PortalRequestManager.handlePortalComponentException(PortalRequestManager.java:969)
         at com.sapportals.portal.prt.core.PortalRequestManager.dispatchRequest(PortalRequestManager.java:444)
         at com.sapportals.portal.prt.core.PortalRequestManager.dispatchRequest(PortalRequestManager.java:527)
         at com.sapportals.portal.prt.component.AbstractComponentResponse.include(AbstractComponentResponse.java:89)
         at com.sapportals.portal.prt.component.PortalComponentResponse.include(PortalComponentResponse.java:232)
         at com.maxager.pct.profitanalysis.HistoricalPerformance.doContent(HistoricalPerformance.java:36)
         at com.sapportals.portal.prt.component.AbstractPortalComponent.serviceDeprecated(AbstractPortalComponent.java:209)
         at com.sapportals.portal.prt.component.AbstractPortalComponent.service(AbstractPortalComponent.java:114)
         at com.sapportals.portal.prt.core.PortalRequestManager.callPortalComponent(PortalRequestManager.java:328)
         at com.sapportals.portal.prt.core.PortalRequestManager.dispatchRequest(PortalRequestManager.java:136)
         at com.sapportals.portal.prt.core.PortalRequestManager.dispatchRequest(PortalRequestManager.java:189)
         at com.sapportals.portal.prt.component.PortalComponentResponse.include(PortalComponentResponse.java:215)
         at com.sapportals.portal.prt.pom.PortalNode.service(PortalNode.java:627)
         at com.sapportals.portal.prt.core.PortalRequestManager.callPortalComponent(PortalRequestManager.java:328)
         at com.sapportals.portal.prt.core.PortalRequestManager.dispatchRequest(PortalRequestManager.java:136)
         at com.sapportals.portal.prt.core.PortalRequestManager.dispatchRequest(PortalRequestManager.java:189)
         at com.sapportals.portal.prt.core.PortalRequestManager.runRequestCycle(PortalRequestManager.java:753)
         at com.sapportals.portal.prt.connection.ServletConnection.handleRequest(ServletConnection.java:232)
         at com.sapportals.portal.prt.dispatcher.Dispatcher$doService.run(Dispatcher.java:522)
         at java.security.AccessController.doPrivileged(Native Method)
         at com.sapportals.portal.prt.dispatcher.Dispatcher.service(Dispatcher.java:405)
         at javax.servlet.http.HttpServlet.service(HttpServlet.java:853)
         at com.sap.engine.services.servlets_jsp.server.servlet.InvokerServlet.service(InvokerServlet.java:153)
         at javax.servlet.http.HttpServlet.service(HttpServlet.java:853)
         at com.sap.engine.services.servlets_jsp.server.HttpHandlerImpl.runServlet(HttpHandlerImpl.java:385)
         at com.sap.engine.services.servlets_jsp.server.HttpHandlerImpl.handleRequest(HttpHandlerImpl.java:263)
         at com.sap.engine.services.httpserver.server.RequestAnalizer.startServlet(RequestAnalizer.java:337)
         at com.sap.engine.services.httpserver.server.RequestAnalizer.startServlet(RequestAnalizer.java:315)
         at com.sap.engine.services.httpserver.server.RequestAnalizer.invokeWebContainer(RequestAnalizer.java:815)
         at com.sap.engine.services.httpserver.server.RequestAnalizer.handle(RequestAnalizer.java:238)
         at com.sap.engine.services.httpserver.server.Client.handle(Client.java:92)
         at com.sap.engine.services.httpserver.server.Processor.request(Processor.java:147)
         at com.sap.engine.core.service630.context.cluster.session.ApplicationSessionMessageListener.process(ApplicationSessionMessageListener.java:37)
         at com.sap.engine.core.cluster.impl6.session.UnorderedChannel$MessageRunner.run(UnorderedChannel.java:71)
         at com.sap.engine.core.thread.impl3.ActionObject.run(ActionObject.java:37)
         at java.security.AccessController.doPrivileged(Native Method)
         at com.sap.engine.core.thread.impl3.SingleThread.execute(SingleThread.java:94)
         at com.sap.engine.core.thread.impl3.SingleThread.run(SingleThread.java:151)
    Caused by: com.sapportals.portal.prt.component.PortalComponentException: Cannot find JSP file: JSPFileInfo :19082348
    JSP File : D:
    usr
    sap
    P66
    JC00
    j2ee
    cluster
    server0
    apps
    sap.com
    irj
    servlet_jsp
    irj
    root
    WEB-INF
    portal
    portalapps
    ProfitAnalysis
    jsp
    maxager.jsp?id=1&username=maxager&password=maxager
    Class Name: sapportalsjspmaxager
    Java File : D:
    usr
    sap
    P66
    JC00
    j2ee
    cluster
    server0
    apps
    sap.com
    irj
    servlet_jsp
    irj
    root
    WEB-INF
    portal
    portalapps
    ProfitAnalysis
    work
    jsp
    _sapportalsjsp_maxager.java
    Package Name : jsp
    Class File : D:
    usr
    sap
    P66
    JC00
    j2ee
    cluster
    server0
    apps
    sap.com
    irj
    servlet_jsp
    irj
    root
    WEB-INF
    portal
    portalapps
    ProfitAnalysis
    work
    jsp
    _sapportalsjsp_maxager.class
    Is out dated : true
         at com.sapportals.portal.prt.core.broker.JSPComponentItem.getComponentInstance(JSPComponentItem.java:96)
         at com.sapportals.portal.prt.core.broker.PortalComponentItemFacade.service(PortalComponentItemFacade.java:355)
         at com.sapportals.portal.prt.core.broker.PortalComponentItem.service(PortalComponentItem.java:931)
         at com.sapportals.portal.prt.core.PortalRequestManager.dispatchRequest(PortalRequestManager.java:435)
         ... 36 more

    Hi Ravi,
    please check if the JSP files (JSP / Java / Class) are where they are expected (paths are given in the error msg).
    Also check Got a Portal runtime error while using JSPDynepage
    Hope it helps
    Detlev

  • Does jsp in OAS 4.0.8.1 supports Multiple Language?

    Hi,
    I've tried using encoding=Big5 for chinese rendering but it throws an UnsupportedEncodingException. Any idea if jsp in OAS supports this?
    Thanks.
    regards,
    Hong Seng

    I don't know. However here is more information for you. JSP requires you specify the page encoding using the IANA character set names. Java APIs require its own (JSDK) character set names. To work correctly JSPs must map the IANA name to a JSDK name. OJSP uses the sun.io.CharacterEncoding CharacterEncoding.aliasName() method to translate. It is entirely possible this method doesn't support your mapping/name. I would suggest you write some code that runs outside of JSP to determine what mapping this method supports.

  • JSP 2.0 as JSF component encoders - continued

    This is in continuation to this topic:
    http://forum.java.sun.com/thread.jsp?forum=427&thread=414850&tstart=15&trange=15
    As I look further into JSP 2.0, I am more and more sold to the idea of encoding JSF components thru JSP 2.0 tag files and/or SimpleTag handlers ...
    Like, I was trying to figure out how could I derive the functionality of JSF facets from JSP tags - and the answer was amazingly straightforward - fragment attributes ... the tag could treat the fragments as facets while evaluating the body with its normal course ...
    If the benefits of tag files/simple tag handlers are felt among the JSF team, I was wondering if the tag file/simple tag handler could be made part of the JSF rendererType paradigm?
    I was wondering if it were a feasible idea to work in encoder-decoder pairs? The declarations in faces-config.xml for the renderers could be something along these lines:
    If the encoding was with a simple tag handler:
    <render-kit>
      <renderer>
        <renderer-type>Component1Renderer</renderer-type>
        <decoder>decoder.Component1Decoder</decoder>
        <encoder type="SimpleTagHandler">encoder.Component1EncoderTag</encoder>
      </renderer>
    </render-kit>
    If the encoding was with a tag file:
    <render-kit>
      <renderer>
        <renderer-type>Component1Renderer</renderer-type>
        <decoder>decoder.Component1Decoder</decoder>
        <encoder type="TagFile">/WEB-INF/tags/component1Encoder.tag</encoder>
      </renderer>
    </render-kit>
    The above may all be very far fetched but I thought I'd just put across what I had in mind.
    Thanks!

    This is in continuation to this topic:
    http://forum.java.sun.com/thread.jsp?forum=427&thread=4
    4850&tstart=15&trange=15
    As I look further into JSP 2.0, I am more and more
    sold to the idea of encoding JSF components thru JSP
    2.0 tag files and/or SimpleTag handlers ...
    As has been pointed out by others, this isn't feasible at all unless JavaServer Faces were to choose JSP 2.0 as the minimum platform. However, even if that were to happen, there are some crucial problems in at least two dimensions:
    * JavaServer Faces integrates nicely with JSP, but does not
    require it. Therefore, the encoding functionality of a
    component (or renderer) needs to operate correctly even for
    a non-JSP rendering environment. How can that be reconciled
    with a desire to use JSP-specific rendering capabilities?
    * JSP 2.0 is very cool, but it doesn't deal at all with the
    issue of handling an incoming request. Therefore,
    a solution that uses JSP as a templating environment (which
    violates the "don't require JSP requirement as mentioned in
    the previous paragraph"), will STILL require some non-JSP
    functionality to do the decoding, validation, and event handling
    parts of the application. To me, it does NOT seem like forcing
    component writers to master two technologies (instead of one)
    would make JavaServer Faces easier to use.
    Implementation technology aside, the logic of decoding (what request parameters do I look at?) is very tightly coupled with the logic of encoding (what markup do I generate?). Splitting those two aspects of the problem into different source files, implemented with different technologies, and requiring changes in both placeds when you make changes, seems like something that goes against all the best practices design principles we've all been learning over the past several decades.
    If JSP had a way to express the functional logic needed for handling events, validations, and calls to business logic, I might be more sympathetic to this approach -- but it doesn't. It is also interesting to note that Struts (among many other frameworks) has embedded markup generation for user interface components in Java logic (in the case of Struts, it's in the HTML tag library) from the very beginning. Why should it be OK there (and 75,000 downloads per month says it's pretty popular) and not in JavaServer Faces?
    Further, why should a page author that is just using components give a rip what the implementation technology is? Isn't that a concern solely of the component writer? I would contend that anyone who builds a non-trivial component, in any technology framework, is going to need functional programming knowledge (be it Java, VB, C#, some XML-based variant, JavaScript, whatever) anyway. Rendering is about 20% of the problem -- the 80% that still needs to be solved is going to require programming knowledge anyway. And JSP, even with all the fantastic things added in 2.0, doesn't address any of those needs.
    Craig McClanahan

  • WAR or JSP to serve HTML in a JAR?

    Hi,
    I want to keep a few hundred static help files in a JAR when I install my appliation on the server to ease installation and management. But what is the best way to serve them up? What litle I know about WARs seems to imply I can have HTML files in one and, with the server set up correctly, redirect a URI to find HTML files in there. Is that so? Is there an exmple out there?!
    cheers,
    Chuck

    Hi,
    Thanks, but to be clear, I want to ONLY have HTML files in this WAR. The rest of the appliation's servlets will not be part of this.
    I am simply looking for an easy way to access the HTML files if I JAR them up. Using a WAR, there is no servlet/jsp required to redirect a URL request to an HTML file in the archive, right? What would the web.xml look like, or is it even needed, when there is no JSP associated with the WAR?
    thanks,
    Chuck

  • JSP Programming model for MI application development

    Hi All,
    While we are using JSP programming model for developing MI applications, there are some Pros and Cons for it.
    one of the Cons is :-
    1. JSP requires more system resources ( local web server)
    Any idea what exactly does it means ?
    2. When we use AWT as the programming model, do we need any additional resources to run this application ?
    Thanks and Regards
    Neha Mahanty

    Hi Neha,
    there are two different runtime options in MI - JSP and AWT - that you already mentioned corredtly.
    Depending what dev model you choose, you have to install the related runtime. That is a logical step. Well, if you are aware, JSP pages are displayed in a browser and are hosted on a server. In our case MI client JSP runtime is that server and especially if you run the application on a small device like a PDA, you will see significant performance issues. The screen response time is something around 2-5seconds. this is due to the messages and the processing time of the different components.
    If you use AWT on the other hand, you are running it in the MI AWT client runtime and so all runs as a single application. This has a better screen response time.
    So from this perspective the decision should clearly be the AWT component. BUT!!!
    If you ever have developed an AWT app, you have noticed, that it is not that easy to develop tables for example in AWT. It is possible, but it is getting complex and slow soon. So depending on the complexity of your screens it can be soon, that JSP itself has a faster rendering time then an AWT application. And because JSP screen development is taht simple, most apps are JSP apps at the moment.
    With MI7.1 this will change. You have the possibility to use eSWT and WebDynpro for UI development as well, and so the development of MI applicartions that use les system performance for the runtime itself will be more easy.
    Hope this helps!
    Regards,
    Oliver

  • Another question about import/export to excel file?

    Hi, I need to know urgently if it's possible to import/export excel files from/to JSP with unpredicted number of fields each row. For example, row 1 in the excel file can have 5 columns of data, row 2 has 3 columns of data, etc...
    Does reading from excel file in JSP require that we know beforehand how many columns there are and what each column represent?

    go read http://jakarta.apache.org/poi !!!!!!
    No it doesnt. the POI api provide method to determine the number of cells in a row.

  • LifeCycle DS ES communication with Tomcat WebServer

    Hi,
        I have written a simple program to accept Name using Flex SDK 3.2 HttpService in Flex builder 3. Using LifeCycle DS ES to communicate with struts 1.2 on Web Server(Tomcat 5.0). My flex code runs and Struts code runs independently. The problem is when trying to send data from client to Server, it does not work. Below given are my client ans Server side code. Copy of services-config.xml & proxy-config.xml is same on both client side and server side. Please help me to run this code.
    Client Side
    ========
    hello.mxml
    <?xml version="1.0" encoding="utf-8"?>
    <mx:Application xmlns:mx="http://www.adobe.com/2006/mxml" layout="absolute">
    <mx:Script>
    <![CDATA[
      public function hello1():void{
       HelloCall.send();
    ]]>
    </mx:Script>
    <mx:HTTPService id= "HelloCall" destination= "myHello">
        <mx:request xmlns= " ">
                <name>  {nameInput.text}</name>
        </mx:request>
    </mx:HTTPService>
    <mx:Label x= "312" y= "47" text= "Enter Name" fontSize= "20" />
    <mx:TextInput id= "nameInput" x="260" y= "104" fontSize= "20" />
    <mx:Button x= "301" y= "186" label= "Submit" fontSize= "20" click= "hello1();" />
    <mx:Label x= "312" y= "285" text= "{HelloCall.lastResult.jlc.message}" fontSize= "20" />
    </mx:Application>
    Server-Side
    ============
    proxy-config.xml
    <?xml version="1.0" encoding="UTF-8"?>
    <service id="proxy-service"
        class="flex.messaging.services.HTTPProxyService">
        <properties>
            <connection-manager>
                <max-total-connections>100</max-total-connections>
                <default-max-connections-per-host>2</default-max-connections-per-host>
            </connection-manager>
            <allow-lax-ssl>true</allow-lax-ssl>
        </properties>
        <adapters>
            <adapter-definition id="http-proxy" class="flex.messaging.services.http.HTTPProxyAdapter" default="true"/>
            <adapter-definition id="soap-proxy" class="flex.messaging.services.http.SOAPProxyAdapter"/>
        </adapters>
        <default-channels>
            <channel ref="my-http"/>
            <channel ref="my-amf"/>
        </default-channels>
    <destination id="myHello">
        <properties>
             <url>/http://localhost:8000/JLCAPP/hello.jsp</url>
        </properties>
    </destination>
    </service>
    struts-config.xml
    <?xml version="1.0" encoding="UTF-8"?>
    <!DOCTYPE struts-config PUBLIC "-//Apache Software Foundation//DTD Struts Configuration 1.2//EN" "http://struts.apache.org/dtds/struts-config_1_2.dtd">
    <struts-config> 
      <form-beans>
           <form-bean name= "helloForm" type= "org.apache.struts.action.DynaActionForm">
                  <form-property name= "name" type="java.lang.String" />
           </form-bean>
       </form-beans>
      <global-forwards>
      <forward name= "success" path= "/index.jsp" />
      </global-forwards>
    <action-mappings>
        <action path= "/hello" name= "helloForm" type="com.jlcindia.struts.HelloAction" input= "/hello.html" />
    </action-mappings>
      <message-resources parameter="com.jlcindia.struts.ApplicationResources" />
    </struts-config>
    services-config.xml
    <?xml version="1.0" encoding="UTF-8"?>
    <services-config>
        <services>
            <service-include file-path="remoting-config.xml" />
            <service-include file-path="proxy-config.xml" />
            <service-include file-path="messaging-config.xml" />
            <service-include file-path="data-management-config.xml" />
            <service class="fiber.data.services.ModelDeploymentService" id="model-deploy-service" />
            <!--
         Application level default channels. Application level default channels are
         necessary when a dynamic destination is being used by a service component
         and no ChannelSet has been defined for the service component. In that case,
         application level default channels will be used to contact the destination.
            -->  
            <default-channels>
               <channel ref="my-rtmp"/>
            </default-channels>
        </services>
        <security>
      <login-command class="flex.messaging.security.TomcatLoginCommand" server="Tomcat"/>       
            <!-- Uncomment the correct app server
            <login-command class="flex.messaging.security.JRunLoginCommand" server="JRun"/>
            <login-command class="flex.messaging.security.WeblogicLoginCommand" server="Weblogic"/>
            <login-command class="flex.messaging.security.WebSphereLoginCommand" server="WebSphere"/>
            -->
            <security-constraint id="basic-read-access">
                <auth-method>Basic</auth-method>
                <roles>
                    <role>guests</role>
                    <role>accountants</role>
                    <role>employees</role>
                    <role>managers</role>
                </roles>
            </security-constraint>
        </security>
        <!-- Socket servers that NIO endpoints all share -->
        <servers>
            <server id="my-nio-server" class="flex.messaging.socketserver.SocketServer">
            </server>
            <!--
            <server id="secure-nio-server" class="flex.messaging.socketserver.SocketServer">
                <properties>
                    <keystore-file>{context.root}/WEB-INF/flex/localhost.keystore</keystore-file>
                    <keystore-password>changeit</keystore-password>
                </properties>
            </server>
            -->
        </servers>
        <channels>
            <!-- Servlet Based endpoints -->
            <channel-definition id="my-amf" class="mx.messaging.channels.AMFChannel">
                <endpoint url="http://localhost:8400/JLCAPP/messagebroker/amf" class="flex.messaging.endpoints.AMFEndpoint"/>
                <properties>
                    <polling-enabled>false</polling-enabled>
                </properties>
            </channel-definition>
            <channel-definition id="my-polling-amf" class="mx.messaging.channels.AMFChannel">
                <endpoint url="http://localhost:8400/JLCAPP/messagebroker/amfpolling" class="flex.messaging.endpoints.AMFEndpoint"/>
                <properties>
                    <polling-enabled>true</polling-enabled>
                    <polling-interval-seconds>8</polling-interval-seconds>
                </properties>
            </channel-definition>
            <channel-definition id="my-http" class="mx.messaging.channels.HTTPChannel">
                <endpoint url="http://{server.name}:{server.port}/{context.root}/messagebroker/http" class="flex.messaging.endpoints.HTTPEndpoint"/>
            </channel-definition>
            <!-- Secure Servlet-based endpoints -->
            <channel-definition id="my-secure-amf" class="mx.messaging.channels.SecureAMFChannel">
                <endpoint url="https://{server.name}:{server.port}/{context.root}/messagebroker/amfsecure" class="flex.messaging.endpoints.SecureAMFEndpoint"/>
                <properties>
                    <!--HTTPS requests on some browsers do not work when pragma "no-cache" are set-->
                    <add-no-cache-headers>false</add-no-cache-headers>
                </properties>
            </channel-definition>
            <channel-definition id="my-secure-http" class="mx.messaging.channels.SecureHTTPChannel">
                <endpoint url="https://{server.name}:{server.port}/{context.root}/messagebroker/httpsecure" class="flex.messaging.endpoints.SecureHTTPEndpoint"/>
                <properties>
                 <!--HTTPS requests on some browsers do not work when pragma "no-cache" are set-->
                    <add-no-cache-headers>false</add-no-cache-headers>
                </properties>
            </channel-definition>
            <!-- NIO based endpoints -->
            <channel-definition id="my-rtmp" class="mx.messaging.channels.RTMPChannel">
                <endpoint url="rtmp://{server.name}:2048" class="flex.messaging.endpoints.RTMPEndpoint"/>
                <properties>
                    <idle-timeout-minutes>20</idle-timeout-minutes>
                    <!-- for deployment on WebSphere, must be mapped to a WorkManager available in the web application's jndi context.
                    <websphere-workmanager-jndi-name>java:comp/env/wm/MessagingWorkManager</websphere-workman ager-jndi-name>
                    -->
                </properties>
            </channel-definition>
            <channel-definition id="my-nio-amf" class="mx.messaging.channels.AMFChannel">
                <endpoint url="http://{server.name}:2888/nioamf" class="flex.messaging.endpoints.NIOAMFEndpoint"/>
                <server ref="my-nio-server"/>
                <properties>
                    <polling-enabled>false</polling-enabled>
                </properties>
            </channel-definition>
            <channel-definition id="my-nio-amf-poll" class="mx.messaging.channels.AMFChannel">
                <endpoint url="http://{server.name}:2888/nioamfpoll" class="flex.messaging.endpoints.NIOAMFEndpoint"/>
                <server ref="my-nio-server"/>
                <properties>
                    <polling-enabled>true</polling-enabled>
                    <polling-interval-millis>3000</polling-interval-millis>
                </properties>
            </channel-definition>
            <channel-definition id="my-nio-http" class="mx.messaging.channels.HTTPChannel">
                <endpoint url="http://{server.name}:2888/niohttp" class="flex.messaging.endpoints.NIOHTTPEndpoint"/>
                <server ref="my-nio-server"/>
                <properties>
                    <polling-enabled>false</polling-enabled>
                </properties>
            </channel-definition>
            <!-- Secure NIO based endpoints -->
            <!--
            <channel-definition id="secure-nio-amf" class="mx.messaging.channels.SecureAMFChannel">
                <endpoint url="https://{server.name}:2443/securenioamf" class="flex.messaging.endpoints.SecureNIOAMFEndpoint"/>
                <server ref="secure-nio-server"/>
                <properties>
                    <polling-enabled>false</polling-enabled>
                </properties>
            </channel-definition>
            <channel-definition id="secure-nio-http" class="mx.messaging.channels.SecureHTTPChannel">
                <endpoint url="https://{server.name}:2443/secureniohttp" class="flex.messaging.endpoints.SecureNIOHTTPEndpoint"/>
                <server ref="secure-nio-server"/>
                <properties>
                    <polling-enabled>false</polling-enabled>
                </properties>
            </channel-definition>
            -->
        </channels>
        <logging>
            <target class="flex.messaging.log.ConsoleTarget" level="Debug">
                <properties>
                    <prefix>[LCDS] </prefix>
                    <includeDate>false</includeDate>
                    <includeTime>false</includeTime>
                    <includeLevel>false</includeLevel>
                    <includeCategory>false</includeCategory>
                </properties>
                <filters>
                    <pattern>Endpoint.*</pattern>
                    <pattern>Service.*</pattern>
                    <pattern>Configuration</pattern>
                    <pattern>SocketServer.*</pattern>
                </filters>
            </target>
        </logging>
        <system>
            <redeploy>
                <enabled>true</enabled>
                <watch-interval>20</watch-interval>
                <watch-file>{context.root}/WEB-INF/flex/services-config.xml</watch-file>
                <watch-file>{context.root}/WEB-INF/flex/proxy-config.xml</watch-file>
                <watch-file>{context.root}/WEB-INF/flex/remoting-config.xml</watch-file>
                <watch-file>{context.root}/WEB-INF/flex/messaging-config.xml</watch-file>
                <watch-file>{context.root}/WEB-INF/flex/data-management-config.xml</watch-file>
                <touch-file>{context.root}/WEB-INF/web.xml</touch-file>
            </redeploy>
        </system>
    </services-config>
    HelloAction.java
    package com.jlcindia.struts;
    import javax.servlet.http.HttpServletRequest;
    import javax.servlet.http.HttpServletResponse;
    import org.apache.struts.action.*;
    import org.apache.struts.action.ActionForm;
    import org.apache.struts.action.ActionForward;
    import org.apache.struts.action.ActionMapping;
    import org.apache.struts.action.DynaActionForm;
    import java.io.PrintWriter;
    public class HelloAction extends Action{
    public ActionForward execute(ActionMapping am,ActionForm af,HttpServletRequest req,HttpServletResponse res) throws Exception {
        System.out.println("Hi am here");
        DynaActionForm daf= (DynaActionForm)af;
        String name= daf.get("name").toString();
        String msg= "Hello!"+ name + "Welcome to JLC FLex LCDS with HttpService";
        res.setContentType("text/html");
        PrintWriter out= res.getWriter();
        out.println("<message>" + msg + "</message>");
        out.close();
        return am.findForward("success");
    Any Help will be appriciated.

    Hi Rohit,
    I am running both LiveCycle DS ES 3.0 and WebServer Tomcat on the same machine. I made changes in services-congig.xml and now the channels are configured as follows on both client end and server end :-
    services-config.xml
       <!-- Servlet Based endpoints -->
            <channel-definition id="my-amf" class="mx.messaging.channels.AMFChannel">
                <endpoint url="http://localhost:8000/JLCAPP/messagebroker/amf" class="flex.messaging.endpoints.AMFEndpoint"/>
                <properties>
                    <polling-enabled>false</polling-enabled>
                </properties>
            </channel-definition>
            <channel-definition id="my-polling-amf" class="mx.messaging.channels.AMFChannel">
                <endpoint url="http://localhost:8000/JLCAPP/messagebroker/amfpolling" class="flex.messaging.endpoints.AMFEndpoint"/>
                <properties>
                    <polling-enabled>true</polling-enabled>
                    <polling-interval-seconds>8</polling-interval-seconds>
                </properties>
            </channel-definition>
            <channel-definition id="my-http" class="mx.messaging.channels.HTTPChannel">
                <endpoint url="http://localhost:8000/JLCAPP/messagebroker/http" class="flex.messaging.endpoints.HTTPEndpoint"/>
            </channel-definition>
    However i am still getting following debug message :-
    [RPC Fault faultString="Send failed" faultCode="Client.Error.MessageSend" faultDetail="Channel.Connect.Failed error NetConnection.Call.Failed: HTTP: Status 404: url:
    'http://localhost:8000/JLCAPP/messagebroker/amf'"]
    at mx.rpc::AbstractInvoker/http://www.adobe.com/2006/flex/mx/internal::faultHandler()[C:\autobuild\3.2.0
    \frameworks\projects\rpc\src\mx\rpc\AbstractInvoker.as:220]
    at mx.rpc::Responder/fault()[C:\autobuild\3.2.0\frameworks\projects\rpc\src\mx\rpc\Responder .as:53]
    at mx.rpc::AsyncRequest/fault()[C:\autobuild\3.2.0\frameworks\projects\rpc\src\mx\rpc\AsyncR equest.as:103]
    at mx.messaging::ChannelSet/faultPendingSends()[C:\autobuild\3.2.0\frameworks\projects\rpc\s rc\mx\messaging\ChannelSet.as:1482]
    at mx.messaging::ChannelSet/channelFaultHandler()[C:\autobuild\3.2.0\frameworks\projects\rpc \src\mx\messaging\ChannelSet.as:975]
    at flash.events::EventDispatcher/dispatchEventFunction()
    at flash.events::EventDispatcher/dispatchEvent()
    at mx.messaging::Channel/connectFailed()[C:\autobuild\3.2.0\frameworks\projects\rpc\src\mx\m essaging\Channel.as:997]
    at mx.messaging.channels::PollingChannel/connectFailed()[C:\autobuild\3.2.0\frameworks\proje cts\rpc\src\mx\messaging\channels\PollingChannel.as:354]
    at mx.messaging.channels::AMFChannel/statusHandler()[C:\autobuild\3.2.0\frameworks\projects\ rpc\src\mx\messaging\channels\AMFChannel.as:390]
    My current hello.jsp code is given below :-
    hello.jsp
    <%@ taglib uri= "/WEB-INF/struts-html.tld" prefix="html" %>
    <html>
    <body>
    <br> <html:form action="/hello.do">
    <h1> Name :  </h1><br/>
    <html:text property ="name" /><br/>
    <html:submit value= "Show" /> <br/>
    </html:form>
    </body>
    </html>
    Is hello.jsp required at server end, as URL specified in proxy-config.xml should directly invoke Action class in my Tomcat WebServer?
    My WebServer Tomcat Server log shows following :-
    [LCDS]Adobe LiveCycle Data Services: 3.0.0.254255
    [LCDS]Server 'my-nio-server' of type 'flex.messaging.socketserver.SocketServer' created.
    [LCDS]Endpoint 'my-nio-amf-poll' created with security: None
    at URL: http://localhost:2888/nioamfpoll
    [LCDS]Endpoint 'my-rtmp' created with security: None
    at URL: rtmp://localhost:2048
    [LCDS]Endpoint 'my-http' created with security: None
    at URL: http://localhost:8000/JLCAPP/messagebroker/http
    [LCDS]Endpoint 'my-polling-amf' created with security: None
    at URL: http://localhost:8000/JLCAPP/messagebroker/amfpolling
    [LCDS]Endpoint 'my-nio-http' created with security: None
    at URL: http://localhost:2888/niohttp
    [LCDS]Endpoint 'my-amf' created with security: None
    at URL: http://localhost:8000/JLCAPP/messagebroker/amf
    [LCDS]Endpoint 'my-nio-amf' created with security: None
    at URL: http://localhost:2888/nioamf
    [LCDS]Endpoint 'my-secure-http' created with security: None
    at URL: https://{server.name}:{server.port}/{context.root}/messagebroker/httpsecure
    [LCDS]Endpoint 'my-secure-amf' created with security: None
    at URL: https://{server.name}:{server.port}/{context.root}/messagebroker/amfsecure
    [LCDS]MessageBroker id: __default__ classLoader is: the MessageBroker's class loader and the context class loader (classLoader hashCode: 31966667 (parent hashCode:
    7043360 (parent system))
    [LCDS]Starting Adobe LiveCycle Data Services: 3.0.0.254255 Developer License
    [LCDS]NIOAMFEndpoint 'my-nio-amf-poll' has started and is using server 'my-nio-server'.
    [LCDS]SocketServer 'my-rtmp-SocketServer' is starting.
    [LCDS]SocketServer 'my-rtmp-SocketServer' is using an assigned executor of type: flex.messaging.util.concurrent.DefaultThreadPoolExecutor
    [LCDS]SocketServer 'my-rtmp-SocketServer' has determined the default thread priority for its executor to be 5.
    [LCDS]Reactor 'Reactor1' for SocketServer 'my-rtmp-SocketServer' is starting.
    [LCDS]Reactor 'Reactor1' for SocketServer 'my-rtmp-SocketServer' has started and is running at priority 5.
    [LCDS]Reactor 'Reactor2' for SocketServer 'my-rtmp-SocketServer' is starting.
    [LCDS]Reactor 'Reactor2' for SocketServer 'my-rtmp-SocketServer' has started and is running at priority 5.
    [LCDS]Acceptor 'Acceptor1' for SocketServer 'my-rtmp-SocketServer' is starting.
    [LCDS]Acceptor 'Acceptor1' for SocketServer 'my-rtmp-SocketServer' has successfully bound '/0.0.0.0:2048' to accept new client connections.
    [LCDS]Acceptor 'Acceptor1' for SocketServer 'my-rtmp-SocketServer' has started and is running at priority 5.
    [LCDS]SocketServer 'my-rtmp-SocketServer' has started.
    [LCDS]NIOHTTPEndpoint 'my-nio-http' has started and is using server 'my-nio-server'.
    [LCDS]NIOAMFEndpoint 'my-nio-amf' has started and is using server 'my-nio-server'.
    [LCDS]SocketServer 'my-nio-server' is starting.
    [LCDS]SocketServer 'my-nio-server' is using an assigned executor of type: flex.messaging.util.concurrent.DefaultThreadPoolExecutor
    [LCDS]SocketServer 'my-nio-server' has determined the default thread priority for its executor to be 5.
    [LCDS]Reactor 'Reactor1' for SocketServer 'my-nio-server' is starting.
    [LCDS]Reactor 'Reactor1' for SocketServer 'my-nio-server' has started and is running at priority 5.
    [LCDS]Reactor 'Reactor2' for SocketServer 'my-nio-server' is starting.
    [LCDS]Reactor 'Reactor2' for SocketServer 'my-nio-server' has started and is running at priority 5.
    [LCDS]Acceptor 'Acceptor1' for SocketServer 'my-nio-server' is starting.
    [LCDS]Acceptor 'Acceptor1' for SocketServer 'my-nio-server' has successfully bound '/0.0.0.0:2888' to accept new client connections.
    [LCDS]Acceptor 'Acceptor1' for SocketServer 'my-nio-server' has started and is running at priority 5.
    [LCDS]SocketServer 'my-nio-server' has started.
    See if this picks the point of failure!!

  • Posted Form contents Problem

    I had this problem with 4.5.1 SP 5 and WebLogic told me it would be
    fixed in 5.1 SP 1 (I believe the issue number was 10214). I've just
    tried my simple test case again with 5.1 SP 3 on NT and it still fails.
    The problem is when text is posted from an HTML form to a servlet in
    WebLogic, WebLogic assumes the posted data is ALWAYS encoded in
    ISO-8859_1. So if your form posts Shift-JIS, WLS still incorrectly
    converts the text to unicode using the ISO8859 code page. The only
    work arround I can find is to take the bad JAVA unicode strings, get the
    bytes with the ISO8859 code page, and then create a new string using
    those bytes and the Shift-JIS code page. This is what the
    fixStringEncoding() method is doing below. This is unacceptable.
    How does the WebLogic server understand how to convert between IANA
    encodings and JAVA encodings when receiving a response? A browser will
    encode the form contents with the same encoding as the HTML page with
    the form is in. How does WLS know when it recieves the response to use
    SJIS (Java encoding) to convert Shift-JIS (IANA) encoded text to
    unicode? My test JSP page is included below. It's form that accepts
    Japanese text and posts it back to itself for display. If I don't "fix"
    the JAVA strings, the Japanese text comes out as garbage. BTW, I have
    verified that I'm using SP 3 correctly. Thanks.
    Kirk Everett
    <%@ page contentType="text/html; charset=Shift-JIS"%>
    <html>
    <head>
    <title></title>
    <meta http-equiv="content-type" content="text/html; charset=Shift-JIS">
    <meta http-equiv="expires" content="0">
    <meta http-equiv="pragma" content="no-cache">
    </head>
    <body>
    <form name="Dummy" action="dummySJIS.jsp" method="post">
    <table>
    <tr>
    <td align="right">DummyString:</td>
    <td><input type="text" name="dummy" size="30"
    maxlength="50"></td>
    </tr>
    </table>
    <input type="submit" value="submit">
    </form>
    <BR>
    DummyString with fixing= <%=
    fixStringEncoding(request.getParameter("dummy")) %>
    <BR>
    DummyString without fixing = <%= request.getParameter("dummy") %>
    <BR>
    Embedded (Shitf-JIS) Japanese --> ?X?V‚É?¬Œ÷‚µ‚Ü‚µ‚½?B
    </body>
    </html>
    <%!
    public String fixStringEncoding(String sourceString)
    String targetEncoding = "SJIS";
    String convertedString = null;
    if(sourceString != null)
    // get the array of bytes for the unicode string using the
    // 8859_1 code page
    try
    byte[] stringBytes = sourceString.getBytes("ISO8859_1");
    // now create a new string based of the array but do it
    // with the correct code page UTF8
    convertedString = new String(stringBytes, targetEncoding);
    catch(UnsupportedEncodingException uee)
    convertedString = "";
    return convertedString;
    %>

    The jsp directive does nothing to help the INPUT data handling. On the other hand, this is a html spec problem, not a weblogic one. RFC2070 has some recommendation on how to do i18n with HTML/HTTP, but neither Netscape nor IE supports it.
    --Ye
    Joseph Weinstein <[email protected]> wrote:
    Hi,
    The ideal approach is to employ the JSP directive for encoding.
    This is documented in the JSP spec. Also, if all your JSPs
    require the same encoding, there is an argument to our JSP
    servlet, to tell it what default charset encoding to use.
    Joe
    Kirk Everett wrote:
    I had this problem with 4.5.1 SP 5 and WebLogic told me it would be
    fixed in 5.1 SP 1 (I believe the issue number was 10214). I've just
    tried my simple test case again with 5.1 SP 3 on NT and it still fails.
    The problem is when text is posted from an HTML form to a servlet in
    WebLogic, WebLogic assumes the posted data is ALWAYS encoded in
    ISO-8859_1. So if your form posts Shift-JIS, WLS still incorrectly
    converts the text to unicode using the ISO8859 code page. The only
    work arround I can find is to take the bad JAVA unicode strings, get the
    bytes with the ISO8859 code page, and then create a new string using
    those bytes and the Shift-JIS code page. This is what the
    fixStringEncoding() method is doing below. This is unacceptable.
    How does the WebLogic server understand how to convert between IANA
    encodings and JAVA encodings when receiving a response? A browser will
    encode the form contents with the same encoding as the HTML page with
    the form is in. How does WLS know when it recieves the response to use
    SJIS (Java encoding) to convert Shift-JIS (IANA) encoded text to
    unicode? My test JSP page is included below. It's form that accepts
    Japanese text and posts it back to itself for display. If I don't "fix"
    the JAVA strings, the Japanese text comes out as garbage. BTW, I have
    verified that I'm using SP 3 correctly. Thanks.
    Kirk Everett
    <%@ page contentType="text/html; charset=Shift-JIS"%>
    <html>
    <head>
    <title></title>
    <meta http-equiv="content-type" content="text/html; charset=Shift-JIS">
    <meta http-equiv="expires" content="0">
    <meta http-equiv="pragma" content="no-cache">
    </head>
    <body>
    <form name="Dummy" action="dummySJIS.jsp" method="post">
    <table>
    <tr>
    <td align="right">DummyString:</td>
    <td><input type="text" name="dummy" size="30"
    maxlength="50"></td>
    </tr>
    </table>
    <input type="submit" value="submit">
    </form>
    <BR>
    DummyString with fixing= <%=
    fixStringEncoding(request.getParameter("dummy")) %>
    <BR>
    DummyString without fixing = <%= request.getParameter("dummy") %>
    <BR>
    Embedded (Shitf-JIS) Japanese --> ?X?V&#8218;É?¬&#338;÷&#8218;µ&#8218;Ü&#8218;µ&#8218;½?B
    </body>
    </html>
    <%!
    public String fixStringEncoding(String sourceString)
    String targetEncoding = "SJIS";
    String convertedString = null;
    if(sourceString != null)
    // get the array of bytes for the unicode string using the
    // 8859_1 code page
    try
    byte[] stringBytes = sourceString.getBytes("ISO8859_1");
    // now create a new string based of the array but do it
    // with the correct code page UTF8
    convertedString = new String(stringBytes, targetEncoding);
    catch(UnsupportedEncodingException uee)
    convertedString = "";
    return convertedString;
    %>--
    PS: Folks: BEA WebLogic is in S.F. with both entry and advanced positions for
    people who want to work with Java and E-Commerce infrastructure products. Send
    resumes to [email protected]
    The Weblogic Application Server from BEA
    JavaWorld Editor's Choice Award: Best Web Application Server
    Java Developer's Journal Editor's Choice Award: Best Web Application Server
    Crossroads A-List Award: Rapid Application Development Tools for Java
    Intelligent Enterprise RealWare: Best Application Using a Component Architecture
    http://www.bea.com/press/awards_weblogic.html

  • Looking for ANY version of RTS to download...

    Looking for ANY version of RTS to download and I can't find it ANYWHERE. Can someone help????
    Rob

    935741 wrote:
    I don't need just any version, but a RT java vm for desktop applications, such as the Java RTS platform.[url http://java.sun.com/javase/technologies/realtime/faq.jsp#8]We have no plans to support Windows XP or Vista at this time as real-time behavior is not well expressed in those systems.
    So, if you want RT on a desktop, drop Windows and install Linux.
    [url http://java.sun.com/javase/technologies/realtime/index.jsp#requirements]Java RTS Minimum Recommended System Requirements
    Although I am not sure it will guarantee RT once you install a desktop on top of Linux.

  • Difference between web server and webcontainer

    Hai all,As i am new to the servlet technology, I am confused with the terminology of webserver and webcontainer. Can anyone tell me the clear difference between these both?
    Thanks in advance

    A web server refers to a server which normally listens at port 80 and serves up html pages, images, etc... The html pages are usually static pages unless they contain JavaScript. An application which uses servlets and jsps requires an application server such as Tomcat, WebSphere, WebLogic, etc.... These application servers include a "web container". Basically the "web container" is software which implements the "servlet contract". If you look at the api documentation for javax.servlet and javax.servlet.http, you will see that the most important objects (e.g. ServletRequest, ServletResponse, Servlet, HttpSession, etc...) are interfaces not classes. The reason for this is that each application server implements its own classes which implement these interfaces.

  • Designing Web applications for better performance

    Hi,
    Let me explain the scenario.
    We are following MVC architecture, where we have our JSP pages interacting with a controller
    servlet , which decides what action to performed . It is using request despatcher method to redirect
    the request object to jsp pages.
    We have most of jsp pages as entry screens. We are not using java beans, fearing the complexity of master
    details forms . ( we dont know how to use "bean technolagy" in case of detail entry screens).
    In forms at a time we can have max 50 rows , with each row having 10 columns. When a particular page
    need to be displayes for editing (may be with already existing data), the servlet will populate objects
    and jsp will access data from these objects. Once the data is accessed , these objects will be removed
    from the session.
    Since we are removing the objects from the session (not keeping it certain amount of time too), if the
    servlet /another jsp requires some information, we are forced to use "hidden variables". In the current
    scenario, we are having at least 40-50 hidden variables passing from a jsp page to servlet.
    We decided not to use session objects fearing that it will give lot of problem to server. But now it
    is making our client "fat".
    Eventhogh our application is big, we are not using any database side coding like triggers,stored procedures
    etc? Is this create performance problems?
    When our application runs, many times we can find that the request will not get processed correctly
    in jrun sever or some times we gets blank window or some time jrun default server hangs.
    we are using Jrun 3.0 and Solaris_JDK_1.2.2_05.
    Pl. find my following questions.
    1. is this right way to do the things (hidden variables).
    2. Is creating session variables is going to hamper the performance of the system?

    Dear sandhyavk,
    From my experience, you are better to put your hidden values into a JavaBean, simply a data object which is saved in a session, after you have accessed to it, you simply invalidate the session indeed. You can find more details from the following links from javaworld.com, I have adopted and amended it for my eIPO system, it is flexible and easy to maintain and understand.
    * http://www.javaworld.com/javaworld/jw-01-2001/jw-0119-jspframe.html
    * http://www.javaworld.com/javaworld/jw-01-2001/jw-0119-jspframe.html
    I do hope that it can give you some ideas.
    Best regards,
    Anthony Lai

Maybe you are looking for