This Bugzilla instance is a read-only archive of historic NetBeans bug reports. To report a bug in NetBeans please follow the project's instructions for reporting issues.

Bug 128100 - Default VW jsp has Invalid standard action error
Summary: Default VW jsp has Invalid standard action error
Status: RESOLVED WORKSFORME
Alias: None
Product: obsolete
Classification: Unclassified
Component: visualweb (show other bugs)
Version: 6.x
Hardware: All All
: P1 blocker (vote)
Assignee: Peter Zavadsky
URL:
Keywords:
Depends on:
Blocks:
 
Reported: 2008-02-22 02:36 UTC by gaikokujin
Modified: 2009-02-19 23:23 UTC (History)
1 user (show)

See Also:
Issue Type: DEFECT
Exception Reporter:


Attachments
Visual Web test project (21.13 KB, text/plain)
2008-02-22 02:38 UTC, gaikokujin
Details

Note You need to log in before you can comment on or make changes to this bug.
Description gaikokujin 2008-02-22 02:36:24 UTC
Not sure if this is strictly an editor issue or also a visual web issue.  Please contact me if you cannot reproduce.

OK, this is very strange.  Performed the following (using latest 6.0.1 patches, WinXP):

1) Have default JSFWeb APP with a single new default Page1.jsp.   Simply copied/pasted Dipesh's .jsp below over my
Page1.jsp source.  Did not reproduce "Invalid standard action" editor error.

2) Created a new default Page2.jsp, then copied/pasted Dipesh's .jsp below over my Page2.jsp source.  Now the "Invalid
standard action" editor error appears in Page2.jsp only on the <jsp:root...> line.  But I do not ever get the build
error - builds fine.

3) Thinking there may be some kind of namespace conflict going on (or something), I deleted Page1.jsp file, and
completely renamed/refactored (Refactor->Rename from the popup menu) Page2.jsp (containing Dipesh's .jsp source) to
Page1.jsp.  This is where it gets really strange.  The result in the editor is a) the red badge in the left hand side
margin disappears, but not the red squiggle underscore for the <jsp:root...> line and b) a red badge appears on the
<webuijsf:form binding="#{Page1.form1}" id="form1"/> line, but no red squiggle underscore!  Again, no errors in the build.

4) Shut down the IDE, deleted everything under my .netbeans/6.0 user dir, and restarted the IDE.  Reopened the JSFWebApp
project. Now the editor red badge and red squiggle underscore are on the same <jsp:root...> line again.  Clean and build OK.

This leads me to believe this is just an editor bug.  I don't know why you are also getting a build error.  Did you at
any time create more than one JSF Page#.jsp?  Does this error occur with any newly created default JSF Web App project
and default pages?

Regards,
-Brad

dipesh wrote:
> hi,
> my source says like this:
>
> <?xml version="1.0" encoding="UTF-8"?>
> <!--
>     Document   : Page1
>     Created on : Feb 21, 2008, 9:23:40 AM
>     Author     : dipesh <dipshrestha@gmail.com <mailto:dipshrestha@gmail.com>>
> -->
>
> <jsp:root version="2.1" xmlns:f="http://java.sun.com/jsf/core" xmlns:h="http://java.sun.com/jsf/html"
xmlns:jsp="http://java.sun.com/JSP/Page" xmlns:webuijsf="http://www.sun.com/webui/webuijsf">
>     <jsp:directive.page contentType="text/html;charset=UTF-8" pageEncoding="UTF-8"/>
>     <f:view>
>         <webuijsf:page binding="#{Page1.page1}" id="page1">
>             <webuijsf:html binding="#{Page1.html1}" id="html1">
>                 <webuijsf:head binding="#{Page1.head1}" id="head1">
>                     <webuijsf:link binding="#{Page1.link1}" id="link1" url="/resources/stylesheet.css"/>
>                 </webuijsf:head>
>                 <webuijsf:body binding="#{Page1.body1}" id="body1" style="-rave-layout: grid">
>                     <webuijsf:form binding="#{Page1.form1}" id="form1">
>                     </webuijsf:form>
>                 </webuijsf:body>
>             </webuijsf:html>
>         </webuijsf:page>
>     </f:view>
> </jsp:root>
>
> regards,
> dipesh
Comment 1 gaikokujin 2008-02-22 02:38:26 UTC
Created attachment 57027 [details]
Visual Web test project
Comment 2 gaikokujin 2008-02-26 19:40:55 UTC
The user reports "Invalid standard action" runtime error.  Therefore this issue prevents the user from running their
application, so I will raise the priority:

hi brad,
sorry i'm late. Yes when i run the project it does start the tomcat
but the web page can't be opened. Error 500 is thrown:

/* Error----------*/
HTTP Status 500 -

type Status report
message
description The server encountered an internal error () that prevented
it from fulfilling this request.

/*---------Error */


The log of tomcat also shows some error.
/* Error----------*/

Feb 24, 2008 10:28:17 PM org.apache.catalina.core.StandardWrapperValve invoke
SEVERE: Servlet.service() for servlet Faces Servlet threw exception
org.apache.jasper.JasperException: /Page1.jsp(8,5) Invalid standard action
        at org.apache.jasper.compiler.DefaultErrorHandler.jspError(DefaultErrorHandler.java:40)
        at org.apache.jasper.compiler.ErrorDispatcher.dispatch(ErrorDispatcher.java:407)
........................

/*-----------Error*/

I checked the issue, could you please add the issue for me in
issuezilla. I hope somebody will pour some quick tips.


regards,
dipesh
Comment 3 Marek Fukala 2008-02-26 20:19:43 UTC
The whole issue is little bit confusing to me - so the problem is in the editor and also in runtime? Doesn't that mean
the code is really errorneous? I cannot even unpack the rar format. Can you please attach it zipped, gzipped or bzipped?
Comment 4 Marek Fukala 2008-02-27 14:17:20 UTC
"Invalid standard action" error means that some of the default jsp tags are incorrectly used in the code. So if you
created the page in the VW editor and the code is errorneous the problem is in VW. 

We have a similar issue for the "persistent" error message - issue #123067 "[60cat][VW] Residual Error Badge" which
looks related to the problem.

But this shouldn't have anything to do with runtime errors, if there is an error in runtime signaled by the server it
there is something wrong either with the code or with the webmodule configuration.

Reassigning to VW since the "persistent error" issue is IMO covered by the mentioned issue #123067.
Comment 5 Peter Zavadsky 2008-02-27 17:32:55 UTC
This belongs to the JSF support, even I don't understand what is this exactly about. If the page has an error in it, it
is just understandable it doesn't run. The same like if java source has an error the program won't run. It also seems to
me that the error was not produced by VW. So I don't understand the issue here. Anyway passing to the other to determine
who this belongs to, this doesn't belong to the designer.
Comment 6 Mark Dey 2008-03-04 06:20:06 UTC
Not enough information to pursue this issue further. Manually copying and pasting from one JSP to another within a visual web project is bound to produce 
anomalies unless you perform all of the necessary refactorings, not just in the JSP but in the backing bean as well. 
Comment 7 javydreamercsw 2008-03-24 21:11:59 UTC
This is still happening both in 6.0.1 and 6.1 Beta. 

It appears in the default jsp page (using new project wizard or creating a new one from scratch. It happens 100% of the
time for me.

Comment 8 Peter Zavadsky 2008-03-25 19:47:57 UTC
Hi I was trying to reproduce it, but couldn't get to it. Could you, please, clarify the steps you did?

I did following:

1) Created new Web Project with Visual JSF Framework,
2) The empty Page1 opened,
3) I switched to its JSP tab,
4) And replaced the source with the one you provided in the first comment,
5) No error in JSP was shown,
6) Switched to the Design tab,
7) Again no error,
8) Created new visual Page2,
9) Switched into its JSP tab,
10) Again copied your code to replace the original,
11) No error shown,
12) Switched to its Design tab,
13) Again no error.

Please, provide the steps you can reproduce the issue. Thanks.
Comment 9 Peter Zavadsky 2008-03-31 17:34:43 UTC
No answer for some time. I am closing this. Please, reopen, when you have the new information or steps, thanks.
Comment 10 jkafeero 2008-10-18 20:12:31 UTC
I am experiencing this problem too. Cannot create any new Visual Web JSF Pages.

I decided to upgrade with the latest NetBeans downloaded 18th Oct 2008 as well as all the plugin updates.

I am going to remove my .netbeans folder and try to continue working. I will update issue ASAP.
Comment 11 Peter Zavadsky 2008-11-07 18:17:42 UTC
Please, could you specify the steps you do, and also attach your log file? Thanks.
Comment 12 Peter Zavadsky 2008-12-05 18:29:11 UTC
No response, I assume it has worked for the user. Closing. Please, reopen with the needed information if it happens again.
Comment 13 mwildam 2008-12-09 15:41:59 UTC
I had the same issue and I discovered that this problem occurs if you specified your email in user properties within <
and >.

So the real problem lies lines above where the email address is specified in the author comment.