[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-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
[JBoss JIRA] Created: (JBIDE-1820) Please use the standard Eclipse files for project dependencies the org.jboss.tools.jst.web.xml is a complete mess
by Stephen Westbom (JIRA)
Please use the standard Eclipse files for project dependencies the org.jboss.tools.jst.web.xml is a complete mess
-----------------------------------------------------------------------------------------------------------------
Key: JBIDE-1820
URL: http://jira.jboss.com/jira/browse/JBIDE-1820
Project: Tools (JBoss Tools)
Issue Type: Feature Request
Components: Cleanup
Affects Versions: 2.0.0.GA
Environment: Windows, any really
Reporter: Stephen Westbom
Priority: Critical
The org.jboss.tools.jst.web.xml file duplicates information that is already contained in the .classpath file and the org.eclipse.wst.common.component file in the settings directory and does it pretty badly (no java environment variables supported, it puts jar files in the web-inf/lib directory that Eclipse should do at build time only). This just adds yet another place to configure a project's artifacts, lots of broken project settings because of conflicts and incompatibility with Maven 2.
Can this be cleaned up in future releases? It is as if the plugin was built with no prior knowledge of Eclipse.
These changes are critical to having a usable tool. Right now I cannot use the plugin for much more than editing JSF pages and building broken deployments.
--
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-1609) enhancement for -> Edit launch configuration properties dialog
by Vitali Yemialyanchyk (JIRA)
enhancement for -> Edit launch configuration properties dialog
---------------------------------------------------------------
Key: JBIDE-1609
URL: http://jira.jboss.com/jira/browse/JBIDE-1609
Project: Tools (JBoss Tools)
Issue Type: Feature Request
Reporter: Vitali Yemialyanchyk
Assigned To: Vitali Yemialyanchyk
Fix For: LATER
Dialog screenshot should be attached.
"Property file" - it has only browse button - should be possibility to create new property file - not only select existed one
it be greate - when the user create property file he get some property file example at least just with comments
http://www.hibernate.org/hib_docs/reference/en/html/session-configuration... as source to find hibernate.properties example.
I'll attach some one and get question ->
>>> what is the preference to setup
>>> hibernate.connection.username, hibernate.connection.password, hibernate.connection.driver_class, hibernate.connection.url, hibernate.dialect
>>> hibernate.properties or hibernate.cfg.xml?
and other
>>> did current version take into account hibernate.properties or just only hibernate.cfg.xml?
the same for "Configuration file" - it is not suitable to get what firstly you should create the file and only then edit or create configuration
--
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