[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, 9 months
[JBoss JIRA] Created: (JBDS-1710) Exception creating web.xml when using the wizard to generate a web service.
by Mustafa Musaji (JIRA)
Exception creating web.xml when using the wizard to generate a web service.
---------------------------------------------------------------------------
Key: JBDS-1710
URL: https://issues.jboss.org/browse/JBDS-1710
Project: Developer Studio (JBoss Developer Studio)
Issue Type: Bug
Components: runtime
Affects Versions: 4.0.0.GA, 3.0.1.GA
Reporter: Mustafa Musaji
When using the attached WSDL to create a new web service an exception is caught with the CoreException: parsing WSDL. However, the client stubs are generated just fine and the only issue seems to be JBoss Tools problems. There are a number of warnings but there is another WSDL attached which also generates warnings but does not fail when creating the web.xml.
--
This message is automatically generated by JIRA.
For more information on JIRA, see: http://www.atlassian.com/software/jira
14 years, 9 months
[JBoss JIRA] Created: (JBIDE-9304) Clean up BPEL Example Projects
by Robert (Bob) Brodt (JIRA)
Clean up BPEL Example Projects
------------------------------
Key: JBIDE-9304
URL: https://issues.jboss.org/browse/JBIDE-9304
Project: Tools (JBoss Tools)
Issue Type: Bug
Components: bpel
Affects Versions: 3.2.1.CR1
Reporter: Robert (Bob) Brodt
Assignee: Feng Qian
Priority: Minor
Fix For: LATER
Many of the BPEL projects create empty folders that don't look like they are used. For example, the "HelloWorld" project contains a "HelloWorld" folder.
Also, the BPEL editor automatically adds the "bpel" namespace prefix to a file if it does not already have this prefix defined. This causes the editor to show as "dirty" the first time it is opened, even though it hasn't been touched (see https://issues.jboss.org/browse/JBIDE-9303). This is a different problem, but for now we should add this prefix to all of the examples, as a quick fix.
--
This message is automatically generated by JIRA.
For more information on JIRA, see: http://www.atlassian.com/software/jira
14 years, 9 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, 9 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, 9 months