Property of panel_grid tag

Here is a part of html_basic.tld .
I want to know how to use frame property and rule property.
Anyone knows these properties?
<tag>
<name>panel_grid</name>
<tag-class>com.sun.faces.taglib.html_basic.Panel_GridTag</tag-class>
<body-content>JSP</body-content>
<attribute>
<name>columnClasses</name>
<required>false</required>
<rtexprvalue>false</rtexprvalue>
</attribute>
<attribute>
<name>rendered</name>
<required>false</required>
<rtexprvalue>false</rtexprvalue>
</attribute>
<attribute>
<name>columns</name>
<required>false</required>
<rtexprvalue>false</rtexprvalue>
</attribute>
<attribute>
<name>footerClass</name>
<required>false</required>
<rtexprvalue>false</rtexprvalue>
</attribute>
<attribute>
<name>headerClass</name>
<required>false</required>
<rtexprvalue>false</rtexprvalue>
</attribute>
<attribute>
<name>panelClass</name>
<required>false</required>
<rtexprvalue>false</rtexprvalue>
</attribute>
<attribute>
<name>rowClasses</name>
<required>false</required>
<rtexprvalue>false</rtexprvalue>
</attribute>
<attribute>
<name>id</name>
<required>false</required>
<rtexprvalue>false</rtexprvalue>
</attribute>
<attribute>
<name>onclick</name>
<required>false</required>
<rtexprvalue>false</rtexprvalue>
</attribute>
<attribute>
<name>ondblclick</name>
<required>false</required>
<rtexprvalue>false</rtexprvalue>
</attribute>
<attribute>
<name>onkeydown</name>
<required>false</required>
<rtexprvalue>false</rtexprvalue>
</attribute>
<attribute>
<name>onkeypress</name>
<required>false</required>
<rtexprvalue>false</rtexprvalue>
</attribute>
<attribute>
<name>onkeyup</name>
<required>false</required>
<rtexprvalue>false</rtexprvalue>
</attribute>
<attribute>
<name>onmousedown</name>
<required>false</required>
<rtexprvalue>false</rtexprvalue>
</attribute>
<attribute>
<name>onmousemove</name>
<required>false</required>
<rtexprvalue>false</rtexprvalue>
</attribute>
<attribute>
<name>onmouseout</name>
<required>false</required>
<rtexprvalue>false</rtexprvalue>
</attribute>
<attribute>
<name>onmouseover</name>
<required>false</required>
<rtexprvalue>false</rtexprvalue>
</attribute>
<attribute>
<name>onmouseup</name>
<required>false</required>
<rtexprvalue>false</rtexprvalue>
</attribute>
<attribute>
<name>title</name>
<required>false</required>
<rtexprvalue>false</rtexprvalue>
</attribute>
<attribute>
<name>style</name>
<required>false</required>
<rtexprvalue>false</rtexprvalue>
</attribute>
<attribute>
<name>lang</name>
<required>false</required>
<rtexprvalue>false</rtexprvalue>
</attribute>
<attribute>
<name>dir</name>
<required>false</required>
<rtexprvalue>false</rtexprvalue>
</attribute>
<attribute>
<name>summary</name>
<required>false</required>
<rtexprvalue>false</rtexprvalue>
</attribute>
<attribute>
<name>bgcolor</name>
<required>false</required>
<rtexprvalue>false</rtexprvalue>
</attribute>
<attribute>
<name>frame</name>
<required>false</required>
<rtexprvalue>false</rtexprvalue>
</attribute>
<attribute>
<name>rules</name>
<required>false</required>
<rtexprvalue>false</rtexprvalue>
</attribute>
<attribute>
<name>border</name>
<required>false</required>
<rtexprvalue>false</rtexprvalue>
</attribute>
<attribute>
<name>cellspacing</name>
<required>false</required>
<rtexprvalue>false</rtexprvalue>
</attribute>
<attribute>
<name>cellpadding</name>
<required>false</required>
<rtexprvalue>false</rtexprvalue>
</attribute>
<attribute>
<name>width</name>
<required>false</required>
<rtexprvalue>false</rtexprvalue>
</attribute>
</tag>

Here is some documentation describing frame and rules:
frame:
     Code specifying which sides of the frame surrounding
     this table will be visible. Valid values are:
     none (no sides, default value); above (top side only);
     below (bottom side only); hsides (top and bottom sides
     only); vsides (right and left sides only); lhs (left
     hand side only); rhs (right hand side only); box
     (all four sides); and border (all four sides).
rules:
     Code specifying which rules will appear between cells
     within this table. Valid values are:     none (no rules,
     default value); groups (between row groups); rows
     (between rows only); cols (between columns only); and
     all (between all rows and columns).
Justyna

Similar Messages

  • How to pass attribute of type java.util.ArrayList Property to a Tag

    How do I pass an attribute of type, java.util.ArrayList<my.entity.Property> to a Tag implementation class?
    Please advise!
    Thanks,
    Joe
    package my.tags;
    import java.io.IOException;
    import java.util.ArrayList;
    import javax.servlet.jsp.tagext.SimpleTagSupport;
    import javax.servlet.jsp.JspException;
    import my.entity.Property;
    public class PropertiesTag extends SimpleTagSupport {
        private ArrayList<Property> properties;
        public void setProperties(ArrayList<Property> properties) {
              this.properties = properties;
         public void doTag() throws JspException, IOException {
    <?xml version="1.0" encoding="utf-8" ?>
    <taglib ...>
         <tag>
              <name>propertiesTag</name>
              <tag-class>my.tags.PropertiesTag</tag-class>
              <body-content>empty</body-content>
              <description>Displays the product selection left menu</description>
              <attribute>
                   <name>properties</name>
                   <required>true</required>
                   <rtexprvalue>true</rtexprvalue>
                   <type>java.util.ArrayList<my.entity.Property></type>
              </attribute>
         </tag>
    </taglib>Here's the error message:
    org.xml.sax.SAXParseException: The element type "my.entity.Property" must be terminated by the matching end-tag "</my.entity.Property>".

    802826 wrote:
    How do I pass an attribute of type, java.util.ArrayList<my.entity.Property> to a Tag implementation class?
    Please advise!
    As already pointed out, there is no way to specify a generic type in a tag library descriptor. You may however specify an Object type in your tld and still have the variable in your tag as a parameterized generic type.
    In your tld change the type to Object.
    <type>java.lang.Object</type>.
    The properties tag itself needs no change and can continue to use parameterized types.
    cheers,
    ram.

  • Panel_Grid Tag

    I tried an example similar to the JSF tutorial. Unfortunately, only the panel_list tag works for me.
    This works:
    <h:panel_list id="testPanel">
         <h:panel_data id="tableData" var="theName" valueRef="customerBean.firstnames">
              <h:output_text id="desc" valueRef="theName.description"/>
              <h:output_text id="door" valueRef="theName.doors"/>
              </h:panel_data>
    </h:panel_list>
    but how does one specify the collection reference with a panel_GRID tag? the example does not show this....
    does anyone know? if someone got a working code example of a panel_grid, thanx a lot.
    cu
    sven

    A section from one of our JSP
    <body bgcolor="white">
         <h1>Please Enter / Correct your Employment Details</h1>
         <f:use_faces>
         <h:form id="employmentDetails" formName="EmploymentDetails">
              <d:stylesheet path="/stylesheet.css"/>
              <h:panel_grid id="info" columns="3" panelClass="medium" columnClasses="subtitle,medium">
              <h:input_text id="niNumber" valueRef="employee.NINumber" readonly="true"/>
              <h:output_text value="National Insurance Number"/>
              <h:input_text id="newNINumber" valueRef="employee.newHRDetails.NINumber"/>
              <h:input_date id="dateEmployed" valueRef="employee.emplpoymentDate" readonly="true"/>
              <h:output_text value="Date Employed"/>
              <h:input_date id="newDateEmployed" valueRef="employee.newHRDetails.emplpoymentDate"/>
              <h:input_text id="taxCode" valueRef="employee.taxCode" readonly="true"/>
              <h:output_text value="Tax Code"/>
              <h:input_text id="newTaxCode" valueRef="employee.newHRDetails.taxCode"/>
              </h:panel_grid>
              <h:command_button id="Continue" action="Continue" label="Continue" commandName="submit"/>
         </h:form>
         </f:use_faces>
    </body>
    Hope this helps

  • Assigning bean property to custom tag's attribute

    1. The #{beanName.property} notation can only be used inside JSF tags.
    2. The attributes of custom tags does not accept embedded tags.
    e.g. <prefix:tagName attrib1="<jsftag>">
    I need to assign a bean's property to the attrib1 attribute. how do I do this?

    Alternatively, how can I assign the value of a bean property to a variable?
    e.g.
    <%
    int var=<bean.property>
    %>
    I can use the variable on the custom tag like this:
    <prefix:tagName attrib1="<%=var%>"> OR
    But this may not be the best solution though because I have to use scriptlets...

  • Custom Tag Capitalization Problem..

    All,
              OS: Windows 2000
              App Server: Weblogic 6.0 sp 2
              JDK: 1.3 (and tried 1.3.1)
              I have a set of custom tags that run fine when I use them on an app server (such as Enhydra) with JDK 1.2.2, but when I switch to JDK 1.3.x, which weblogic 6.x requires, they suddenly start generating errors with attributes which have capitalized letters in them. For example, in my taglib I have:
              <attribute>
              <name>closeConnection</name>
              <required>false</required>
              <rtexprvalue>true</rtexprvalue>
              </attribute>
              and in the support class I have:
              * Get the value of closeConnection.
              * @return value of closeConnection.
              public boolean getCloseConnection() {
              return closeConnection;
              * Set the value of closeConnection.
              * @param v Value to assign to closeConnection.
              public void setCloseConnection(String v) {
              if(v.toUpperCase().equals("TRUE")){
              this.closeConnection = true;
              } else {
              this.closeConnection = false;
              When I go to the page that this tag is on, I get the following output:
              Parsing of JSP File '/index.jsp' failed:
              /index.jsp(1): Error in using tag library uri='/cwerks' prefix='cwerks': There is no setter method for property 'closeconnection', for Tag class 'net.cwerks.taglib.MyTag'
              probably occurred due to an error in /index.jsp line 1:
              <%@ taglib uri="/cwerks" prefix="cwerks" %>
              Thu Aug 02 19:06:52 PDT 2001
              Note that the 'closeconnection' is all lowercase despite the fact that it is upper case in the tld and in the class itself.
              I came across a similar problem in weblogic 5.1 when I upgraded from JDK 1.2.2 to JDK 1.3. I tried changing the JDK for weblogic 6.0 sp 2 to 1.2.2, but a dll was missing. I also tried switching it to 1.3.1, but that did not help. It seems like introspection may have changed slightly between the two version. I'm shocked, and a bit suspicious, that I haven't seen this problem all over the newsgroups. Anyone else seen this?
              Thank you,
              Carson Gross
              [email protected]
              [att1.html]
              

    A solution presents itself:
              The problem was NOT with capitalization. Instead, the problem was as
              follows:
              My method was for setting a boolean, but I took a string so that people
              wouldn't have to type:
              <mytags:tag foo="<%=true%>" />
              instead, they could type:
              <mytags:tag foo="true" />
              which would call the setter method with a string "true", which would be then
              converted to a boolean within my class.
              So my setter has this signature:
              public void setFoo(String s)
              and my getter has this signature:
              public boolean getFoo() /* I know this isn't standard, but isFoo doesn't
              sound good to me*/
              I can't tell if it's because JavaBeans changed slightly between jdk 1.2.2
              and 1.3.x, or if Weblogic changed the way that they do things (I suspect the
              latter, since I had things working fine in WL 5.2 w/ jdk 1.2.2 and then
              things broke with WL 5.2 w/ jdk 1.3), but this no longer returns foo as a
              valid property to be set, and since weblogic 6.x relies on JavaBeans,
              instead of straight up introspection, it barfs. (I found this out by using
              jad/emacs, a wicked combination for those who want to poke around in jars).
              Anyway, I hope I can save someone else who has this same, albeit
              specialized, problem a lot of pain by my discovery. Your getters and
              setters better be of the same type with custom tags, or weblogic w/ jdk1.3.x
              is gonna barf when parsing the tld.
              Cheers, and thank God that's behind me,
              Carson Gross
              [email protected]
              ====================================================
              "Carson Gross" <[email protected]> wrote in message
              news:[email protected]...
              The plot grows thicker...
              The tags work fine on Tomcat 3.2.2
              I deploy the example tags that came with wl60 that have more than one
              capital letter in thier attributes, and they work fine. But my tag library
              stubbornly insists on not working so long as I keep the attributes with more
              than one capital letter in. If I remove the offending attributes, or change
              them to have only one capital letter, they work, but this is not an
              acceptable solution. (I guess.)
              I even created an simple introspection class to make sure that the acutal
              methods were there. They were.
              I am at a complete loss here... I guess it's tomcat for now.
              Cheers,
              Carson Gross
              [email protected]
              "Carson Gross" <[email protected]> wrote in message
              news:[email protected]...
              All,
              OS: Windows 2000
              App Server: Weblogic 6.0 sp 2
              JDK: 1.3 (and tried 1.3.1)
              I have a set of custom tags that run fine when I use them on an app server
              (such as Enhydra) with JDK 1.2.2, but when I switch to JDK 1.3.x, which
              weblogic 6.x requires, they suddenly start generating errors with attributes
              which have capitalized letters in them. For example, in my taglib I have:
              <attribute>
              <name>closeConnection</name>
              <required>false</required>
              <rtexprvalue>true</rtexprvalue>
              </attribute>
              and in the support class I have:
              * Get the value of closeConnection.
              * @return value of closeConnection.
              public boolean getCloseConnection() {
              return closeConnection;
              * Set the value of closeConnection.
              * @param v Value to assign to closeConnection.
              public void setCloseConnection(String v) {
              if(v.toUpperCase().equals("TRUE")){
              this.closeConnection = true;
              } else {
              this.closeConnection = false;
              When I go to the page that this tag is on, I get the following output:
              Parsing of JSP File '/index.jsp' failed:
              /index.jsp(1): Error in using tag library uri='/cwerks' prefix='cwerks':
              There is no setter method for property 'closeconnection', for Tag class
              'net.cwerks.taglib.MyTag'
              probably occurred due to an error in /index.jsp line 1:
              <%@ taglib uri="/cwerks" prefix="cwerks" %>
              Thu Aug 02 19:06:52 PDT 2001
              Note that the 'closeconnection' is all lowercase despite the fact that it is
              upper case in the tld and in the class itself.
              I came across a similar problem in weblogic 5.1 when I upgraded from JDK
              1.2.2 to JDK 1.3. I tried changing the JDK for weblogic 6.0 sp 2 to 1.2.2,
              but a dll was missing. I also tried switching it to 1.3.1, but that did not
              help. It seems like introspection may have changed slightly between the two
              version. I'm shocked, and a bit suspicious, that I haven't seen this
              problem all over the newsgroups. Anyone else seen this?
              Thank you,
              Carson Gross
              [email protected]
              

  • Problem with child tag - Could not resolve x to a component implementation.

    Hello.
    I am writing some chart component and got a problem setting property via child tag. Property is a custom class.
    My directory structure:
    Makefile  oxcharts  Session.vim  stats.as  stats.mxml  stats.swf
    ./oxcharts:
    ColumnChart.as MyTest.as
    stats.mxml:
    <mx:Application xmlns:mx="http://www.adobe.com/2006/mxml" xmlns:oxcharts="oxcharts.*">
        <oxcharts:ColumnChart id="myChart" showDataTips="true" width="600" height="310">
            <oxcharts:test x="5"></oxcharts:test>
         </oxcharts:ColumnChart>
    </mx:Application>
    ColumnChart.as:
    package oxcharts {
        public class ColumnChart extends UIComponent {
            public var test:MyTest;
    MyTest.as:
    package oxcharts {
        public class MyTest {
            public var x:Number;
    I got this error:
    Error: Could not resolve <oxcharts:test> to a component implementation.
    I guess something wrong with imports. Setting Number property via child tag works just fine.

    I'm gonna give a clerear example, I hope it'll help you better understand what I mean let's say I have a custom class named Login:
    package ec
             [Bindable]
         public class Login
              public var ID:int;
              public var Role:String;         
              public function Login()
    And I need to use this class within MyAmazingCanvas, so my main app will be like this:
    <?xml version="1.0" encoding="utf-8"?>
    <mx:Application xmlns:mx="http://www.adobe.com/2006/mxml" layout="absolute" xmlns:oxcharts="ec.*">
         <mx:Script>
              <![CDATA[
                   import ec.Login;
                   [Bindable]
                   private var myLoginStatus:Login=new Login();
                   private function setLoginData():void{
                        myLoginStatus.ID=myID.text
                        myLoginStatus.Role=myRole.text;
              ]]>
         </mx:Script>
         <oxcharts:MyAmazingCanvas id="myCustomComp" myPublicNumber="323" LoginStatus="{myLoginStatus}" />
         <mx:TextInput id="myID" />
         <mx:TextInput id="myRole" />
         <mx:Button id="setData" label="Set Data" click="setLoginData()" />
    </mx:Application>
    When I said at the top level I meant outside the scope of any function, altough is not a requierement, you can as well set it at a function level.

  • Problem with JSP Tag class

    Hi,
              After some time of work, WLS ends up with the following error message:
              weblogic.servlet.jsp.JspException: (line -1): Error in tag library at:
              'cm': There is no setter method for property 'limit', for Tag
              class 'com.hp.module.cm.tag.GetDocumentsTag'
              at
              weblogic.servlet.jsp.StandardTagLib.jspException(StandardTagLib.java:138)
              at
              weblogic.servlet.jsp.StandardTagLib.processTag(StandardTagLib.java:272)
              at
              weblogic.servlet.jsp.StandardTagLib.processTagElements(StandardTagLib.java:146)
              at
              weblogic.servlet.jsp.StandardTagLib.<init>(StandardTagLib.java:125)
              at weblogic.servlet.jsp.JspLexer.loadTagLib(JspLexer.java:87)
              at
              weblogic.servlet.jsp.JspLexer.mTAGLIB_DIRECTIVE_BODY(JspLexer.java:3811)
              at
              weblogic.servlet.jsp.JspLexer.mTAGLIB_DIRECTIVE(JspLexer.java:3561)
              at weblogic.servlet.jsp.JspLexer.mDIRECTIVE(JspLexer.java:3422)
              at
              weblogic.servlet.jsp.JspLexer.mSTANDARD_THING(JspLexer.java:1760)
              at weblogic.servlet.jsp.JspLexer.mTOKEN(JspLexer.java:1601)
              at weblogic.servlet.jsp.JspLexer.nextToken(JspLexer.java:1491)
              at weblogic.servlet.jsp.JspLexer.parse(JspLexer.java:880)
              at weblogic.servlet.jsp.JspParser.doit(JspParser.java:69)
              at weblogic.servlet.jsp.JspParser.parse(JspParser.java:116)
              at weblogic.servlet.jsp.Jsp2Java.outputs(Jsp2Java.java:97)
              at
              weblogic.utils.compiler.CodeGenerator.generate(CodeGenerator.java:242)
              at weblogic.servlet.jsp.JspStub.compilePage(JspStub.java:302)
              at weblogic.servlet.jsp.JspStub.prepareServlet(JspStub.java:217)
              at
              weblogic.servlet.internal.ServletStubImpl.getServlet(ServletStubImpl.java:164)
              at
              weblogic.servlet.internal.ServletStubImpl.invokeServlet(ServletStubImpl.java:101)
              at
              weblogic.servlet.internal.ServletStubImpl.invokeServlet(ServletStubImpl.java:124)
              at
              weblogic.servlet.internal.ServletContextImpl.invokeServlet(ServletContextImpl.java:907)
              at
              weblogic.servlet.internal.ServletContextImpl.invokeServlet(ServletContextImpl.java:851)
              at
              weblogic.servlet.internal.ServletContextManager.invokeServlet(ServletContextManager.java:252)
              at
              weblogic.socket.MuxableSocketHTTP.invokeServlet(MuxableSocketHTTP.java:364)
              at
              weblogic.socket.MuxableSocketHTTP.execute(MuxableSocketHTTP.java:252)
              at weblogic.kernel.ExecuteThread.run(ExecuteThread.java:129)
              The class does contain the setter, so we don't know why the message pops
              up. After rebooting the server, the page works properly (!) Does anyone
              know how to get rid of it ? We're running out of ideas, and rebooting
              the server every 2-3 days is not acceptable.
              The configuration consists of BEA WebLogic 5.1.0 SP8 + JDK 1.2.2_07 +
              HPUX 11.0.
              Any help is greatly appreciated.
              Jacek Laskowski
              

    so doesn you bean have a
              void setLimit(String) {}
              String getLimit() {}
              or does it have mismatched getter and setter?
              like
              setLimit(String) {}
              int getLimit() {}
              take a look at :
              http://developer.java.sun.com/developer/bugParade/bugs/4407050.html
              -Nagesh
              Jacek Laskowski wrote:
              > Hi Mike,
              >
              > Thanks for the response. Unfortunatelly, it's happening on a production
              > server and nobody's changing anything. The error message pops up every
              > 2-3 days and the only way to get rid of that is to reboot the server.
              > Hmmm...I could even say it's hitting us quite regularly.
              >
              > The first time I've seen this I thought that there might be somewhere a
              > class which does not really have the necessary setter. It might've been
              > a case, but it's not. Even though we assume it might happen, what's
              > going on with the WLS classloaders that they pick up the right class at
              > the startup and after some time they change their mind and pick up the
              > wrong one. That would be a bug, shouldn't it ?
              >
              > What's more annoying is the fact that we're not able to open a case in
              > the support as there is nothing to be shown. There is merely the error
              > message which anybody can clearly explain that it relates to a wrong
              > class - no setter in it.
              >
              > The only way I can think of would be to enable remote debugging and as
              > soon as it's happend, connect to the WLS JVM and see what's wrong. We
              > don't have the WLS sources, though.
              >
              > -Jacek
              >
              > Mike Reiche wrote:
              > >
              > > Is it possible that the tag was changed - an attribute was added in the .tld and
              > > to the class?
              > >
              > > The new .tld is seen immediately. The new class is not - not until you restart
              > > WL.
              > >
              > > Mike
              > >
              > > Jacek Laskowski <[email protected]> wrote:
              > > >Hi,
              > > >
              > > >After some time of work, WLS ends up with the following error message:
              > > >
              > > >weblogic.servlet.jsp.JspException: (line -1): Error in tag library at:
              > > >'cm': There is no setter method for property 'limit', for Tag
              > > > class 'com.hp.module.cm.tag.GetDocumentsTag'
              > > > at
              > > >weblogic.servlet.jsp.StandardTagLib.jspException(StandardTagLib.java:138)
              > > > at
              > > >weblogic.servlet.jsp.StandardTagLib.processTag(StandardTagLib.java:272)
              > > > at
              > > >weblogic.servlet.jsp.StandardTagLib.processTagElements(StandardTagLib.java:146)
              > > > at
              > > >weblogic.servlet.jsp.StandardTagLib.<init>(StandardTagLib.java:125)
              > > > at weblogic.servlet.jsp.JspLexer.loadTagLib(JspLexer.java:87)
              > > > at
              > > >weblogic.servlet.jsp.JspLexer.mTAGLIB_DIRECTIVE_BODY(JspLexer.java:3811)
              > > > at
              > > >weblogic.servlet.jsp.JspLexer.mTAGLIB_DIRECTIVE(JspLexer.java:3561)
              > > > at weblogic.servlet.jsp.JspLexer.mDIRECTIVE(JspLexer.java:3422)
              > > > at
              > > >weblogic.servlet.jsp.JspLexer.mSTANDARD_THING(JspLexer.java:1760)
              > > > at weblogic.servlet.jsp.JspLexer.mTOKEN(JspLexer.java:1601)
              > > > at weblogic.servlet.jsp.JspLexer.nextToken(JspLexer.java:1491)
              > > > at weblogic.servlet.jsp.JspLexer.parse(JspLexer.java:880)
              > > > at weblogic.servlet.jsp.JspParser.doit(JspParser.java:69)
              > > > at weblogic.servlet.jsp.JspParser.parse(JspParser.java:116)
              > > > at weblogic.servlet.jsp.Jsp2Java.outputs(Jsp2Java.java:97)
              > > > at
              > > >weblogic.utils.compiler.CodeGenerator.generate(CodeGenerator.java:242)
              > > > at weblogic.servlet.jsp.JspStub.compilePage(JspStub.java:302)
              > > > at weblogic.servlet.jsp.JspStub.prepareServlet(JspStub.java:217)
              > > > at
              > > >weblogic.servlet.internal.ServletStubImpl.getServlet(ServletStubImpl.java:164)
              > > > at
              > > >weblogic.servlet.internal.ServletStubImpl.invokeServlet(ServletStubImpl.java:101)
              > > > at
              > > >weblogic.servlet.internal.ServletStubImpl.invokeServlet(ServletStubImpl.java:124)
              > > > at
              > > >weblogic.servlet.internal.ServletContextImpl.invokeServlet(ServletContextImpl.java:907)
              > > > at
              > > >weblogic.servlet.internal.ServletContextImpl.invokeServlet(ServletContextImpl.java:851)
              > > > at
              > > >weblogic.servlet.internal.ServletContextManager.invokeServlet(ServletContextManager.java:252)
              > > > at
              > > >weblogic.socket.MuxableSocketHTTP.invokeServlet(MuxableSocketHTTP.java:364)
              > > > at
              > > >weblogic.socket.MuxableSocketHTTP.execute(MuxableSocketHTTP.java:252)
              > > > at weblogic.kernel.ExecuteThread.run(ExecuteThread.java:129)
              > > >
              > > >The class does contain the setter, so we don't know why the message pops
              > > >up. After rebooting the server, the page works properly (!) Does anyone
              > > >know how to get rid of it ? We're running out of ideas, and rebooting
              > > >the server every 2-3 days is not acceptable.
              > > >
              > > >The configuration consists of BEA WebLogic 5.1.0 SP8 + JDK 1.2.2_07 +
              > > >HPUX 11.0.
              > > >
              > > >Any help is greatly appreciated.
              > > >
              > > >Jacek Laskowski
              

  • Html:select tag

    Hi all,
    In my jsp page i am using struts html:select tag,some contents are not fitting in the alloted size so i want to give horizontal scrolling for this select box,pls any body can tell me which property of select tag can be used,or any html tricks by which i can achive horizontal scrolling.examples will be help full.
    thanks,

    There aren't any tricks. This has nothing to do with Struts or JSP. It only has to to with HTML. The width is controlled by the size of the options or the size of the HTML area it has to display in. The latter if it's restricted otherwise by some table cell's width. I don't believe that I've ever seen a select box which has horizontol scrolling in any browser ever.

  • Can we pass the ant property to the wlst script?

    Hi,
    I am using WLST to configure domain. Is there ant way in which we can pass the ant property to script tag? Rite now we are hardcoding the username, password and serverIp in the script.
    <target name="configServer">
    <wlst debug="false" failOnError="false" executeScriptBeforeFile="true" fileName="./myscript.py">
    <script> connect('weblogic','weblogic','t3://localhost:7001')
    </script>
    </wlst>
    </target>
    So essentially the above script will lok like following
    <target name="configServer">
    <wlst debug="false" failOnError="false" executeScriptBeforeFile="true" fileName="./myscript.py">
    <script> connect(${username},${password},'t3://${serverIP}:7001')
    </script>
    </wlst>
    </target>
    Thanks,

    In 10.3, we added a replaceProperties option to allow ant properties to be
    evaluated in <script> tag.
    In the meantime, you may be able to use the load properties command in WLST.
    <Scott Ding> wrote in message news:[email protected]..
    Hi,
    I am using WLST to configure domain. Is there ant way in which we can pass
    the ant property to script tag? Rite now we are hardcoding the username,
    password and serverIp in the script.
    <target name="configServer">
    <wlst debug="false" failOnError="false" executeScriptBeforeFile="true"
    fileName="./myscript.py">
    <script> connect('weblogic','weblogic','t3://localhost:7001')
    </script>
    </wlst>
    </target>
    So essentially the above script will lok like following
    <target name="configServer">
    <wlst debug="false" failOnError="false" executeScriptBeforeFile="true"
    fileName="./myscript.py">
    <script> connect(${username},${password},'t3://${serverIP}:7001')
    </script>
    </wlst>
    </target>
    Thanks,

  • Can't set bean1's int property with bean 2's int property

    Using JDeveloper 3.2.3 (with JSP 1.1), the following fails to compile:
    <jsp:useBean id="user" type="pkg.User" scope="session"/>
    <jsp:useBean id="user2" type="pkg.User"/>
    <jsp:setProperty name="user2" property="id" value=" <jsp:getProperty name="user" property="id"/> "/>
    The compile error is...
    Error in attribute list: Unable to convert constant to property type: int
    The pkg.User id property is an int. If I change the code to set a String property it works fine!
    The workaround is to do the following:
    <jsp:setProperty name="user2" property="id" value=" <%= user.getId() %> "/>
    However, I prefer the XML syntax.
    Environment:
    JDeveloper 3.2.3 (build 1018)
    Windows 2000
    null

    Unfortunately, this is the major limitation of using cooperating beans in a JSP. The JSP tag translation mechanisms just don't handle passing non-String parameters between beans very well. I have half a mind to write a tag extension where you can pass in a source bean and property and a destination bean and property and the tag will generate the code to set the destination property based on the source property.
    Unless someone already has one out there, I may just do this and pass it around. Something like:
    <jfh:passObject
    source="bean1" source_property="id"
    dest="bean2" dest_property="id"
    />Of course, I would have to worry about ClassCastExceptions if the source property and destination property are not convertible, but it would be useful nonetheless to be able to pass around Java objects without having to write the code into the JSP.
    Ideas, thoughts?
    John H.

  • Contains HTML tags & print

    Hi,
    Reports6i patch10
    Scenario is: I have a column (database colummn text with embedded HTML ) where I set property 'Contains HTML tags'
    I get the column incl html rendered find where desformat=html&destype=file&desname=myfile.html '
    but when setting
    destype=printer&desformat=html&desname=myqueue and sending output straight to printerqueue the html is not being rendered in fact the column is not rendered at all
    HAs anyone similar experience ? solutions ?
    TIA
    Per

    Hello Per Elmgreen,
    When DESTYPE is specified as PRINTER, Reports formats output in PS or PCL format (depending on the printer language understood by the destination printer). Since these formats do not understand HTML tags, any such markup in the output will remain unformatted.
    In order to get properly formatted output using HTML tags, you could generate the report to a HTML file (with the 'Contains HTML tags' property set) and then print the file using a browser.
    Thanks,
    The Oracle Reports Team.

  • JSP 2.0 tags with JSF

    Hi! I'm trying to mix jsf template with JSP 2.0 tag.
    I almost did it, but still have some trouble.
    MyForm.jspf:
    <%@ taglib uri="http://java.sun.com/jsf/html" prefix="h" %>
    <%@ taglib uri="http://java.sun.com/jsf/core" prefix="f" %>
    <%@ taglib prefix="tmpl" tagdir="/WEB-INF/tags" %>
    <tmpl:date bean="${MyForm}" property="date" />
    date.tag
    <%@ taglib uri="http://java.sun.com/jsp/jstl/core" prefix="c" %>
    <%@ taglib uri="http://java.sun.com/jsf/html" prefix="h" %>
    <%@ taglib uri="http://java.sun.com/jsf/core" prefix="f" %>
    <%@ attribute name="bean" type="java.lang.Object" %>
    <%@ attribute name="property" %>
    <c:set var="form" value="${bean}" scope="session"/>
    <c:set var="property" value="${property}" scope="session"/>
    <f:subview id="time">
    <h:inputText id="date" value="#{form[property]}">
    <f:convertDateTime pattern="dd/MM/yyyy" />
    </h:inputText>
    because I have to use JSP EL (${MyForm}) to pass a parameter to the tag the managed bean is not initialized, submit fails for the first time, but works after the bean being initialized.
    Again setting "property" to session scope otherwise it doesn't work, so I will have this during the session... I am lost in JSP EL/JSF EL context relation.
    Does anyone use it???
    Sincerely,
    D.

    I made a little improvement, but still have some questions...
    MyForm.jspf:
    <%@ taglib uri="http://java.sun.com/jsf/html" prefix="h" %>
    <%@ taglib uri="http://java.sun.com/jsf/core" prefix="f" %>
    <%@ taglib prefix="tmpl" tagdir="/WEB-INF/tags" %>
    <tmpl:date bean="ResidentAttentionForm" property="date" />
    date.tag:
    <%@ taglib uri="http://java.sun.com/jsp/jstl/core" prefix="c" %>
    <%@ taglib uri="http://java.sun.com/jsp/jstl/fmt" prefix="fmt" %>
    <%@ taglib uri="http://java.sun.com/jsf/html" prefix="h" %>
    <%@ taglib uri="http://java.sun.com/jsf/core" prefix="f" %>
    <%@ attribute name="bean" %>
    <%@ attribute name="property" %>
    <c:set var="bean" value="${bean}" scope="request"/>
    <jsp:scriptlet>
    javax.faces.context.FacesContext.getCurrentInstance().getApplication().getVariableResolver().resolveVariable(javax.faces.context.FacesContext.getCurrentInstance(), (String)request.getAttribute("bean"));
    </jsp:scriptlet>
    <c:set var="form" value="${sessionScope[bean]}" scope="session"/>
    <c:set var="property" value="${property}" scope="session"/>
    <f:subview id="time">
    <h:inputText id="date" value="#{form[property]}">
    <f:convertDateTime pattern="dd/MM/yyyy" />
    </h:inputText>
    The problem here:
    1. how can I access from JSF EL to the tag attribute without passing it to the request??? (I've seen the question in the forum, but not the answer...)
    2. Is there a way to initialize a bean with dynamic name (<c: set var="${name}"?
    3. When we will have jsf 1.2 done? ;-) I know they said "with J2EE5", but it also has been said "J2EE5 - summer 2005" and now everyone is talking about 2006 (?). Why can't they make jsr for jsp 2.1 and jsf 1.2 before J2EE5?.
    Sincerely,
    D.

  • How to use the JRun Custom tag library wiith Weblogic 5.1?

    Hello,
    is it possible to use the JRUN Tag Library with Bea Weblogic 5.1? We
    got an error message like:
    weblogic.servlet.jsp.JspException: (line -1): Error in tag library at:
    'jrun': T
    here is no setter method for property 'code', for Tag class
    'allaire.taglib.Serv
    letTag'
    Thank you for any info!
    Stefan

    Hi Joe,
    I don't know, however someone that follows the JSP newsgroup [1] may be
    able to help. Could you try your post there.
    Thanks,
    Bruce
    [1]
    http://newsgroups.bea.com/cgi-bin/dnewsweb?cmd=xover&group=weblogic.developer.interest.jsp
    Joe Kamenar wrote:
    >
    I have a question. I need to do a sort on news articles in our database, sorting
    by the date they were posted. I then want to take only the top 6 articles. We
    are using Weblogic 5.1. When I use the following statement, 6 articles are taken
    from the database, then sorted, which ends up leaving out the most recent articles:
    <cm:select contentHome="com.beasys.commerce.axiom.document.Document" query="<%=contentQuery%>"
    sortby = "creationDate DESC, headlineDate DESC" max="6" id="contentList" />
    I need to get ALL the articles for the sort, then just take the most recent 6.
    So, I know that I can use the following code and monitor the counter variable,
    "i". But, how do i do this to only display the top 6 items?
    <es:foreachinarray id="content" array="contentList" type="com.beasys.commerce.axiom.content.Content"
    counterId="i">
    <% myStr=content.getIdentifier(); %>
    <% if (i<6) {
    %>
    <div class="marginText">
    <cm:printproperty id="content" name="title" encode="html" />  
    <a href="<%=new String(news_display.jsp?id="+myStr)%">">more</a>
    </div>
    <% } %>
    </es:foreachinarray>
    However, when I run this, no results show up. What is the correct way to do this?
    - Joe</a>

  • How to use the JRun Custom tag library with Weblogic 5.1?

    Hello,
              is it possible to use the JRUN Tag Library with Bea Weblogic 5.1? We
              got an error message like:
              weblogic.servlet.jsp.JspException: (line -1): Error in tag library at:
              'jrun': T
              here is no setter method for property 'code', for Tag class
              'allaire.taglib.Serv
              letTag'
              Thank you for any info!
              Stefan
              

    Hi Joe,
    I don't know, however someone that follows the JSP newsgroup [1] may be
    able to help. Could you try your post there.
    Thanks,
    Bruce
    [1]
    http://newsgroups.bea.com/cgi-bin/dnewsweb?cmd=xover&group=weblogic.developer.interest.jsp
    Joe Kamenar wrote:
    >
    I have a question. I need to do a sort on news articles in our database, sorting
    by the date they were posted. I then want to take only the top 6 articles. We
    are using Weblogic 5.1. When I use the following statement, 6 articles are taken
    from the database, then sorted, which ends up leaving out the most recent articles:
    <cm:select contentHome="com.beasys.commerce.axiom.document.Document" query="<%=contentQuery%>"
    sortby = "creationDate DESC, headlineDate DESC" max="6" id="contentList" />
    I need to get ALL the articles for the sort, then just take the most recent 6.
    So, I know that I can use the following code and monitor the counter variable,
    "i". But, how do i do this to only display the top 6 items?
    <es:foreachinarray id="content" array="contentList" type="com.beasys.commerce.axiom.content.Content"
    counterId="i">
    <% myStr=content.getIdentifier(); %>
    <% if (i<6) {
    %>
    <div class="marginText">
    <cm:printproperty id="content" name="title" encode="html" />  
    <a href="<%=new String(news_display.jsp?id="+myStr)%">">more</a>
    </div>
    <% } %>
    </es:foreachinarray>
    However, when I run this, no results show up. What is the correct way to do this?
    - Joe</a>

  • No setter method found - custom tag

              Hi Guys
              When I attempt to access a .jsp that is making use of a custom tag library that
              I've written I'm seeing the following message:
              "weblogic.servlet.jsp.JspException: (line 1): Error in using tag library uri='/WEB-INF/LSTreeControl.tld'
              prefix='tree':
              There is no setter method for property 'colIndex', for Tag class 'com.levelseas.core.web.tag.treecontrol.LSSubmitParamTag"
              The method has a signature of:
              "public void setColIndex(String index) throws JspTagException"
              and the Class has a number of sets defined on it and this is the only one that
              is being complained about. If I remove this attribute then no complaint!
              I'm new to bea but have been around jsp for a while so I'm wondering if this is
              a feature of wls 6.1 and would love to know a way around it.
              Any help appreciated
              J
              

              Hi Guys
              Problem is almost certainly because I've gone and defined the get as returning
              an int, (hence no property!)
              Apols
              J
              

Maybe you are looking for