How JSF tag uri resovled..

Sorry for asking basic JSF (or JSP) question..
<%@ taglib uri="http://java.sun.com/jsf/core" prefix="f" %>
<%@ taglib uri="http://java.sun.com/jsf/html" prefix="h" %>
how the above two tag - URI resolved?
will it happen on demand?
or while container loading the application it scanns all the war file's tld (it may be within other jar) and preidentifies the uri's
Thanks

Below is the stack-trace copied using Eclipse during Tomcat startup. So Tomcat scans and loads all the tags from web-application during startup. StartupServletContextListener is triggered from MyFaces tab-library.
StartupServletContextListener is registered in myfaces_core.tld which resides myfaces-impl-1.2.0.jar.
Thread [main] (Suspended (breakpoint at line 37 in LifecycleFactoryImpl))     
     LifecycleFactoryImpl.<init>() line: 37     
     NativeConstructorAccessorImpl.newInstance0(Constructor, Object[]) line: not available [native method]     
     NativeConstructorAccessorImpl.newInstance(Object[]) line: 39     
     DelegatingConstructorAccessorImpl.newInstance(Object[]) line: 27     
     Constructor<T>.newInstance(Object...) line: 494     
     Class<T>.newInstance0() line: 350     
     Class<T>.newInstance() line: 303     
     FactoryFinder.newFactoryInstance(Class, Iterator, ClassLoader) line: 138     
     FactoryFinder.getFactory(String) line: 107     
     FacesConfigurator.configureLifecycle() line: 643     
     FacesConfigurator.configure() line: 144     
     StartupServletContextListener.initFaces(ServletContext) line: 69     
     StartupServletContextListener.contextInitialized(ServletContextEvent) line: 52     
     StandardContext.listenerStart() line: 3764     
     StandardContext.start() line: 4216     
     StandardHost(ContainerBase).start() line: 1014     
     StandardHost.start() line: 736     
     StandardEngine(ContainerBase).start() line: 1014     
     StandardEngine.start() line: 443     
     StandardService.start() line: 448     
     StandardServer.start() line: 700     
     Catalina.start() line: 552     
     NativeMethodAccessorImpl.invoke0(Method, Object, Object[]) line: not available [native method]     
     NativeMethodAccessorImpl.invoke(Object, Object[]) line: 39     
     DelegatingMethodAccessorImpl.invoke(Object, Object[]) line: 25     
     Method.invoke(Object, Object...) line: 585     
     Bootstrap.start() line: 295     
     Bootstrap.main(String[]) line: 433

Similar Messages

  • Jsf 1s phase of life cycle how knows ths components of the jsp with jsf tag

    i wish to know how faces servlet knows the jsp s view components while creaTI NG component tree at first request to input jsp which may have jsf tags.in the first phase faces servlet doesnot know input jsp with jsf tags what componnets it has. it is actually atthe response send or forward time which is the final phase when the tag ge executed and output is sent to client.i did understandin jsf life cycle in 1 st phase component tree is created at first request in 1 st phase .

    Hi,
    though a FacesContext holds the values used by a request, it doesn't mean it lives for as long as the request. The best explanation I found is from the JavaDocs
    release
    public abstract void release()
    +Release any resources associated with this FacesContext instance. Faces implementations may choose to pool instances in the associated FacesContextFactory to avoid repeated object creation and garbage collection. After release() is called on a FacesContext instance (until the FacesContext instance has been recycled by the implementation for re-use), calling any other methods will cause an IllegalStateException to be thrown.+
    The implementation must call setCurrentInstance(javax.faces.context.FacesContext) passing null to remove the association between this thread and this dead FacesContext instance.
    Throws:
    java.lang.IllegalStateException - if this method is called after this instance has been released
    Frank

  • How to add raw HTML tags inside JSF tags...

    Hi
    I would like to use <input type = text > inside my project in some area..The following code hides the input = type html tag and forwards the click event to jsf command button...After selecting the file,it should forward the value to jsf textfield....
    My code seems as below.
    <h:form id="detailForm" onsubmit="printElements(detailForm,this)">
    <f:verbatim>
    <input id="uploadFile" type="file" style ="dispaly:none"size="100" />
    </f:verbatim>
    <h:inputText id="docName" style="width:650px;" maxlength="100"/>
    <h:commandButton id="visibleBrowseButton" value="Select File..." onclick="'detailForm:uploadFile'.click();callClick();">
    </h:commandButton>
    </h:form>
    <script type="text/Javascript">
    function callClick()
    var val = document.detailForm.uploadFile.value;
    document.getElementById('detailForm:docName').value = val;
    </script>
    While running this page it works fine in IE but in Mozilla firefox it troubles me during detailForm:uploadFile'.click().
    I suspect the jsf page cannot able to detect the raw html tag inside jsf tags...Eventhough i tried using inside<f:verbatim> it wont works..
    I would like to know
    1.Whether the code is right,,if the code goes wrong why it got runned in IE not in firefox....
    2.How can raw html tags can be integrated inside JSF tags....

    First of all, why are you ignoring valuable answers about a JSF fileupload component in your previous topic?
    Second, you can just nest raw HTML anywhere in your JSF page. Your problem is rather related to JavaScript. It has completely nothing to do with Java nor JSF. Learn JavaScript -there is a nice tut at w3schools.com- and look for a JavaScript forum if you still stucks. There are ones at webdeveloper.com and dynamicdrive.com.
    The f:verbatim is only required if you was using JSF 1.1 or older, which is not the case. You would have occurred completely different problems.

  • How to convert div to JSF tag ?

    Hi guys,
    I got a problem on using the following code:
                                       <c:if test="${requestScope.error == 'errLogin'}">
                                  <div class="error">
                                  <h:graphicImage styleClass="imageStyle" value="/images/iconWarning.gif"/>
                             <h:messages styleClass="errorMessage" globalOnly="true"/>
                        </div>
                        </c:if>
    to be display correctly with the whole page. I really don't know how to descripe the weird result. Anyway, anyone know how to put the above <div> into JSF tag type?
    I put the above code within <h:form id="loginForm">.... </h:form> is there a problem?
    Thanks !
    regards,
    kmthien
    regards,
    Mark

    Hi,
    I had a requirement to use the Div in my code and here is the sample of the code and it is working fine.
    and I am using WASD 5.1.2.
    <h:panelGrid columns="1" border="1" styleClass="scrollPane">
                   <h:panelGroup>
                                  <f:verbatim>
                                       <DIV STYLE="overflow: auto; height: 100px; width: 400px">
                                  </f:verbatim>
                                  <h:selectManyCheckbox id="userRoles" layout="pageDirection"
                                       valueChangeListener="#{pc_UserPage.handleUserRolesValueChange}"
                                       value="#{pc_UserPage.searchBean.userRoles}">
                                       <f:selectItems value="#{pc_UserPage.dataTable.userRoles}" />
                                  </h:selectManyCheckbox>
                                  <f:verbatim>
                                       </DIV>
                                  </f:verbatim>
                             </h:panelGroup>
    </h:panelGrid>

  • How we can use jsf tags in included jsp enclosed in subview tags

    Hello everybody,
    I am developing web app by using jsf. I am including a jsp page "header.jsp" into another jsp page "main.jsp". The header.jsp page is enclosed in jsf subview tag on main.jsp page. The header.jsp contains some static html code and some jsf tags like "outputText". When i added tag library url in header.jsp then my app was not even not initiating and i was getting following exception
    ERROR [UIComponentTag] Faces context not found. getResponseWriter will fail. Check if the FacesServlet has been initialized at all in your web.xml.
    16:22:16,890 ERROR [[jsp]] Servlet.service() for servlet jsp threw exception
    java.lang.NullPointerException
    at javax.faces.webapp.UIComponentTag.setupResponseWriter(UIComponentTag.java:929)
    at javax.faces.webapp.UIComponentTag.doStartTag(UIComponentTag.java:310)
    ....Now i removed jsf tag library url from included jsp "header.jsp" so now my app is running but only static html data is being displayed but the value in the jsf tag "outputText" is not being printed in the browser
    kindly help me. i would be very thankful....

    Your question has nothing to do with Sun Java System Directory Server.
    Please use the right forum(s).
    Thanks

  • How to run generated JSF tags ?

    I am beginner in JSF. I would like execute JSF tags generated dynamically by XSLT, but in the JSP page,
    these tags are not interpreted. Does anyone has the solution ? Thanks a lot.
    Example below is only a simple test,
    ResearchBean.java :
    public String researchAction() {
        // Actually, htmlResponse is the output string after the XSLT transformation, and it contains JSF tags
        htmlResponse = "<h:outputText value=\"Text\"/>";
        return "response";
    }response.xhtml :
    <f:view xmlns:f="http://java.sun.com/jsf/core
    xmlns:h="http://java.sun.com/jsf/html
    <html>
    #{researchBean.htmlResponse}
    </html>
    </f:view>In the page received by the browser, <h:outputText value="Text"/> isn't replaced by the html code.
    Edited by: wondergarance on Jul 2, 2009 1:24 PM

    The JSF tags are apparently generated after the FacesServlet has done its work. You in fact need to pass the generated output through the FacesServlet again. If you're using a servlet/filter to run XSLT, you need to run it before the FacesServlet kicks in. You can control the servlet/filter invocation order in the web.xml.

  • Replace JSF tag by an own tag

    Hi,
    I'm trying to replace a <h:inputText> by my own tag. The used HtmlInputText component should not be replaced.
    The reason is, that i want to pass permissions to the tag and map them to readonly and rendered attributes. My Problem is, that my own tag doesn't reolv bean values. If i use the <h:inputText> the bean values show up correctly. If i use my own tag, the input text shows "#{myBean.value}".
    What could be the problem?
    Thx in advance
    Henrik
    Here is my tag:
    import javax.faces.component.UIComponent;
    import javax.faces.component.html.HtmlInputText;
    import javax.faces.context.FacesContext;
    import javax.faces.webapp.UIComponentTag;
    import com.arvato.jsf.security.JSFSecurity;
    import com.arvato.jsf.security.Permissions;
    import com.sun.faces.taglib.html_basic.InputTextTag;
    public class ArvatoTextFieldTag extends InputTextTag {
        private String role;
        private String onkeypress;
        private String id;
        private String value;
        public String getRole() {
            return role;
        public void setRole(String permissions) {
            this.role = permissions;
        protected void setProperties(UIComponent component) {
            super.setProperties(component);
            if(id != null) {
                component.getAttributes().put("id", id);
            if(onkeypress != null) {
                component.getAttributes().put("onkeypress", onkeypress);
            if(value != null) {
                component.getAttributes().put("value", value);
            if(role != null) {
                FacesContext facesContext = FacesContext.getCurrentInstance();
                Permissions p = JSFSecurity.getInstance().getPermissionsForRole(role, facesContext);
                if(!p.isWritable()) {
                    component.getAttributes().put("readonly", true);
                if(!p.isReadable()) {
                    component.getAttributes().put("rendered", false);
            } else {
                component.getAttributes().put("readonly", false);
                component.getAttributes().put("rendered", true);
        @Override
        public String getComponentType() {
            return "javax.faces.HtmlInputText";
        @Override
        public String getRendererType() {
            return null; // no standalone renderer
        @Override
        public void release() {
            super.release();
            role = null;
        public String getValue() {
            return value;
        public void setValue(String value) {
            this.value = value;
        public String getOnkeypress() {
            return onkeypress;
        public void setOnkeypress(String onkeypress) {
            this.onkeypress = onkeypress;
        public String getId() {
            return id;
        public void setId(String id) {
            this.id = id;
    }and my tld definition:
    <taglib>
       <tlib-version>0.03</tlib-version>
       <jsp-version>1.2</jsp-version>
       <short-name>arvato-jsf</short-name>
       <uri>http://arvato.com/jsf/component/tags</uri>
       <description>Arvato JSF tags</description>
       <tag>
          <name>textfield</name>
          <tag-class>com.arvato.jsf.tag.ArvatoTextFieldTag</tag-class>
          <attribute>
             <name>id</name>
          </attribute>
          <attribute>
             <name>role</name>
          </attribute>
          <attribute>
             <name>value</name>
          </attribute>
          <attribute>
             <name>onkeypress</name>
          </attribute>
       </tag>
    </taglib>

    In the setProperties method, you've got to resolve the valuebinding (#{blah.whatever}) to get the actual value. But you only want to do that if the attribute is set to a valuebinding.
    Here's an example:
          * @see javax.faces.webapp.UIComponentTag#setProperties(UIComponent)
         protected void setProperties(UIComponent component) {
              super.setProperties(component);
              //Set the field reference property
              if (fieldRef != null) {
                   if (UIComponentTag.isValueReference(fieldRef)) {
                        ValueBinding vb = getFacesContext().getApplication().
                             createValueBinding(fieldRef);
                        component.setValueBinding("fieldRef", vb);
                   } else {
                        component.getAttributes().put("fieldRef", fieldRef);
         }This example shows how to determine if the "fieldRef" attribute is a value binding, and extracts the value accordingly. But there's one more step. In your component class, or anywhere you access the attributes of your custom tag, use the following code:
         public String getFieldRef() {
              if (fieldRef != null)
                   return fieldRef;
              ValueBinding vb = getValueBinding("fieldRef");
              if (vb != null)
                   return (String)vb.getValue(getFacesContext());
              else
                   return null;
         }The above snippet is what you would put in your custom component getter method.
    JSF is open source. Something I found very helpful while learning how to create custom components was looking at how the JSF developers created theirs. You should go ahead and download the JSF source code.
    CowKing

  • Exception when running JSF Tags

    Hi,
    I am using MyEclipse 5.0.1 GA and jboss-4.0.3SP1. I am trying out a small JSF tag where the command button is not getting displayed and if i click the refresh button three i am getting this error. could anyone tell me what exactly the problem is.
    Exception
    org.apache.jasper.JasperException: /one.jsp(11,4) No tag "form" defined in tag library imported with prefix "f"
         org.apache.jasper.compiler.DefaultErrorHandler.jspError(DefaultErrorHandler.java:39)
         org.apache.jasper.compiler.ErrorDispatcher.dispatch(ErrorDispatcher.java:405)
         org.apache.jasper.compiler.ErrorDispatcher.jspError(ErrorDispatcher.java:196)
         org.apache.jasper.compiler.Parser.parseCustomTag(Parser.java:1308)
         org.apache.jasper.compiler.Parser.parseElements(Parser.java:1564)
         org.apache.jasper.compiler.Parser.parseBody(Parser.java:1793)
         org.apache.jasper.compiler.Parser.parseOptionalBody(Parser.java:1060)
         org.apache.jasper.compiler.Parser.parseCustomTag(Parser.java:1367)
         org.apache.jasper.compiler.Parser.parseElements(Parser.java:1564)
         org.apache.jasper.compiler.Parser.parse(Parser.java:126)
         org.apache.jasper.compiler.ParserController.doParse(ParserController.java:211)
         org.apache.jasper.compiler.ParserController.parse(ParserController.java:100)
         org.apache.jasper.compiler.Compiler.generateJava(Compiler.java:146)
         org.apache.jasper.compiler.Compiler.compile(Compiler.java:286)
         org.apache.jasper.compiler.Compiler.compile(Compiler.java:267)
         org.apache.jasper.compiler.Compiler.compile(Compiler.java:255)
         org.apache.jasper.JspCompilationContext.compile(JspCompilationContext.java:556)
         org.apache.jasper.servlet.JspServletWrapper.service(JspServletWrapper.java:293)
         org.apache.jasper.servlet.JspServlet.serviceJspFile(JspServlet.java:314)
         org.apache.jasper.servlet.JspServlet.service(JspServlet.java:264)
         javax.servlet.http.HttpServlet.service(HttpServlet.java:810)
         org.jboss.web.tomcat.filters.ReplyHeaderFilter.doFilter(ReplyHeaderFilter.java:81)
    one.jsp
    <%@ page contentType="text/html" %>
    <%@ taglib uri="http://java.sun.com/jsf/html" prefix="h" %>
    <%@ taglib uri="http://java.sun.com/jsf/core" prefix="f" %>
    <html>
    <body>
    This is my JSF page. <br>
    <f:view>
    <f:form>
         <h:commandButton id="cmd" action="" value="Submit" />
    </f:form>
         </f:view>
    </body>
    </html>
    web.xml
    <?xml version="1.0" encoding="UTF-8"?>
    <web-app xmlns="http://java.sun.com/xml/ns/j2ee" xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance" version="2.4" xsi:schemaLocation="http://java.sun.com/xml/ns/j2ee http://java.sun.com/xml/ns/j2ee/web-app_2_4.xsd">
    <context-param>
    <param-name>javax.faces.CONFIG_FILES</param-name>
    <param-value>/WEB-INF/faces-config.xml</param-value>
    </context-param>
    <servlet>
    <servlet-name>Faces Servlet</servlet-name>
    <servlet-class>javax.faces.webapp.FacesServlet</servlet-class>
    <load-on-startup>0</load-on-startup>
    </servlet>
    <servlet-mapping>
    <servlet-name>Faces Servlet</servlet-name>
    <url-pattern>*.faces</url-pattern>
    </servlet-mapping>
    </web-app>
    faces-config.xml
    <?xml version="1.0" encoding="UTF-8"?>
    <!DOCTYPE faces-config PUBLIC "-//Sun Microsystems, Inc.//DTD JavaServer Faces Config 1.1//EN" "http://java.sun.com/dtd/web-facesconfig_1_1.dtd">
    <faces-config >
         <application></application></faces-config>

    No tag "form" defined in tag library imported with prefix "f"This error is clear and correct: the tag library defined with the prefix f does not have a tag named form. So you cannot use <f:form>. Likely you intended <h:form>.

  • JSF tags are not rendered in error page

    I have configured error page for HTTP 404 error in web.xml like this
    <error-page>
    <error-code>404</error-code>
    <location>/Common/error.jspx</location>
    </error-page>
    Faces Servlet is configured as follows
    <servlet-mapping>
    <servlet-name>Faces Servlet</servlet-name>
    <url-pattern>/faces/*</url-pattern>
    </servlet-mapping>
    My error page (error.jspx) looks like this
    <?xml version='1.0' encoding='UTF-8'?>
    <jsp:root xmlns:jsp="http://java.sun.com/JSP/Page" version="2.1" xmlns:f="http://java.sun.com/jsf/core"
    xmlns:h="http://java.sun.com/jsf/html" xmlns:trh="http://myfaces.apache.org/trinidad/html"
    xmlns:tr="http://myfaces.apache.org/trinidad" xmlns:c="http://java.sun.com/jsp/jstl/core">
    <jsp:directive.page contentType="text/html;charset=UTF-8"/>
    <html>
    <head>
    <title>Error Page</title>
    <meta http-equiv="Content-Type" content="text/html; charset=UTF-8"/>
    </head>
    <body id="b1">
    <h4 style="color:red">An Error Occured. Please click Back button or Signout.</h4>
    <input type="button" value="Back" onclick="history.back()"/>
    <tr:commandButton id="cb1" text="SIGN OUT" action="exit" actionListener="#{Login.LogOut}"/>
    </body>
    </html>
    </jsp:root>
    When I deploy application and run into 404 error, page displays error message with only Back button. I don't see SingOut button. I have checked url and it follows /faces/* pattern. Still to double check, I made a change and configured servlet mapping in web.xml as
    <servlet-mapping>
    <servlet-name>Faces Servlet</servlet-name>
    <url-pattern>/faces/*</url-pattern>
    <url-pattern>*.jspx</url-pattern>
    </servlet-mapping>
    Still commandButton is not rendered. I understand that my error page don't have access to FacesContext or not going through Faces Servlet. I know this is a small issue, but couldn't figure out what can be done. I have also tried using .xhtml and .jsf as per googled suggestion. But no luck
    I have tried different solutions to my problem and googled for solutions. But I couldn't get it resolved.
    So can you please provide any suggestions...
    Edited by: user1818355 on May 22, 2013 2:29 PM

    I think my faces servlet is configured to handle URLs having /faces/* pattern. I don't have any folder named with faces but I can access all my web pages which have /faces/ in their url. All jspx pages in application are configured in task flows. So I think they have access in FacesContext. But error page is configured in only web.xml and some how it is missing access to FacesContext and not rendering JSF tags. Any help?

  • JSF tag inside another JSF tag

    Hi,
    Note: It's a bit of a long post but I will try to cut to the point without leaving behind any pertinent details.
    I've created some simple custom JSF tags in the past. The tags usually consisted of one or two attributes that would be beans. The tags would then print out the data for those beans or process them and then output the results.
    What I am trying to do now is a bit more complicated for me. I have a JSP page with a scriplet on it. It iterates over a bean containing a list of items. The loop adds those items to an HTML select menu one at a time. The outline of the code looks similar to this,
    <% extract data List from the bean and store it in variable called dataList %>
    <select>
    <%
      for (int i=0; i<dataList.size(); i++;){
        ListItem item = dataList.get(i);
        String name = item.getName();
        String value = item.getValue();
    %>
    <option value="<%=value%>">
      <%=name%>
    </option>
    <%}%>
    </select>
    <h:commandButton id="gobtn" action="go_to_page" actionListener="#{action.fetch}" value="Go"/>What I want to do is take all the above code and put it into a custom JSF tag. This tag would contain all the scriplet code, output the HTML code and also the commandButton code at the end.
    All of that is pretty easy except for the commandButton part. I am not sure how to output a commandButton from a custom JSF tag. How do I pass it the action.fetch part for the actionListener attribute? Can I create a commandButton object in my custom JSF tag and pass it this information?
    I've followed a tutorial at this site in the past but it doesn't go into too much detail
    http://www.exadel.com/tutorial/jsf/jsftutorial-customcomponents.html
    Any help is appreciated,
    Nick

    I guess I missed some information. The dataList in the bean is stored in a HashMap. So some work has to be done with the bean before hand to determine what list to pull out and then "massage" it a bit for viewer consumption. This is not easily accomplished with the standard JSF html tags, hence my going with a custom tag approach.
    Processing this bean and getting a list from the Hashmap in the bean before displaying it is easy, so is outputting the HTML. The hard part is rendering the commandButton with all the attributes I listed previously.
    Is there a way in general to have other JSF tags nested inside a custom JSF tag?

  • Unable to view jsp page containing jsf tags

    I'm pretty new to this JSF world, so facing lot of problems. I have installed JWSDP ver 1.2 When I start tomcat and specify URL http://localhost:8080 the site goes in waiting phase for ever. So even I'm not able to view/run the samples provided for jsf.
    Moreover, i have created a simple appln to test jsf tag, but it's giving following error:
    javax.servlet.ServletException: This absolute uri (http://java.sun.com/jsf/core) cannot be resolved in either web.xml or the jar files deployed with this application
         at javax.faces.webapp.FacesServlet.service(FacesServlet.java:207)
    I don't know where the problem is. The code for sample i have downloaded from http://www.horstmann.com/corejsf/tutorial.html
    but with no success in running jsf app.
    anyone know the reason, why??
    Thanx in Advance,
    K.K.

    Roger, here are the contents of log file.
    Here goes the contents of launcher.server.log :
    Sep 17, 2003 10:25:07 AM org.apache.commons.modeler.modules.MbeansDescriptorsDOMSource execute
    INFO: Reading descriptors ( dom ) 921
    Sep 17, 2003 10:25:07 AM org.apache.commons.modeler.modules.MbeansDescriptorsDOMSource execute
    INFO: Reading descriptors ( dom ) 171
    Sep 17, 2003 10:25:08 AM org.apache.commons.modeler.modules.MbeansDescriptorsDOMSource execute
    INFO: Reading descriptors ( dom ) 781
    Sep 17, 2003 10:25:08 AM org.apache.commons.modeler.modules.MbeansDescriptorsDOMSource execute
    INFO: Reading descriptors ( dom ) 200
    Sep 17, 2003 10:25:09 AM org.apache.commons.modeler.modules.MbeansDescriptorsDOMSource execute
    INFO: Reading descriptors ( dom ) 190
    Sep 17, 2003 10:25:09 AM org.apache.commons.modeler.modules.MbeansDescriptorsDOMSource execute
    INFO: Reading descriptors ( dom ) 71
    Sep 17, 2003 10:25:09 AM org.apache.commons.modeler.modules.MbeansDescriptorsDOMSource execute
    INFO: Reading descriptors ( dom ) 80
    Sep 17, 2003 10:25:09 AM org.apache.commons.modeler.modules.MbeansDescriptorsDOMSource execute
    INFO: Reading descriptors ( dom ) 290
    Sep 17, 2003 10:25:09 AM org.apache.commons.modeler.modules.MbeansDescriptorsDOMSource execute
    INFO: Reading descriptors ( dom ) 110
    Sep 17, 2003 10:25:09 AM org.apache.commons.modeler.modules.MbeansDescriptorsDOMSource execute
    INFO: Reading descriptors ( dom ) 50
    Sep 17, 2003 10:25:10 AM org.apache.commons.modeler.modules.MbeansDescriptorsDOMSource execute
    INFO: Reading descriptors ( dom ) 341
    Sep 17, 2003 10:25:10 AM org.apache.commons.modeler.modules.MbeansDescriptorsDOMSource execute
    INFO: Reading descriptors ( dom ) 170
    Sep 17, 2003 10:25:10 AM org.apache.commons.modeler.modules.MbeansDescriptorsDOMSource execute
    INFO: Reading descriptors ( dom ) 90
    Sep 17, 2003 10:25:12 AM org.apache.coyote.http11.Http11Protocol init
    INFO: Initializing Coyote HTTP/1.1 on port 8080
    Sep 17, 2003 10:25:12 AM org.apache.catalina.startup.Catalina load
    INFO: Initialization processed in 6670 ms
    Sep 17, 2003 10:25:14 AM org.apache.catalina.core.StandardService start
    INFO: Starting service Java Web Services Developer Pack
    Sep 17, 2003 10:25:14 AM org.apache.catalina.core.StandardEngine start
    INFO: Starting Servlet Engine: Java Web Services Developer Pack/1.2
    Sep 17, 2003 10:25:15 AM org.apache.catalina.core.StandardHost getDeployer
    INFO: Create Host deployer for direct deployment ( non-jmx )
    Sep 17, 2003 10:25:46 AM org.apache.struts.util.PropertyMessageResources <init>
    INFO: Initializing, config='org.apache.struts.util.LocalStrings', returnNull=true
    Sep 17, 2003 10:25:46 AM org.apache.struts.util.PropertyMessageResources <init>
    INFO: Initializing, config='org.apache.struts.action.ActionResources', returnNull=true
    Sep 17, 2003 10:26:15 AM org.apache.struts.util.PropertyMessageResources <init>
    INFO: Initializing, config='org.apache.webapp.admin.ApplicationResources', returnNull=true
    Sep 17, 2003 10:26:24 AM com.sun.xml.rpc.server.http.JAXRPCContextListener contextInitialized
    INFO: JAX-RPC context listener initializing
    Sep 17, 2003 10:26:26 AM com.sun.xml.rpc.server.http.JAXRPCServletDelegate init
    INFO: JAX-RPC servlet initializing
    And here the contents of jwsdp_log :
    2003-09-17 10:25:14 createObjectName with StandardEngine[Catalina]
    2003-09-17 10:25:14 preRegister with Catalina:type=Logger
    2003-09-17 10:25:54 createObjectName with StandardEngine[Catalina].StandardHost[localhost].StandardContext[jaxrpc-HelloWorld]
    2003-09-17 10:25:55 preRegister with Catalina:type=Logger,path=/jaxrpc-HelloWorld,host=localhost
    2003-09-17 10:26:28 createObjectName with StandardEngine[Catalina].StandardHost[localhost].StandardContext[jsf-cardemo]
    2003-09-17 10:26:28 preRegister with Catalina:type=Logger,path=/jsf-cardemo,host=localhost

  • Building JSF tag using existing Tags

    Hi all
    I wonder if it's possible to create a new JSF tag using existing JSF Tags?
    For example, I have a JSF tag which renders a lable and a textinputfield, let's call it <f:field>
    Now I want to build a new JSF tag, which will re-use the existing tag <f:field>. IS it possible?
    Thanks in advance

    Did you have a chance to look at facelets solution. Facelets provide several approach how to create composition components.
    Sergey : https://ajax4jsf.dev.java.net

  • Can't get JSF tags to execute in Visual Editor (JDeveloper 10.1.3.0.3.3412)

    Hi,
    I have searched this discussion forum for this problem and apparently I can't find any solution / tried a few but none works. I am feeling quite frustrated about this as on Manning's "JavaServer Faces in Action" online extension gave real examples in JDeveloper that looked so attractive, but in reality it doesn't work!
    However, I could get 10.1.2 to associate with JSF by following online's howto's, but that would lose all the cool tools that come with 10.1.3 EA...
    I would appreciate it if anyone can provide a clue as how to make JSF tags execute in the Visual Editor...

    Hi shay,
    I discover that the problem was with my JSF source. I was importing from a source file (WAR) that comes with the book "JavaServer Faces in Action", when I import the file and try to open, I get a few exceptions shown on the console window, and the JSF tags were all unexecuted.
    And as I create a new JSF file on my own in JDeveloper, everything was fine...

  • How to tag attribute member with standard dimension member in EIS

    hi,
    would any one please help me how to tag attribute member with standard dimension member in EIS
    THANK U IN ADVANCE

    In your OLAP model, view columns for the base dimension table. Go into the column properties and for the columns that have Attribute values highlight them and click the Attribute button.
    Go into Metadata Model and those fields will be available to drag into your outline as attribute members.
    Once in the outline, go into the properties of the attribute and assign the level of the base dimension they associate with.

  • JSP ${} expressions in JSF tag attributes

    Does anyone know why the expert group decided not to allow ${} style expressions within JSF tag attributes? I understand that a different syntax is needed to implement the 'late binding' #{} expressions used to link input controls to form beans, but not why the JSF tags actually prevent the use of immediately evaluated ${} expressions for accessing variables in the page scope in JSP 2.0.
    I know there has been a lot of discussion about this and other threads mention a security loophole that would be opened up by allowing expressions like #{blah.${someProperty}}, but I'm not sure why this sort of thing would cause a problem. Is there any way to enable this behaviour, such as editing the JSF tag library descriptors to allow runtime expressions (horrible though that sounds)? Or perhaps another JSF implementation that supports both immediately evaluated and late-binding expressions? It seems a rather unnecessary restriction that is going to cause much confusion and mistyping for all...
    Thanks in advance,
    Keith.

    Thanks Adam, I see the problem now. It's a fairly obscure loophole but serious nonetheless. Of course, this problem could also be avoided by not using request parameters within JSF tags as it doesn't affect the majority of legitimate uses for expressions.
    I have to disagree with you about mixing ${} and #{} expressions though. The majority of developers will be used to writing ${} expressions in JSTL and JSP text and so will expect them to do work the same in JSF tags. Judging by the number of posts in this forum about being unable to use page scope variables in JSF tags this issue is already confusing a lot of people.
    As a rule of thumb, "use ${} for expressions that are output to the page and #{} for binding controls to backing beans and invoking methods" (which perform clearly distinct functions) is a lot simpler and easier to learn IMHO than the current one, which is "use ${} for expressions that are output to the page except within a JSF tag, where you use #{} for the same thing and also to update form values and invoke action methods"! (OK, I'm exaggerating a little for effect, but you get the point... :-)
    I agree that mixing both types of expression in the same attribute might be a little confusing, but this is an unlikely edge case that should probably be prevented in value binding or action attributes anyway. It's more of an issue for label values where mistyping one for the other is already very common and, although not especially difficult to debug, is just another pitfall awaiting the unwary JSP developer. I'm not sure that JSP expressions would be much more difficult to debug anyway as the value and method bindings will simply not work, which is pretty obvious as soon as you try and test the thing.
    Is this something that the EG would be prepared to reconsider for the next release of JSF, or perhaps getting the security loophole addressed in the next JSP spec? In the meantime, is there any reason that developers shouldn't enable runtime expressions in the TLD file provided that they're willing to live with the consequences?
    (Sorry to harp on about it, but I've already had several complaints about this after recommending JavaServer Faces for a major development project at ingenta.com.)
    Many thanks,
    Keith.

Maybe you are looking for