Bug 875656 - XML validation errors after importing Blog example to JBDS
Summary: XML validation errors after importing Blog example to JBDS
Keywords:
Status: CLOSED INSUFFICIENT_DATA
Alias: None
Product: JBoss Enterprise WFK Platform 2
Classification: Retired
Component: Seam
Version: 2.1.0
Hardware: Unspecified
OS: Unspecified
unspecified
medium
Target Milestone: ---
: 2.4.0
Assignee: Marek Novotny
QA Contact:
URL:
Whiteboard: Seam2.3
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2012-11-12 10:04 UTC by Tomas Remes
Modified: 2013-07-22 13:24 UTC (History)
3 users (show)

Fixed In Version:
Clone Of:
Environment:
Last Closed: 2013-07-22 13:24:07 UTC
Type: Bug
Embargoed:

Attachments (Terms of Use)


Links
System ID Private Priority Status Summary Last Updated
Red Hat Bugzilla 869348 0 unspecified CLOSED Seam2.3 blog example atom feed not working and JBDS import errors 2021-02-22 00:41:40 UTC
Red Hat Issue Tracker JBIDE-12990 0 None None None Never
Red Hat Issue Tracker WFK2-99 0 Minor New XML validation errors after importing Blog example to JBDS 2013-11-19 11:48:05 UTC

Internal Links: 869348

Description Tomas Remes 2012-11-12 10:04:00 UTC 
Description of problem:
Seam Blog example displays following errors after import to JBDS:

Referenced file contains errors (file:/home/tremes/JBDS/5.0.1.GA/studio/plugins/org.jboss.tools.jst.web.kb_3.3.1.v20120715-0241-H93-Final/taglibs/tld/facelets_jsf_core.taglib.xml).

cvc-elt.1: Cannot find the declaration of element 'f:view'.
Comment 1 mark yarborough 2012-11-12 14:43:26 UTC 
Marek to provide CCFR.
Comment 3 Isaac Rooskov 2012-11-15 03:51:08 UTC 
Thanks for the CC Marek. 

Are you able to answer the following question for me though please:

- Are the errors presented incorrect or is there still an issue in the example?
Comment 4 Marek Novotny 2012-11-15 07:36:55 UTC 
Isaac, 
errors are still there because of https://issues.jboss.org/browse/JBIDE-12990.

No workaround is known to me or JBDS team.
Comment 5 Sneha 2013-03-25 07:16:58 UTC 
Doc Text is updated.
Note You need to log in before you can comment on or make changes to this bug.