JSF 1.2 on Websphere 6.1

We have an application which uses JSF 1.2. It works fine on Tomcat, but when we want to deploy it on Websphere 6.1, it fails.
I've done some research on the internet and I was wondering if it's even possible to do this. We added a shared library to the server and make sure the classloading was correct. The problem still persists. I've found something on the net which stated that JSF 1.2 needs an application server who meets the JEE5 specificiations, which Websphere 6.1 doesn't.
Anybody else tried this? Because it's very urgent :-/.

If I recall correctly WAS 6.1 just supports Servlet 2.5 / JSP 2.1. You must be doing something wrong. E.g. having some old versioned JAR's spreading out over the classpath which took preference in classloading. It would be helpful if you elaborate a bit more about "it fails".

Similar Messages

  • How to adapt Marty Hall's jsf-blank project to WebSphere 7?

    Marty Hall had a great idea for getting your feet wet in JSF2: He provides a project named jsf-blank that you deploy in Eclipse on a Tomcat container.
    In 10 minutes you are running a JSF 2 project!
    How can I deploy this jsf-blank project on WebSphere 7? I tried a quick-and-dirty, but it seems to fail on mapping.
    Thanks
    Eli

    How can I deploy this jsf-blank project on WebSphere 7?There just isn't an easy way out. The project should deploy with no problems of Websphere is truly compliant - if something fails then you have no choice but to try and figure out what exactly it is that Websphere doesn't like about the deployed application. It might be a configuration issue, it might be a JVM issue, it might be a rights issue, who knows.
    If you want further help then you might want to try and post the errors you are getting.

  • How to include page fragment for JSF application deployed on WebSphere?

    Hi all,
    I have the following urgent JSF problem, I hope that you can support me in solving it;
    - I have JSF application need to be deployed on IBM WebSphere 6.0.1 Application Server.
    - I have the tag:
    <jsp:directive.include file="Actions.jspf"/>
    which includes a page fragment.
    - This is working file with Tomcat 5.5 & Sun Application Server 9, but it didn't work on WebSphere and each time the page fragment contents rendered as text, I mean that the JSF components in the fragment doesn't converted to html controls.
    Please help...
    Message was edited by:
    AHmadQ

    We use:
    <%@ include file="../WEB-INF/jspf/head.jspf" %>where the head.jspf is a jsp fragment like:
    <% response.addHeader("Cache-Control", "no-cache"); %>
    <% response.addHeader("Pragma", "no-cache"); %>
    <% response.addIntHeader("Expires", -1); %>
    <html>
    <head>
         <meta http-equiv="Content-Type" content="text/html; charset=ISO-8859-1">
         <meta http-equiv="Pragma" content="no-cache" />
         <meta http-equiv="Expires" content="-1" />
         <title><%= pageTitle %></title>
         <link href="../style/style.css" rel="stylesheet" type="text/css" />
    </head>Cheers,
    Illu

  • JSF connect ODBC by WEBSPHERE

    hi
    i have created a jsf project,it's simple,but now i want to do a connect to my database with bridge ODBC-JDBC.
    i create a class:
    import java.sql.*;
    import sun.jdbc.odbc.*;
    public class Connect {
         private Statement stmt;
         private String url;
         private ResultSet rs;
         private Connection con;
         Connect(){
                           try
                                         Class.forName("sun.jdbc.odbc.JdbcOdbcDriver");
                                          url = "jdbc:odbc:scrutinio";
                                          con = DriverManager.getConnection (url,"dba","sql");
                                          stmt = con.createStatement();
                                     catch (ClassNotFoundException e)
                                          e.printStackTrace();
                                     } catch (SQLException e) {
                                          e.printStackTrace();
              public Statement getStatement()
                   return stmt;
    }now in my backbean i call getStatement()(i try a login web ):
    import java.sql.*;
    import sun.*;
    public class BackLogin {
         private String Nome;
         private String Password;
         private Statement stmt;
         private ResultSet rs;
        public void setNome(String Nome){
             this.Nome=Nome;
         public void setPSW(String PSW){
                 this.Password=PSW;
         public String getNome(){
                 return Nome;
            public String getPSW(){
                     return Password;
         public String id_Login(){
           Connect cn=new Connect();
              stmt=cn.getStatement();
              try {
                   rs=stmt.executeQuery("SELECT CODICE,password FROM SECURITY_UTENTI");
                while(rs.next()){
                     if((rs.getString(1).equalsIgnoreCase(Nome))&&(rs.getString(2).equalsIgnoreCase(Password)))
                    return "success";
              } catch (SQLException e) {
                   e.printStackTrace();
              return "failure";
    }but the console return:
    [03/03/05 13.45.00:281 CET] 560ebb9c WebGroup I SRVE0180I: [ArgoNet1.0] [ArgoNet1.0] [Servlet.LOG]: /login.jsp: init
    [03/03/05 13.45.07:531 CET] 5271fb9c SystemErr R java.lang.ClassNotFoundException: sun.jdbc.odbc.JdbcOdbcDriver
    please can we help me?

    my error isn't in compilation but it is in run-time

  • Running Oracle Reports from JSF Application in Websphere Application Server

    Hi everybody;
    in our company we are developing jsf applications and we want to use our existing Oracle reports. Reports are deployed in Oracle Application Server 10G. Is there a way to call those reports from our jsf applications deployed in websphere application server.

    Calling reports is just constructing and submitting a URL. So constuct the url in your jsf app or create static hyperlinks in your jsf app to go to the needed url. The url should look something like:
    http ://hostname:7777/reports/rwservlet?report=myrep.jsp&userid=scott/tiger@dev10g&desformat=html&destype=cache

  • JSF 2.0 pages are not compiled.

    Eventually I managed to define a shared library of JSF 2.0 in Websphere 7.0.0.0 and make it loaded when my application starts. But I was that the JSF code has not been compiled to html so that it can be viewed on a browser. This the code on my page
    <?xml version="1.0" encoding="UTF-8" ?>
    <!-- jsf:pagecode language="java" location="/src/pagecode/Login.java" --><!-- /jsf:pagecode -->
    <!DOCTYPE html PUBLIC "-//W3C//DTD XHTML 1.1//EN" "http://www.w3.org/TR/xhtml11/DTD/xhtml11.dtd">
    <html xmlns="http://www.w3.org/1999/xhtml"
         xmlns:ui="http://java.sun.com/jsf/facelets"
         xmlns:f="http://java.sun.com/jsf/core"
         xmlns:h="http://java.sun.com/jsf/html">
    <h:head>
         <title>login</title>
         <meta http-equiv="Content-Type"
              content="application/xhtml+xml; charset=UTF-8" />
         <link rel="stylesheet" type="text/css" title="Style"
              href="theme/stylesheet.css" />
    </h:head>
    <h:body>
         <h:form styleClass="form" id="form1">
              <h:outputText value="hello"/>
         </h:form>
    </h:body>
    </html>even though the response has to be like
    hello
    it shows the entire code of the page on the browser as
    <?xml version="1.0" encoding="UTF-8" ?>
    <!-- jsf:pagecode language="java" location="/src/pagecode/Login.java" --><!-- /jsf:pagecode -->
    <!DOCTYPE html PUBLIC "-//W3C//DTD XHTML 1.1//EN" "http://www.w3.org/TR/xhtml11/DTD/xhtml11.dtd">
    <html xmlns="http://www.w3.org/1999/xhtml"
         xmlns:ui="http://java.sun.com/jsf/facelets"
         xmlns:f="http://java.sun.com/jsf/core"
         xmlns:h="http://java.sun.com/jsf/html">
    <h:head>
         <title>login</title>
         <meta http-equiv="Content-Type"
              content="application/xhtml+xml; charset=UTF-8" />
         <link rel="stylesheet" type="text/css" title="Style"
              href="theme/stylesheet.css" />
    </h:head>
    <h:body>
         <h:form styleClass="form" id="form1">
              <h:commandButton type="submit" value="Submit"
                   styleClass="commandButton" id="button1"/>
         </h:form>
    </h:body>
    </html>
    What can I do to shake this issue off. Unfortunately in our organization we have to use RAD 8 and WAS 7.0.0.0. If we used netbeans with Glassfish, we don't face these problems.

    If there is no way to map a schema uri to a physical resource in netbeans, then I'm not sure what can be done.
    We won't be posing the schema to the website until later in the spec development cycle.

  • Connection TimeOut in Websphere App Server.

    Hi,
    I am using JSF with JNDI and WebSphere to get query details. We have set the Connection Pooling Timeout in JNDI DataSource settings in WebSphere to 60 minutes.
    I have attached the Exception Stack Trace for your verification. This is a very serious exception which is hindering us from running any query that is running more than 10 minutes. Please suggest.
    Exception = com.ibm.wsspi.webcontainer.ClosedConnectionException
    Source = com.ibm.ws.webcontainer.srt.BufferedWriter.writeOut
    probeid = 416
    Stack Dump = com.ibm.wsspi.webcontainer.ClosedConnectionException: OutputStream encountered error during write
         at com.ibm.ws.webcontainer.channel.WCCByteBufferOutputStream.write(WCCByteBufferOutputStream.java:108)
         at com.ibm.ws.webcontainer.srt.SRTOutputStream.write(SRTOutputStream.java:96)
         at sun.nio.cs.StreamEncoder$ConverterSE.implFlushBuffer(StreamEncoder.java:293)
         at sun.nio.cs.StreamEncoder$ConverterSE.implFlush(StreamEncoder.java:299)
         at sun.nio.cs.StreamEncoder.flush(StreamEncoder.java:210)
         at java.io.OutputStreamWriter.flush(OutputStreamWriter.java:236)
         at com.ibm.wsspi.webcontainer.util.BufferedWriter.writeOut(BufferedWriter.java:486)
         at com.ibm.wsspi.webcontainer.util.BufferedWriter.flushChars(BufferedWriter.java:372)
         at com.ibm.wsspi.webcontainer.util.BufferedWriter.flush(BufferedWriter.java:347)
         at java.io.PrintWriter.flush(PrintWriter.java:291)
         at com.ibm.ws.cache.servlet.CacheProxyWriter.flush(CacheProxyWriter.java:159)
         at com.ibm.ws.cache.servlet.CacheProxyWriter.flush(CacheProxyWriter.java:159)
         at com.ibm.ws.cache.servlet.FragmentComposer.requestFinished(FragmentComposer.java:393)
         at com.ibm.ws.cache.servlet.CacheHook.handleFragment(CacheHook.java:480)
         at com.ibm.ws.cache.servlet.CacheHook.handleServlet(CacheHook.java:281)
         at com.ibm.ws.cache.servlet.ServletWrapper.service(ServletWrapper.java:256)
         at com.ibm.ws.webcontainer.servlet.ServletWrapper.service(ServletWrapper.java:989)
         at com.ibm.ws.webcontainer.servlet.ServletWrapper.service(ServletWrapper.java:930)
         at com.ibm.ws.webcontainer.filter.WebAppFilterChain.doFilter(WebAppFilterChain.java:118)
         at com.ibm.ws.webcontainer.filter.WebAppFilterChain._doFilter(WebAppFilterChain.java:87)
         at com.ibm.ws.webcontainer.filter.WebAppFilterManager.doFilter(WebAppFilterManager.java:766)
         at com.ibm.ws.webcontainer.filter.WebAppFilterManager.doFilter(WebAppFilterManager.java:674)
         at com.ibm.ws.webcontainer.servlet.ServletWrapper.handleRequest(ServletWrapper.java:498)
         at com.ibm.ws.wswebcontainer.servlet.ServletWrapper.handleRequest(ServletWrapper.java:464)
         at com.ibm.wsspi.webcontainer.servlet.GenericServletWrapper.handleRequest(GenericServletWrapper.java:122)
         at com.ibm.ws.jsp.webcontainerext.AbstractJSPExtensionServletWrapper.handleRequest(AbstractJSPExtensionServletWrapper.java:225)
         at com.ibm.ws.webcontainer.webapp.WebAppRequestDispatcher.forward(WebAppRequestDispatcher.java:321)
         at com.ibm.faces.context.MultipartExternalContextImpl.dispatch(MultipartExternalContextImpl.java:320)
         at com.sun.faces.application.ViewHandlerImpl.renderView(ViewHandlerImpl.java:257)
         at com.sun.faces.lifecycle.RenderResponsePhase.execute(RenderResponsePhase.java:87)
         at com.sun.faces.lifecycle.LifecycleImpl.phase(LifecycleImpl.java:220)
         at com.sun.faces.lifecycle.LifecycleImpl.render(LifecycleImpl.java:118)
         at javax.faces.webapp.FacesServlet.service(FacesServlet.java:198)
         at com.ibm.ws.cache.servlet.ServletWrapper.serviceProxied(ServletWrapper.java:276)
         at com.ibm.ws.cache.servlet.CacheHook.handleFragment(CacheHook.java:463)
         at com.ibm.ws.cache.servlet.CacheHook.handleServlet(CacheHook.java:281)
         at com.ibm.ws.cache.servlet.ServletWrapper.service(ServletWrapper.java:256)
         at com.ibm.ws.webcontainer.servlet.ServletWrapper.service(ServletWrapper.java:989)
         at com.ibm.ws.webcontainer.servlet.ServletWrapper.service(ServletWrapper.java:930)
         at com.ibm.ws.webcontainer.filter.WebAppFilterChain.doFilter(WebAppFilterChain.java:145)
         at com.filter.ApplicationSessionExpiryFilter.doFilter(Unknown Source)
         at com.ibm.ws.webcontainer.filter.FilterInstanceWrapper.doFilter(FilterInstanceWrapper.java:190)
         at com.ibm.ws.webcontainer.filter.WebAppFilterChain.doFilter(WebAppFilterChain.java:130)
         at com.ibm.ws.webcontainer.filter.WebAppFilterChain._doFilter(WebAppFilterChain.java:87)
         at com.ibm.ws.webcontainer.filter.WebAppFilterManager.doFilter(WebAppFilterManager.java:766)
         at com.ibm.ws.webcontainer.filter.WebAppFilterManager.doFilter(WebAppFilterManager.java:674)
         at com.ibm.ws.webcontainer.servlet.ServletWrapper.handleRequest(ServletWrapper.java:498)
         at com.ibm.ws.wswebcontainer.servlet.ServletWrapper.handleRequest(ServletWrapper.java:464)
         at com.ibm.ws.webcontainer.servlet.CacheServletWrapper.handleRequest(CacheServletWrapper.java:90)
         at com.ibm.ws.webcontainer.WebContainer.handleRequest(WebContainer.java:744)
         at com.ibm.ws.wswebcontainer.WebContainer.handleRequest(WebContainer.java:1455)
         at com.ibm.ws.webcontainer.channel.WCChannelLink.ready(WCChannelLink.java:113)
         at com.ibm.ws.http.channel.inbound.impl.HttpInboundLink.handleDiscrimination(HttpInboundLink.java:454)
         at com.ibm.ws.http.channel.inbound.impl.HttpInboundLink.handleNewInformation(HttpInboundLink.java:383)
         at com.ibm.ws.http.channel.inbound.impl.HttpInboundLink.ready(HttpInboundLink.java:263)
         at com.ibm.ws.tcp.channel.impl.NewConnectionInitialReadCallback.sendToDiscriminators(NewConnectionInitialReadCallback.java:214)
         at com.ibm.ws.tcp.channel.impl.NewConnectionInitialReadCallback.complete(NewConnectionInitialReadCallback.java:113)
         at com.ibm.ws.tcp.channel.impl.AioReadCompletionListener.futureCompleted(AioReadCompletionListener.java:165)
         at com.ibm.io.async.AbstractAsyncFuture.invokeCallback(AbstractAsyncFuture.java:217)
         at com.ibm.io.async.AsyncChannelFuture.fireCompletionActions(AsyncChannelFuture.java:161)
         at com.ibm.io.async.AsyncFuture.completed(AsyncFuture.java:136)
         at com.ibm.io.async.ResultHandler.complete(ResultHandler.java:195)
         at com.ibm.io.async.ResultHandler.runEventProcessingLoop(ResultHandler.java:743)
         at com.ibm.io.async.ResultHandler$2.run(ResultHandler.java:873)
         at com.ibm.ws.util.ThreadPool$Worker.run(ThreadPool.java:1469)
    Caused by: java.io.IOException: Async IO operation failed, reason: RC: 32 There is no process to read data written to a pipe.
         at com.ibm.io.async.AbstractAsyncChannel.multiIO(AbstractAsyncChannel.java:474)
         at com.ibm.io.async.AsyncSocketChannelHelper.write(AsyncSocketChannelHelper.java:478)
         at com.ibm.io.async.AsyncSocketChannelHelper.write(AsyncSocketChannelHelper.java:396)
         at com.ibm.ws.tcp.channel.impl.AioSocketIOChannel.writeAIO(AioSocketIOChannel.java:281)
         at com.ibm.ws.tcp.channel.impl.AioTCPWriteRequestContextImpl.processAsyncWriteRequest(AioTCPWriteRequestContextImpl.java:49)
         at com.ibm.ws.tcp.channel.impl.TCPWriteRequestContextImpl.writeInternal(TCPWriteRequestContextImpl.java:166)
         at com.ibm.ws.tcp.channel.impl.TCPWriteRequestContextImpl.write(TCPWriteRequestContextImpl.java:137)
         at com.ibm.ws.http.channel.impl.HttpServiceContextImpl.asynchWrite(HttpServiceContextImpl.java:2376)
         at com.ibm.ws.http.channel.impl.HttpServiceContextImpl.sendOutgoing(HttpServiceContextImpl.java:2165)
         at com.ibm.ws.http.channel.inbound.impl.HttpInboundServiceContextImpl.sendResponseBody(HttpInboundServiceContextImpl.java:778)
         at com.ibm.ws.webcontainer.channel.WCChannelLink.writeBufferAsynch(WCChannelLink.java:307)
         at com.ibm.ws.webcontainer.channel.WCChannelLink.writeBufferResponse(WCChannelLink.java:287)
         at com.ibm.ws.webcontainer.channel.WCChannelLink.writeBuffer(WCChannelLink.java:241)
         at com.ibm.ws.webcontainer.channel.WCCByteBufferOutputStream.flushWriteBuffer(WCCByteBufferOutputStream.java:401)
         at com.ibm.ws.webcontainer.channel.WCCByteBufferOutputStream.write(WCCByteBufferOutputStream.java:147)
         at com.ibm.ws.webcontainer.srt.SRTOutputStream.write(SRTOutputStream.java:96)
         at sun.nio.cs.StreamEncoder$ConverterSE.implFlushBuffer(StreamEncoder.java:293)
         at sun.nio.cs.StreamEncoder$ConverterSE.implFlush(StreamEncoder.java:299)
         at sun.nio.cs.StreamEncoder.flush(StreamEncoder.java:210)
         at java.io.OutputStreamWriter.flush(OutputStreamWriter.java:236)
         at com.ibm.wsspi.webcontainer.util.BufferedWriter.writeOut(BufferedWriter.java:486)
         at com.ibm.wsspi.webcontainer.util.BufferedWriter.flushChars(BufferedWriter.java:372)
         at com.ibm.wsspi.webcontainer.util.BufferedWriter.flush(BufferedWriter.java:347)
         at java.io.PrintWriter.flush(PrintWriter.java:291)
         at com.ibm.ws.cache.servlet.CacheProxyWriter.flush(CacheProxyWriter.java:159)
         at com.ibm.ws.cache.servlet.CacheProxyWriter.flush(CacheProxyWriter.java:159)
         at org.apache.jasper.runtime.JspWriterImpl.flush(JspWriterImpl.java:233)
         at java.io.PrintWriter.flush(PrintWriter.java:291)
         at com.ibm.ws.cache.servlet.CacheProxyWriter.flush(CacheProxyWriter.java:159)
         at com.ibm.ws.cache.servlet.FragmentComposer.requestFinished(FragmentComposer.java:393)
         at com.ibm.ws.cache.servlet.CacheHook.handleFragment(CacheHook.java:480)
         at com.ibm.ws.cache.servlet.CacheHook.handleServlet(CacheHook.java:281)
         at com.ibm.ws.cache.servlet.ServletWrapper.service(ServletWrapper.java:256)
         at com.ibm.ws.webcontainer.servlet.ServletWrapper.service(ServletWrapper.java:989)
         at com.ibm.ws.webcontainer.servlet.ServletWrapper.service(ServletWrapper.java:930)
         at com.ibm.ws.webcontainer.filter.WebAppFilterChain.doFilter(WebAppFilterChain.java:118)
         at com.ibm.ws.webcontainer.filter.WebAppFilterChain._doFilter(WebAppFilterChain.java:87)
         at com.ibm.ws.webcontainer.filter.WebAppFilterManager.doFilter(WebAppFilterManager.java:766)
         at com.ibm.ws.webcontainer.filter.WebAppFilterManager.doFilter(WebAppFilterManager.java:674)
         at com.ibm.ws.webcontainer.servlet.ServletWrapper.handleRequest(ServletWrapper.java:498)
         at com.ibm.ws.wswebcontainer.servlet.ServletWrapper.handleRequest(ServletWrapper.java:464)
         at com.ibm.wsspi.webcontainer.servlet.GenericServletWrapper.handleRequest(GenericServletWrapper.java:122)
         at com.ibm.ws.jsp.webcontainerext.AbstractJSPExtensionServletWrapper.handleRequest(AbstractJSPExtensionServletWrapper.java:225)
         at com.ibm.ws.webcontainer.webapp.WebAppRequestDispatcher.include(WebAppRequestDispatcher.java:639)
         at org.apache.jasper.runtime.JspRuntimeLibrary.include(JspRuntimeLibrary.java:1034)
         at org.apache.jasper.runtime.JspRuntimeLibrary.include(JspRuntimeLibrary.java:997)
         at com.ibm._jsp._extract_5F__jspService(_extract_5F_java:91)
         at com.ibm.ws.jsp.runtime.HttpJspBase.service(HttpJspBase.java:87)
         at javax.servlet.http.HttpServlet.service(HttpServlet.java:856)
         at com.ibm.ws.cache.servlet.ServletWrapper.serviceProxied(ServletWrapper.java:276)
         at com.ibm.ws.cache.servlet.CacheHook.handleFragment(CacheHook.java:463)
         ... 51 more

    http://redeyeinteractive.com/index.eye?cart=1027565021121425&membersku=[membersku]&action=specific&SKU=507921572586523
    if this link don't work go to http://redeyeinteractive.com
    go to there java\applets path u will see a file upload component
    u can down load trial version free it is very easy to use.
    Good luck.

  • Multiple forms in JSF not working

    Hi
    I am using JSF 1.1 via WebSphere 6.1 and am having problems with multiple forms in a jsf page. I have a search command button on the page and a bunch of command links in a datatable. I have a h:form for the command button and another h:form for the datatable.
    The command button works fine. But the links don't. They just show the same page again and the action behind the commandLink is never called. I see many posts from way back about multiple forms not working in a jsf page.
    Is there a fix or workaround to this problem?
    Any pointers would be much appreciated.

    All replies so far have focused on solving multiple form issues. I have no problem with multiple forms per page but exactly like the original poster I can not get my h:commandLinks to work when embedded in a h:datatable.
    I have command buttons before and after the data table working great, but for whatever reason command links just do a post back to the backing bean.
    At this point I am not even trying to process data, just verify the action method is being executed.
    Another item of note, the links will always post to the same bean regardless of what bean is referenced in action="...."
    Any ideas?
    Message was edited by:
    jasontc
    It appears once the page is rendered for the first time any future rendering will display the link(s) but the link(s) will be junk.
    I ran a test with a pre populated ArrayList for my datatable, link worked. I then reload the datatable with a different ArrayList and the link is still referencing the original item in the list. So the action method I want to call is called but the .getRowData is incorrect. In addition of the number of items in my list grows the links become junk beyond the original size of the list.

  • Unable to read facec-config.xml in META-INF folder of webui-jsf.jar

    Hi
    I was getting following error when I placed webui-jsf.jar file in websphere 6.0 server
    /WEB-INF/lib/jsf-extensions-dynamic-faces-0.1.jar!/META-INF/faces-config.xml
    Digester E org.apache.commons.digester.Digester error Parse Error at line 24 column 14: Document is invalid: no grammar found.
    org.xml.sax.SAXParseException: Document is invalid: no grammar found.
    Do I need to add any other parser to read this file ?
    Thanks
    Himaja

    Your classpath is polluted with different JSF implementations/versions. Clean it up.

  • Working with WSAD 5.1.1 and JSF 1.0

    Hi,
    am new to JSF and am trying to put up a sample application with JSF and WSAD and Websphere 5.1 together.
    When I create a Faces enabled JSP , and write
    <f:loadBundles.....>, it simply states -
    Cannot find this tag under <%@ taglib uri="http://java.sun.com/jsf/html" prefix="h" %>
    <%@ taglib uri="http://java.sun.com/jsf/core" prefix="f" %>
    I have imported the above two taglibs.
    Also, hv put jsf-impl.jar and jsf-api.jar along with commons* -.jar in the project classpath in WSAD.
    Wht could be the problem? plz help.
    regards,
    Jayashree.

    java.library.path=C:\Program Files\IBM\WebSphere
    Studio\Application
    Developer\v5.1.\eclipse\jre\bin;.;C:\WINNT\System32;C:
    \WINNT;C:\Program Files\IBM\WebSphere
    Studio\Application
    Developer\v5.1.2\eclipse\jre\bin;C:\SQLLIB\java\db2jav
    a.zip;C:\SQLLIB\bin\db2jdbc.dllI don't know where you're defining java.library.path (it's not an OS environment variable, in case that's what you're trying). But don't you notice the other entries just point to directories that contain dll files in them, and does not specifically add individual .dll files? You're likely only supposed to add "C:\SQLLIB\bin" to it, not a specific .dll file (which it would treat as a directory name, which directory does not exist).

  • Websphere (Yes or No?)

    Can someone on the Creator team please give us a clear answer about JSC2 and Websphere? The installation notes say that Websphere 5 is a supported deployment server. The web site http://developers.sun.com/prodtech/javatools/jscreator/features/sysreqs/depservers.html says Websphere 6 is supported. The forums and everything I can gather from IBM would indicate that neither is true, due to the incompatability of SUN's JSF 1.1 and IBM's implementation of JSF 1.0 in Websphere 5.1.x / 6.0 So what is it? Is Websphere a supported deployment server or not?

    I'm with WebSphere 5.0.2 and I can deploy an Export from Creator 2 (making litle changes in web.xml and portlet.xml) but when I want to show the portlet I got this error:
    2006.02.06 18:38:32.234 E org.apache.pluto.invoker.impl.PortletInvokerImpl invoke
    java.lang.IllegalStateException: Response already committed.
    at com.ibm.ws.webcontainer.srt.SRTServletResponseContext.sendError(SRTServletRespo nseContext.java:131)
    at com.ibm.ws.webcontainer.srt.SRTServletResponse.sendError(SRTServletResponse.jav a:654)
    at com.ibm.ws.webcontainer.servlet.SimpleFileServlet.doGet(SimpleFileServlet.java: 329)
    at javax.servlet.http.HttpServlet.service(HttpServlet.java(Compiled Code))
    at javax.servlet.http.HttpServlet.service(HttpServlet.java(Compiled Code))
    at com.ibm.ws.webcontainer.servlet.StrictServletInstance.doService(StrictServletIn stance.java(Compiled Code))
    at com.ibm.ws.webcontainer.servlet.StrictLifecycleServlet._service(StrictLifecycle Servlet.java(Compiled Code))
    at com.ibm.ws.webcontainer.servlet.IdleServletState.service(StrictLifecycleServlet .java(Compiled Code))
    at com.ibm.ws.webcontainer.servlet.StrictLifecycleServlet.service(StrictLifecycleS ervlet.java(Inlined Compiled Code))
    at com.ibm.ws.webcontainer.servlet.ServletInstance.service(ServletInstance.java(Co mpiled Code))
    at com.ibm.ws.webcontainer.servlet.ValidServletReferenceState.dispatch(ValidServle tReferenceState.java(Compiled Code))
    at com.ibm.ws.webcontainer.servlet.ServletInstanceReference.dispatch(ServletInstan ceReference.java(Inlined Compiled Code))
    at com.ibm.ws.webcontainer.webapp.WebAppRequestDispatcher.handleWebAppDispatch(Web AppRequestDispatcher.java(Compiled Code))
    at com.ibm.ws.webcontainer.webapp.WebAppRequestDispatcher.dispatch(WebAppRequestDi spatcher.java(Compiled Code))
    at com.ibm.ws.webcontainer.webapp.WebAppRequestDispatcher.include(WebAppRequestDis patcher.java(Compiled Code))
    at org.apache.pluto.invoker.impl.PortletInvokerImpl.invoke(PortletInvokerImpl.java :223)
    at org.apache.pluto.invoker.impl.PortletInvokerImpl.render(PortletInvokerImpl.java :139)
    at com.ibm.wps.pe.pc.std.PortletContainerImpl.renderPortlet(PortletContainerImpl.j ava:142)
    at com.ibm.wps.pe.pc.PortletContainerImpl.doRenderPortlet(PortletContainerImpl.jav a:406)
    at com.ibm.wps.pe.ext.ppr.ParallelRenderManager.performService(ParallelRenderManag er.java:395)
    at com.ibm.wps.pe.pc.PortletContainerImpl.renderPortlet(PortletContainerImpl.java: 94)
    at com.ibm.wps.pe.pc.PortletContainer.renderPortlet(PortletContainer.java:95)
    at com.ibm.wps.composition.PortletHolder.render(PortletHolder.java:87)
    at com.ibm.wps.engine.tags.PortletRenderTag.doStartTag(PortletRenderTag.java:151)< br> at org.apache.jsp._Control._jspService(_Control.java:1949)
    2006.02.0 6 18:38:32.234 E com.ibm.wps.engine.tags.PortletRenderTag doStartTag
    FWEN0066E: The portlet could not be rendered. - StackTrace follows...
    2006.02.06 18:38:32.234 E com.ibm.wps.engine.tags.PortletRenderTag doStartTag
    javax.portlet.PortletException
    at org.apache.pluto.invoker.impl.PortletInvokerImpl.invoke(PortletInvokerImpl.java :261)
    at org.apache.pluto.invoker.impl.PortletInvokerImpl.render(PortletInvokerImpl.java :139)
    Then... I can't use Creator to develop my portlets?? .�(
    Thank yu.
    Sergi

  • Facelet to crare web app, instead of using JSP; JSF1.2 spec in WebSphere6.1

    Novice to JSF and Facelet. But, I had been using Struts since its inception.
    I am required to use IBM's WebSphere Application Server 6.1 that comes with Servlet 2.4 and JSP 2.0. WebSphere 6.1 App Server limits me to using JSF 1.1. This is because, JSF 1.2 requires Servlet 2.5 and JSP 2.1, that is a part of WebSphere App Server 7.0; not a part of WebSphere 6.1.
    Somebody suggested that it will be possible to use JSF 1.2 in WebSphere 6.1, if I were using Facelet, instead of JSP.
    I am not eager to use JSF 1.1 and may have to forego JSF; unless and until I can use JSF 1.2.
    The hold-up is that I cannot use JSF 1.2 spec in WebSphere 6.1. Is there is any way to use JSF 1.2 in WebSphere 6.1? Can I create an entire application using Facelet (instead of JSP) that will let me use JSF 1.2 spec in WebSphere 6.1? If so, how?
    Here are my questions, especially because I am not very familiar with JSF and Facelet technology:
    1. Can I use JSF 1.2 specification in WebSphere 6.1, if I were using facelet (as opposed to JSP) as my view technology?
    2. Will it be possible to create an entire web app with facelt, instead o fusing any JSP at all? If so, how? Does it mean that all the GUI screens will only use facelet and no JSP at all?
    3. Please explain how I can write a complex web app with 100s of screens using only facelet, instead of using JSP.
    4. Please provide pointer on how JSF and facelet differ, or what are their demarcations boundaries.
    Any comment and pointer will be greatly appreciated.

    Don't doublepost. It's rude. Stick to one topic. Continue here: [http://forums.sun.com/thread.jspa?threadID=5335001].

  • ADF Faces - showOneTab PPR problem in Internet Explorer

    Hoping someone has some insight into this that may help. This is causing us a lot of problems for us and could end up causing us to drop ADF faces from our project.
    Basically we are using af:showOneTab in our application and the first time we change tabs and every other time after that, the progress bar in IE basically runs forever and we have problems with afh:script tags that set the focus to the desired input field. We get a Javascript error that the element doesn't exist (it does, checked with a DOM explorer), or its not ready (may not be because of the progress bar) or isn't visible (it is).
    So after a lot of debugging in our application I just went back to the adf demo war file and the showOneTab component demo page in there shows exactly the same behavior. Firefox 1.5.0.7 does not have this problem.
    Here are the relevent versions of everything:
    ADF faces standalone jars, version 10.1.3.0.4 from the main ADF faces page download.
    JSF 1.1_01 RI
    Websphere 6.0 App Server
    Internet Explorer version 6.0.2900.2180.xpsp_sp2_gdr.050301-1519
    JDK 1.4 - required because of WAS 6.0
    Thanks!
    Steve

    I did find a workaround to this problem. I think its pretty ugly though. I had to add the following to the page:
    <!-- This code is necessary to prevent the IE progress bar runs forever problem. -->
    <f:verbatim>
         <iframe height="1px" marginheight="0px" marginwidth="0px" id="garbageFrame" name="garbageFrame" width="1px" style="visibility:hidden; position:absolute; top:-200px">
         </iframe>
    </f:verbatim>
    <afh:script id="iframeUpdate"
         text="window.garbageFrame.document.write('');
         window.garbageFrame.close()"/>
    <!-- End of code for IE progress bar problem. -->     
    Then I add the iframeUpdate script as a partial Target in my tab disclosure listener:
         UIComponent c = (UIComponent)de.getComponent();
         UIComponent target = c.findComponent(":iframeUpdate");
         AdfFacesContext adfContext = AdfFacesContext.getCurrentInstance();
         if(target != null) {
              adfContext.addPartialTarget(target);
    Just thought I'd follow up as I remember others having the progress bar run forever in IE as well.
    Steve

  • The JSP container failed to load the TagExtraInfo class

    We are upgrading our system. We were using JSF 1.1 with WebSphere V6. Now we are moving to JSF 1.2 and Websphere V7
    I am getting the error below over and over in the WebSphere V7 environment, in the ear
    [8/30/10 8:30:20:402 EDT] 0000000e jsp W com.ibm.ws.jsp.taglib.TldParser endElement JSPG0235E: The JSP container failed to load the TagExtraInfo class [com.sun.faces.taglib.FacesTagExtraInfo] from META-INF/odyssey.tld
    The ear can be set up to use either the sun reference implementation 1.2 or the MyFaces 1.2 implementation.
    It is currently set up for the sun reference implementation. Should this change, or is there something else I am missing.
    Thanks

    Hi Wrisillito,
    Regarding to the error message you provided, since SSIS uses VSTA 2.0, we need to fix that one only if there is SSIS trouble. Visual Studio doesn’t really related to the VSTA install.
    Seems  you have problems while opening VSTA inside BIDS to edit SSIS scripts, so please  try one of these methods:
    A. Uninstalling SQL Server 2008 and Reinstalling it may fix the problem.
    B. If you can't do that try the manual approach credit to SSIS script.
    For more information and steps, please follow the
    blog about VSTA setup and configuration troubles for SSIS 2008 and R2 installations.
    Meanwhile you can refer to these threads with the same error as yours
    1. VSTA designer issues with Sql 2008
    2. The VSTA designer failed to load
    This is SSIS related issue, if this does not work please link to
    SSIS forum for further help. 
    Regards,
    Amber zhang
    TechNet Subscriber Support
    If you are TechNet Subscription user and have any feedback on our support quality, please send your feedback
    here

  • WebSphere Custering and JSF Backing Beans

    Hello All,
    Can anyone enlighten me on exactly how backing bean state is maintained by JSF?
    In what scope does JSF store the backing beans? (session perhaps)
    Does it make sense to use JSF without stateful backing beans?
    What would happen if a client post did not find its corresponding backing bean on the application server calling it?
    Background:
    In a clustered WebSphere Server environment, a client post may be directed to any one of the machines in the cluster. If the client post gets directed to a machine other then the machine that originally sent the client a response, the page will not find the corresponding page beans.
    It is possible to serialize session beans in WebSphere and have each machine share its memory with all the boxes in the cluster. However, this practice is not permitted in some environments.
    Any thoughts? Thanks in advance.

    I am probably not an expert on the subject. But here are some thoughts:
    1. A backing bean can have (application, session, request or None) as a scope.
    Less app or session scope beans the better (from server perspective). But
    There are practical reasons why you would want to use them in many cases.
    2. JSF supports Client State Saving mode. But keep in mind the overhead
    Involved (serialization, de-serialization, bandwidth,...).
    3. You probably need to read about WebSphere load balancing capability. From
    what I know it is somehow sophisticated. People typically use session affinity
    to force requests initiated by same session to be served by the same app
    server (enforced by network, hardware/software tools available to do so,...). Of
    course with failover mechanism to ensure high availability.
    Hope that helps!

Maybe you are looking for