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.
I created a seam(2.2.GA) project from seam command and open it from NetBeans IDE 6.8 RC1. There are some errors markers on xhtml page(in the layout folder, each page are marked as errors occurred), but there are no errors. The seam taglib are also marked as errors, but no indication about it. Please research the attachment.
Created attachment 92023 [details] screenshot
Could you provide sample project to reproduce?
Do you have any errors during build and deploy?
This is a new created project... without one line extra code, I deployed it into JBoss 5.1, and it works well. From the indication of the error marker, it can not determine the xmlns attribute if the root element is not "html". You can download Seam 2.2.0GA release package, and use ./seam setup and ./seam create-project in seam directory to create a new project and verify the problem. The seam scaffold is based on ant, so the project includes all needed jars, it is two big, so I will not upload it here. I reused the NetBeans user dir from Beta version(move folder 6.8beta to 6.8rc1 in ~/.netbeans directly), and I will remove my NetBeans user dir, and reinstall IDE to verify this problem later.
The problem is still here after I installed a clean version(I removed the userdir for 6.8rc1).
Created attachment 92028 [details] screenshot after reinstallation
Marek, could you take a look, as I remember you were fixing similar issues with error highlighting. IMHO it is P3, not P2, since it is not break anything.
I think this bug must be fixed in this version(before 6.8fcs). By the way, the project created by the seam scaffold is a freeform project.
Just from the glimpse I see two problems here: 1) the default xmlns attribute is marked as nonexisting - this is a P3 bug, the error checks doesn't find this attribute in the component's interface, but since this is a generic xml attribute it must not be flagged as error. 2) there is apparently a problem with parsing the seams facelets descriptors or TLDs. I'm downloading seams right now, I'll check the issue in a half an hour.
There doesn't seem to be a jar file containing a facelets descriptor or at least a tld file for the "http://jboss.com/products/seam/taglib" namespace. Hence all the references to this library are marked as errors. Other facelets libraries like the richfaces works fine, they have their jars on the project classpath. Please specify where the descriptors for http://jboss.com/products/seam/taglib library are in the project structure.
OK, I finally found it - it's in jboss-seam-ui.jar, I'll check why this is not indexed properly while other jars from the same folder are.
Hmmm, the jboss-seam-ui.jar is not on the project's compile classpath, which is used by the jsf support for indexing the facelets libraries. Once you add lib/jboss-seam-ui.jar to the proper entry in ${project_home}/nbproject/project.xml the library is parsed and editor works fine for the component usages. <java-data xmlns="http://www.netbeans.org/ns/freeform-project-java/2"> <compilation-unit> <package-root>src/main</package-root> <classpath mode="compile">lib/jboss-seam-ui.jar: [snip]
Created attachment 92036 [details] screenshot I added it, but the error marker did not disappear. I restarted NetBeans IDE, there is no effect.
hantsy, as I've written already, there used to be two issues: 1) the xmlns being marked as error 2) the components from "http://jboss.com/products/seam/taglib" library marked as unknown #2 is caused by the issue with missing compile classpath entry in the project.xml #1 is unrelated to that and not fixed yet. On your last screenshot I can see just #2. Does the #1 problem disappears once you add the jboss-seam-ui.jar jar file to the compile classpath as I suggested? Just this problem can be considered as P1, the second is really minor issue which cannot harm anyone.
As displayed in the last screenshot, you can see that I'v added the jboss-seam-ui.jar(in the right editor)... But the problem still occurs and no change, it is same with that before added the jboss-seam-ui jar. The indicator information on error marker has no different from before. Yes, when added jboss seamui jar, the s prefix taglib can be recognized. I think this is a big problem when using facelets as jsf page template. It is strange that xhtml is also xml, there is no problem when I use more than one namespace in the Spring configuration file, why xhtml is problematic? The difference I think is that facelets xhtml mapped the tranditinal taglib tld defs to xml namespace but xml using native dtd or schema to define xml element and attribute.
>Yes, when added jboss seamui jar, the s prefix taglib can be recognized. Which was the reason why this issue was P1, wasn't it? Again, the xmlns attribute being marked as error is a bug which I consider as minor by contrast to the problem with the unrecognized library. Do you consider the issue with xmlns attribute as a stopper for your workflow? [YES/NO] If YES, please explain why. Thanks.
Beside the xmlns attribute error marker...The root element attribute name and value code completion also does not work. This will make user feel it is strange that XHTML is xml, but it works not like xml. I think if tld is treat as a normal xml schema definition form, like DTD and xml schema, this problem can be fixed easily.
This is only my idea. If you think this is not a stopper, you can skip it.
I think this problem can be categorised as : 1. If xmlns value is missing(the jboss seam ui taglib is missing in the picture but no indication on the xmlns declaration ),the error marker may be marked on it(basically, indicated it is not found in classpath, more effective provide fix action,eg search in classpath, or replace it a known one)... 2. Process the root element as XML(the rich:xxx root element declaration error which complained the xmlns attribute was invalid, I think you must rethink which tags of the taglib(eg. rich:) can be process as root element. I've said if treat tld as a xml definition form, this problem can be fix quickly)...
It is fixed in NetBeans 6.9 ???
(TM == Next) ==> No, its not fixed. And I must admit I'm having troubles trying to understand what the latest state of you problem is. Could you please try to summarize it again for me? I'm sorry but I do not understand some of your thoughts/comments much :-|
Now, NetBeans determin if a xml file is validated by its dtd definition (declared in doctype) or xml schema definition(declared xmlns in root element). In facelets file(xhtml), some tags are not from standard DTD or xsd file, but from the JSF specific tld file(on the seam framework website, somebody suggested jsf taglib definition file use xsd directly). In a word, treat tld as another xml tag definition form(beside dtd, xsd, and relaxng). Then, like provide in dtd and xsd, provide a tldparser to process jsf specific tag in the xhtml file.
(In reply to comment #22) > Now, NetBeans determin if a xml file is validated by its dtd definition > (declared in doctype) or xml schema definition(declared xmlns in root element). > In facelets file(xhtml), some tags are not from standard DTD or xsd file, but > from the JSF specific tld file(on the seam framework website, somebody > suggested jsf taglib definition file use xsd directly). > > In a word, treat tld as another xml tag definition form(beside dtd, xsd, and > relaxng). Then, like provide in dtd and xsd, provide a tldparser to process jsf > specific tag in the xhtml file. What is the *real* problem? Is that the xmlns attribute being marked as unknown and therefire the file having a "red" status? This is issues is already fixed. Is there anything else *in particular*?
What is the *real* problem? Is it the xmlns attribute being marked as unknown and therefore the file having a "red" status? This issue is already fixed. Is there anything else *in particular*?
The issue seems to be fixed now. Reporter please reopen if you object and describe the erroneous case.