[JBoss JIRA] Created: (JBIDE-9310) JBoss tools does not take AS 6's jsf.deployer into account
by arjan tijms (JIRA)
JBoss tools does not take AS 6's jsf.deployer into account
----------------------------------------------------------
Key: JBIDE-9310
URL: https://issues.jboss.org/browse/JBIDE-9310
Project: Tools (JBoss Tools)
Issue Type: Bug
Reporter: arjan tijms
In JBoss AS 6, one can change which JSF implementation JBoss AS uses by editing /deployers/jsf.deployer/META-INF/jsf-integration-deployer-jboss-beans.xml. JBoss bundles Mojarra 1.2, 2.0 and MyFaces 2.0 by default.
However, if one changes this, JBoss tools keeps putting the two hardcoded libs in /deployers/jsf.deployer/Mojarra-2.0/jsf-libs on the IDE's lookup path. This means that stepping through JSF source code is totally broken then.
A workaround is to copy the libs from the other configuration to /deployers/jsf.deployer/Mojarra-2.0/jsf-libs and rename them to jsf-api-2.0.3-b05.jar and jsf-impl-2.0.3-b05.jar. This works, but there is something unsettling of having e.g. the 2.1.2 libs called 2.0.3 just for the sake of the ability to debug.
--
This message is automatically generated by JIRA.
For more information on JIRA, see: http://www.atlassian.com/software/jira
13 years, 11 months
[JBoss JIRA] Created: (JBIDE-9375) JPA: validate @ForeignKey inverseName for ManyToMany mapping
by Dmitry Geraskov (JIRA)
JPA: validate @ForeignKey inverseName for ManyToMany mapping
------------------------------------------------------------
Key: JBIDE-9375
URL: https://issues.jboss.org/browse/JBIDE-9375
Project: Tools (JBoss Tools)
Issue Type: Feature Request
Components: Hibernate
Affects Versions: 3.3.0.M2
Reporter: Dmitry Geraskov
Assignee: Dmitry Geraskov
Fix For: 3.3.0.M3
@ForignKey annotations can be used in OneToMany, ManyToOne, and OneToOne
relationships, ManyToMany relationships.
Inverse name should be validated only in ManyToMany relationships at owner side (not owner side has mappedBy attribute).
Test case:
1. Create JPA project with Hibernate platform
2. Create 2 Entities with many to many reference
3. Add @ForeignKey(name="x", inverseName="") to both sides
Check that error appeared and only on the owning size.
--
This message is automatically generated by JIRA.
For more information on JIRA, see: http://www.atlassian.com/software/jira
13 years, 11 months
[JBoss JIRA] Created: (JBIDE-9510) Add openshift express capabilities to AS7 server adapter
by Andre Dietisheim (JIRA)
Add openshift express capabilities to AS7 server adapter
--------------------------------------------------------
Key: JBIDE-9510
URL: https://issues.jboss.org/browse/JBIDE-9510
Project: Tools (JBoss Tools)
Issue Type: Feature Request
Components: JBossAS
Affects Versions: 3.3.0.M3
Reporter: Andre Dietisheim
Assignee: Andre Dietisheim
Fix For: 3.3.0.M3
Bascially you can already use eclipse and the AS7 server adapter to work with Openshift Express. The whole workflow is pretty much rough though and we need to improve that. We want to add ease of use so that deploying to Openshift Express gets as easy as possible.
--
This message is automatically generated by JIRA.
For more information on JIRA, see: http://www.atlassian.com/software/jira
13 years, 11 months
[JBoss JIRA] Created: (JBIDE-9402) Load CDI extensions dynamically
by Alexey Kazakov (JIRA)
Load CDI extensions dynamically
-------------------------------
Key: JBIDE-9402
URL: https://issues.jboss.org/browse/JBIDE-9402
Project: Tools (JBoss Tools)
Issue Type: Task
Components: cdi (jsr-299)
Affects Versions: 3.3.0.M3
Reporter: Alexey Kazakov
Assignee: Viacheslav Kabanovich
Fix For: 3.3.0.M3
We need to have something like {code}public <T extends IFeature> Set<T> getFeatures(Class<T> cls);{code} in CDIExtensionManager to get a set of all the available features registered for particular CDI extensions.
--
This message is automatically generated by JIRA.
For more information on JIRA, see: http://www.atlassian.com/software/jira
13 years, 11 months