November 2009 - jbosstools-issues

[JBoss JIRA] Created: (JBIDE-3695) We need to add properties to Context Assistant from javax.faces.model.DataModel

by Daniel Azarov (JIRA)

We need to add properties to Context Assistant from javax.faces.model.DataModel ------------------------------------------------------------------------------- Key: JBIDE-3695 URL: https://jira.jboss.org/jira/browse/JBIDE-3695 Project: Tools (JBoss Tools) Issue Type: Feature Request Components: Seam Affects Versions: 3.0.0.CR2 Reporter: Daniel Azarov Assignee: Alexey Kazakov We need to add next properties: rowAvailable, rowIndex, rowData, wrappedData Test case: 1. Start Studio 2. Select Help->Project Exaples.. 3. Select Seam DVD Store Example and press Finish button 4. Open WebContent/showorders.xhtml Assert: There are no error markers for properties from DataModel -- 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, 11 months

4
10
0 / 0

[JBoss JIRA] Created: (JBIDE-2630) Create minimal Seam project (no DB), or/and add Seam facet with minimal impact (no DB)

by Francisco Jose Peredo Noguez (JIRA)

Create minimal Seam project (no DB), or/and add Seam facet with minimal impact (no DB) -------------------------------------------------------------------------------------- Key: JBIDE-2630 URL: https://jira.jboss.org/jira/browse/JBIDE-2630 Project: Tools (JBoss Tools) Issue Type: Feature Request Affects Versions: 2.1.2 Reporter: Francisco Jose Peredo Noguez Currently, to create a Seam project, one needs to configure a database connection, but Seam can be used in other contexts that maybe do not need a database connection, or that may not need to use JPA (for example a Web applications that is acting as the client of a WebService, or that needs to interact with a legacy database using plain JDBC or Ibatis, or to create an small example project. I find the need to specify the database connection cumbersome, specially if I just want to create a small "test project" to try to solve an small non database related problem in isolation (or to demonstrate Seam capabilities beyond its integration with JPA). I think it should be possible to create a Minimal Seam project using the wizard, one that does not ask for a database connection, and does not need to use a database connection. It should also be possible to add the Seam facet to a project with minimal impact to the project (minimal web.xml alteration for support for JSF, or perhaps only do that if JavaServer Faces facet is selected, copying of minimal required libs, and a components.xml with literally everything disabled (specially anything database related)). -- 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, 11 months

3
14
0 / 0

[JBoss JIRA] Created: (JBIDE-5013) Don't remove "\" from property file

by Krasimir Goutcev (JIRA)

Don't remove "\" from property file ----------------------------------- Key: JBIDE-5013 URL: https://jira.jboss.org/jira/browse/JBIDE-5013 Project: Tools (JBoss Tools) Issue Type: Bug Components: Visual Page Editor core Affects Versions: 3.1.0.M4 Reporter: Krasimir Goutcev Attachments: prop1.png, prop2.png Here is an example of the contents of a properties file: # a comment ! a comment a = a string b = a string with escape sequences \t \n \r \\ \" \' \ (space) \u0123 c = a string with a continuation line \ continuation line Now if you put something like key = a string with a continuation line \ continuation line next time when you open file will see: key = a string with a continuation line continuation line Second: Now "Add property" is :see pic1 why not to be: see pic2 -- 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, 11 months

3
8
0 / 0

[JBoss JIRA] Created: (JBDS-902) ESB transformation action property "smooksConfig" has a custom panel

by Svetlana mukhina (JIRA)

ESB transformation action property "smooksConfig" has a custom panel -------------------------------------------------------------------- Key: JBDS-902 URL: https://jira.jboss.org/jira/browse/JBDS-902 Project: JBoss Developer Studio Issue Type: Task Components: Doc - ESB Affects Versions: 2.1.0 Reporter: Svetlana mukhina Assignee: Svetlana mukhina Fix For: 2.1.0-doc check screens, make sure panel is mentioned in esb guide -- 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, 11 months

4
8
0 / 0

[JBoss JIRA] Created: (JBIDE-5036) JDT Internal Error connected with JBossAS while java method renaming

by Daniel Azarov (JIRA)

JDT Internal Error connected with JBossAS while java method renaming --------------------------------------------------------------------- Key: JBIDE-5036 URL: https://jira.jboss.org/jira/browse/JBIDE-5036 Project: Tools (JBoss Tools) Issue Type: Bug Components: JBossAS Affects Versions: 3.1.0.M3 Reporter: Daniel Azarov Assignee: Rob Stryker Testcase: 1. Create jsf KickStart project 2. Open \JavaSource\demo\User.java in java editor 3. Select getName() method name 4. Mouse right click 5. Select Refactor->Rename 6. Type new name, "getName2" for instance 7. Press Enter FAIL: java.lang.reflect.InvocationTargetException at org.eclipse.ltk.internal.ui.refactoring.WorkbenchRunnableAdapter.run(WorkbenchRunnableAdapter.java:91) at org.eclipse.jface.operation.ModalContext$ModalContextThread.run(ModalContext.java:121) Caused by: Java Model Exception: Java Model Status [1.0.com.sun.tools.xjc.reader.xmlschema.bindinfo [in C:\JBoss\jboss-4.2.0.GA\client\jaxb-xjc.jar] does not exist] at org.eclipse.jdt.internal.core.JavaElement.newJavaModelException(JavaElement.java:502) at org.eclipse.jdt.internal.core.Openable.generateInfos(Openable.java:246) at org.eclipse.jdt.internal.core.Openable.openAncestors(Openable.java:504) at org.eclipse.jdt.internal.core.Openable.generateInfos(Openable.java:240) at org.eclipse.jdt.internal.core.SourceRefElement.generateInfos(SourceRefElement.java:107) at org.eclipse.jdt.internal.core.JavaElement.openWhenClosed(JavaElement.java:515) at org.eclipse.jdt.internal.core.JavaElement.getElementInfo(JavaElement.java:252) at org.eclipse.jdt.internal.core.JavaElement.getElementInfo(JavaElement.java:238) at org.eclipse.jdt.internal.core.BinaryMethod.getFlags(BinaryMethod.java:113) at org.eclipse.jdt.internal.corext.util.JavaModelUtil.isVisibleInHierarchy(JavaModelUtil.java:240) at org.eclipse.jdt.internal.corext.refactoring.rename.RippleMethodFinder2.uniteWithSupertypes(RippleMethodFinder2.java:407) at org.eclipse.jdt.internal.corext.refactoring.rename.RippleMethodFinder2.uniteWithSupertypes(RippleMethodFinder2.java:403) at org.eclipse.jdt.internal.corext.refactoring.rename.RippleMethodFinder2.createUnionFind(RippleMethodFinder2.java:384) at org.eclipse.jdt.internal.corext.refactoring.rename.RippleMethodFinder2.findAllRippleMethods(RippleMethodFinder2.java:196) at org.eclipse.jdt.internal.corext.refactoring.rename.RippleMethodFinder2.getAllRippleMethods(RippleMethodFinder2.java:168) at org.eclipse.jdt.internal.corext.refactoring.rename.RippleMethodFinder2.getRelatedMethods(RippleMethodFinder2.java:161) at org.eclipse.jdt.internal.corext.refactoring.rename.RenameMethodProcessor.initializeMethodsToRename(RenameMethodProcessor.java:236) at org.eclipse.jdt.internal.corext.refactoring.rename.RenameMethodProcessor.doCheckFinalConditions(RenameMethodProcessor.java:360) at org.eclipse.jdt.internal.corext.refactoring.rename.RenameVirtualMethodProcessor.doCheckFinalConditions(RenameVirtualMethodProcessor.java:143) at org.eclipse.jdt.internal.corext.refactoring.rename.JavaRenameProcessor.checkFinalConditions(JavaRenameProcessor.java:46) at org.eclipse.ltk.core.refactoring.participants.ProcessorBasedRefactoring.checkFinalConditions(ProcessorBasedRefactoring.java:224) at org.eclipse.ltk.core.refactoring.CheckConditionsOperation.run(CheckConditionsOperation.java:85) at org.eclipse.ltk.core.refactoring.CreateChangeOperation.run(CreateChangeOperation.java:121) at org.eclipse.core.internal.resources.Workspace.run(Workspace.java:1800) at org.eclipse.ltk.internal.ui.refactoring.WorkbenchRunnableAdapter.run(WorkbenchRunnableAdapter.java:87) ... 1 more Root exception: Java Model Exception: Java Model Status [1.0.com.sun.tools.xjc.reader.xmlschema.bindinfo [in C:\JBoss\jboss-4.2.0.GA\client\jaxb-xjc.jar] does not exist] at org.eclipse.jdt.internal.core.JavaElement.newJavaModelException(JavaElement.java:502) at org.eclipse.jdt.internal.core.Openable.generateInfos(Openable.java:246) at org.eclipse.jdt.internal.core.Openable.openAncestors(Openable.java:504) at org.eclipse.jdt.internal.core.Openable.generateInfos(Openable.java:240) at org.eclipse.jdt.internal.core.SourceRefElement.generateInfos(SourceRefElement.java:107) at org.eclipse.jdt.internal.core.JavaElement.openWhenClosed(JavaElement.java:515) at org.eclipse.jdt.internal.core.JavaElement.getElementInfo(JavaElement.java:252) at org.eclipse.jdt.internal.core.JavaElement.getElementInfo(JavaElement.java:238) at org.eclipse.jdt.internal.core.BinaryMethod.getFlags(BinaryMethod.java:113) at org.eclipse.jdt.internal.corext.util.JavaModelUtil.isVisibleInHierarchy(JavaModelUtil.java:240) at org.eclipse.jdt.internal.corext.refactoring.rename.RippleMethodFinder2.uniteWithSupertypes(RippleMethodFinder2.java:407) at org.eclipse.jdt.internal.corext.refactoring.rename.RippleMethodFinder2.uniteWithSupertypes(RippleMethodFinder2.java:403) at org.eclipse.jdt.internal.corext.refactoring.rename.RippleMethodFinder2.createUnionFind(RippleMethodFinder2.java:384) at org.eclipse.jdt.internal.corext.refactoring.rename.RippleMethodFinder2.findAllRippleMethods(RippleMethodFinder2.java:196) at org.eclipse.jdt.internal.corext.refactoring.rename.RippleMethodFinder2.getAllRippleMethods(RippleMethodFinder2.java:168) at org.eclipse.jdt.internal.corext.refactoring.rename.RippleMethodFinder2.getRelatedMethods(RippleMethodFinder2.java:161) at org.eclipse.jdt.internal.corext.refactoring.rename.RenameMethodProcessor.initializeMethodsToRename(RenameMethodProcessor.java:236) at org.eclipse.jdt.internal.corext.refactoring.rename.RenameMethodProcessor.doCheckFinalConditions(RenameMethodProcessor.java:360) at org.eclipse.jdt.internal.corext.refactoring.rename.RenameVirtualMethodProcessor.doCheckFinalConditions(RenameVirtualMethodProcessor.java:143) at org.eclipse.jdt.internal.corext.refactoring.rename.JavaRenameProcessor.checkFinalConditions(JavaRenameProcessor.java:46) at org.eclipse.ltk.core.refactoring.participants.ProcessorBasedRefactoring.checkFinalConditions(ProcessorBasedRefactoring.java:224) at org.eclipse.ltk.core.refactoring.CheckConditionsOperation.run(CheckConditionsOperation.java:85) at org.eclipse.ltk.core.refactoring.CreateChangeOperation.run(CreateChangeOperation.java:121) at org.eclipse.core.internal.resources.Workspace.run(Workspace.java:1800) at org.eclipse.ltk.internal.ui.refactoring.WorkbenchRunnableAdapter.run(WorkbenchRunnableAdapter.java:87) at org.eclipse.jface.operation.ModalContext$ModalContextThread.run(ModalContext.java:121) -- 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, 11 months

8
40
0 / 0

[JBoss JIRA] Created: (JBIDE-3807) Some exceptions occures during refractoring

by Yura Zhishko (JIRA)

Some exceptions occures during refractoring ------------------------------------------- Key: JBIDE-3807 URL: https://jira.jboss.org/jira/browse/JBIDE-3807 Project: Tools (JBoss Tools) Issue Type: Bug Components: jsp/jsf/xml source editing Affects Versions: 3.0.0.GA Reporter: Yura Zhishko Assignee: Alexey Kazakov See flash video to reproduce this bug -- 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

5
12
0 / 0

[JBoss JIRA] Created: (JBIDE-3070) Problem with typing text in empty blank page

by Yura Zhishko (JIRA)

Problem with typing text in empty blank page -------------------------------------------- Key: JBIDE-3070 URL: https://jira.jboss.org/jira/browse/JBIDE-3070 Project: Tools (JBoss Tools) Issue Type: Bug Components: Visual Page Editor core Affects Versions: 3.0.0.beta1 Reporter: Yura Zhishko Assignee: Maxim Areshkau STEP 1: Open empty blank JSP or XHTML page STEP 2: Go to visual pane STEP 3: Try to print any text EXPECTED: Text must appear in Visual and Source pane ACTUAL: Text doesn't appear STEP 4: Print some text in source pane ASSERT: Text appears in Visual pane STEP 5: Go to visual pane STEP 6: Put cursor at the end of line STEP 7. Continue to print EXPECTED: Text must appear in Visual and Source pane ACTUAL: Text doesn't appear -- 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

3
4
0 / 0

[JBoss JIRA] Created: (JBIDE-1113) DnD on Mac OS X

by Sergey Vasilyev (JIRA)

DnD on Mac OS X --------------- Key: JBIDE-1113 URL: http://jira.jboss.com/jira/browse/JBIDE-1113 Project: JBoss Tools Issue Type: Feature Request Components: Visual Page Editor Affects Versions: 2.0.0.CR1 Environment: Mac OS X Reporter: Sergey Vasilyev Assigned To: Maxim Areshkau Fix For: 2.1 -- 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

5
8
0 / 0

[JBoss JIRA] Created: (JBIDE-4001) Create xulrunner bundle for solaris OS

by Maxim Areshkau (JIRA)

Create xulrunner bundle for solaris OS -------------------------------------- Key: JBIDE-4001 URL: https://jira.jboss.org/jira/browse/JBIDE-4001 Project: Tools (JBoss Tools) Issue Type: Feature Request Components: Visual Page Editor core Reporter: Maxim Areshkau Assignee: Maxim Areshkau Priority: Minor see forum reference http://www.jboss.org/index.html?module=bb&op=viewtopic&p=4217018#4217018. -- 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

3
8
0 / 0

[JBoss JIRA] Created: (JBIDE-5044) VPE should use JSF Tools model to get composite components

by Maxim Areshkau (JIRA)

VPE should use JSF Tools model to get composite components ---------------------------------------------------------- Key: JBIDE-5044 URL: https://jira.jboss.org/jira/browse/JBIDE-5044 Project: Tools (JBoss Tools) Issue Type: Feature Request Components: Visual Page Editor core Affects Versions: 3.1.0.M4 Reporter: Maxim Areshkau Assignee: Maxim Areshkau Fix For: LATER VPE should use JSF Tools model to get composite components. When this functionality will be resolved by moskov team. For now to get composite components VPE use composite component scanner, the same as for jsf resources. -- 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

2
4
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 November 2009