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 84778 - Validator does not not recognize all allowed tags
Summary: Validator does not not recognize all allowed tags
Status: CLOSED INVALID
Alias: None
Product: soa
Classification: Unclassified
Component: BPEL Validation (show other bugs)
Version: 5.x
Hardware: PC Windows XP
: P3 blocker (vote)
Assignee: issues@soa
URL:
Keywords:
Depends on:
Blocks:
 
Reported: 2006-09-13 10:49 UTC by Maksim Khramov
Modified: 2006-10-03 10:48 UTC (History)
0 users

See Also:
Issue Type: DEFECT
Exception Reporter:


Attachments

Note You need to log in before you can comment on or make changes to this bug.
Description Maksim Khramov 2006-09-13 10:49:12 UTC
Create new diagram.
Add new Scope activity to diagram and perform validation.
The error message says: 'The content of element 'scope' is not complete. One of
'{"http://schemas.xmlsoap.org/ws/2004/03/business-process/":documentation,...'
go to source view and add <documentation></documentation> code into scope.
Save and validate document again. 
We see the same message
Comment 1 Maksim Khramov 2006-09-13 10:59:03 UTC
The error messages should be more human readable. 
In this case for example the error message is 2373 symbols length but the
visible part of message is about 180 chars...
Also it contains a lot of URL-like links which cannot be opened. It is confusing
Comment 2 Michael Frisino 2006-09-13 11:37:09 UTC
if message comes from XML Schema validator we have no way to influence the text
of the message. These messages come from the standard xml schema validator. We
only invoke the validator and then distribute the messages so that user can see
the messages. We cannot control message content.
Comment 3 Michael Frisino 2006-09-19 18:15:35 UTC
Ok, several things here.

Why is the subject line of this message "Validator does not not recognize all
allowed tags". I do not understand that description at all. I would suggest
changing this subject to "Long XML Validaton messages are being truncated in the
output window"

The message cannot be modified since it comes from XML Validaton subsystem. Out
of our control.

However, there could be two things done to improve readability of this message.

1) The message is truncated in the output window. Praveen why is this? Shouldn't
it either scroll to right or wrap around?

2) The Hyperlink should in my opinion Open the callout window on the element.
Today the hyperlink ONLY selects the invalid element, it does not open the
callout, therefore from the user persective it may look like it does nothing at
all, especially if the invalid element is already selected, which is the case if
you follow this scenario.



Comment 4 Michael Frisino 2006-09-19 19:37:15 UTC
On further review and discussion with engineers, we come to conclusion that this
is not a new bug - unless we are missing something. Again, I do not understand
the summary line. It does not seem to have any relationship to the bug description.

As for other observations. The "truncated" text in output window is not actually
truncated. There is a different bug in NetBeans already filed (i do not know
number but I have been told it is a well known issue). This bug says that
occasionally, the NetBeans output window does not show horizontal scroll bar
when it should show it. Usually, on next write, the horizontal scroll bar
appears. That is a NetBeans bug, not a BPEL validation bug. 

In either event, the full text is there and you can see it more easily if you
select "Wrap text" option in the output window.

Finally, as for the hyperlink. The hyperlink does do something, it selects the
activity associated with the error message. So if that activity is scrolled off
sreen , or not selected, you would see this behavior. It only appears to do
nothing if the acitvity is already selected.

HIE has determined that auto-opening the callout window is not a bug. It is by
design. You may open an RFE for that feature if you wish. 

In sum, I am closing this as invalid.
Comment 5 Maksim Khramov 2006-10-03 10:48:18 UTC
Closed as invalid