[JBoss JIRA] Created: (JBIDE-7768) BPEL validation is broken.
by Marek Baluch (JIRA)
BPEL validation is broken.
--------------------------
Key: JBIDE-7768
URL: https://jira.jboss.org/browse/JBIDE-7768
Project: Tools (JBoss Tools)
Issue Type: Bug
Affects Versions: 3.2.0.Beta2
Environment: JBoss Tools Build: 3.2_trunk.2010-11-30_18-42-49-H400
Reporter: Marek Baluch
Assignee: Max Andersen
Priority: Critical
Attachments: broken_validation.jpg
BPEL validator does not mark errors in the process file. This includes missing imports, XML elements which are not well-formed etc. See attached image for more details (see selected area in the editor).
--
This message is automatically generated by JIRA.
-
For more information on JIRA, see: http://www.atlassian.com/software/jira
14 years, 5 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, 5 months
[JBoss JIRA] Created: (JBDS-1637) Finer granularity structure of JBDS update site
by Jiri Peterka (JIRA)
Finer granularity structure of JBDS update site
-----------------------------------------------
Key: JBDS-1637
URL: https://issues.jboss.org/browse/JBDS-1637
Project: Developer Studio (JBoss Developer Studio)
Issue Type: Feature Request
Components: updatesite
Affects Versions: 4.0.0.GA
Environment: JBDS 4.x
Reporter: Jiri Peterka
Currently JBDS 4 update site contain one big feature containing full JBDS 4.0 updates
This should be granular providing detailed tree with particular sub-features
Current limits:
1. During update there is no detailed overview what will be updated
2. Check for update doesn't work for updates with fixes that are added as new features in the list (currently Teiid tools)
I would like to see this in JBDS 5.x if not in JBDS 4.x
--
This message is automatically generated by JIRA.
For more information on JIRA, see: http://www.atlassian.com/software/jira
14 years, 5 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, 5 months
[JBoss JIRA] Created: (JBIDE-6537) Helios support for JBT v3.1.1
by Darryl Miles (JIRA)
Helios support for JBT v3.1.1
-----------------------------
Key: JBIDE-6537
URL: https://jira.jboss.org/browse/JBIDE-6537
Project: Tools (JBoss Tools)
Issue Type: Task
Components: Hibernate, Seam
Affects Versions: 3.1.1
Reporter: Darryl Miles
Assignee: Max Rydahl Andersen
Both the "Hibernate Tools" and "Seam Tools" for JBT v3.1.1 have too narrow version requirements for com.ibm.icu to be compatible with Helios.
Helios comes with com.ibm.icu v4.2.1
Currently the version requirements are set to [3.4.4,4.1.0) so this should be changed at a minimum to [3.4.4,4.3.0) to allow both these JBT components to install on top of Helios.
However you should consider using an even wider version width of [3.4.4,5) since it is accepted practise that minor version increments are backwardly compatible and a major version change is potentially API breaking. This means that generally JBT should (and is expected to) work on all future versions of com.ibm.icu up until version 5 is released.
--
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