[JBoss JIRA] Created: (JBIDE-1794) NullPointerException at Mapping Diagramm
by Dima Geraskov (JIRA)
NullPointerException at Mapping Diagramm
----------------------------------------
Key: JBIDE-1794
URL: http://jira.jboss.com/jira/browse/JBIDE-1794
Project: Tools (JBoss Tools)
Issue Type: Bug
Reporter: Dima Geraskov
Assigned To: Dima Geraskov
Fix For: 2.1
If we have mapping when id class not embedded in the entity NullPointer occured when you select id-property at the mapping diagramm.
For ex:
<class name="Customer">
<composite-id class="CustomerId" mapped="true">
<key-property name="orgName" column="org_name"/>
<key-property name="customerName" column="cust_name"/>
</composite-id>
</class>
(See "mapping.idclass" pack in test mapping project ).
Persistance class for the property is null. (Properties view demands it).
I'll change it to return null (when it threw NullPointerException).
But for the Composite properties Diagram uses SpecialPersistanceClas,
as properties view demands it, we have here some inconsistency between shown Persistance class in Properties view and real Persistance class (think about Address object - properties view will show it like Persistance class for the street, but real persistance class is null).
--
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
18 years
[JBoss JIRA] Created: (JBIDE-1902) contributing own completion metadata is impossible (contibutions to org.jboss.tools.common.kb.tldResource must come from org.jboss.tools.common.kb)
by Heiner Westphal (JIRA)
contributing own completion metadata is impossible (contibutions to org.jboss.tools.common.kb.tldResource must come from org.jboss.tools.common.kb)
---------------------------------------------------------------------------------------------------------------------------------------------------
Key: JBIDE-1902
URL: http://jira.jboss.com/jira/browse/JBIDE-1902
Project: Tools (JBoss Tools)
Issue Type: Bug
Components: jsp/jsf/xml source editing
Affects Versions: 2.0.0.GA
Environment: eclipse 3.3.2 with WTP 2.0.2 on Windows XP
Reporter: Heiner Westphal
We want to contribute to extension point "org.jboss.tools.common.kb.tldResource"
supplying our own meta data in our own plugin.
But the schema-location is not interpreted relative to our plugin:
org.jboss.tools.common.kb/src/org/jboss/tools/common/kb/KbTldStore.java
...
File shemaLocation = new File(kbPluginLocation, location);
..
Contributing plugins will not put their schema files inside the org.jboss.tools.common.kb plugin,
thus the location should be resolved relative to the contributing plugin, not relative to
org.jboss.tools.common.kb.
As a workaround I used a path containing ../pluginname_version/...:
<?xml version="1.0" encoding="UTF-8"?>
<?eclipse version="3.0"?>
<plugin>
<extension
point="org.jboss.tools.common.kb.tldResource">
<tld
jsf="true"
name="My Components"
schema-location="../some.company.jsf.kb.mycomponents_1.0.0/tldschema/MyComponents.xml"
uri="http://www.company.some/mycomponents"/>
</extension>
</plugin>
--
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
18 years
[JBoss JIRA] Created: (JBIDE-1778) Improve updating package structure in Seam project
by Viacheslav Kabanovich (JIRA)
Improve updating package structure in Seam project
--------------------------------------------------
Key: JBIDE-1778
URL: http://jira.jboss.com/jira/browse/JBIDE-1778
Project: Tools (JBoss Tools)
Issue Type: Feature Request
Affects Versions: 2.0.0.GA
Reporter: Viacheslav Kabanovich
Assigned To: Viacheslav Kabanovich
Fix For: 2.1
In current implementation, loading each component is followed by exhausting checking of seam package structure.
This is redundant and time consuming, loading N components results in ~ N * N checks, which is inadmissible for large projects.
1) Remove exhausting checking of seam package structure.
2) Implement incremental modification of seam package structure at adding/removing/modifying a seam component.
Testing: already existing tests for seam model should not fail.
--
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
18 years