JSP validation warning.

empty

Does this happen in the course of just modifying JSPs and resource files, or
when a resource file is added or refactored?
It would be great if you can provide us with the steps you follow to
experience this problem.
M7 Support
PS: Sending requests to [email protected] usually has faster response time.
"DanBar" <[email protected]> wrote in message news:[email protected]..
DanBar wrote:There' a bug(?) causing Nitrox (build225) to report warnings like that:
I've tried build 226 - nothing's changed.
DanBar

Similar Messages

Seeking help on JSP Validator

hi,
I want to write a jsp validator which will detect syntax
errors in a JSP Page so that it can be validated before
deploying it in a Web Server.I have no clue as how to do it.
Please guide me in this regard.
Thanks and Regards,
Indranilr

Save yourself a lot of time and get an ide that does this for you. Eclipse is free and I think it has this feature (WSAD definitely does)

JSP Validation failed

Hi,
I am working on WSAD environment. In the package explorer view, in one of the projects, error symbol is there. It says "JSP Validation Failed". I was not sure if this is effecting my project execution in any way. But I was wondering what does it mean by "JSP Validation Failed".
Thanks

In the task Lists , this error will be displayed,
Double click on that and it will give the details of that.
Yes it can create problems later, better fix it when you see it ..
Try rebuliding the project , that might fix the problem sometimes

Validation warning

This is primarily an architecture question. I have a number of warning type validations to run. In the forms world I would do this with a procedure feeding it the field_name, and entered value, and then compare this against a table of field_names, min_value, max_values. I have followed numerous threads on displaying warnings, but most seem to hard-code the min / max values in the JavaScript function. Does anyone have some guidance on how to construct a more generic, table driven way of displaying warnings?

There are a couple of basic ways to do validations. The first is to build a simple validation for each rule you want. The benefits of this are ease of enabling/disabling validations when business rules change or just in debugging. The negative is that you can end up with a lot of validations and only one validation warning will show when you submit the page.
If you create a single warning, you can create something like this:
declare
begin
for c_othr in (select TO_NUMBER(c001) v_tc, c003 v_pycd,
 c004 v_jbcd, TO_NUMBER(c019) v_rt, NVL(TO_NUMBER(c005),0) v_hrs,
 NVL(TO_NUMBER(c020),0) v_pay, TO_NUMBER(c008) v_loc,
 NVL(TO_NUMBER(c007),0) v_eqhrs
 from apex_collections
 where collection_name = 'TC_OTHR')
loop
 IF c_othr.v_pycd IS NOT NULL and c_othr.v_loc IS NOT NULL THEN
 IF c_othr.v_rt = 0 THEN
 RETURN ''||c_othr.v_pycd||'-'||c_othr.v_jbcd||' at '||c_othr.v_loc||' is invalid.';
 ELSE
 IF c_othr.v_pycd = 'MSC' and c_othr.v_pay <=0 THEN
 RETURN 'MSC codes require a flat pay amount.';
 ELSIF c_othr.v_pycd = 'STU' and c_othr.v_pay <=0 THEN
 RETURN 'STU codes require a flat pay amount.';
 ELSIF c_othr.v_pycd = 'MOB' and c_othr.v_pay <=0 THEN
 RETURN 'MOB codes require a flat pay amount.';
 ELSIF c_othr.v_pycd = 'HDR' and c_othr.v_hrs <=0 THEN
 RETURN 'HDR codes require task hours.';
 ELSIF c_othr.v_pycd = 'TRN' and c_othr.v_pay <=0 THEN
 RETURN 'TRN codes require a flat pay amount.';
 ELSIF c_othr.v_pycd = 'LDR' and c_othr.v_eqhrs <=0
 and c_othr.v_jbcd NOT IN ('91A','91','A','89C') THEN
 RETURN 'LDR codes require equipment hours.';
 ELSE
 NULL;
 END IF;
 END IF;
 ELSE
 NULL;
 END IF;
end loop;
end;This is obviously a complex example where I'm trying to validate input from a collection, but you get the idea. If you want, you can even concatenate the errors together using a break to separate them.
I strongly recommend using the Validations, as then you don't have to worry about where to put the return text or the formatting as APEX does it for you.
Good luck.

Process Flow Validation Warning.

Hi All,
OWB Config Details is as follows:
Oracle 9i Warehouse Builder Client: 9.2.0.2.8
Oracle 9i Warehouse Builder Repository: 9.2.0.2.0
1> Following Warning is displayed when Process Flow is validated in Process Editor in OWB.
VLD-10005: The following path in the process flow is a loop and may cause the process to loop infinitely,
START->EXT_SHELL_SCRIPT->M_STG_GRADE_OF_SERVICE->EMAIL_ERROR->UPDATE_MAP_PROCESS_ERROR->
2> A mapping is developed in OWB with some default configuration parameters e.g. In a mapping involves Source Text File as Source and Staging Table as Target.
Readsize and Bindsize config parameters are set to 5000 respectively. I included the same mapping in process flow as mapping. The above mentioned Config Parameters are modified to 5242880. I committed the changes & synchornized in the process flow editor. I was expecting the modified config parameter will be displayed in the process flow editor. However I found that it still displays old config parameters and not modified config parameters. Is this expected or Did i miss some steps ?
Can someone please let me know more on these issues?
Regards,
Vidyanand

Please go the OWB forum for these questions:
Warehouse Builder
Thanks, Mark

Hierarchical Filter Web Item causes validation warning.

When I validate my web template which contains a hierarchical filter web item agianst the server I get the following warning (W1):
Mapping for Service item_validation_service for Object HIERARCHICAL_FILTER_ITEM missing
Maybe this also relates to my problem of not having the possibility to choose a characteristic for the hierarchical filter (see my post <a href="https://forums.sdn.sap.com/thread.jspa?threadID=209968&tstart=0">https://forums.sdn.sap.com/thread.jspa?threadID=209968&tstart=0</a>)
How can I fix this mapping issue?
Thanks to any answers in advance.
Best regards,
Philipp

Hello,
Your first problem is that ABAP SP does not equal Java SP. This is not a valid scenario.
Please update both to the same SP level.
After it, please retest your problem. I think that the problems will be solved (at least this one with validation service).
Short explanation to validation service:
Every template created in WAD will be validated before saving it. We have two validations:
1. one is locally with the meta data this checks if:
- all used parameters are on its place,
- all parameter values are valid,
- all defined items are existing...
2. second one is extended validation on the Java Server: this one checks i.e. following:
- are all used data providers valid
- are all used characteristics valid
- item dependent validation (e.g. if one item needs a dependency between to setting - this can be checked here)
The first one will be executed in Front-End and in ABAP Back-End. The second one in Java. Because your Java stack is /probably/ lower than ABAP, this validation does not work.
I hope I have explained it clearly.
Regards, Karol
BI Development

XML Schematron Validation Warning Message

Hi I have created an XML Schematron validation for my process, I'm getting the following warning in the process
Warning: Schematron file has invalid context "/imp1:WMWROOT/imp1:WMWDATA/imp1:WMFWUpload/imp1:Shipments/imp1:Shipment", validation may not happen properly. Please verify file manually.
I have verified the ".sch" file thoroughly there is no mistake in the namespace or paths . On testing this works perfectly well. I do not know what is causing this warning.
Could some one please help.
Thanks in advance
Nikhil

Warnings you can skip, having said that check the format of your file, use xmlspy IDE to check the file format.
- It is considered good etiquette to reward answerers with points (as "helpful" - 5 pts - or "correct" - 10pts).
Thanks,
Vijay

JSP classes warning:

I have a webroot/WEB-INF/jsp directory with my jsps. When I compile I get the following warning for all my jsps:
Warning: package name web2d_inf._jsps does not match source file name C:\CVSHome\Orion\jdev\registration\regView\classes\.jsps\_WEB_2d_INF\_jsps\_testname.java
I am using JDev 9.03x

I've had the same problem. I'm interested in this on too.

Invalid JSP editor warning

The following JSP will produce the following warning:
The attribute value tag "c:choose" should end with "/>".
================ badWarning.jsp ===============
<%@ page contentType="text/html;charset=UTF-8" language="java" %>
<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.01//EN"
"http://www.w3.org/TR/html4/loose.dtd">
<%@ taglib uri="/WEB-INF/c.tld" prefix="c" %>

<c:when test="true"> even </c:when><c:otherwise> odd </c:otherwise></c:choose>' >
some text

==========================================

Thanks for the catch, this will be fixed for the final 2.0 release, later this month.
In the mean time, an alternative (simpler?) way is:

some text

Validator warning: Character Encoding mismatch!

I have been following the discussion on favicons with
interest. A few days ago
I added a favicon to the page:
http://www.corybas.com/, and
eventually persuaded
IE6 to show the favicon, provided I loaded it by clicking the
icon. It did not
show it when the page reloaded itself, and now it has
forgotten all about it.
Following some discussions here this morning I ran the
Validator over the page
and got the diagnostic "The character encoding specified in
the HTTP header
(utf-8) is different from the value in the <meta>
element (iso-8859-1). I will
use the value from the HTTP header (utf-8) for this
validation. "
As far as I can work out, this is caused by an
incompatibility in the witchcraft
Dreamweaver includes in a basic HTML page, which is as
follows:
<!DOCTYPE html PUBLIC "-//W3C//DTD XHTML 1.0
Transitional//EN"
http://www.w3.org/TR/xhtml1/DTD/xhtml1-transitional.dtd">
<html xmlns="
http://www.w3.org/1999/xhtml">
<head>
<meta http-equiv="Content-Type" content="text/html;
charset=iso-8859-1"
/>
<title>Untitled Document</title>
</head>
Should I worry about this warning?
(I removed a few other insignificant errors, but IE6 still
can't see the
favicon.)
Clancy

On 22 Apr 2008 in macromedia.dreamweaver, Clancy wrote:
> Following some discussions here this morning I ran the
Validator
> over the page and got the diagnostic "The character
encoding
> specified in the HTTP header (utf-8) is different from
the value in
> the <meta> element (iso-8859-1). I will use the
value from the HTTP
> header (utf-8) for this validation. "
>
> As far as I can work out, this is caused by an
incompatibility in
> the witchcraft Dreamweaver includes in a basic HTML
page, which is
> as follows:
>
> <!DOCTYPE html PUBLIC "-//W3C//DTD XHTML 1.0
Transitional//EN"
> "
http://www.w3.org/TR/xhtml1/DTD/xhtml1-transitional.dtd">
> <html xmlns="
http://www.w3.org/1999/xhtml">
> <head>
> <meta http-equiv="Content-Type" content="text/html;
> charset=iso-8859-1"
> />
> <title>Untitled Document</title>
> </head>
>
> Should I worry about this warning?
At an offhand guess, you're on an Apache 2.x server. In its
default
setup, it sends a UTF-8 charset header. That is sufficient
for the
browser. It also conflicts with the iso-8859-1 charset in the
document. The fastest cure for it is to remove the charset
meta from
the page, or change it to UTF-8. But it has no bad effects
that I know
of on a browser.
Joe Makowiec
http://makowiec.net/
Email:
http://makowiec.net/contact.php

JSP-VALIDATION

Pls, I want to do validation with jsp. I want it to return error messages that some data are omitted on the same page with the form submitting, but its not working. pls, assist!. See the code
<html>
<body>
<% String first = request.geParameter(firstname);
 if(first !=null || !first.equals(""))
 // go to another page
 else
 %>
Fill in your first name
<form method="post action="accept.jsp">
First Name: <input type="text" name="firstname"> <%=first%>
<input type="submit" value="Submit">
<%}%>
</body>
</html>

spelling mistake "getparameter"

Prevent jsp validation rules from view source

is there any way to prevent jsp or js validation script,from html view source (other than using struts validation framework).

is there any way to prevent jsp or js validation
script,from html view source (other than using struts
validation framework).JS files get downloaded in the browser temp directory so there's no way of preventing a user from not accessing it.
***Annie***

JSP Enum warn disabling

          Is there any way of disabling the following error message when starting weblogic?
          [JSPEnum] no match: 'META-INF/'
          [JSPEnum] no match: 'images/'
          [JSPEnum] no match: 'WEB-INF/'
          [JSPEnum] no match: 'WEB-INF/classes/'
          [JSPEnum] no match: 'WEB-INF/classes/com/'
          This is all the information I can find on the net:
          When the server is restarted, each resource in the the web application is checked
          to see if it needs to be compiled. The server console will log a message for each
          file compiled. Ignore any [JSP Enum] no match messages. These are displayed for
          files that do not match the .jsp file extension


refresh
Can someone give me any insight into this issue - possible workarounds etc. ??? Maybe Juan Oropeza or Robert Hoexter?
TIA, Simon Cullen

NoClassDefFoundError while validating JSP

Hello, I am using the trial version of NitroX for Struts with Eclipse 3.0.2. Everything seemed to be OK for the first 5 days or so, but now, every time I do a build, I get this warning in the "Problems" tab of the Web Perspective:
Run-time exception java.lang.NoClassDefFoundError occurred during validation. The validator being run was JSP Validator and the message thrown was com/genuitec/eclipse/core/util/Util. I get one of these messages for every JSP in my project, regardless of simplicity. Thank you in advance any help/advice you can give.

Hi,
What are the different plug-ins configured for your eclipse?
Send the following log files to [email protected]
* ..eclipse\workspace\.metadata - .log file
* <NitroX Install Folder>\NitroX\eclipse\plugins\com.m7.nitrox_2.0.0 - m7.log.0 file
M7 Support

Forms and validations - here's some of my ideas, what are yours?

One of the big things still missing from the JFX space (especially where JEE is concerned) is forms and form validations. Maybe you guys have been luckier but at least 80% of the screens I've had to build in my career have been boring old forms - enter data in the fields, validate them and hit submit.
So, I've been hacking around on this to try and get a pattern and hopefully some reusable classes for doing this in JavaFX. I have something that works but the code is verbose and less than elegant. I'm hoping some of you guys might want to kick around some ideas on this with me here. If we can come up with something that works, I'd like to either include it in [url http://www.zenjava.com/jfx-flow/]JFX Flow, or put it out as a separate open source project (whichever makes more sense).
What I think needs to be supported:
* Map between a normal Java bean and the fields on a form
* Validate the data, i.e. specifying the constraints on a field and then checking those constraints
* Show a validation summary at the top of the form
* Highlight individual fields if they have validation errors
* Support auto-validation, i.e. the validation highlights and messages will instantly update as the user types
Some extra restrictions:
* The data input will ideally be a normal bean and so it won't have observable values on it. In most projects I use, the beans are coming from the server and sometimes may be shared between desktop client and a jsp/web client, or even be a third party API so they can't be changed. End result: we don't want any JFX complexities or dependencies in our server code (design leak). This rule could be bent but only as a last resort.
* The validations must be defined relative to the normal data bean not a JFX model or controller, etc. This is so the bean can be validated on the server as well as the client. The server must do validation to prevent dodgy data getting in (never trust a client). Ideally we don't want to be specifying the validations in two places (i.e. once for the client and once for the server) as this creates maintenance problems and weakens the integrity of the system over time.
* Ideally the validation mechanism will be based on [url http://java.dzone.com/articles/bean-validation-and-jsr-303]JSR 303 - Bean Validations as this is quite nice. This is flexible however if there is a suitable alternative that integrates better.
To give us something to reference in conversation, I've created a small working sample. This is only meant to be a rough starting point (at best) and I'd really like to get feedback on both the code (i.e. should we have a 'presentation model', how could bindings be better used, etc) and the general way I'm representing errors (i.e. should we use tooltips to show errors, or actually show the errors next to the field, should we use border colours or put a little exclamation mark over the field, should the fields be auto-validated or only validated on submit, etc).
The example is a single form for editing a person. It has three fields, first name, last name and gender. When the form is blank, auto-editing is off. When the user submits the form it is validated and from that point on auto-validating is on. Error fields are highlighted with a style change, and a tooltip is added with details (I think we can do better - what's your ideas?).
I have used all plain Java to keep thngs simple, but I'd be looking for the end result to translate to FXML as well. I've also coded everything into the one class but the eventual goal would be to have the common stuff moved out to reusable base classes, etc.
Here's a workspace with some example code in it: http://code.google.com/p/jfxee/source/browse/trunk/jfxforms/
Here's a running deploy of that code: http://zenjava.com/demo/form/forms.html
(edit: I've moved the code to its own project and changed the url for the launch - the values above are the new, correct ones)
Looking forward to hearing some thoughts on this topic.
Edited by: zonski on 01-Dec-2011 13:41

At Devoxx I did some straw man prototype that you might find useful (or hopeless, I'm not sure which, I did it in a hurry :-)). I followed some principles that I was influenced by years back by JGoodies, but I haven't looked at the JGoodies stuff in forever and know it isn't all the same. But anyway, like I said, I'm not sure it is actually useful but maybe there is something genius hidden in there.
I have a Validator, which is just a simple SAM:
import javafx.scene.control.Control;
* @author Richard
public interface Validator<C extends Control> {
 public ValidationResult validate(C control);
}The idea is that it is given a Control, it will validate that control, and then return a ValidationResult. ValidationResult is actually only needed in cases of errors, since returning null indicates success, so the following is somewhat of a crock but you could rename it ValidationError or something and remove the "SUCCESS" type and there you are.
public class ValidationResult {
 public enum Type { ERROR, WARNING, SUCCESS }
 private final String message;
 private final Type type;
 public ValidationResult(String message, Type type) {
 this.message = message;
 this.type = type;
 public final String getMessage() {
 return message;
 public final Type getType() {
 return type;
 }For good measure I threw in a ValidationEvent.
import javafx.event.Event;
import javafx.event.EventType;
* @author Richard
public class ValidationEvent extends Event {
 public static final EventType<ValidationEvent> ANY =
 new EventType<ValidationEvent>(Event.ANY, "VALIDATION");
 private final ValidationResult result;
 public ValidationEvent(ValidationResult result) {
 super(ANY);
 this.result = result;
 public final ValidationResult getResult() { return result; }
}Because Control's don't presently have the notion of validation built in, I created a ValidationPane which is like a specialized StackPane, where there is a bottom layer, the control, and a glass pane layer. And from CSS you can style it however you like. The ValidationPane has a CSS style class set in case of errors / warnings. So without augmenting controls, the idea is that a ValidationPane subclass would exist to wrap each type of control you needed to validate. It did this because somebody has to wire up the listeners to the control to react on text input etc, and so I thought I'd like that encapsulated in something reusable, and there it was.
import javafx.beans.DefaultProperty;
import javafx.beans.property.ObjectProperty;
import javafx.beans.property.ReadOnlyObjectProperty;
import javafx.beans.property.ReadOnlyObjectWrapper;
import javafx.beans.property.SimpleObjectProperty;
import javafx.beans.value.ChangeListener;
import javafx.beans.value.ObservableValue;
import javafx.event.EventHandler;
import javafx.scene.control.Control;
import javafx.scene.layout.Region;
* @author Richard
@DefaultProperty("content")
public abstract class ValidatorPane<C extends Control> extends Region {
 * The content for the validator pane is the control it should work with.
 private ObjectProperty<C> content = new SimpleObjectProperty<C>(this, "content", null);
 public final C getContent() { return content.get(); }
 public final void setContent(C value) { content.set(value); }
 public final ObjectProperty<C> contentProperty() { return content; }
 * The validator
 private ObjectProperty<Validator<C>> validator = new SimpleObjectProperty<Validator<C>>(this, "validator");
 public final Validator<C> getValidator() { return validator.get(); }
 public final void setValidator(Validator<C> value) { validator.set(value); }
 public final ObjectProperty<Validator<C>> validatorProperty() { return validator; }
 * The validation result
 private ReadOnlyObjectWrapper<ValidationResult> validationResult = new ReadOnlyObjectWrapper<ValidationResult>(this, "validationResult");
 public final ValidationResult getValidationResult() { return validationResult.get(); }
 public final ReadOnlyObjectProperty<ValidationResult> validationResultProperty() { return validationResult.getReadOnlyProperty(); }
 * The event handler
 private ObjectProperty<EventHandler<ValidationEvent>> onValidation =
 new SimpleObjectProperty<EventHandler<ValidationEvent>>(this, "onValidation");
 public final EventHandler<ValidationEvent> getOnValidation() { return onValidation.get(); }
 public final void setOnValidation(EventHandler<ValidationEvent> value) { onValidation.set(value); }
 public final ObjectProperty<EventHandler<ValidationEvent>> onValidationProperty() { return onValidation; }
 public ValidatorPane() {
 content.addListener(new ChangeListener<Control>() {
 public void changed(ObservableValue<? extends Control> ov, Control oldValue, Control newValue) {
 if (oldValue != null) getChildren().remove(oldValue);
 if (newValue != null) getChildren().add(0, newValue);
 protected void handleValidationResult(ValidationResult result) {
 getStyleClass().removeAll("validation-error", "validation-warning");
 if (result != null) {
 if (result.getType() == ValidationResult.Type.ERROR) {
 getStyleClass().add("validation-error");
 } else if (result.getType() == ValidationResult.Type.WARNING) {
 getStyleClass().add("validation-warning");
 validationResult.set(result);
 fireEvent(new ValidationEvent(result));
 @Override
 protected void layoutChildren() {
 Control c = content.get();
 if (c != null) {
 c.resizeRelocate(0, 0, getWidth(), getHeight());
 @Override
 protected double computeMaxHeight(double d) {
 Control c = content.get();
 return c == null ? super.computeMaxHeight(d) : c.maxHeight(d);
 @Override
 protected double computeMinHeight(double d) {
 Control c = content.get();
 return c == null ? super.computeMinHeight(d) : c.minHeight(d);
 @Override
 protected double computePrefHeight(double d) {
 Control c = content.get();
 return c == null ? super.computePrefHeight(d) : c.prefHeight(d);
 @Override
 protected double computePrefWidth(double d) {
 Control c = content.get();
 return c == null ? super.computePrefWidth(d) : c.prefWidth(d);
 @Override
 protected double computeMaxWidth(double d) {
 Control c = content.get();
 return c == null ? super.computeMaxWidth(d) : c.maxWidth(d);
 @Override
 protected double computeMinWidth(double d) {
 Control c = content.get();
 return c == null ? super.computeMinWidth(d) : c.minWidth(d);
}And finally the TextInputValidatorPane instance good for any TextInputControl. I think.
import javafx.beans.InvalidationListener;
import javafx.beans.Observable;
import javafx.beans.value.ChangeListener;
import javafx.beans.value.ObservableValue;
import javafx.scene.control.TextInputControl;
* @author Richard
public class TextInputValidatorPane<C extends TextInputControl> extends ValidatorPane<C> {
 private InvalidationListener textListener = new InvalidationListener() {
 public void invalidated(Observable o) {
 final Validator v = getValidator();
 final ValidationResult result = v != null ?
 v.validate(getContent()) :
 new ValidationResult("", ValidationResult.Type.SUCCESS);
 handleValidationResult(result);
 public TextInputValidatorPane() {
 contentProperty().addListener(new ChangeListener<C>() {
 public void changed(ObservableValue<? extends C> ov, C oldValue, C newValue) {
 if (oldValue != null) oldValue.textProperty().removeListener(textListener);
 if (newValue != null) newValue.textProperty().addListener(textListener);
 public TextInputValidatorPane(C field) {
 this();
 setContent(field);
}This should also be usable as is from FXML since you can easily wrap a TextInputValidatorPane around a TextField, and CSS does all the styling, so I think it all just works. You probably need to have some library of sophisticated Validators which know how to read text from a TextField and compare against the validation annotations, but otherwise it should work well enough. Anyway, in the actual implementation I think I would omit the ValidationPane stuff completely and just build that part into the controls / skins. Like I said, this was a quick hack but seemed to get the "how do I visualize validation errors" part of the problem solved.
Richard

JSP validation warning.

Similar Messages

Maybe you are looking for