Missing nisDomainObject - Iplanet 5.1

Sparc Solaris 8 E450 installing iplanet 5.1. Cannot add nisDomainObject for native ldap setup.
When trying to import the following ldif (as noted in book):
dn: dc=xxxx,dc=edu
changetype: modify
add: objectclass
objectclass: nisDomainObject
add: nisdomain
nisdomain: xxxx.xxxx.edu
I get the following error:
Error modifying object 'dn: dc=xxxx,dc=edu'. The error sent by the server was
'Object class violation'. The modifications were:
[Lnetscape.ldap.LDAPModification;@7fdc2d.
When I do a search �objectclass=*�, I get nothing.
How do I build the missing object �nisDomainObject� (maybe the console)?
Any direction is appreciated.
Regard,
Al

The line starts with "sie:" in the file <server-root>/admin-serv/config/adm.conf is the Ldap DN the admin servers binds to config server to get the configuration during start up and also when you login to console as uid=admin.
In your case I guess problem is either the userPassword for above mentioned admin server DN (cn=admin-serv-<hostname>, cn=server group, cn=<FQDN of host>.....) expired or DN is completely missing as Mark mentioned.
If you don't have password policy turned on the instance where you have config "o=Netscaperoot" then there is no question of expiration. The best way to trouble shoot this kind of problem is, look at access log of config ldap server and see what error it is logging when you login in to console. You will see err=49 if you typed invalid password or typed correct password but expired.
ldapsearch -h <configldap host> -b "o=netscaperoot" -D "cn=directory manager" -w <password> \* passwordexpirationtime passwordretrycount
The above command dump your config including operational attributes passwordexpirationtime passwordretrycount

Similar Messages

  • RE: [iPlanet-JATO] Re: Deployment problem

    Chidu,
    I think that you are mired in the very common confusion of the default
    behavior of the ApplicationServletBase.parsePathInfo() which will determine
    the controlling/handling ViewBean via a URL design pattern. Lets take a look
    at the URL
    /NASApp/MigtoolboxSampleAppWar/MigtoolboxSample/IndexPage.jsp
    is decomposed as follows:
    /NASApp -> well, this is long story but is absolutely necessary, welcome to
    iAS
    /MigtoolboxSampleAppWar -> is the web application name, taken as the name of
    the WAR file when there is no EAR file (this allows the Servlet/JSP
    container to deferences the web application root under
    <ias>/APPS/modules/MigtoolboxSampleAppWar) I think this part of the URL is
    called th Context Path
    /MigtoolboxSample -> is the Servlet Path, and will either directly reference
    or match a Servlet Mapping
    for instance
    <servlet-mapping>
    <servlet-name>MigtoolboxSampleServlet</servlet-name>
    <url-pattern>/MigtoolboxSample/*</url-pattern>
    </servlet-mapping>
    tells the Servlet Container that the Servlet Path
    /MigtoolboxSample
    maps to the Module Servlet MigtoolboxSampleServlet
    This is how EVERY request makes its way to the "front controller" pattern in
    JATO. It is fundamental to JATO Applicatioan that every request pass
    through the ModuleServlet.
    every else on the URL past the Servlet Path is the PATH INFO. Based on this
    understanding, you will see why the
    ApplicationServletBase.parsePathInfo()
    is so important. In parsePathInfo() the PATH INFO is compared to the design
    pattern
    /VIEWBEANNAME*
    to determine the handling ViewBean from the first String Token in the path
    info. For instance, the starting URL of the Sample Application is
    /NASApp/MigtoolboxSampleAppWar/MigtoolboxSample/IndexPage
    The PATH INFO is [IndexPage]
    and IndexPage[ViewBean] is the handling ViewBean. Therefore, any simiarl
    URL like
    /NASApp/MigtoolboxSampleAppWar/MigtoolboxSample/IndexPage.jsp
    /NASApp/MigtoolboxSampleAppWar/MigtoolboxSample/IndexPage.matt
    /NASApp/MigtoolboxSampleAppWar/MigtoolboxSample/IndexPage.mike
    /NASApp/MigtoolboxSampleAppWar/MigtoolboxSample/IndexPage.chidu
    /NASApp/MigtoolboxSampleAppWar/MigtoolboxSample/IndexPage.XXX
    will all result in the same handling View Bean
    IndexPageViewBean
    It is very important to understand that you CANNOT hit the JATO JSPs
    directly. You must hit the "front controller" ModuleServlet which will
    always delegate control to the handling ViewBean (a la, the "service to
    workers" pattern)
    You can attempt to hit the JSP directly but you need the right J2EE URL
    /NASApp/MigtoolboxSampleAppWar/MigtoolboxSampleApp/MigtoolboxSample/IndexPag
    e.jsp
    this URL will directly hit the JSP. However, you will recieve an error
    because the JATO framework quickly determines that there is no
    RequestContext in the HttpRequest attributes and assumes that the "front
    controller" was bypassed. Try it. You will get ERROR.
    Lets go back to what you are trying to do, place Models and Viewbeans in
    separate directories. I recommend that you move the Models. Models are
    ONLY referenced by TYPE via the ModelManager, the compiler will ensure that
    your code is correct and matches the packages, file locations, import
    statements, etc. ViewBeans, on the other hand are related to the
    ModuleServlet their are contained in and are loaded via type names according
    to a design pattern.
    if you want to separate models and Viewbean then simply move the Model and
    make sure everything compiles.
    you cannot move the ViewBeans
    if you do want to move the JSP peers of the Viewbeans, then you can put them
    anywhere in the web application doc root. When you do, update the
    DEFAULT_DISPLAY_URL as Mike suggested
    matt
    -----Original Message-----
    From: Mike Frisino [mailto:<a href="/group/SunONE-JATO/post?protectID=174176219122158198138082063148231088239026066196217193234150166091061">Michael.Frisino@S...</a>]
    Sent: Thursday, July 26, 2001 10:48 PM
    Subject: Re: [iPlanet-JATO] Re: Deployment problem
    Chidu,
    Did you have it running fine in the original default configuration, before
    you started changing things around? The URL should not access the .jsp
    directly. The URL should look more like this
    "/NASApp/MigtoolboxSampleAppWar/MigtoolboxSample/IndexPage", without the
    .jsp.
    Also, please read the "Migration Tech Notes" document that is
    linked to the
    main doc index page. There is some information in there related
    to trying to
    run the sample application under iAS (see Tech Note 4 in
    particular, "Note
    on running the iMT "MigtoolboxSample" in iPlanet Application Server )
    ----- Original Message -----
    From: <<a href="/group/SunONE-JATO/post?protectID=219015020150194233215218164140244063078048234051197">chidusv@y...</a>>
    Sent: Thursday, July 26, 2001 7:27 PM
    Subject: [iPlanet-JATO] Re: Deployment problem
    Hi Mike,
    I tried changing the url in all the viewbeans to reflect the new sub-
    directory for the viewbeans(I have placed the jsps and viewbeans in
    a sub-directory under MigtoolboxSampleApp/MigtoolboxSample). But I'm
    still not able to get access to the jsps. I basically see the
    message "GX Error Socket Error Code missing!!" error on the browser
    thrown by iPlanet, but the log doesn't tell me anything. Does the url
    which I give to access the jsp change accordingly, i.e., should I
    give something other
    than /NASApp/MigtoolboxSampleAppWar/MigtoolboxSample/IndexPage.jsp.
    If I try to use any other url other
    than /NASApp/MigtoolboxSampleAppWar/MigtoolboxSample/IndexPage.jsp, I
    see the FileNotFoundException in the log.
    I guess I'm still missing something.
    Thanks for your help.
    --Chidu.
    --- In <a href="/group/SunONE-JATO/post?protectID=210083235237078198050118178206047166136158139046209">iPlanet-JATO@y...</a>, "Mike Frisino" <<a href="/group/SunONE-JATO/post?protectID=174176219122158198138082063148231088239026066196217130152150">Michael.Frisino@S...</a>> wrote:
    Chidu.
    Did you also adjust the following member in each of the ViewBeans?
    public static final String DEFAULT_DISPLAY_URL=
    "/jatosample/module1/Index.jsp";
    Try adjusting this to be consistent with your new hierarchy.
    Also, if you still have problems, send us the error message thatyou recieve
    when you try to access the page. That would help.
    ----- Original Message -----
    From: <<a href="/group/SunONE-JATO/post?protectID=219015020150194233215218164036129208">chidusv@y...</a>>
    Sent: Thursday, July 26, 2001 4:48 PM
    Subject: [iPlanet-JATO] Deployment problem
    Hi,
    We have a requirement to seperate the models and viewbeans and
    keep
    them in seperate directories. Is it possible to seperate the
    viewbeans and models not be in the same directory?
    I tried seperating the two in the MigtoolboxSampleApp application
    provided by JATO. I changed the package and import statements
    accordingly in the viewbeans, jsps and the models. But when I
    deployed the application, I'm not able to access the Index page or
    any of the jsps. Does the ApplicationServletBase always look forthe
    viewbean in the same path as that of the module servlet?
    Any help will be appreciated.
    Thanks,
    Chidu.
    <a href="/group/SunONE-JATO/post?protectID=210083235237078198050118178206047166215146166214017110250006230056039126077176105140127082088124241215002153">[email protected]</a>
    <a href="/group/SunONE-JATO/post?protectID=210083235237078198050118178206047166215146166214017110250006230056039126077176105140127082088124241215002153">[email protected]</a>
    <a href="/group/SunONE-JATO/post?protectID=210083235237078198050118178206047166215146166214017110250006230056039126077176105140127082088124241215002153">[email protected]</a>

    Hi Mike,
    I tried changing the url in all the viewbeans to reflect the new sub-
    directory for the viewbeans(I have placed the jsps and viewbeans in
    a sub-directory under MigtoolboxSampleApp/MigtoolboxSample). But I'm
    still not able to get access to the jsps. I basically see the
    message "GX Error Socket Error Code missing!!" error on the browser
    thrown by iPlanet, but the log doesn't tell me anything. Does the url
    which I give to access the jsp change accordingly, i.e., should I
    give something other
    than /NASApp/MigtoolboxSampleAppWar/MigtoolboxSample/IndexPage.jsp.
    If I try to use any other url other
    than /NASApp/MigtoolboxSampleAppWar/MigtoolboxSample/IndexPage.jsp, I
    see the FileNotFoundException in the log.
    I guess I'm still missing something.
    Thanks for your help.
    --Chidu.
    --- In iPlanet-JATO@y..., "Mike Frisino" <Michael.Frisino@S...> wrote:
    >
    Chidu.
    Did you also adjust the following member in each of the ViewBeans?
    public static final String DEFAULT_DISPLAY_URL=
    "/jatosample/module1/Index.jsp";
    Try adjusting this to be consistent with your new hierarchy.
    Also, if you still have problems, send us the error message that you recieve
    when you try to access the page. That would help.
    ----- Original Message -----
    From: <chidusv@y...>
    Sent: Thursday, July 26, 2001 4:48 PM
    Subject: [iPlanet-JATO] Deployment problem
    Hi,
    We have a requirement to seperate the models and viewbeans and
    keep
    them in seperate directories. Is it possible to seperate the
    viewbeans and models not be in the same directory?
    I tried seperating the two in the MigtoolboxSampleApp application
    provided by JATO. I changed the package and import statements
    accordingly in the viewbeans, jsps and the models. But when I
    deployed the application, I'm not able to access the Index page or
    any of the jsps. Does the ApplicationServletBase always look for the
    viewbean in the same path as that of the module servlet?
    Any help will be appreciated.
    Thanks,
    Chidu.
    [email protected]

  • Re: [iPlanet-JATO] Re: using begin childName Display method

    Steve,
    It sounds like you have your display fields in a container view, and
    that container view is inside of a view bean. I haven't tested whether
    the fireChildDisplayEvents has a "deep" effect on its container view
    children. Meaning that you may have to set fireChildDisplayEvents="true"
    for the <jato:containerView> tag instead. If all else fails and you need
    to just get it working, you can set the fireDisplayEvents="true" for
    each display field tag separately.
    craig
    stephen_winer wrote:
    I should clarify my earlier statement. The data I want to display is
    coming from a model (tied in in the createChild method). I want to
    conditionally reformat the text that is being substituted in the JSP
    for a JATO form element, but I want this to happen on the server, not
    with JavaScript. The begin<childName>Display and
    end<childName>Display methods allow me to do this, in theory, but I
    can not get them to execute.
    Steve
    --- In iPlanet-JATO@y..., Belinda Garcia <belinda.garcia@s...> wrote:
    I don't currently use a begin or end Display method. I merely bind
    the fields to
    the model when the child is created and use the setValue to
    initially set the
    value to what's in the model. I get nulls though if I try to use a
    tiled View. I
    haven't quite got this figured out.
    Belinda
    X-eGroups-Return:
    sentto-2343287-1135-1008613974-belinda.garcia=sun.com@r...
    X-Sender: stephen_winer@y...
    User-Agent: eGroups-EW/0.82
    From: "stephen_winer" <stephen_winer@y...>
    X-Originating-IP: 155.188.191.4
    X-Yahoo-Profile: stephen_winer
    Mailing-List: list iPlanet-JATO@y...; contact
    iPlanet-JATO-owner@y...
    Date: Mon, 17 Dec 2001 18:32:48 -0000
    Subject: [iPlanet-JATO] using begin<childName>Display method
    Content-Transfer-Encoding: 7bit
    I want to be able to conditionally show/hide data as well as
    format
    it for display without touching the model. I found the
    begin<childName>Display and end<childName>Display methods that
    provide the hooks to do this, but I have been unsuccessful in
    getting
    these method to execute. I added the
    fireChildDisplayEvents="true"
    attribute to the jato:useViewBean tag, but this has not helped.
    I
    also added some debug to the ContainerViewBase class in the
    public
    boolean beginChildDisplay(ChildDisplayEvent event) method to see
    what
    was happening. The displayMethodMap was returning null for the
    child
    display methods that were in the view bean. I covered all the
    bases
    (compiling, redeploying, etc.) and nothing has worked. Is there
    anything I am missing or is there some working example of this?
    Steve
    For more information about JATO, please visit:
    http://developer.iplanet.com/tech/appserver/framework/index.jsp
    >For more information about JATO, please visit:
    http://developer.iplanet.com/tech/appserver/framework/index.jsp

    The hidden field was present in the page, but it looked like this:
    <input type="hidden" name="jato.defaultCommand" value=""../search"">
    Seems like there is a small bug in the code generating this tag.
    FYI - I am using JATO1.2
    What file displays this text? Maybe I can go in and fix it and rejar
    it.
    Steve
    --- Mike Frisino wrote:
    Steve,
    Can you check the HTML source that shows up in the browser? Do you see an entry that looks like this at the bottom of the form in
    question?
    >
    <input type="hidden" name="jato.defaultCommand" value="/search">
    To answer your question - it should work as you described. Some of the JatoSample make use of the defaultCommandChild. Can you try
    running the sample BasicSample->Field Types and let us know what you
    see.
    >
    Failing this you can send me your jsp file , maybe there is some subtle issue there. michael.frisino@s...
    >
    >
    ----- Original Message -----
    From: stephen_winer
    Sent: Friday, December 07, 2001 8:05 AM
    Subject: [iPlanet-JATO] Using the defaultCommandChild in a form
    I am trying to set the defaultCommandChild in my jato:form tag to be
    the searcg button. The search button definition is:
    <jato:button name="search"/>.
    The form tag definition is:
    <jato:form name="PendingIA" defaultCommandChild="/search">
    Clicking on the search button works fine, but hitting return in one
    of the textFields (which submits the form) passes a value of "" to
    the createChild method in my viewBean, which throws an error. Why
    does this not just work as normal and trigger the handleSearchRequest
    () method?
    Steve
    For more information about JATO, please visit:
    http://developer.iplanet.com/tech/appserver/framework/index.jsp
    Service.
    >
    >
    >
    [Non-text portions of this message have been removed]

  • Re: [iPlanet-JATO] Back Button functionality

    Hi Mike,
    Our test environment does not include proxy server.
    regards,
    syam.
    Please respond to [email protected]
    cc:
    Subject: Re: [iPlanet-JATO] Back Button functionality
    Guys,
    Please clarify something for me, the JATO code is commented as follows
    protected void addResponseHeaders(RequestContext requestContext)
    // These values should make any proxy between the client and
    // server avoid caching, and ensure that pages from one user
    // can never be seen by another user (if they're cached anyway)
    requestContext.getResponse().addHeader("Pragma","no-cache");
    requestContext.getResponse().addHeader
    ("Cache-Control","private");Yet you make no mention of whether your test environment includes a Proxy
    Server, or does your browser
    go directly to the Application Server's web server?
    Can you clarify, please?
    ----- Original Message -----
    From: <syam_reddy@p...>
    Sent: Wednesday, April 25, 2001 2:59 PM
    Subject: [iPlanet-JATO] Back Button functionality
    >
    Hi,
    We observed the following difference in behaviour between JATO pages
    and NetD served pages.
    We have the following scenario. User will login to the
    site. After login he will get a frame set. This frame set has threeframes.
    Top and bottom frames are used for navigation (to switch between various
    sections on the site.) .The middle frame(main frame) shows the actual
    content. When the the frame set gets loaded main frame shows page1. User
    will click on a link on page1. Page 2 will be loaded in main frame. Atthis
    point if the user clicks on back button , with migrated application(JATO
    pages) the following message appears in the main frame.
    In Netscape Communicator 4.61 the following message appears in the main
    frame :
    Data Missing
    This document resulted from a POST operation and has expired fromcache.If
    you wish you can repost the form data to recreate the document by
    presenting the reload button.
    In IE 4.72/5.5 the following message appears in the main frame:
    Warning : Page has Expired
    The page you requested was created using information you submitted in a
    form.This page is no longer available.As a security precaution, Internet
    Explorer does not automatically resubmit your information for you. To
    resubmit your information and view the web page click teh refresh button.
    However, in the NetD site page1 will appear in main frame.
    How do we mimic the NetD behaviour with the migrated
    applications ?
    We think the above behaviour with migrated Apps, is due to the
    headers that are get set in Application ServletBase , see the following
    code snippet :
    protected void addResponseHeaders(RequestContext requestContext)
    // These values should make any proxy between the client and
    // server avoid caching, and ensure that pages from one user
    // can never be seen by another user (if they're cached anyway)
    requestContext.getResponse().addHeader("Pragma","no-cache");
    requestContext.getResponse().addHeader
    ("Cache-Control","private");
    If we comment the above code , we were able to mimic theNetD
    behaviour. Are there any alternatives/thoughts on how to mimic the NetD
    behaviour ?
    Thanks in Advance,
    syam&ravi.
    [email protected]
    [email protected]

    OK, here's what I'm trying to do: We have, like you said, a menu
    page. The pages that it goes to and the number of links are all
    variable and read from the database. In NetD we were able to create
    URLs in the form
    pgXYZ?SPIDERSESSION=abcd
    so this is what I'm trying to replicate here. So the URL that works
    is
    pgContactUs?GXHC_GX_jst=fc7b7e61662d6164&GXHC_gx_session_id_=cc9c6dfa5
    601afa7
    which I interpreted to be the equivalent of the old Netd way. Our
    javascript also loads other frames of the page in the same manner.
    And I believe the URL-rewritten frame sources of a frameset look like
    this too.
    This all worked except for the timeout problem. In theory we could
    rewrite all URLs to go to a handler, but that would be...
    inconvenient.

  • Re: [iPlanet-JATO] using begin childName Display method

    Oops. Sorry about that, Craig. I didn't realize I might leave that impression.
    I'm sure the tiled
    views work since you have so many examples of these and it's a relatively
    simple concept, isn't it?
    Not to mention a necessary one. I didn't have time to debug my code and find
    out what I was doing
    wrong where the tiled views are concerned. I decide to just try to implement
    tiled views later and
    just stick with one of everything for now and get that working.
    Yes, I have reviewed your comments and am taking them into consideration. I am
    able to save and
    retrieve values with my model at this point.
    Thanks.
    Belinda
    X-eGroups-Return:
    sentto-2343287-1143-1008622698-belinda.garcia=sun.com@r...
    X-Sender: craig.conover@s...
    User-Agent: Mozilla/5.0 (Windows; U; Windows NT 5.0; en-US; rv:0.9.4)Gecko/20011019 Netscape6/6.2
    X-Accept-Language: en-us
    From: "Craig V. Conover" <craig.conover@s...>
    X-Yahoo-Profile: cvconover
    Mailing-List: list [email protected]; contact
    [email protected]
    Date: Mon, 17 Dec 2001 13:00:10 -0800
    Subject: Re: [iPlanet-JATO] using begin<childName>Display method
    Content-Transfer-Encoding: 7bit
    Belinda,
    He may also be binding the models, howerver, he needs to change the way
    the value appears before it is displayed which is why you would use the
    display events.
    Your null value issue is a completely different issue and has nothing to
    do with it being a tiled view. I don't want anyone getting the idea
    that the tiledView binding is broken. It does work. You issue should
    have something to do with the inconsistent way in which you are getting
    your model. At least from what I could tell in your source code that you
    sent me.
    Have you reviewed my comments I sent to you in your source code?
    craig
    Belinda Garcia wrote:
    I don't currently use a begin or end Display method. I merely bind the
    fields to
    the model when the child is created and use the setValue to initially setthe
    value to what's in the model. I get nulls though if I try to use a tiledView. I
    haven't quite got this figured out.
    Belinda
    X-eGroups-Return:
    sentto-2343287-1135-1008613974-belinda.garcia=sun.com@r...
    X-Sender: stephen_winer@y...
    User-Agent: eGroups-EW/0.82
    From: "stephen_winer" <stephen_winer@y...>
    X-Originating-IP: 155.188.191.4
    X-Yahoo-Profile: stephen_winer
    Mailing-List: list [email protected]; contact
    [email protected]
    Date: Mon, 17 Dec 2001 18:32:48 -0000
    Subject: [iPlanet-JATO] using begin<childName>Display method
    Content-Transfer-Encoding: 7bit
    I want to be able to conditionally show/hide data as well as format
    it for display without touching the model. I found the
    begin<childName>Display and end<childName>Display methods that
    provide the hooks to do this, but I have been unsuccessful in getting
    these method to execute. I added the fireChildDisplayEvents="true"
    attribute to the jato:useViewBean tag, but this has not helped. I
    also added some debug to the ContainerViewBase class in the public
    boolean beginChildDisplay(ChildDisplayEvent event) method to see what
    was happening. The displayMethodMap was returning null for the child
    display methods that were in the view bean. I covered all the bases
    (compiling, redeploying, etc.) and nothing has worked. Is there
    anything I am missing or is there some working example of this?
    Steve
    For more information about JATO, please visit:
    http://developer.iplanet.com/tech/appserver/framework/index.jsp
    For more information about JATO, please visit:
    http://developer.iplanet.com/tech/appserver/framework/index.jsp
    For more information about JATO, please visit:
    http://developer.iplanet.com/tech/appserver/framework/index.jsp

    The hidden field was present in the page, but it looked like this:
    <input type="hidden" name="jato.defaultCommand" value=""../search"">
    Seems like there is a small bug in the code generating this tag.
    FYI - I am using JATO1.2
    What file displays this text? Maybe I can go in and fix it and rejar
    it.
    Steve
    --- Mike Frisino wrote:
    Steve,
    Can you check the HTML source that shows up in the browser? Do you see an entry that looks like this at the bottom of the form in
    question?
    >
    <input type="hidden" name="jato.defaultCommand" value="/search">
    To answer your question - it should work as you described. Some of the JatoSample make use of the defaultCommandChild. Can you try
    running the sample BasicSample->Field Types and let us know what you
    see.
    >
    Failing this you can send me your jsp file , maybe there is some subtle issue there. michael.frisino@s...
    >
    >
    ----- Original Message -----
    From: stephen_winer
    Sent: Friday, December 07, 2001 8:05 AM
    Subject: [iPlanet-JATO] Using the defaultCommandChild in a form
    I am trying to set the defaultCommandChild in my jato:form tag to be
    the searcg button. The search button definition is:
    <jato:button name="search"/>.
    The form tag definition is:
    <jato:form name="PendingIA" defaultCommandChild="/search">
    Clicking on the search button works fine, but hitting return in one
    of the textFields (which submits the form) passes a value of "" to
    the createChild method in my viewBean, which throws an error. Why
    does this not just work as normal and trigger the handleSearchRequest
    () method?
    Steve
    For more information about JATO, please visit:
    http://developer.iplanet.com/tech/appserver/framework/index.jsp
    Service.
    >
    >
    >
    [Non-text portions of this message have been removed]

  • Re: [iPlanet-JATO] sp3 jsp compiler problem

    Weiguo,
    First, Matt is correct, the regular expression tool is perfect for general text
    substitution situations, and as a completely independent tool its use is not
    restricted to migration situations (or file types for that matter).
    Second, I sympathize with the unfortunate trouble you are experiencing due to
    Jasper's (perhaps more strict) compilation, but in what way did the iMT
    automated translation contribute to these inconsistencies that you cited?
    1. Changed the case of the tag attribute to be the same as what's
    defined in tld.
    example: changed OnClick to onClick
    The iMT does not generate any OnClick or onClick clauses per se. In a
    translation situation, the only way "OnClick" would have been introduced was if
    it had been part of the pre-existing project's "extraHTML" (which was written
    by the original customer and just passed through unchanged by the iMT) or if it
    was added manually by the post-migration developer.
    2. Removed attributes which are not defined in tld.
    example: escape attribute only defined in three tags
    but in some pages, it's used although it's not defined as an
    attribute
    of certain tags. The jasper compiler doesn't like it.Can you give soem examples? Is there a definite pattern? Again, this might be
    similar to the OnClick situation described above?
    3. In an end tag, there can't be any space.
    example: </content > doesn't work. </content> works.
    Again, the content tag would never have been generated by the iMT. There was no
    equivalent in the NetDynamics world, so any content tags in your code must have
    been introduced by your developers manually. Its a shame that jasper is so
    particular, but the iMT could not help you out here even if we wanted to. The
    constants that are used by the iMT are defined in
    com.iplanet.moko.jsp.convert.JspConversionConstants. From what I can see, the
    only situation of a closing tag with any space in it is
    public static final String CLOSE_EMPTY_ELEMENT = " />";
    But that should not cause the type of problem you are referring to.
    Mike
    ----- Original Message -----
    From: Matthew Stevens
    Sent: Thursday, September 06, 2001 10:16 AM
    Subject: RE: [iPlanet-JATO] sp3 jsp compiler problem
    Weiguo,
    Others will chime in for sure...I would highly recommend the Regex Tool from
    the iMT 1.1.1 for tackling this type of problem. Mike, Todd and myself have
    posted to the group (even recently) on directions and advantages of creating
    your own RULES (rules file) in XML for arbitary batch processing of source.
    matt
    -----Original Message-----
    From: weiguo.wang@b...
    [mailto:<a href="/group/SunONE-JATO/post?protectID=125056020108194190033029175101192165174144234026000079108238073194105057099246073154180137239239223019162">weiguo.wang@b...</a>]
    Sent: Thursday, September 06, 2001 12:25 PM
    Subject: [iPlanet-JATO] sp3 jsp compiler problem
    Matt/Mike/Todd,
    We are trying to migrate to sp3 right now, but have had a lot of
    issues with the new jasper compiler.
    The following workaround has been employed to solve the issues:
    1. Changed the case of the tag attribute to be the same as what's
    defined in tld.
    example: changed OnClick to onClick
    2. Removed attributes which are not defined in tld.
    example: escape attribute only defined in three tags
    but in some pages, it's used although it's not defined as an
    attribute
    of certain tags. The jasper compiler doesn't like it.
    3. In an end tag, there can't be any space.
    example: </content > doesn't work. </content> works.
    As I see it, we have two options to go about solving this problem:
    1. Write a script which will iterate through all the jsp files and
    call jspc on them. Fix the errors manually when jspc fails. Jspc will
    flag the line number where an error occurs.
    2. Write a utility which scans the jsp files and fix the errors when
    they are encountered. We should define what's an error and how to
    correct it. It's best if we combine this with solution 1 since we
    might miss an error condition.
    Actually, there might be another option, which is seeking help from
    you guys since you have better understanding of JATO and iAS. Can you
    do anything to help us?
    We would be happy to hear your thoughts.
    At last, I would like to suggest modifying the moko tool so that
    these rules are enforced and the generated JSPs work with the new
    compiler. This is for the benefit of any new migration projects.
    Thanks a lot.
    Weiguo
    [email protected]
    Choose from 1000s of job listings!
    [email protected]
    [Non-text portions of this message have been removed]

    Thanks a lot Matt and Mike for your prompt replies.
    I agree completely that iMT doesn't introduce the inconsistencies.
    About the three cases I mentioned, the third one happens only in
    manually created JSPs. So it has nothing to do with iMT. The first
    two are mainly due to the existing HTML code, as you rightly pointed
    out.
    The reason I made the suggestion is since we know that case 1 and 2
    won't pass the japser compiler in sp3, we have to do something about
    it. The best place to do this, in my mind, is iMT. Of course, there
    might be some twists that make it impossible or difficult to do this
    kind of case manipulation or attribute discard.
    Weiguo
    --- In iPlanet-JATO@y..., "Mike Frisino" <Michael.Frisino@S...> wrote:
    Weiguo,
    First, Matt is correct, the regular expression tool is perfect for general text substitution situations, and as a completely independent
    tool its use is not restricted to migration situations (or file types
    for that matter).
    >
    Second, I sympathize with the unfortunate trouble you are experiencing due to Jasper's (perhaps more strict) compilation, but
    in what way did the iMT automated translation contribute to these
    inconsistencies that you cited?
    >
    1. Changed the case of the tag attribute to be the same as what's
    defined in tld.
    example: changed OnClick to onClick
    The iMT does not generate any OnClick or onClick clauses per se. In a translation situation, the only way "OnClick" would have been
    introduced was if it had been part of the pre-existing
    project's "extraHTML" (which was written by the original customer and
    just passed through unchanged by the iMT) or if it was added manually
    by the post-migration developer.
    >
    2. Removed attributes which are not defined in tld.
    example: escape attribute only defined in three tags
    but in some pages, it's used although it's not defined as an
    attribute
    of certain tags. The jasper compiler doesn't like it.Can you give soem examples? Is there a definite pattern? Again, this might be similar to the OnClick situation described above?
    >
    >
    3. In an end tag, there can't be any space.
    example: </content > doesn't work. </content> works.
    Again, the content tag would never have been generated by the iMT. There was no equivalent in the NetDynamics world, so any content tags
    in your code must have been introduced by your developers manually.
    Its a shame that jasper is so particular, but the iMT could not help
    you out here even if we wanted to. The constants that are used by the
    iMT are defined in
    com.iplanet.moko.jsp.convert.JspConversionConstants. From what I can
    see, the only situation of a closing tag with any space in it is
    public static final String CLOSE_EMPTY_ELEMENT = " />";
    But that should not cause the type of problem you are referring to.
    Mike
    ----- Original Message -----
    From: Matthew Stevens
    Sent: Thursday, September 06, 2001 10:16 AM
    Subject: RE: [iPlanet-JATO] sp3 jsp compiler problem
    Weiguo,
    Others will chime in for sure...I would highly recommend the Regex Tool from
    the iMT 1.1.1 for tackling this type of problem. Mike, Todd and myself have
    posted to the group (even recently) on directions and advantages of creating
    your own RULES (rules file) in XML for arbitary batch processing of source.
    >
    matt
    -----Original Message-----
    From: weiguo.wang@b...
    [mailto:<a href="/group/SunONE-JATO/post?protectID=125056020108194190033029175101192165174048139046">weiguo.wang@b...</a>]
    Sent: Thursday, September 06, 2001 12:25 PM
    Subject: [iPlanet-JATO] sp3 jsp compiler problem
    Matt/Mike/Todd,
    We are trying to migrate to sp3 right now, but have had a lot of
    issues with the new jasper compiler.
    The following workaround has been employed to solve the issues:
    1. Changed the case of the tag attribute to be the same as
    what's
    defined in tld.
    example: changed OnClick to onClick
    2. Removed attributes which are not defined in tld.
    example: escape attribute only defined in three tags
    but in some pages, it's used although it's not defined as an
    attribute
    of certain tags. The jasper compiler doesn't like it.
    3. In an end tag, there can't be any space.
    example: </content > doesn't work. </content> works.
    As I see it, we have two options to go about solving this problem:
    >>
    1. Write a script which will iterate through all the jsp files and
    call jspc on them. Fix the errors manually when jspc fails. Jspc will
    flag the line number where an error occurs.
    2. Write a utility which scans the jsp files and fix the errors when
    they are encountered. We should define what's an error and how to
    correct it. It's best if we combine this with solution 1 since we
    might miss an error condition.
    Actually, there might be another option, which is seeking help from
    you guys since you have better understanding of JATO and iAS. Can you
    do anything to help us?
    We would be happy to hear your thoughts.
    At last, I would like to suggest modifying the moko tool so that
    these rules are enforced and the generated JSPs work with the new
    compiler. This is for the benefit of any new migration projects.
    Thanks a lot.
    Weiguo
    [email protected]
    Choose from 1000s of job listings!
    [email protected]
    Service.
    >
    >
    >
    [Non-text portions of this message have been removed]

  • Re: [iPlanet-JATO] More on ComputedColumn issue

    Vladimir--
    I'm going to answer this question without doing my full homework on it;
    please let me know if I hit the mark or not. If I understand correctly, you
    have a problem using a model for both UPDATE and SELECT queries because of a
    computed column...correct?
    If so, this issue is solved in JATO 1.2. 1.2 has an attribute in the field
    descriptor to indicate in which type of queries a field should be used. You
    can use this attribute to indicate that a field should only be used for
    UPDATE queries, SELECT queries, or whatever combination of query types you
    require. You can then define synthetic fields for use only during one of
    the query types.
    Does this sound useful in fixing your issue? A way around this in JATO 1.1
    would be to create separate models for SELECT and UPDATE queries. The
    SELECT model could contain all the fields for the joined query, but the
    UPDATE model would contain info for only one table. The 1.2 feature simple
    allows you to do the same using one model.
    Todd
    ----- Original Message -----
    From: "vivanov4114" <vivanov@b...>
    Sent: Friday, January 11, 2002 8:12 AM
    Subject: [iPlanet-JATO] More on ComputedColumn issue
    We have a similar problem with do's ComputedColumn after the
    translation as Kostas described in his detailed message #439.
    We have JATO/iMT version 1.1. Is the resolution of this problem added
    to the version 1.2 (or 1.2.1)?
    I've tried to adjust the ModelImpl class based on the .sdo file
    (using ComputedColumn attributes) for these fields and failed.
    Whether I missed something else, or our situation is a little bit
    different.
    In our case the dataObject has one Computed Field from one table and
    another Computed Field from another table along with joint between
    these two tables and third one, and, finally, the whole stuff is
    under the repeatable (with static fields bindings to these two
    computed fields).
    The modelImpl class after the translation (as in the #439) has the
    same values "" and "." for ..._NAME and QUALIFIED_..._NAME strings
    respectively (for each computed do's field).
    I guess that we could meet extra problem with this (for manual
    adjustment) because of there is no TableName attribute in .sdo file
    for computed field (as well as there is no ColumnName attribute for
    computed field). If ComputedColumn attribute (computed field) could
    play a role of ColumnName attribute (regular case), what would be an
    analog of TableName attribute for computed field?
    The bottom line of this is as follows: we have a same
    SQLException "Invalid Column Name"
    from ResultSetModelBase.updateModel() as Kostas described. It causes
    the problem for
    RequestHandlingTiledViewBase.executeAutoRetrieving() method that
    can't bind the proper Model.
    Finally, beginDisplay() method from
    pgXXXXPriorityCountTiledView.class throws exception and
    jasper compiler brings run-time error (Tomcat 3.2).
    Kostas, if this problem still exists for translation of such cases,
    could you please post a fragment that fixed you original problem in
    addition to the message #439 (just to be sure, that I haven't missed
    something important).
    Thank you very much in advance.
    Vladimir Ivanov,
    P. S. I've enclosed the excerption from the .sdo file for this
    dataObject below.
    Class "SQLObject" ;
    Name "doPriorityCount" ;
    DataFields {
    0 { // first df is a computed column from the first
    //table
    Class "DataField" ;
    Name "dfPriorityDesc" ;
    ComputedColumn "MIN
    (MOS.PRIORITY.PDESCRIPTION)" ;
    1 { // second df is a computed column from the second
    // table
    Class "DataField" ;
    Name "dfPriorityCount" ;
    ComputedColumn "COUNT
    (ASSIGNEDTASKSWORKQUEUE.PRIORITYID)" ;
    2 { // third df is a regular df
    Class "DataField" ;
    Name "MOS_PRIORITY_PRIORITYID" ;
    TableName "MOS.PRIORITY" ; // this attribute
    // doesn't exist for ComputedColumn
    ColumnName "PRIORITYID" ; // this attribute
    // doesn't exist for ComputedColumn
    DataCachingEnabled "False" ;
    DataCachingDuration "0" ;
    DataCachingMaxRows "200" ;
    DataObjectType "Select" ;
    Tables "MOS.ASSIGNEDTASKSWORKQUEUE,MOS.PRIORITY,MOS.DEAL" ;
    SQLDistinct "False" ;
    SelectFilter {
    "MOS.DEAL.SCENARIORECOMMENDED" ;
    "=" ;
    "'Y'" ;
    "AND" ;
    "MOS.DEAL.COPYTYPE" ;
    "<>" ;
    "'T'" ;
    SelectOrder {
    "MOS.PRIORITY.PRIORITYID ASC" ;
    SelectGroup {
    "MOS.PRIORITY.PRIORITYID" ;
    EnableEntireTableDelete "False" ;
    EnableEntireTableUpdate "False" ;
    SQLTextOverrideSelect "Partial" ;
    SQLTextOverrideDelete "None" ;
    SQLTextSelectJoin "MOS.ASSIGNEDTASKSWORKQUEUE.DEALID =
    MOS.DEAL.DEALID
    AND MOS.PRIORITY.PRIORITYID <> 0
    AND MOS.PRIORITY.PRIORITYID =
    MOS.ASSIGNEDTASKSWORKQUEUE.PRIORITYID(+)
    AND MOS.ASSIGNEDTASKSWORKQUEUE.TASKSTATUSID
    (+) = 1 " ;
    For more information about JATO, including download information, pleasevisit:
    http://developer.iplanet.com/tech/appserver/framework/index.jsp

    Todd,
    Sorry for the delay with the answer, I've tried to obtain JATO 1.2
    and repeat the project migration to verify whether version 1.2 solves
    my problem or not (actually, it is a pilot sub-project).
    Unfortunately, I still have no 1.2 version.
    Let me try to answer on your question without getting the results
    with JATO 1.2. Your explanation sounds like version 1.2 is very close
    to solve the problem. Actually, our situation is easier because we
    have SELECT object only, not SELECT and UPDATE. For data integrity
    the only 'Select' ND's do(s) have been used through the whole
    project. The backend communication (update, delete) is provided via
    EJB like (entity) Java classes.
    My question is: could I define synthetic field with 1.1.1 version. By
    the way, word synthetic reflects the possibility to construct the
    field under certain SQL circumstances (SELECT, UPDATE, e.g.) or the
    possibility to construct a `fake' field (for example,
    CountColumn of a do) as well. If the later is true, could you please
    give a brief idea how to create this synthetic field.
    After the translation in the doPriorityCountModelImpl class we've
    got:
    public static final String COLUMN_DFPRIORITYDESC="";
    public static final String QUALIFIED_COLUMN_DFPRIO
    RITYDESC=".";
    public static final String COLUMN_DFPRIORITYCOUNT="";
    public static final String QUALIFIED_COLUMN_DFPRIO
    RITYCOUNT=".";
    (see my original post please with details, as well).
    If this is not a problem for 1.2 please do not waste your time to fix
    it for 1.1.1. I need to repeat my results with the version 1.2 anyway.
    We have a number of similar idioms through the project. In this
    particular case, the CountColumn that counts the field from another
    table may bring problem for manual adjustment (see my original
    notes). The whole SQL query is as follows (for this case):
    SELECT MIN(MOS.PRIORITY.PDESCRIPTION),
    COUNT(ASSIGNEDTASKSWORKQUEUE.PRIORITYID),
    MOS.PRIORITY.PRIORITYID
    FROM MOS.ASSIGNEDTASKSWORKQUEUE, MOS.PRIORITY, MOS.DEAL
    WHERE MOS.DEAL.SCENARIORECOMMENDED = 'Y'
    AND MOS.DEAL.COPYTYPE <> 'T'
    GROUP BY MOS.PRIORITY.PRIORITYID
    ORDER BY MOS.PRIORITY.PRIORITYID ASC
    During the pre-handler activity (it is the part of our Object
    Framework on the top of Netdynamics Object Framework) system passes
    id (and mos.deal.dealid = XXX) to the do (select query). After the
    run-time execution of this do the results are displayed on the screen
    bind to the repeatable statics.
    Thank you very much,
    Vladimir
    --- In iPlanet-JATO@y..., "Todd Fast" <Todd.Fast@S...> wrote:
    Vladimir--
    I'm going to answer this question without doing my full homework on it;
    please let me know if I hit the mark or not. If I understand correctly, you
    have a problem using a model for both UPDATE and SELECT queries because of a
    computed column...correct?
    If so, this issue is solved in JATO 1.2. 1.2 has an attribute in the field
    descriptor to indicate in which type of queries a field should be used. You
    can use this attribute to indicate that a field should only be used for
    UPDATE queries, SELECT queries, or whatever combination of query types you
    require. You can then define synthetic fields for use only during one of
    the query types.
    Does this sound useful in fixing your issue? A way around this in JATO 1.1
    would be to create separate models for SELECT and UPDATE queries. The
    SELECT model could contain all the fields for the joined query, but the
    UPDATE model would contain info for only one table. The 1.2 feature simple
    allows you to do the same using one model.
    Todd
    ----- Original Message -----
    From: "vivanov4114" <vivanov@b...>
    Sent: Friday, January 11, 2002 8:12 AM
    Subject: [iPlanet-JATO] More on ComputedColumn issue
    We have a similar problem with do's ComputedColumn after the
    translation as Kostas described in his detailed message #439.
    We have JATO/iMT version 1.1. Is the resolution of this problem
    added
    to the version 1.2 (or 1.2.1)?
    I've tried to adjust the ModelImpl class based on the .sdo file
    (using ComputedColumn attributes) for these fields and failed.
    Whether I missed something else, or our situation is a little bit
    different.
    In our case the dataObject has one Computed Field from one table and
    another Computed Field from another table along with joint between
    these two tables and third one, and, finally, the whole stuff is
    under the repeatable (with static fields bindings to these two
    computed fields).
    The modelImpl class after the translation (as in the #439) has the
    same values "" and "." for ..._NAME and QUALIFIED_..._NAME strings
    respectively (for each computed do's field).
    I guess that we could meet extra problem with this (for manual
    adjustment) because of there is no TableName attribute in .sdo file
    for computed field (as well as there is no ColumnName attribute for
    computed field). If ComputedColumn attribute (computed field) could
    play a role of ColumnName attribute (regular case), what would be an
    analog of TableName attribute for computed field?
    The bottom line of this is as follows: we have a same
    SQLException "Invalid Column Name"
    from ResultSetModelBase.updateModel() as Kostas described. It causes
    the problem for
    RequestHandlingTiledViewBase.executeAutoRetrieving() method that
    can't bind the proper Model.
    Finally, beginDisplay() method from
    pgXXXXPriorityCountTiledView.class throws exception and
    jasper compiler brings run-time error (Tomcat 3.2).
    Kostas, if this problem still exists for translation of such cases,
    could you please post a fragment that fixed you original problem in
    addition to the message #439 (just to be sure, that I haven't missed
    something important).
    Thank you very much in advance.
    Vladimir Ivanov,
    P. S. I've enclosed the excerption from the .sdo file for this
    dataObject below.
    Class "SQLObject" ;
    Name "doPriorityCount" ;
    DataFields {
    0 { // first df is a computed column from the first
    //table
    Class "DataField" ;
    Name "dfPriorityDesc" ;...........................................
    ComputedColumn "MIN
    (MOS.PRIORITY.PDESCRIPTION)" ;............................................
    1 { // second df is a computed column from the second
    // table
    Class "DataField" ;
    Name "dfPriorityCount" ;
    ComputedColumn "COUNT
    (ASSIGNEDTASKSWORKQUEUE.PRIORITYID)" ;
    2 { // third df is a regular df
    Class "DataField" ;
    Name "MOS_PRIORITY_PRIORITYID" ;
    TableName "MOS.PRIORITY" ; // this attribute
    // doesn't exist for ComputedColumn
    ColumnName "PRIORITYID" ; // this attribute
    // doesn't exist for ComputedColumn
    DataCachingEnabled "False" ;
    DataCachingDuration "0" ;
    DataCachingMaxRows "200" ;
    DataObjectType "Select" ;
    Tables "MOS.ASSIGNEDTASKSWORKQUEUE,MOS.PRIORITY,MOS.DEAL" ;
    SQLDistinct "False" ;
    SelectFilter {
    "MOS.DEAL.SCENARIORECOMMENDED" ;
    "=" ;
    "'Y'" ;
    "AND" ;
    "MOS.DEAL.COPYTYPE" ;
    "<>" ;
    "'T'" ;
    SelectOrder {
    "MOS.PRIORITY.PRIORITYID ASC" ;
    SelectGroup {
    "MOS.PRIORITY.PRIORITYID" ;
    EnableEntireTableDelete "False" ;
    EnableEntireTableUpdate "False" ;
    SQLTextOverrideSelect "Partial" ;
    SQLTextOverrideDelete "None" ;
    SQLTextSelectJoin "MOS.ASSIGNEDTASKSWORKQUEUE.DEALID =
    MOS.DEAL.DEALID
    AND MOS.PRIORITY.PRIORITYID <> 0
    AND MOS.PRIORITY.PRIORITYID =
    MOS.ASSIGNEDTASKSWORKQUEUE.PRIORITYID(+)
    AND
    MOS.ASSIGNEDTASKSWORKQUEUE.TASKSTATUSID
    (+) = 1 " ;
    For more information about JATO, including download information, please
    visit:
    http://developer.iplanet.com/tech/appserver/framework/index.jsp

  • RE: [iPlanet-JATO] Parse error in JSP parser in IAS6

    Hi Todd,
    removing the defaultValue="" attribute works.
    I have not got around to testing the SP3.
    BTW. The reason the default value tag was added was to stop Null pointer
    exceptions being thrown in the
    HrefTag.beginDisplay().
    buffer.append("?")
    .append(field.getQualifiedName()) // "FooHref"
    .append("=")
    .append(URLEncoder.encode(value.toString())); // "/foo"
    If you don't explicitly add a defaultValue="" to the jsp HREF tag ,
    HrefTag.getDefaultValue() returns null.
    Our hack was to add the following in HrefTag.java.
    if (value==null)
    value=getDefaultValue();
    //===========================
    //IP6 ADDED THE FOLLOWING LINE
    value = (value== null? "":value);
    //============================
    Is that pheasible work-around ? This eliminates the need to add
    defaultValue="" to all HREF tags.
    Also, I might as well point another behavior that we encountered with HREFS.
    In ND, if a HREF's display Field was bound to a column in DataObject and the
    particular record had no value, no URL would be rendered on the page.
    The HTML would look something like this( from memory ):
    <A
    HREF="../AppName/PgMsgMain.hrfSubject_onWebEvent(hrfSubject).994226335140? +
    ND URL STUFF"></A>
    In JATO by default a url get displayed with "null" as the link. ie.
    <a href="../AppName/PgMsgMain?PgMsgMain.hrfSubject= + URL STUFF">null</a>
    Our hack was modify the HrefTag.doEndTag method to not append "null" to the
    buffer.
    if (displayed)
    buffer.append(getBodyContent().getString().equals("null")? "":
    getBodyContent().getString()))
    // IP6 HACK buffer.append(getBodyContent().getString())
    .append("</a>");
    writeOutput(fireEndDisplayEvent(buffer.toString()));
    Is there a better way to do this?
    thanks
    Kostas
    -----Original Message-----
    From: Todd Fast [mailto:<a href="/group/SunONE-JATO/post?protectID=189233080150012190218067203043176090006144139218183041">toddwork@c...</a>]
    Sent: Tuesday, July 03, 2001 12:46 AM
    Subject: Re: [iPlanet-JATO] Parse error in JSP parser in IAS6
    Hey Kostas--
    I personally haven't seen this kind of error. Have you tried simplifying
    the expression inside the href tag? For example:
    <% Object foo =
    viewBean.getRptAssignmentMatch().getvwAssignmentMatchModel().getValue(
    vwAssignmentMatchModel.FIELD_ASSIGNMENT_ASSIGNMENT_ID);
    %>
    <jato:href name="hrefASSIGNMENT_ASSIGNMENT_ID" fireDisplayEvents="true">
    <%= foo %>
    </jato:href>
    Also, is there a different version you could upgrade to? iAS SP3 includes
    the Jasper compiler from Tomcat, which should behave quite differently.
    Todd
    ----- Original Message -----
    From: "Kostas Morfis" <kmorfis@i...>
    Sent: Tuesday, July 03, 2001 12:17 AM
    Subject: [iPlanet-JATO] Parse error in JSP parser in IAS6
    >
    Hi all,
    has anyone come across the following error in iPlanet?
    [02/Jul/2001 12:21:32:1] error: Exception: SERVLET-compile_failed: Failedin
    compiling template: /ras/ras/voyager4/pgAssignmentMatch.jsp, Parse errorin
    JSP parser. Missing endtag: /jato:href
    Exception Stack Trace:
    java.lang.Exception: Parse error in JSP parser. Missing endtag: /jato:href
    at com.netscape.jsp.JSP.parseBlock(Unknown Source)
    at com.netscape.jsp.JSP.parseUserTag(Unknown Source)
    at com.netscape.jsp.JSP.parseTag(Unknown Source)
    at com.netscape.jsp.JSP.parseNext(Unknown Source)
    etc etc.
    We have tested the page in Resin and it works fine.
    It seems the JSP parser has a problem with the following type of HREFtags.
    >
    <jato:href name="hrefASSIGNMENT_ASSIGNMENT_ID" fireDisplayEvents="true"
    defaultValue=""><%=
    viewBean.getRptAssignmentMatch().getvwAssignmentMatchModel().getValue(com.cb
    >
    re.ras.voyager4.model.vwAssignmentMatchModel.FIELD_ASSIGNMENT_ASSIGNMENT_ID)
    %></jato:href></font></td>
    anyone have any suggestions/thoughts/comments ?
    Kostas Morfis
    Senior Consultant
    iRise
    www.iRise.com
    [Non-text portions of this message have been removed]
    [email protected]
    [email protected]

    Hi Todd,
    removing the defaultValue="" attribute works.
    I have not got around to testing the SP3.
    BTW. The reason the default value tag was added was to stop Null pointer
    exceptions being thrown in the
    HrefTag.beginDisplay().
    buffer.append("?")
    .append(field.getQualifiedName()) // "FooHref"
    .append("=")
    .append(URLEncoder.encode(value.toString())); // "/foo"
    If you don't explicitly add a defaultValue="" to the jsp HREF tag ,
    HrefTag.getDefaultValue() returns null.
    Our hack was to add the following in HrefTag.java.
    if (value==null)
    value=getDefaultValue();
    //===========================
    //IP6 ADDED THE FOLLOWING LINE
    value = (value== null? "":value);
    //============================
    Is that pheasible work-around ? This eliminates the need to add
    defaultValue="" to all HREF tags.
    Also, I might as well point another behavior that we encountered with HREFS.
    In ND, if a HREF's display Field was bound to a column in DataObject and the
    particular record had no value, no URL would be rendered on the page.
    The HTML would look something like this( from memory ):
    <A
    HREF="../AppName/PgMsgMain.hrfSubject_onWebEvent(hrfSubject).994226335140? +
    ND URL STUFF"></A>
    In JATO by default a url get displayed with "null" as the link. ie.
    <a href="../AppName/PgMsgMain?PgMsgMain.hrfSubject= + URL STUFF">null</a>
    Our hack was modify the HrefTag.doEndTag method to not append "null" to the
    buffer.
    if (displayed)
    buffer.append(getBodyContent().getString().equals("null")? "":
    getBodyContent().getString()))
    // IP6 HACK buffer.append(getBodyContent().getString())
    .append("</a>");
    writeOutput(fireEndDisplayEvent(buffer.toString()));
    Is there a better way to do this?
    thanks
    Kostas
    -----Original Message-----
    From: Todd Fast [mailto:<a href="/group/SunONE-JATO/post?protectID=189233080150012190218067203043176090006144139218183041">toddwork@c...</a>]
    Sent: Tuesday, July 03, 2001 12:46 AM
    Subject: Re: [iPlanet-JATO] Parse error in JSP parser in IAS6
    Hey Kostas--
    I personally haven't seen this kind of error. Have you tried simplifying
    the expression inside the href tag? For example:
    <% Object foo =
    viewBean.getRptAssignmentMatch().getvwAssignmentMatchModel().getValue(
    vwAssignmentMatchModel.FIELD_ASSIGNMENT_ASSIGNMENT_ID);
    %>
    <jato:href name="hrefASSIGNMENT_ASSIGNMENT_ID" fireDisplayEvents="true">
    <%= foo %>
    </jato:href>
    Also, is there a different version you could upgrade to? iAS SP3 includes
    the Jasper compiler from Tomcat, which should behave quite differently.
    Todd
    ----- Original Message -----
    From: "Kostas Morfis" <kmorfis@i...>
    Sent: Tuesday, July 03, 2001 12:17 AM
    Subject: [iPlanet-JATO] Parse error in JSP parser in IAS6
    >
    Hi all,
    has anyone come across the following error in iPlanet?
    [02/Jul/2001 12:21:32:1] error: Exception: SERVLET-compile_failed: Failedin
    compiling template: /ras/ras/voyager4/pgAssignmentMatch.jsp, Parse errorin
    JSP parser. Missing endtag: /jato:href
    Exception Stack Trace:
    java.lang.Exception: Parse error in JSP parser. Missing endtag: /jato:href
    at com.netscape.jsp.JSP.parseBlock(Unknown Source)
    at com.netscape.jsp.JSP.parseUserTag(Unknown Source)
    at com.netscape.jsp.JSP.parseTag(Unknown Source)
    at com.netscape.jsp.JSP.parseNext(Unknown Source)
    etc etc.
    We have tested the page in Resin and it works fine.
    It seems the JSP parser has a problem with the following type of HREFtags.
    >
    <jato:href name="hrefASSIGNMENT_ASSIGNMENT_ID" fireDisplayEvents="true"
    defaultValue=""><%=
    viewBean.getRptAssignmentMatch().getvwAssignmentMatchModel().getValue(com.cb
    >
    re.ras.voyager4.model.vwAssignmentMatchModel.FIELD_ASSIGNMENT_ASSIGNMENT_ID)
    %></jato:href></font></td>
    anyone have any suggestions/thoughts/comments ?
    Kostas Morfis
    Senior Consultant
    iRise
    www.iRise.com
    [Non-text portions of this message have been removed]
    [email protected]
    [email protected]

  • Org.xml.sax.SAXParseException: Document root element is missing.

    Hi,
    I am trying to get the portal login id from a weblogic server based application from iplaet portal server.
    I get this follwoing error
    org.xml.sax.SAXParseException: Document root element is missing.
    at com.sun.xml.parser.Parser.fatal(Parser.java:2817)
    at com.sun.xml.parser.Parser.fatal(Parser.java:2805)
    at com.sun.xml.parser.Parser.parseInternal(Parser.java:493)
    at com.sun.xml.parser.Parser.parse(Parser.java:284)
    at com.sun.xml.tree.XmlDocument.createXmlDocument(XmlDocument.java:226)
    at com.iplanet.portalserver.util.XMLParser.<init>(XMLParser.java:70)
    at com.iplanet.portalserver.naming.share.NamingResponseParser.<init>(NamingResponseParser.java:33)
    at com.iplanet.portalserver.naming.share.NamingResponse.parseXML(NamingResponse.java:74)
    at com.iplanet.portalserver.naming.WebtopNaming.updateNamingTable(WebtopNaming.java:174)
    at com.iplanet.portalserver.naming.WebtopNaming.getNamingProfile(WebtopNaming.java:155)
    at com.iplanet.portalserver.naming.WebtopNaming.getServiceURL(WebtopNaming.java:57)
    at com.iplanet.portalserver.session.Session.getSessionServiceURL(Session.java:534)
    at com.iplanet.portalserver.session.Session.getSessionServiceURL(Session.java:520)
    at com.iplanet.portalserver.session.Session.getSession(Session.java:414)
    at jsp_servlet.__eatonPortalLogin._jspService(__eatonPortalLogin.java:155)
    at weblogic.servlet.jsp.JspBase.service(JspBase.java:27)
    at weblogic.servlet.internal.ServletStubImpl$ServletInvocationAction.run(ServletStubImpl.java:1075)
    at weblogic.servlet.internal.ServletStubImpl.invokeServlet(ServletStubImpl.java:418)
    at weblogic.servlet.internal.ServletStubImpl.invokeServlet(ServletStubImpl.java:462)
    at weblogic.servlet.internal.ServletStubImpl.invokeServlet(ServletStubImpl.java:306)
    at weblogic.servlet.internal.WebAppServletContext$ServletInvocationAction.run(WebAppServletContext.java:5517)
    at weblogic.security.service.SecurityServiceManager.runAs(SecurityServiceManager.java:685)
    at weblogic.servlet.internal.WebAppServletContext.invokeServlet(WebAppServletContext.java:3156)
    at weblogic.servlet.internal.ServletRequestImpl.execute(ServletRequestImpl.java:2506)
    at weblogic.kernel.ExecuteThread.execute(ExecuteThread.java:234)
    at weblogic.kernel.ExecuteThread.run(ExecuteThread.java:210)
    <May 19, 2004 9:01:12 AM EDT> <Error> <HTTP> <101017> <[ServletContext(id=4873279,name=ematrix,context-path=/ematrix)] Root cause of ServletException
    com.iplanet.portalserver.session.SessionException
    at com.iplanet.portalserver.session.Session.getSessionServiceURL(Session.java:539)
    at com.iplanet.portalserver.session.Session.getSessionServiceURL(Session.java:520)
    at com.iplanet.portalserver.session.Session.getSession(Session.java:414)
    at jsp_servlet.__eatonPortalLogin._jspService(__eatonPortalLogin.java:155)
    at weblogic.servlet.jsp.JspBase.service(JspBase.java:27)
    at weblogic.servlet.internal.ServletStubImpl$ServletInvocationAction.run(ServletStubImpl.java:1075)
    at weblogic.servlet.internal.ServletStubImpl.invokeServlet(ServletStubImpl.java:418)
    at weblogic.servlet.internal.ServletStubImpl.invokeServlet(ServletStubImpl.java:462)
    at weblogic.servlet.internal.ServletStubImpl.invokeServlet(ServletStubImpl.java:306)
    at weblogic.servlet.internal.WebAppServletContext$ServletInvocationAction.run(WebAppServletContext.java:5517)
    at weblogic.security.service.SecurityServiceManager.runAs(SecurityServiceManager.java:685)
    at weblogic.servlet.internal.WebAppServletContext.invokeServlet(WebAppServletContext.java:3156)
    at weblogic.servlet.internal.ServletRequestImpl.execute(ServletRequestImpl.java:2506)
    at weblogic.kernel.ExecuteThread.execute(ExecuteThread.java:234)
    at weblogic.kernel.ExecuteThread.run(ExecuteThread.java:210)
    Any help/pointers will be appreciated.
    Ashish

    Just for anyone else who hits this problem: I encountered the same issue with an XML document that XMLSpy claims is quite well formed. I opened the document in a hex editor, and there at the from was a three-byte byte order marker - the marker that I believe the UTF-8 standard says is optional. I removed these three bytes, and the file was parsed correctly.
    In this case, the XML file was created using a Microsft DOM (save).
    My solution is to make the java parser - as I use it - a tad more robust: Open the file and create an input stream - a pushback input stream. Read the first three bytes; if they are NOT a BOM, then push those bytes back. Now - in any case - give the stream to the parser to read.
    try {
    // Open file for reading.
    f = new File(path);
    FileInputStream fis = new FileInputStream(f);
    PushbackInputStream pis = new PushbackInputStream(fis);
    byte[] buf = new byte[3];
    pis.read(buf, 0, 3);
    if (! (buf[0] == 0x00EF) && (buf[1] == 0x00BB) && (buf[2] == 0x00BF) ) {
         pis.unread(buf, 0, 3);
    builder = DocumentBuilderFactory.newInstance().newDocumentBuilder();
    doc = builder.parse(pis);
    catch (Exception x) {
         x.printStackTrace();
    }

  • Issue in iPlanet loading obj.conf file in admin console module

    Dear all,
    I have done following chanegs in obj.conf file to block insecure http methods,but whenever I try to access admin module of iPlanet and restart, all manual changes done in obj.conf disappears.
    Only one time it asked me with message that file has been modified manually do you want to load?
    but this is not happening every time.I am using iplanet 9.
    Please let me know if there is any issue with this or I am missing something.
    to just brief, only after trying 20 times it asked me above mentioned message
    ---obj.conf file contents----
    <Object name="WebCon1" ppath="*/WebCon/*">
    *<Client method="(GET|POST)">*
    AuthTrans fn="match-browser" browser="MSIE*" ssl-unclean-shutdown="true"*
    *</Client>*
    *<Client method="(HEAD|PUT|TRACE|TRACK|SEARCH|INDEX|OPTIONS|DELETE|MKDIR|SHOWMETHOD|UNLINK|CHECKIN|TEXTSEARCH|SPACEJUMP|CONNECT|PATCH|PROPFIND|PROPPATCH|MKCOL|COPY|MOVE|LOCK|UNLOCK|CHECKOUT|RMDIR|ACL|VERSION-CONTROL|REPORT|UNCHECKOUT|ORDERPATCH)">*
    *AuthTrans fn="set-variable" remove-headers="transfer-encoding" set-headers="content-length: -1" error="405"*
    *</Client>*
    NameTrans fn="pfx2dir" from="/mc-icons" dir="/home/cedera/iPlanetServer/Installation/ns-icons" name="es-internal"
    PathCheck fn="unix-uri-clean"
    PathCheck fn="find-pathinfo"
    ObjectType fn="type-by-extension"
    ObjectType fn="force-type" type="text/plain"
    Service method="(GET|POST)" type="image/gif" fn="send-file"
    Service method="(GET|POST)" type="image/jpeg" fn="send-file"
    Service method="(GET|POST)" type="text/css" fn="send-file"
    Service method="(GET|POST)" type="application/x-javascript" fn="send-file"
    Service method="(GET|POST)" type="magnus-internal/imagemap" fn="imagemap"
    Service method="(GET|POST)" type="magnus-internal/directory" fn="send-error" path="/WebCon/WebCon/restrict.htm"
    Service method="(GET|POST)" fn="wl_proxy" WebLogicHost="10.10.61.224" WebLogicPort="444" HungServerRecoverSecs="600" Debug="ALL" DebugConfigInfo="TRUE" RequireSSLHostMatch="FALSE" WLLogFile="/home/cedera/iPlanetServer/Installation/https-webcon2/logs/Log_JSP.txt" PathTrim="/WebCon" PathPrepend="/WebConverter" SecureProxy="ON" URIContainsSpace="true" ErrorPage="/home/cedera/iPlanetServer/Installation/docs/WebCon/WebCon/serviceUnavailable.htm" MaxPostSize="-1" DefaultFileName="WebCon/login.jsp" ConnectTimeoutSecs="10" ConnectRetrySecs="2" WLDNSRefreshInterval="0" TrustedCAFile="/home/cedera/iPlanetServer/Installation/https-webcon2/config/trustedcafile.pem"
    AddLog fn="flex-log" name="access"
    </Object>
    I have added contents marked in bold manually....
    but it was not picking up it from frontend...then suddenly after 20 time, it picked up these changes in admin...
    but now if I am trying to change in <client> tag , but it does not recognise any new changes done manually...it loads same obj.conf...whenever i restart instance from frontend...
    Edited by: sweetvish on Nov 9, 2009 9:26 PM

    After making manual changes in obj.conf, have you tried clicking the 'Apply' link in admin console and then choosing 'Load configuration Changes' option?

  • Works in Tomcat but not in iPlanet Web server

    I have a servlet which first generates a form which has one input field, when user fills in the text field and submits the form it is posted to same servlet. The posted data is processed and redirected to another servlet. Everything works fine on Tomcat3.2 but fails to work on iPlanet web server and throws HTTP Error 500.
    Can someone help me with this? What might be the problem?

    Don't know whey it worked in Tomcat and not in iPlanet, but the reason is because I missed '/' in getRequestDispatcher() methoc
    public RequestDispatcher getRequestDispatcher(java.lang.String path)
    The pathname must begin with a "/" and is interpreted as relative to the current context root.

  • Is the jsp forward tag fails in iplanet application server sp2?

    11/Feb/2002 17:55:41:2] error: Exception: SERVLET-compile_failed: Failed in compiling template: /EinsWebTool/QueryScreen.jsp, Parse error in JSP parser. Missing endtag: /jsp:forward
    Exception Stack Trace:
    java.lang.Exception: Parse error in JSP parser. Missing endtag: /jsp:forward
    at java.lang.Throwable.fillInStackTrace(Native Method)
    at java.lang.Throwable.fillInStackTrace(Compiled Code)
    at java.lang.Throwable.<init>(Compiled Code)
    at java.lang.Exception.<init>(Compiled Code)
    at com.netscape.jsp.JSP.parseBlock(Compiled Code)
    at com.netscape.jsp.JSP.parseReqDisp(Unknown Source)
    at com.netscape.jsp.JSP.parseTag(Compiled Code)
    at com.netscape.jsp.JSP.parseNext(Compiled Code)
    at com.netscape.jsp.JSP.parseBlock(Compiled Code)
    at com.netscape.jsp.JSP.parse(Unknown Source)
    at com.netscape.jsp.JSP.compile(Unknown Source)
    at com.netscape.server.servlet.jsp.JSPCompiler.JSPtoJava(Unknown Source)
    at com.netscape.server.servlet.jsp.JSPCompiler.compileJSP(Compiled Code)
    at com.netscape.server.servlet.jsp.JSPCompiler.compileOrLoadJSP(Unknown Source)
    at com.netscape.server.servlet.jsp.JSPCompiler.compileInstance(Unknown Source)
    at com.netscape.server.servlet.jsp.JSPCompiler.compileInstance(Unknown Source)
    at com.netscape.server.servlet.platformhttp.PlatformHttpServletResponse.callJspCompiler(Unknown Source)
    at com.netscape.server.servlet.platformhttp.PlatformHttpServletResponse.callUri(Unknown Source)
    at com.netscape.server.servlet.platformhttp.PlatformHttpServletResponse.callUriRestrictOutput(Unknown Source)
    at com.netscape.server.servlet.platformhttp.PlatformRequestDispatcher.forward(Unknown Source)
    at com.netscape.jsp.PageContextImpl.forward(Unknown Source)
    at jsp.APPS.EinsWebTool.Login._jspService(Compiled Code)
    at jsp.APPS.EinsWebTool.Login.service(Login.java:42)
    at javax.servlet.http.HttpServlet.service(HttpServlet.java:865)
    at com.netscape.server.servlet.servletrunner.ServletInfo.service(Unknown Source)
    at com.netscape.server.servlet.servletrunner.ServletRunner.callJSP(Unknown Source)
    at com.netscape.server.servlet.platformhttp.PlatformHttpServletResponse.callJspCompiler(Unknown Source)
    at com.netscape.server.servlet.platformhttp.PlatformHttpServletResponse.callUri(Unknown Source)
    at com.netscape.server.servlet.platformhttp.PlatformHttpServletResponse.callUriRestrictOutput(Unknown Source)
    at com.netscape.server.servlet.platformhttp.PlatformRequestDispatcher.forward(Unknown Source)
    at com.netscape.server.servlet.jsp.JSPRunner.service(Unknown Source)
    at javax.servlet.http.HttpServlet.service(HttpServlet.java:865)
    at com.netscape.server.servlet.servletrunner.ServletInfo.service(Unknown Source)
    at com.netscape.server.servlet.servletrunner.ServletRunner.execute(Unknown Source)
    at com.kivasoft.applogic.AppLogic.execute(Compiled Code)
    at com.kivasoft.applogic.AppLogic.execute(Compiled Code)
    at com.kivasoft.thread.ThreadBasic.run(Native Method)
    at com.kivasoft.thread.ThreadBasic.run(Native Method)
    at com.kivasoft.thread.ThreadBasic.run(Native Method)
    at com.kivasoft.thread.ThreadBasic.run(Native Method)
    at com.kivasoft.thread.ThreadBasic.run(Compiled Code)
    at java.lang.Thread.run(Compiled Code)

    Hi,
    Yes, I was able to code this sucessfully and got it working. Here is the code I used...
    <%
    String fortune = (String) request.getAttribute("fortune_string");
    %>
    <HTML>
    <HEAD><TITLE>Fortune Sample Application</TITLE></HEAD>
    <BODY BGCOLOR=#FFFFFF>
    <H2>The Oracular Servlet greets you!</H2>
    <p>
    Your fortune is...
    <%= fortune%>
    <p>
    <p>
    <hr size=0>
    <p>
    <FONT SIZE=2>Sample Applications
    <jsp:forward page="/ias-samples/index.html">
    </jsp:forward>
    </BODY>
    </HTML>
    and I got it working. I believe the code is missing some tag, which I tried, but got error in KJS like...
    [15/Feb/2002 11:23:49:7] info: --------------------------------------
    [15/Feb/2002 11:23:49:7] info: jsp.APPS.fortune.fortune: init
    [15/Feb/2002 11:23:49:7] info: --------------------------------------
    Null text data??
    2002-02-15 11:24:16 - error-the file '\fortune.jsp' generated the following pars
    e exception: org.apache.jasper.compiler.ParseException: C:\iplanet\ias6\ias\APPS
    \fortune\fortune\fortune.jsp(17,0) Expected "param" tag with "name" and "value"
    attributes after the "params" tag.
    In your case, I suspect, either the parser is not able to convert the .jsp file appropriately, or some inappropriate tag. If this doesn't help please send me your code & I can help you on this regard.
    Regards
    Raj
    [email protected]

  • Mail Missing From Restore

    Hello, We are having some issues with missing mail (mainly in Inbox, Sent and Trash) from a restore process. Several users' mail was inadvertently deleted on the mail server. We figured out who the users were and set about restoring their mail from our Tivoli backups.
    A "reconstruct" was done once the restore was complete, and everything appeared consistent. However, users are missing mail in their desktop client (thunderbird). But we can see the mail (message count) on the server.
    The problem seems to be that after a mailbox has been restored from tape, the iPlanet reconstruct command does not like the store.idx file and deletes most of the messages.
    Is there a piece we're missing? We've restore mail folders for users in the past with no problems of this sort. I don't think we've ever had to restore the full mail for a user.
    We're running an old version ... waiting for a migration this spring.
    Planet Messaging Server 5.2 HotFix 2.01 (built Aug 26 2004)
    libimta.so 5.2 HotFix 2.01 (built 11:07:49, Aug 26 2004)
    SunOS inflow 5.9 Generic_122300-42 sun4u sparc SUNW,Sun-Fire-V240
    Any ideas would be greatly appreciated.
    Thanks!
    Karol

    kdpittman wrote:
    Hello, We are having some issues with missing mail (mainly in Inbox, Sent and Trash) from a restore process. Several users' mail was inadvertently deleted on the mail server. What do you mean by "inadvertently delete"?
    Did the users delete the emails using an email client (e.g. Thunderbird or Messenger Express) or did they "magically" disappear due to some kind of system level corruption?
    A "reconstruct" was done once the restore was complete, and everything appeared consistent. However, users are missing mail in their desktop client (thunderbird). But we can see the mail (message count) on the server. You cannot restore previously deleted/expunged individual *.msg files back into the original mailbox and expect them to show up. You need to restore the emails into a completely new folder.
    For example, you can create a "recovered" folder (./mboxutil -c user/<uid>/recovered) then restore the emails to the directory created by that command.
    Running reconstruct of this new folder will then cause the restored emails to show up and the user then just needs to subscribe to the folder in their IMAP client.
    If you were using imsbackup/imsrestore this problem wouldn't have occurred as imsrestore marks the emails as "new".
    The problem seems to be that after a mailbox has been restored from tape, the iPlanet reconstruct command does not like the store.idx file and deletes most of the messages.If you restore a folder, and the backup was taken after the email had already been marked-as-deleted by the email client then the email will remain "deleted". The *.msg files aren't cleaned up until the daily imexpire run.
    Later versions of Messaging Server have an option to "undelete/expunge" messages that have been deleted by the client by not removed off disk.
    Regards,
    Shane.

  • Iplanet ds5

    I have configured the iplanet in Solaris 9 yesterday.
    1. The directory server was configured with cognos user and cognos group with 1388 port.
    2. The admin server port number is 1391 and it was given with root user access.
    3. Created another instance with port: 1389.
    4. Every thing was fine yesterday.
    5. Today when I tried to login, it was no allowing.
    6. When I tried to restart the iplanet server, both the directory instances are starting.
    7. When I tried to start the admin server, it is responding as: iplanet-Webserver-Enterprise/6.0SP2 B01/06/2003 22:24
    8. When I give stop-admin command, it responds as server not running.
    AM I missing some thing? Any help will be appreciated.
    Thanks

    I'll assume that you can login admin console before via web server console (startconsole to DS admin server). Today, you can't because of admin (web server) restarting failure.
    Check web server errors log and give us what you can see. It should be under /opt/SUNWwbsvr/https-admserv/logs (assume you install at default directory) Jerry

  • Missing Parameters when JSP Forwarding

    I am having difficulty with passing parameters when a forward occurs from
    one JSP to a second JSP. When I try to get those parameters on the second
    JSP I am getting nulls since it never actually receives them as parameters.
    Here is what the code looks like ...
    first JSP
    ======
    <jsp:forward page="second.jsp" >
    <jsp:param name="arg1" value="hi" />
    <jsp:forward>
    second JSP
    ========
    String arg1 = request.getParameter( "arg1" )
    This situation is occuring for me on iPlanet Web Server 4.1. (Fyi, when I
    use the same JSPs on Tomcat through JBuilder, the parameter is passed to the
    second JSP.) I am wondering if if I am missing something on how iPlanet
    wants me to do pass arguments when forwarding or whether I just need to find
    an alternative way to accomplish my goal. Thanks in advance.

    In your second JSp try using.
    String arg1 = (String) request.getAttribute('arg1");
    I'm not sure if this is correct but from my understanding of Servlets you can not set a parameter programatically without overriding the ServletRequest. However, you can set an attribute. If this does not work then the following absolutely will:
    JSP 1
    <% request.setAttribute("args1","hi");
    <jsp:forward page="second.jsp"/>
    JSP 2
    <% String param = (String) request.getAttribute("arg1"); %>
    Hope this helps

Maybe you are looking for

  • How do I get out of the fullscreen of death?

    Hi, Hoping someone alse has experienced this and come up with a solution: I've lost control of Aperture and don't know what to do. I'm running Aperture 3.3.2 and Mac OSX 10.7.5(11G56) on a 15 inch mid-2010 MBP. I inadvertently pressed some combinatio

  • Using UTL_HTTP

    Hi ... I am using oracle 9i release 2 .... I want to use UTL_HTTP package to POST the Data .... Can Anyone Plz give me the hint of how to use it ..... I am also worried abt testing the above problem ... Is there anything on Internet to Test the Posti

  • Youtube Video Bug

    I've been having this issue with Youtube since this morning. I load a video on YouTube and it streams as usual for a few seconds, before the circle slider used to navigate in the video jumps right to the beginning and cannot be used. I can still inte

  • Localization with welcome message to the respecitve user in OBIEE-11g

    How do we can acheive localization with welcome message along with time to the respecitve country user in OBIEE-11g.

  • Any simple "task based" SPS examples?

    Hi all, I'm trying to learn more about SPS, and have a MS and RA installed, talking over ssh: all seems fine so far. Going through the docs, I'm slogging through plans, made up of components, which run procedures etc... lots of terminology to learn u