[
http://jira.jboss.com/jira/browse/JBIDE-803?page=all ]
Max Andersen reassigned JBIDE-803:
----------------------------------
Assignee: Viacheslav Kabanovich (was: Marshall Culpepper)
I know this is probably just a duplicate of the seam 2 components.xml issue, but why do
our error messages contain:
0.0 instead of a proper location ?
null instead of a proper content ?
e.g this would be what I expected if the error is on line 7 and column not known:
ERROR: Line 7 Unallowed child <managed-persistence-context> of <components>
note the null is removed and no 0.0 which looks more like bugs in our code than bug in
users files ;)
Build error creating a new seam 2.0 project in RHDS Beta 1
----------------------------------------------------------
Key: JBIDE-803
URL:
http://jira.jboss.com/jira/browse/JBIDE-803
Project: JBoss Tools
Issue Type: Bug
Components: JBoss Tools Core
Affects Versions: 2.0.0.Beta3
Environment: Windows XP SP2. Redhat Dev Studio Beta1, Seam 2.0, JDK 1.5.0.9
Reporter: Gary Pinkham
Assigned To: Viacheslav Kabanovich
Priority: Minor
Creating a new seam project using Seam 2.0 and Redhat Dev Studio Beta 1 creates a
Component.XML with the following error:
ERROR: 0.0 Unallowed child null:managed-persistence-context of components
The error shows in the tree view in the Redhat XML Editor and in the Problems tab as it
causes a build error. Modifying the Component.xml file (adding in
entity-manager-factory="" to the
"persistence:managed-persistence-context" tag and saving causes the build error
to go away but the error still shows on the Tree view tab. I removed the
entity-manager-factory="" from the file and re-saved. Build still works. If
I reopen the file in Tree view mode the build error returns.
--
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators:
http://jira.jboss.com/jira/secure/Administrators.jspa
-
For more information on JIRA, see:
http://www.atlassian.com/software/jira