Created attachment 59591 [details]
project file plus driver jars

The attached project may be invalid, but still I wouldn't expect an Assertion error to occur when opening CONSTANTSview.jsp

To setup the project:
1) Unzip the attachment (includes both a project and driver jar files).
2) In NetBeans, switch to the Services tab, expand Databases, right-click on Drivers and add new Driver.
Provide the both jar files that are included in the root of the folder extracted by the zip file

3) Open the project, a warning dialog opens, click OK
4) Right-click on project and choose Resolve Database problem menuitem
5) In the Resolve Data Sources dialog, select the data source then click Add Database Connection then accept the default
values and click OK

6) Open CONSTANTSview.jsp
If you don't get the Assertion error then click on the JSP tab for the page then back to Design view

If I open the same project in 6.0 and CONSTANTSview.jsp then the page opens fine.

This seems to be a regression in 6.1

The assertion is from this check:

        Element element = dom.getDocumentElement();
        
        if (element.hasAttribute("xmlns:ui")) { // NOI18N
            assert element.getAttribute("xmlns:ui").equals("http://www.sun.com/web/ui"); // NOI18N
            
            return true;
        }

So need to look inside the .jsp source to see if the value of the xmlns:ui is in fact 'http://www.sun.com/web/ui'. If
not, how it got changed?

Sure enough...in the .jsp source I see:

xmlns:ui="http://www.sun.com/webui/webuijsf"

which looks like the one from Woodstock.

The project seems to be a JSF 1.2 project...in which case the namespace should be:

xmlns:webuijsf="http://www.sun.com/webui/webuijsf"

(which is the case in Page1.jsp in the same project)

and you cannot use Bravehart components in JSF 1.2 based projects.

Theoretically 

xmlns:ui="http://www.sun.com/webui/webuijsf"

is correct. As long as all the prefix to the woodstock components in the page also has ui: prefix.

Actually, I see in nbdev users arguing about "stupid" naming convention (webuijsf). In fact one user has changed the
template to xmlns:w="http://www.sun.com/webui/webuijsf" and all the component prefix to w: and claims now on all the
pages she creates correctly generating with w: (impressive flexibility she says :) )

yes, I see the incompatibility, but the page opens fine in 6.0

Also, if there is stricter checking for component versions then at least the Assertion error could be more descriptive.

Since the page is invalid may not be P2 but still need to understand why the page opens in 6.0 

May be the page opens but does it work?

Do you have the 6.0 FCS. In the FCS product assertions are off.

Well Insync always had this code to detect the Bravehart vs. Woodstoick and the mechanism was recommended by component
team. I think Designer also uses it.

User is cc'd to describe what he did

In 6.1 the page opens blank, but in 6.0 the page the components render fine.

I guess you didn't try opening the project?

hi
I am unable to understand what is cc'd.

Actully i am also unable to open page of V6.0 in V6.1

but on my side my page only does not display in netbeans 6.1.
when i deploy my project through V6.1 . my page displays properly on browser.

now i am asking to u why ur 2 versions (V6.0 and V6.1)are not compatible with each other???
V6.1 is the updated version of V6.0, so it should support V6.0 code also.

if u r able to solve my problem(Edit,Update,Delete) on V6.0 , then i need not to sift from V6.0 to V6.1.

I have not done anything different in this project. I have created my project according to ur sample code.

Thanks
waiting for reply

cc'd means that your netbeans user id is on the cc list which means that you are included in discussions of this issue
see above.

The problem with your application does not appear to be any incompatibility with 6.0 and 6.1.
I've provided you an example of the correct way to do Inserts Updates Deletes.  Also, I provided information on how
to get more help with your application. http://developers.sun.com/services/expertassistance/index.jsp?intcmp=1365

Fixed.
The assertion was removed, and also the check for the relevant xmlns: attribute improved.

changeset:   101838:e5455167b93c
tag:         tip
user:        Peter Zavadsky <pzavadsky@netbeans.org>
date:        Fri Sep 12 14:51:29 2008 -0700
summary:     #131894 Fixing assertion, improving checking for braveheart and woodstock type of components.

Integrated into 'main-golden', will be available in build *200809130201* on http://bits.netbeans.org/dev/nightly/ (upload may still be in progress)
Changeset: http://hg.netbeans.org/main/rev/e5455167b93c
User: Peter Zavadsky <pzavadsky@netbeans.org>
Log: #131894 Fixing assertion, improving checking for braveheart and woodstock type of components.