January 2010 - jbosstools-issues - Jboss List Archives

[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, 10 months

2
3
0 / 0

[JBoss JIRA] Created: (JBIDE-873) Code assist does not work for style attribute of jsf tag

by Adrian Mitev (JIRA)

Code assist does not work for style attribute of jsf tag -------------------------------------------------------- Key: JBIDE-873 URL: http://jira.jboss.com/jira/browse/JBIDE-873 Project: JBoss Tools Issue Type: Bug Environment: rhds beta 1, jdk 1.5_0.12, windows xp Reporter: Adrian Mitev Priority: Minor In style attribute of normal html tags code assist works, in jsf tags it doesn't. -- 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

14 years, 10 months

6
12
0 / 0

[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, 10 months

4
21
0 / 0

[JBoss JIRA] Created: (JBDS-838) Find a better home for nightly and archiving of JBDS builds

by Max Rydahl Andersen (JIRA)

Find a better home for nightly and archiving of JBDS builds ----------------------------------------------------------- Key: JBDS-838 URL: https://jira.jboss.org/jira/browse/JBDS-838 Project: JBoss Developer Studio Issue Type: Task Components: Build Affects Versions: 3.0.0.M4 Reporter: Max Rydahl Andersen Assignee: Max Rydahl Andersen Priority: Critical For a while we have been archiving at an QA server located in ATL which is now in PHO but it only gives about 40 kb/s download from europe. Moving it to porkchop would help here since the main site has 80 kb/s and can be mirrored to Brno giving 120 kb/s. End result: 10-24hrs download times gets reduced to 1-2 hrs download for European devs. -- 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, 10 months

5
28
0 / 0

[JBoss JIRA] Created: (JBIDE-5284) Warning related to incorrect Seam project name don't appear

by Aliaksey Nis (JIRA)

Warning related to incorrect Seam project name don't appear ----------------------------------------------------------- Key: JBIDE-5284 URL: https://jira.jboss.org/jira/browse/JBIDE-5284 Project: Tools (JBoss Tools) Issue Type: Bug Components: Seam Affects Versions: 3.1.0.CR1 Environment: WindowsXP SP2 JBoss Tools Version: 3.1.0.CR1 eclipse-SDK-3.5RC3-win32.zip Build id: JBossTools-Update-3.1.0.v200911251807N-H130-RC1 JRE 1.6 Reporter: Aliaksey Nis Priority: Optional Attachments: NoWarningSeam.JPG Related to JBIDE-5223 EXECUTE: New Seam project. EXECUTE: Input name "blahblah+". EXECUTE: Press next few times. ASSERT: At step "Web module" button Next is in disable state, due to incorrect project name. FAILURE: No warning appears. It appears only if you press Back, then Next again. Screenshot attached. -- 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, 10 months

7
10
0 / 0

[JBoss JIRA] Created: (JBIDE-2242) Taglib declaration <%@ taglib uri="" is inserted after DnD tags from Pallete on some XHTML pages in default Seam web project.

by Anton Klimkovich (JIRA)

Taglib declaration <%@ taglib uri="" is inserted after DnD tags from Pallete on some XHTML pages in default Seam web project. ----------------------------------------------------------------------------------------------------------------------------- Key: JBIDE-2242 URL: http://jira.jboss.com/jira/browse/JBIDE-2242 Project: Tools (JBoss Tools) Issue Type: Bug Components: Seam Affects Versions: 2.1.0.GA Reporter: Anton Klimkovich Assigned To: Maxim Areshkau Priority: Minor EXECUTE: Create default Seam project EXECUTE: Open menu.xhtml EXECUTE: Make DnD of JBoss Ajax4jsf tag on the page from Palette. FAILURE: <%@ taglib uri="http://java.sun.com/jsf/html" prefix="h"%> inserted instead of xmlns:h="http://java.sun.com/jsf/html" ASSERT: Seam gen should create xhtml pages with declaration that tells it's a XHTML. (<!DOCTYPE composition PUBLIC "-//W3C//DTD XHTML 1.0 Transitional//EN" "http://www.w3.org/TR/xhtml1/DTD/xhtml1-transitional.dtd">) All pages w/o declaration are attached. -- 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

14 years, 10 months

6
9
0 / 0

[JBoss JIRA] Created: (JBDS-904) JBDS 2.1 GA, JBPM and Seam

by Gary Lamperillo (JIRA)

JBDS 2.1 GA, JBPM and Seam -------------------------- Key: JBDS-904 URL: https://jira.jboss.org/jira/browse/JBDS-904 Project: JBoss Developer Studio Issue Type: Bug Components: integration Affects Versions: 2.1.0 Environment: JBDS 2.1 GA, EAP 5 Beta 2, Seam 2.2 , jBPM Reporter: Gary Lamperillo The jBPM New Process Definition wizard will not create a process in the EAR level. According to the Seam Reference manual, it should go at the EAR level. The Process Definition created by the wizard creates 3 files in a directory. the components.xml can not use the directory for the process definition, you get the following on deploy: Caused by: org.jbpm.jpdl.JpdlException: [[ERROR] resource not found: /seam_drools10_15-ejb/jbpm_to_rules] at org.jbpm.graph.def.ProcessDefinition.parseXmlResource(ProcessDefinition.java:162) at org.jboss.seam.bpm.Jbpm.deployProcess(Jbpm.java:311) at org.jboss.seam.bpm.Jbpm.installProcessDefinitions(Jbpm.java:294) ... 85 more when using a location for the processdefinition.xml in this directory, you will get: Caused by: java.lang.RuntimeException: could not deploy a process definition at org.jboss.seam.bpm.Jbpm.installProcessDefinitions(Jbpm.java:300) at org.jboss.seam.bpm.Jbpm.startup(Jbpm.java:80) at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method) at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:57) at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43) at java.lang.reflect.Method.invoke(Method.java:616) at org.jboss.seam.util.Reflections.invoke(Reflections.java:22) at org.jboss.seam.util.Reflections.invokeAndWrap(Reflections.java:144) at org.jboss.seam.Component.callComponentMethod(Component.java:2249) at org.jboss.seam.Component.callCreateMethod(Component.java:2172) at org.jboss.seam.Component.newInstance(Component.java:2132) ... 75 more Caused by: org.jbpm.jpdl.JpdlException: [[ERROR] resource not found: /seam_drools10_15-ejb/jbpm_to_rules/processdefinition.xml] at org.jbpm.graph.def.ProcessDefinition.parseXmlResource(ProcessDefinition.java:162) at org.jboss.seam.bpm.Jbpm.deployProcess(Jbpm.java:311) at org.jboss.seam.bpm.Jbpm.installProcessDefinitions(Jbpm.java:294) ... 85 more Is the plan for this process definition editor to work with Seam? Is there something missing in this setup? -- 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, 10 months

7
23
0 / 0

[JBoss JIRA] Created: (JBIDE-5720) EAR Libraries in Dynamic Web Project

by Burr Sutter (JIRA)

EAR Libraries in Dynamic Web Project ------------------------------------ Key: JBIDE-5720 URL: https://jira.jboss.org/jira/browse/JBIDE-5720 Project: Tools (JBoss Tools) Issue Type: Feature Request Components: core Environment: jbdevstudio-win32-3.0.0.v201001060655N-H50-CR1 Reporter: Burr Sutter Attachments: EAR_Libraries.jpg Creation of a New Dynamic Web Project adds "EAR Libraries" - that does not make sense because I (the user) am building a WAR and I do not want anything to do with an EAR in this case. -- 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, 10 months

4
11
0 / 0

[JBoss JIRA] Created: (JBIDE-1354) Runtimes should be configurable with respect to what jars to return for certain runtimes

by Max Andersen (JIRA)

Runtimes should be configurable with respect to what jars to return for certain runtimes ---------------------------------------------------------------------------------------- Key: JBIDE-1354 URL: http://jira.jboss.com/jira/browse/JBIDE-1354 Project: JBoss Tools Issue Type: Feature Request Components: JBossAS Reporter: Max Andersen Fix For: 2.1 deploy only runtime could have preferences to control which jars they would actually return for various facets etc. optimally these would actually work on on any of our runtimes and just use variables/clever-defaults depending and allow users to override them if necessary. The user should be able to point to jars in a project, workspace, filesystem, classpath library, maven/ivy dependency even ...etc. -- 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

14 years, 10 months

6
26
0 / 0

[JBoss JIRA] Created: (JBIDE-4127) "Add JSF-Capabilities" adds jsf-facelets.jar which is older than the one in .classpath

by Leiv Hellebo (JIRA)

"Add JSF-Capabilities" adds jsf-facelets.jar which is older than the one in .classpath -------------------------------------------------------------------------------------- Key: JBIDE-4127 URL: https://jira.jboss.org/jira/browse/JBIDE-4127 Project: Tools (JBoss Tools) Issue Type: Bug Components: JSF Affects Versions: 3.0.0.GA Environment: JBDS 2.0.GA Seam 2.1.X Reporter: Leiv Hellebo The Add JSF-Capabilities dialog makes it possible to shoot oneself in the foot: It will happily add jsf-facelets.jar with Implementation-Version: 1.1.11, even if the one mentioned in .classpath has Implementation-Version: 1.1.15.B1 AFAICS, when performing a redirect within a long-running conversation, this makes "DEBUG [org.jboss.seam.contexts.ServletLifecycle] >>> Begin re-initialization" disappear from server.log, and needed context vars are not initialized. I'd file this as an "Improvement", not a "Bug" if it was possible. You may want to say "PEBKAC" to this... -- 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, 10 months

5
7
0 / 0

2026

2025

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

2009

2008

2007

2006

jbosstools-issues January 2010