[JBoss JIRA] Created: (JBIDE-5728) Enhance OpenOn for the name param of some JSF 2.0 tags (add JAR files and i18n support)
by Yahor Radtsevich (JIRA)
Enhance OpenOn for the name param of some JSF 2.0 tags (add JAR files and i18n support)
----------------------------------------------------------------------------------------
Key: JBIDE-5728
URL: https://jira.jboss.org/jira/browse/JBIDE-5728
Project: Tools (JBoss Tools)
Issue Type: Feature Request
Components: jsp/jsf/xml source editing
Affects Versions: 3.1.0.CR1
Reporter: Yahor Radtsevich
Assignee: Alexey Kazakov
Fix For: 3.2.next
JSF 2.0 allows the following tags to refer to the resources:
h:outputStylesheet name="RESOURCE_NAME"
h:outputScript name="RESOURCE_NAME"
h:graphicImage name="RESOURCE_NAME"
This is quotation from the JSF 2.0 Documentation (http://java.sun.com/javaee/6/docs/api/javax/faces/application/ResourceHan... ):
The default implementation must support packaging resources in the web application root under the path
resources/<resourceIdentifier>
relative to the web app root.
For the default implementation, resources packaged in the classpath must reside under the JAR entry name
META-INF/resources/<resourceIdentifier>
<resourceIdentifier> consists of several segments, specified as follows.
[localePrefix/][libraryName/][libraryVersion/]resourceName[/resourceVersion]
The HTML Editor supports OpenOn only for the resources which are placed in WEB_ROOT/resources/[libraryName/]resourceName .
There is no support for:
1. JAR files
2. Locale
3. Library version
4. Resource version
The support should be added.
Also see: JBIDE-5382.
--
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators: https://jira.jboss.org/jira/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira
14 years, 6 months
[JBoss JIRA] Created: (JBIDE-3795) Hibernate Config view cannot create JPA based configuration with @GeneratedValue using a @GenericGenerator
by Bob Thule (JIRA)
Hibernate Config view cannot create JPA based configuration with @GeneratedValue using a @GenericGenerator
----------------------------------------------------------------------------------------------------------
Key: JBIDE-3795
URL: https://jira.jboss.org/jira/browse/JBIDE-3795
Project: Tools (JBoss Tools)
Issue Type: Bug
Components: Hibernate
Affects Versions: 3.0.0.CR2
Environment: Hibernate Tools 3.2.4.GA-N200902101801, Java Persistence API Tools 2.1.0.v200812180210
Reporter: Bob Thule
This may be related to issue JBIDE-3636. https://jira.jboss.org/jira/browse/JBIDE-3636
With a @GenericGenerator declared as:
@GenericGenerator(name = "SeqBase",... ) //either in package-info.java or on the class
and used with:
@GeneratedValue(generator = "SeqBase") private Long id;
when in the "Hibernate Config" view and the hibernate configuration is trying to be displayed or rebuilt, Eclipse gives the following exception:
org.hibernate.console.HibernateConsoleRuntimeException: Could not create JPA based Configuration
Could not create JPA based Configuration
<No message>
java.lang.reflect.InvocationTargetException
java.lang.reflect.InvocationTargetException: <no message>
java.lang.reflect.InvocationTargetException
javax.persistence.PersistenceException: org.hibernate.AnnotationException: Unknown Id.generator: SeqBase
org.hibernate.AnnotationException: Unknown Id.generator: SeqBase
org.hibernate.AnnotationException: Unknown Id.generator: SeqBase
Unknown Id.generator: SeqBase
--
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators: https://jira.jboss.org/jira/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira
14 years, 6 months
[JBoss JIRA] Created: (JBDS-1235) 3rd party certification
by Max Rydahl Andersen (JIRA)
3rd party certification
-----------------------
Key: JBDS-1235
URL: https://jira.jboss.org/browse/JBDS-1235
Project: Developer Studio (JBoss Developer Studio)
Issue Type: Feature Request
Components: Requirements
Reporter: Max Rydahl Andersen
Priority: Blocker
Fix For: 4.0.0.GA
We should define what kind of certifications we want and then certify 3rd party plugins with JBDS
Certifiaction could for example be for Groovy Plugin we know it installs, but beyond that there aren't any guarantees.
For m2eclipse it would be the same with respect to installation but that we support the maven integration plugins and provide fixes for that - but not m2eclipse it self.
--
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators: https://jira.jboss.org/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira
14 years, 6 months