Some suggestions on the occasion of viewing styles of <h:column> in VPE
------------------------------------------------------------------------
Key: JBIDE-2815
URL: https://jira.jboss.org/jira/browse/JBIDE-2815
Project: Tools (JBoss Tools)
Issue Type: Task
Components: Visual Page Editor
Affects Versions: 3.0.0.alpha
Reporter: Andrei Scherbovich
Assignee: Maxim Areshkau
Priority: Optional
Attachments: booksale.rar
It would be nice to view changing styles of <h:column> using attributes "headerClass", "footerClass" in VPE stright away with changing these attributes on the page
--
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
Problems with Substituted EL expressions
----------------------------------------
Key: JBIDE-2828
URL: https://jira.jboss.org/jira/browse/JBIDE-2828
Project: Tools (JBoss Tools)
Issue Type: Bug
Components: Visual Page Editor
Affects Versions: 3.0.0.alpha
Reporter: Andrei Scherbovich
Assignee: Maxim Areshkau
STEP 1: Open Page Designe Options
STEP 2: Add any EL Value separated coma or dot with coma
STEP 3: Add any Value separated coma or dot with coma
STEP 4: See screenshot -1
STEP 5: Press Finish and then OK
STEP 6: Look up again Page Designe Options
STEP 7: See results in screenshot-2
--
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
Adding custom (Richfaces) capabilities lead to error in web.xml
---------------------------------------------------------------
Key: JBDS-404
URL: https://jira.jboss.org/jira/browse/JBDS-404
Project: Developer Studio
Issue Type: Bug
Affects Versions: 2.0.0.alpha
Reporter: Nick Belaevski
Assignee: Max Rydahl Andersen
1. Create new Maven web application project and add it to Eclipse
2. Add JSF capabilities using default settings -> FacesServlet is added as "Faces Config" into web.xml
3. Add custom Richfaces capabilities -> error marker "Attribute servlet-name references to Faces Servlet that is not a servlet" appears. Changing filter-mapping to "Faces Config" resolves the problem.
--
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
Provide seam variables to WTP JSF code completion/editor
--------------------------------------------------------
Key: JBIDE-1984
URL: http://jira.jboss.com/jira/browse/JBIDE-1984
Project: Tools (JBoss Tools)
Issue Type: Feature Request
Components: Seam
Affects Versions: 2.1.0.beta1
Reporter: Max Andersen
Fix For: 2.2.x
we should look into implementing a proper JSF variable resolver for eclipse jst.jsf instead of the current one where we just return null_symbol to make it stop "lying" about errors.
--
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
Both 'org.jboss.tools.smooks.model' and 'org.jboss.tools.smooks.ui' register a package for 'http://www.milyn.org/xsd/smooks-1.0.xsd' warning message is occured in the latest JBoss Tools build.
-------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------
Key: JBIDE-2754
URL: https://jira.jboss.org/jira/browse/JBIDE-2754
Project: Tools (JBoss Tools)
Issue Type: Bug
Components: smooks
Affects Versions: 3.0.0.beta1
Environment: JBossTools-200809100010-nightly-ALL
Reporter: Anton Klimkovich
Priority: Minor
FAILURE: warning message is occured when run JBDS.
Both 'org.jboss.tools.smooks.model' and 'org.jboss.tools.smooks.ui' register a package for 'http://www.milyn.org/xsd/smooks-1.0.xsd'
An exception stack trace is not available.
--
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
Ensure that correct provider name appears for plug-ins
------------------------------------------------------
Key: JBIDE-3117
URL: https://jira.jboss.org/jira/browse/JBIDE-3117
Project: Tools (JBoss Tools)
Issue Type: Bug
Components: smooks
Affects Versions: 3.0.0.cr1
Environment: JBossTools-3.0.0.CR1-N200811050757-ALL-linux-gtk
Reporter: John Graham
Assignee: Xue Peng
Fix For: 3.0.0.cr1
Make sure that all the Smooks plug-in providers are set to "JBoss, a division of Red Hat"
--
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
.smooks.graph file contains absolute file path
----------------------------------------------
Key: JBIDE-2995
URL: https://jira.jboss.org/jira/browse/JBIDE-2995
Project: Tools (JBoss Tools)
Issue Type: Bug
Components: smooks
Reporter: Tom Fennelly
Assignee: Xue Peng
Priority: Minor
Fix For: 3.0.0.cr1
The "sourceDataPath" in the .smooks.graph file is absolute even if you select a workspace relative file. This will break project portability i.e. I can't zip up my project and email to you, right?
--
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
BPMN -> jPDL wizard should filter selections
--------------------------------------------
Key: JBIDE-3108
URL: https://jira.jboss.org/jira/browse/JBIDE-3108
Project: Tools (JBoss Tools)
Issue Type: Bug
Components: jbpm
Affects Versions: 3.0.0.cr1
Environment: JBossTools-3.0.0.CR1-N200811050757-ALL-linux-gtk
Reporter: John Graham
Assignee: Feng Qian
Fix For: 3.0.0.cr1
The BPMN resource selection page in the export wizard should filter:
1. Closed projects
2. Only BPMN resources
3. Only folders/projects with BPMN resources in them
--
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
BPMN -> jPDL wizard should filter target location selections
------------------------------------------------------------
Key: JBIDE-3110
URL: https://jira.jboss.org/jira/browse/JBIDE-3110
Project: Tools (JBoss Tools)
Issue Type: Bug
Components: jbpm
Affects Versions: 3.0.0.cr1
Environment: JBossTools-3.0.0.CR1-N200811050757-ALL-linux-gtk
Reporter: John Graham
Assignee: Feng Qian
The page for selecting target locations should filter:
1. Closed projects
2. Only show IContainer objects (that is, IProject and IFolder locations)
--
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
BPMN -> jPDL wizard should select available pools by default
------------------------------------------------------------
Key: JBIDE-3109
URL: https://jira.jboss.org/jira/browse/JBIDE-3109
Project: Tools (JBoss Tools)
Issue Type: Bug
Components: jbpm
Affects Versions: 3.0.0.cr1
Environment: JBossTools-3.0.0.CR1-N200811050757-ALL-linux-gtk
Reporter: John Graham
Assignee: Feng Qian
Priority: Minor
Fix For: 3.0.0.cr1
In the pool selection page of the wizard, all of the available pools should be selected by default and the "Select All" button should be disabled. If the user then deselects a pool or does "Deselect All", then the "Select All" button should be enabled.
--
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