Of the version attribute of a HelpSet tag

Okay, I admit to being somewhat stumped here.
Is there any way to access the value of the version attribute of the helpset element (or indeed, any of the version attributes of any of the various index, content & map files)?
I'm trying to version an app's help content, and while these version attributes seem ready made for my purposes, without any way to access them from w/in the JH API, they're effectively useless (I don't want to have to resolve the known location of the .hs or .jhm file(s) just to parse them and get the version attribute(s) value(s) if possible, and I don't want to explore viable alternate versioning methods until I know why this one won't work).
I'm having a really hard time understanding why this attrib. isn't/wasn't exposed. Maybe I'm just having a brainblock in seeing where/how it's exposed.
All thoughts, comments, suggestions and questions are entertained, if not outright entertaining. Thanks in advance,
-dSn

See what happens when ya don't read the spec's backing the API's ya use? I haven't read that spec in over 2 years, and apparently it didn't jump out at me at that time as importand and/or major. Guess it all depends on what you're looking for when you read something.
Thanks for the quick help; I'm off to implement my own personal version...erm...vision of versioning...um...anyway, back to it.
Thanks again!
-dSn

Similar Messages

Reg : xml version attribute in xml

Hi, van body tell me what is the significance of version attribute.
sometimes we use 1.0 , some times we use 4.0.
2 ) encoding attribute...? when we use UTF , ISO. and tell me among the
version , encoding which are mandatory, optional.
<?xml....?> --tag is optinal or not

The version attribute specifies the version of the XML standard you are using. 4.0 is not a valid version. You get 1.0 or (maybe if the parser supports it), 1.1. There is no XML version 4.0.
This value is not to be used for versioning your documents within your application context but is for parsers to determine which version of XML they must comply with when parsing your document.
See the prolog section in the XML specification:
http://www.w3.org/TR/xml/#sec-prolog-dtd
The encoding lets your parser know how the document's bytes were encoded so it can decode them properly. A simple google search for info on the encoding types, UTF-8, UTF-16, ISO-8859-1, etc. will tell you all you need to know.
Finally, the declaration <?xml ...?> is optional but recommended. Not only is it good practice, but it will ensure maximum portability of your documents (some parsers will reject the doc if you don't have it).

The name attribute on the img element is obsolete. Use the id attribute instead.

When I valadate my page I get an error "The name attribute on the img element is obsolete. Use the id attribute instead." In DW CS5.5 I cannot seem to enter an ID without DW also adding the ID as a name attribute too. Aside from manually going in and removing the name attribute from the code.

It won't hurt to leave the name attribute in your <img> tag. In fact, it may be necessary if you are going to add an image rollover behavior, since DW's javascript relies on that name attribute's value to correctly identify the desired image on the page.

How can I apply new attributes to a table-Tag in an JEditorPane?

I'm using a JEditorPane as a base for a small HTML-Editor. The manipulating of the attributes of an image-tag such as href works fine. But now I want to add the width-attribute to an table-tag.
The result: Nothing in the table-tag, but other strange things (width is set to any TD oder in every cell a new table is added.
How can I do this? Any suggestions??
Thanks.

Did you ever solve this problem?
I can manipulte the <p> tags and character styles, but the manipulation of <td>, <div> and other standard tags I cannot figure out.
Please let us know, [email protected]
By the way:
If you have only a width tag in your images, does it resize proportionaly, as in a normal browser or is the height taken from the original picture, as it happens with me?
This is quite nasty, since I do not know the original picture sizes.

Attribute styleclass invalid for tag dataTable according to TLD

I'm trying to use the styleclass attribute for the dataTable tag as described in Sun's "Core Java Server Faces", pg 179.
I get the error "Attribute styleclass invalid for tag dataTable according to TLD".
Any ideas?

Oooops. I missed the capitalisation of "C" in styleClass.
Works now.

What is the use of version attribute in jnlp tag??

Hello,
I want to know what is the use of version attribute in jnlp tag.
For ex:
<jnlp spec="6.0+" codebase="$$codebase" href="$$name" version="1.1">
</jnlp>
In the spec it explains:
In the Jnlp tag:
version = The version of the application being launched, as well as the version of the JNLP file itself.
1. Is this version attribute would work as version attribute in jar tag. Ex: <jar href="application.jar" version="1.1"/> ?
i.e. can we specify different jnlp's with the same name as we do for jar's with the help of version.xml.
Any help is greatly appreciated.
//Anjali

Hi Reddy,
If one Info Object depends on another info object we will make that dependent info object as a compounding attribute of main Info object.
Eg: Storage Location – Plant
In above eg there is no meaning of Storage Location without Plant. So, we will make storage location as compounding attribute of Plant.
Regards,
Sreehari.

Using the binding attribute within Tomahawk's t:dataList tag

I am trying to create a .jsp page with a dynamic list of tables. Each table on the page has a dynamic number of columns. I read an excellent blog ([The BalusC Code - Using datatables|http://balusc.blogspot.com/2006/06/using-datatables.html#PopulateDynamicDatatable]) that taught me how to create dynamic tables using the binding attribute. I can now get the tables with dynamic columns working.
What I would like to do next is nest the dynamic tables within a Tomahawk t:dataList tag:
<t:dataList value="#{utilitiesTableSegBean.attributeTables}" var="attributeTable">
    <h:outputText value="#{attributeTable.title}"/>
    <h:panelGroup binding="#{attributeTable.dynamicTableGroup}/>
</t:dataList>
{code}
When I run my app I get this error:
javax.servlet.ServletException: javax.servlet.jsp.JspException: org.apache.jasper.el.JspPropertyNotFoundException: /s/UtilitiesTableSeg.jsp(57,56) '#{attributeTable.dynamicTableGroup}' Target Unreachable, identifier 'attributeTable' resolved to null
Why do I get this error?
If I remove the h:panelGroup tag then the h:outputText tag works just fine. Why does 'attributeTable' resolve to null for the binding attribute of h:panelGroup, yet works for the value attribute of h:outputText?
So then I thought that I might be able to make it work with an index into a bean property that returned the list of table objects. So I tried to modify my panel group tag to:
{code}<h:panelGroup binding="#{utilitiesTableSegBean.attributeTables[0].dynamicTableGroup}"/>{code}
I was just doing a quick initial test and expected to see the first table repeated over and over because I had hard coded the value of '0' as the index. But I was wrong. It listed through all of the tables correctly. Why? This makes no sense to me!
So I changed my jsp again so that it looked like this:
{code}
<t:dataList rowIndexVar="tableIndex" value="#{utilitiesTableSegBean.attributeTables}" var="attributeTable">
    <h:outputText value="#{attributeTable.title}"/>
    <h:panelGroup binding="#{utilitiesTableSegBean.attributeTables[tableIndex].dynamicTableGroup}"/>
</t:dataList>
{code}
This is how I expected to code it so that the tables would all be shown correctly. And it gives this error:
org.apache.jasper.JasperException: An exception occurred processing JSP page /s/UtilitiesTableSeg.jsp at line 57
(Line 57 is the line with the h:panelGroup tag.)
Root cause: javax.servlet.ServletException: javax.servlet.jsp.JspException: java.lang.IllegalArgumentException: null
I would really like to get the original version working, but any feedback and/or suggestions would be greatly appreciated. I have spent a lot of time trying to figure this out and I just don't know where else to look.
Thank you very much!
Dave

Yes, sorry about that - I started off trying to prove a potential solution.
Aim:
A user logs onto a weblogic application and is authenticated against OID. The application is making SOAP service calls to a proxy endpoint monitored by another vendors software which authenticates the user against the ldap and checks their roles to see if the user can call the service.
Solution so far:
The initial application gets the username from the JAAS principal, but the password is not supplied. I can easily supply the SHA password digest to it (but putting a cleartext password in the header will probably not be given the go-ahead). This would enable the application to make the SOAP call with a username and digest.
The software protecting the services can be configured in a variety of ways to authenticate the user to the ldap. One involves using the wsse username token in the header (cleartext password or digest).
This authentication is failing and I don't yet have the diagnostic tools available to see which stage is in error. I was trying to prove that you could actually authenticate with an SHA password digest by doing a bind.
Regards

How to set an attribute of a HTML tag with a value in the Servlet

I have a HTML page and a Servlet.
The HTML page sends a request to the Servlet.
The Servlet has to read the contents of the HTML page. When the Servlet encounters the body tag it should set the bgcolor attribute of the body tag with a string(For eg.a string called color with a value blue) in the servlet.
After doing this the Servlet has to update the original HTML page with the changes (in the body tag).
I need a help on this.

Hi sangee,
you could get what you want to do by using a Java Server Page instead of both a HTML page and a Servlet.
I should code something like this:
<%Strung color="yourColor"%>
<html><head><title></title></head>
<body bgcolor="<%=color%>
</body>
</html>

A version attribute is required, but this version of the Weblogic Server

Hello,
I am seeing below error in my weblogic server logs couple of times in a day. I have gone through couple of blogs and seems this error is related to weblogic patch.
Could someone please help me understand what exactly this error represent to and what could be impact because of this. So far we dont see any issue in our development enviroment but want to fix this error.
we are using WLS 10.3.5
Error :-
<Feb 7, 2013 1:03:03 PM EST> <Warning> <Munger> <BEA-2156203> <A version attribute was not found in element application in the deployment descriptor in
Oracle/Middleware/user_projects/domains/osb_domain/sbgen/_ALSB_1360084990664.ear/META-INF/application.xml. A version attribute is required, but this
version of the Weblogic Server will assume that the JEE5 is used. Future versions of the Weblogic Server will reject descriptors that do not specify the JEE
version.>

Yes. It is a bug!!!
Apply the patch for bug 11720907.
1. Download the patch
Sign in in My Oracle Support. Choose Patches & Updates
Type 11720907 in textfield 'Patche Name or Number'
This is the path:
Patch 11720907: SU Patch [2IE6]: <A VERSION ATTRIBUTE WAS NOT FOUND IN ELEMENT PERSISTENCE ..>
2. Appy the path using Smart Update

Modifying Category Attributes without bumping the version of a versioned do

Hi,
I was wondering if anybody knows how I can make a change to a document's category attributes without having the document bump up a version.
I have an Event Handler that detects specific events where I am required to change a couple of attribute values.
The document itself could have versioning turned on explicitly or it could have inherited the feature via the folder. Either way, I'd like to shut down the versioning for a moment, make the change and re-set it to normal operation.
Thanks
Winston

Hi Winston,
Once the file is under version control and checked-in, there is no way to make a subsequent change(s) without causing a new version to be created.
One option you could do from your event handler after changing the metadata (which causes a new version to be created), is to remove the old version, then look to update the new version's creator/lastmodifier with the old version's details.
As the code above may likely re-trigger your event handler, you may need to some how flag the file (using metadata) so as to be able to determine whether the new version resulted from the event handler rather than end-user so as to be able to skip processing.

Restriction and the Fixed attribute and JAXB

Hi
I have what I believe is a valid XSD, with two complex types BaseType and OtherType. What I want is for BaseType (abstract) to have an attribute but no fixed value for it. OtherType would restrict the allowable values to just "Test". I have checked the XSD with xmlspy and the W3C site.
so happy with the xsd I try to use JAXB to generate classes:
xjc.bat -p com.me.test example.xsd -d gen
but I get :
[ERROR] derivation-ok-restriction.2.1.1: Error for type 'OtherType'. An attibute use in this type has a REQUIRED setting which is inconsistent with a matching attribute use in the base type.
(removing the Fixed attribute solves it but I'd like to keep it)
Any ideas?
Thanks
Des Field Corbett
XSD Follows:
================================================================================
<?xml version="1.0" encoding="UTF-8"?>
<xs:schema xmlns:xs="http://www.w3.org/2001/XMLSchema" elementFormDefault="qualified" attributeFormDefault="unqualified">
<xs:complexType name="BaseType" abstract="true">
<xs:attribute name="name" type="xs:string" use="required"/>
</xs:complexType>
<xs:complexType name="OtherType">
<xs:complexContent>
<xs:restriction base="BaseType">
<xs:attribute name="name" fixed="Test"/>
</xs:restriction>
</xs:complexContent>
</xs:complexType>
<xs:element name="root" type="OtherType"></xs:element>
</xs:schema>

Got it to work...
My XSD had the line in BaseTypes:
<xs:attribute name="name" type="xs:string" use="required"/>
and the line in OtherTypes:
<xs:attribute name="name" fixed="Test"/>
Changing this to:
<xs:attribute name="name" type="xs:string" use="required" fixed="Test"/>
Got it to work.
Not sure if this is a Bug in JAXB or its just being fussy... Sure going to make it a pain to hand code in the extra tags in to my real life XSD!
If there is a better way I'd be grateful to know....
Thanks
Des
BTW getting a java.lang.reflect.InvocationTargetException now - but as I'm just learning JAXB so I'm guessing thats something else.

How-To dinamically add an attribute using "c:if" tag?

Hi,
I have a problem with f:attribute tag.
I need to dinamically add an attribute to a h:panelGroup tag according to the value of a ELExpression. For example the fragment below should output an HTML page with two radio controls; depending to the clicked radio, the "foo" section or the "baz" section is showed (this is controlled client-side vie the javascript function called in the onclick event of the "foobaz" component):
<h:selectOneRadio id="foobaz" layout="lineDirection" value="#{myBean.foobazMode}" onclick="showHideFooBaz(this);">
<f:selectItem itemValue="#{myBean.fooMode}" itemLabel="Show Foo"/>
<f:selectItem itemValue="#{myBean.bazMode}" itemLabel="Show Baz"/>
</h:selectOneRadio>
<h:panelGroup id="foo">
<c:if test="#{myBean.bazVisibile}">
    <f:attribute name="style" value="display: none"/>
</c:if>
</h:panelGroup>
<h:panelGroup id="baz">
<c:if test="#{myBean.fooVisibile}">
    <f:attribute name="style" value="display: none"/>
</c:if>
</h:panelGroup>Well, the problem is this not work.
So my idea was to develop a new AttributeTag with a JSP body content in order to write:
<h:panelGroup id="foo">
<my:attribute name="style">
    <c:choose>
      <c:when test="#{myBean.fooVisibile}">
        <f:verbatim>display: block</f:verbatim>
      </c:when>
      <c:otherwise>
        <f:verbatim>display: none</f:verbatim>
      </c:otherwise>
    </c:choose>
</my:attribute>
</h:panelGroup>
...but don't work too.
Starting from the SUN JSF-RI AttributeTag, I developed my version extending from BodyTagSupport class instead of TagSupport one.
public class AttributeTag extends BodyTagSupport
    public int doStartTag() throws JspException {
        return (EVAL_BODY_INCLUDE);
    public int doEndTag() throws JspException {
       // Locate our parent UIComponentTagBase
        UIComponentClassicTagBase tag = UIComponentELTag.getParentUIComponentClassicTagBase(pageContext);
        if (tag == null) {
                throw new JspException("com.sun.faces.NOT_NESTED_IN_UICOMPONENT_TAG_ERRO");
        // Add this attribute if it is not already defined
        UIComponent component = tag.getComponentInstance();
        if (component == null) {
                throw new JspException("com.sun.faces.NO_COMPONENT_ASSOCIATED_WITH_UICOMPONENT_TAG");
        FacesContext context = FacesContext.getCurrentInstance();
        ELContext elContext = context.getELContext();
        String nameVal = null;
        Object valueVal = null;
        boolean isLiteral = false;
        int result = EVAL_PAGE;
        if (name != null) {
            nameVal = (String) name.getValue(elContext);
        if (value != null) {
            if (isLiteral = value.isLiteralText()) {
                valueVal = value.getValue(elContext);
        else
                BodyContent bodyContent = null;
                String content = null;
                String trimContent = null;
                if (
                        (bodyContent = this.getBodyContent()) == null
                        || (content = bodyContent.getString()) == null
                        || (trimContent = content.trim()).length() == 0
                        || (
                                trimContent.startsWith("<!--")
                        return result;
                valueVal = trimContent;;
                bodyContent.clearBody();
                isLiteral = true;
        if (component.getAttributes().get(nameVal) == null) {
            if (isLiteral) {
                component.getAttributes().put(nameVal, valueVal);
            else {
                component.setValueExpression(nameVal, value);
        this.release();
        return result;
}So guy, have you any idea of how to solve my problem?
Any help is very very appreciated!!
Regards,
-- Anthony

Hi BalusC
The first one is not for me because the "rendered" attribute is set on the server-side: the current "invisibl"e section would not be included in the renderer page (what I want is render the page displaying the current visible section and to switch to another section at client-side)
...but...
The second solution you propose is OK!!!! and so simple!!
Yeah man I really really thank you (sorry I didn't find the "?:" expression in the JSP manual http://java.sun.com/products/jsp/syntax/2.0/syntaxref20.html. Now looking again - and better - I find it as "ChoiceExpression")
Again, thanks!!!
-- Anthony

Attribute onselect invalid for tag selectOneMenu according to TLD

Hi All
I am seeing the error message "Attribute onselect invalid for tag selectOneMenu according to TLD" with html_basic.tld version 1.0 even though the tag and attribute are present in the TLD. The error occurs on Windows XP in Jboss 4.0.2. I don't see the error on Linux.
I'd appreciate any help.
Thanks
Murthy

Hi Raymond
Found that Jboss was loading html_basic.tld from an unknown jar. When I set the URI in the JSP to the TLD file placed in WEB-INF/lib, the error went away.
Changed
<%@ taglib prefix="h" uri="http://java.sun.com/jsf/html"%>
<%@ taglib prefix="h" uri="WEB-INF/lib/html_basic.tld"%>
Wonder in which jar the TLD lies.
Thanks for your help
Murthy

Attribute validation error for tag CFQUERY

I have a CF application that's running fine on a shared host. I now have a VPS running version of CF 9. When I try to use this on the VPS, I get the following error:
Attribute validation error for tag CFQUERY.
The value of the attribute datasource, which is currently '', is invalid.
The datasource is being set in application.cfc, and again works just fine in the shared environment.
The only differences is the shared is running on Windows, and the VPS is Linux. Also, the Windows is running version 9,0,1,274733 and the Linux is 9,0,0,251028
Any help would be greatly appreciated.

bbholdem wrote:
I have a CF application that's running fine on a shared host. I now have a VPS running version of CF 9. When I try to use this on the VPS, I get the following error:
Attribute validation error for tag CFQUERY.
The value of the attribute datasource, which is currently '', is invalid.
The cause of the error is obvious. Somewhere in your application, the cfquery tag is used as follows, with an empty string as datasource:
<cfquery datasource="">
</cfquery>
That is a mistake. The error message should tell you where that occurs.

Assigning a String Value to the value attribute of html:file

Hi,
we facing a problem while assigning a value to the VALUE attribute of file tag
<html:file property="fileupload" size='25' value="sample.xls" onchange="callsheet()" />
can anyone help me out plzzz,

Two points -
1) Java is not Javascript or HTML; you would do better to find a more appropriate forum.
2) When you take this to a better forum, you need to describe the problem.

Of the version attribute of a HelpSet tag

Similar Messages

Maybe you are looking for