December 2008 - jbosstools-issues

[JBoss JIRA] Created: (JBIDE-2509) Migrate Seam rg.jboss.tools.seam.ui.SeamActionSet and org.eclipse.search.seamSearchActionSet to org.eclipse.ui.menus extension point

by Denis Golovin (JIRA)

Migrate Seam rg.jboss.tools.seam.ui.SeamActionSet and org.eclipse.search.seamSearchActionSet to org.eclipse.ui.menus extension point ------------------------------------------------------------------------------------------------------------------------------------ Key: JBIDE-2509 URL: http://jira.jboss.com/jira/browse/JBIDE-2509 Project: Tools (JBoss Tools) Issue Type: Sub-task Reporter: Denis Golovin -- 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

15 years, 6 months

4
11
0 / 0

[JBoss JIRA] Created: (JBIDE-3471) if a subprocess have only a default task, then there are not gpd.xml for this subprocess in generated jpdl folder.

by Feng Qian (JIRA)

if a subprocess have only a default task, then there are not gpd.xml for this subprocess in generated jpdl folder. ------------------------------------------------------------------------------------------------------------------ Key: JBIDE-3471 URL: https://jira.jboss.org/jira/browse/JBIDE-3471 Project: Tools (JBoss Tools) Issue Type: Bug Components: jbpm Affects Versions: 3.0.0.cr1 Reporter: Feng Qian Assignee: Feng Qian Priority: Blocker Fix For: LATER -- 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

15 years, 6 months

1
1
0 / 0

[JBoss JIRA] Deleted: (JBIDE-3470) CA doesn't work for the project, which uses different named faces-configs

by Yura Zhishko (JIRA)

[ https://jira.jboss.org/jira/browse/JBIDE-3470?page=com.atlassian.jira.plu... ] Yura Zhishko deleted JBIDE-3470: -------------------------------- > CA doesn't work for the project, which uses different named faces-configs > ------------------------------------------------------------------------- > > Key: JBIDE-3470 > URL: https://jira.jboss.org/jira/browse/JBIDE-3470 > Project: Tools (JBoss Tools) > Issue Type: Bug > Reporter: Yura Zhishko > Assignee: Alexey Kazakov > > 1) Import attached project > 2) Go to pages -> calendar -> calendar.jsp > 3) Call CA for weekDayLabelsShort="#{}" attribute > ASSERT: calendarBean line should be visible > RESULT: there is no such line in CA window > 4) Move > > <managed-bean> > <managed-bean-name>calendarBean</managed-bean-name> > <managed-bean-class>calendar.calendar</managed-bean-class> > <managed-bean-scope>request</managed-bean-scope> > </managed-bean> > from faces-calendar.xml to faces-config.xml > 5) Repeat steps 1-3 > ASSERT: everything works OK -- 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

15 years, 6 months

1
0
0 / 0

[JBoss JIRA] Created: (JBIDE-3470) CA doesn't work for the project, which uses different named faces-configs

by Yura Zhishko (JIRA)

CA doesn't work for the project, which uses different named faces-configs ------------------------------------------------------------------------- Key: JBIDE-3470 URL: https://jira.jboss.org/jira/browse/JBIDE-3470 Project: Tools (JBoss Tools) Issue Type: Bug Components: jsp/jsf/xml source editing Affects Versions: 3.0.0.cr1 Reporter: Yura Zhishko Assignee: Alexey Kazakov 1) Import attached project 2) Go to pages -> calendar -> calendar.jsp 3) Call CA for weekDayLabelsShort="#{}" attribute ASSERT: calendarBean line should be visible RESULT: there is no such line in CA window 4) Move <managed-bean> <managed-bean-name>calendarBean</managed-bean-name> <managed-bean-class>calendar.calendar</managed-bean-class> <managed-bean-scope>request</managed-bean-scope> </managed-bean> from faces-calendar.xml to faces-config.xml 5) Repeat steps 1-3 ASSERT: everything works OK -- 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

15 years, 6 months

1
0
0 / 0

[JBoss JIRA] Created: (JBIDE-3466) There is an error message on pages.xml editor for some valid pages.xml for Seam 2.1: Editor model doesn't support child element rule of navigation.

by Alexey Kazakov (JIRA)

There is an error message on pages.xml editor for some valid pages.xml for Seam 2.1: Editor model doesn't support child element rule of navigation. --------------------------------------------------------------------------------------------------------------------------------------------------- Key: JBIDE-3466 URL: https://jira.jboss.org/jira/browse/JBIDE-3466 Project: Tools (JBoss Tools) Issue Type: Bug Components: Seam Affects Versions: 3.0.0.cr1 Reporter: Alexey Kazakov Assignee: Viacheslav Kabanovich Fix For: 3.0.0.CR2 Here is a valid pages.xml: <?xml version="1.0" encoding="UTF-8"?> <pages xmlns="http://jboss.com/products/seam/pages" xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance" xsi:schemaLocation="http://jboss.com/products/seam/pages http://jboss.com/products/seam/pages-2.1.xsd" no-conversation-view-id="/home.xhtml" login-view-id="/login.xhtml"> <page view-id="/admin/post.xhtml"> <navigation from-action="#{postHome.update}"> <end-conversation/> <rule if-outcome="updated"> <redirect view-id="/home.xhtml"/> </rule> </navigation> </page> </pages> But pages.xml editor shows an error for such pages. See screenshot. This xml is not correct for pages-2.0.xsd but it is correct for pages-2.1.xsd. -- 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

15 years, 6 months

2
2
0 / 0

[JBoss JIRA] Created: (JBDS-501) Spaces in Project Name when generate Package Names

by Svetlana mukhina (JIRA)

Spaces in Project Name when generate Package Names -------------------------------------------------- Key: JBDS-501 URL: https://jira.jboss.org/jira/browse/JBDS-501 Project: Developer Studio Issue Type: Task Components: Doc - Seam Affects Versions: 2.0.0.beta1 Reporter: Svetlana mukhina Assignee: Svetlana mukhina Fix For: 2.0.0.cr1 Check that in our samples, screens there no space in Package names, correct if found Make a not that this should be avoid -- 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

15 years, 6 months

2
6
0 / 0

[JBoss JIRA] Created: (JBIDE-3469) change the bpmn -> jpdl wizard page logic to support to generate jpdl files directly without any settings

by Feng Qian (JIRA)

change the bpmn -> jpdl wizard page logic to support to generate jpdl files directly without any settings --------------------------------------------------------------------------------------------------------- Key: JBIDE-3469 URL: https://jira.jboss.org/jira/browse/JBIDE-3469 Project: Tools (JBoss Tools) Issue Type: Bug Components: jbpm Affects Versions: 3.0.0.cr1 Reporter: Feng Qian Assignee: Feng Qian Fix For: LATER -- 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

15 years, 6 months

1
1
0 / 0

[JBoss JIRA] Created: (JBIDE-3447) change the default value of jpdl node name during bpmn -> jpdl

by Feng Qian (JIRA)

change the default value of jpdl node name during bpmn -> jpdl -------------------------------------------------------------- Key: JBIDE-3447 URL: https://jira.jboss.org/jira/browse/JBIDE-3447 Project: Tools (JBoss Tools) Issue Type: Bug Components: jbpm Affects Versions: 3.0.0.cr1 Reporter: Feng Qian Assignee: Feng Qian Priority: Minor Fix For: LATER -- 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

15 years, 6 months

1
3
0 / 0

[JBoss JIRA] Created: (JBDS-417) Wierd pathes on screenshots

by Svetlana mukhina (JIRA)

Wierd pathes on screenshots ---------------------------- Key: JBDS-417 URL: https://jira.jboss.org/jira/browse/JBDS-417 Project: Developer Studio Issue Type: Task Components: documentation Affects Versions: 1.1.0.GA Reporter: Svetlana mukhina Assignee: Svetlana mukhina Priority: Minor Fix For: 2.0.0.alpha Make sure that paths on screens don't contain any personal names and display real paths to resources (see also the linked issues) -- 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

15 years, 6 months

3
21
0 / 0

[JBoss JIRA] Created: (JBIDE-3438) errors updating JB Tools CR1 features to newer versions

by Nick Boldt (JIRA)

errors updating JB Tools CR1 features to newer versions ------------------------------------------------------- Key: JBIDE-3438 URL: https://jira.jboss.org/jira/browse/JBIDE-3438 Project: Tools (JBoss Tools) Issue Type: Quality Risk Reporter: Nick Boldt Assignee: Max Rydahl Andersen 1. Install Eclipse 3.4.1 JEE bundle. 2. Unpack JBossTools-3.0.0.CR1-R200812191611-ALL-linux-gtk.zip into eclipse/dropins 3. Start Eclipse. Notice that BIRT feature is disabled. 4. fire up Help > Software Updates... > Available Software > Manage Sites > enable BIRT 2.3 site 5. add http://download.jboss.org/jbosstools/updates/nightly/trunk/ 6. Update BIRT feature to newer version from nightly update site. 7. On restart, BIRT feature is enabled. 8. Now, fire up Help > Software Updates... > Update... 9. (system freezes briefly while computation is done) 10. checking osgi console log, we see the attached file, suggesting that something in JBT (perhaps AS?) depends on WTP WST version 2.x, not 3.x, which in turn causes p2 to be unable to find a solution where it can install EMF [2.2.0,2.4.0), since the JEE bundle (step 1 above) already contains EMF 2.4.1. -- 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

15 years, 6 months

3
7
0 / 0

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

2009

2008

2007

2006

jbosstools-issues December 2008