December 2009 - jbosstools-issues

[JBoss JIRA] Created: (JBIDE-5431) Main menu: Source -> Generate Hibernate/JPA annotations - visible for Mapping Diagram

by Vitali Yemialyanchyk (JIRA)

Main menu: Source -> Generate Hibernate/JPA annotations - visible for Mapping Diagram ------------------------------------------------------------------------------------- Key: JBIDE-5431 URL: https://jira.jboss.org/jira/browse/JBIDE-5431 Project: Tools (JBoss Tools) Issue Type: Bug Components: Hibernate Affects Versions: 3.1.0.CR1 Reporter: Vitali Yemialyanchyk Assignee: Vitali Yemialyanchyk Priority: Minor Fix For: 3.1.0.GA ordinally it disabled, but sametimes enabled and then I get this exception: org.eclipse.core.commands.NotEnabledException: Trying to execute the disabled command org.hibernate.eclipse.jdt.ui.run_jpaaction at org.eclipse.core.commands.Command.executeWithChecks(Command.java:469) at org.eclipse.core.commands.ParameterizedCommand.executeWithChecks(ParameterizedCommand.java:508) at org.eclipse.ui.internal.handlers.HandlerService.executeCommand(HandlerService.java:169) at org.eclipse.ui.internal.handlers.SlaveHandlerService.executeCommand(SlaveHandlerService.java:241) at org.eclipse.ui.menus.CommandContributionItem.handleWidgetSelection(CommandContributionItem.java:770) at org.eclipse.ui.menus.CommandContributionItem.access$10(CommandContributionItem.java:756) at org.eclipse.ui.menus.CommandContributionItem$5.handleEvent(CommandContributionItem.java:746) at org.eclipse.swt.widgets.EventTable.sendEvent(EventTable.java:84) at org.eclipse.swt.widgets.Widget.sendEvent(Widget.java:1003) -- 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, 6 months

1
3
0 / 0

[JBoss JIRA] Created: (JBDS-828) A JBDS generated WAR project with reverse-engineered entities doesn't work

by Ondrej Skutka (JIRA)

A JBDS generated WAR project with reverse-engineered entities doesn't work -------------------------------------------------------------------------- Key: JBDS-828 URL: https://jira.jboss.org/jira/browse/JBDS-828 Project: JBoss Developer Studio Issue Type: Bug Components: seam Affects Versions: 2.1.0 Reporter: Ondrej Skutka Priority: Critical Fix For: 2.1.0 A patch proposed in JBSEAM-4276 is not applied into JBDS seam war project creation. -- 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, 6 months

6
12
0 / 0

[JBoss JIRA] Created: (JBIDE-5232) Refactoring methods and properties of managed bean doesn't work for corresponding ELs.

by Alexey Kazakov (JIRA)

Refactoring methods and properties of managed bean doesn't work for corresponding ELs. -------------------------------------------------------------------------------------- Key: JBIDE-5232 URL: https://jira.jboss.org/jira/browse/JBIDE-5232 Project: Tools (JBoss Tools) Issue Type: Bug Components: JSF Affects Versions: 3.1.0.CR1 Reporter: Alexey Kazakov Assignee: Daniel Azarov Fix For: 3.1.0.CR1 1. Create JSF 1.2. KickStart 2. Open User.java 3. Rename getName() to getFirstName() (use java refactoring) 4. Open hello.jsp 5. #{user.name} should be #{user.firstName}. But now there is unchanged #{user.name}. -- 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, 6 months

2
3
0 / 0

[JBoss JIRA] Created: (JBDS-535) workflow/usability questions - Step 4: Select Java VM

by Nick Boldt (JIRA)

workflow/usability questions - Step 4: Select Java VM ----------------------------------------------------- Key: JBDS-535 URL: https://jira.jboss.org/jira/browse/JBDS-535 Project: Developer Studio Issue Type: Quality Risk Components: installer Affects Versions: 2.0.0.cr1 Reporter: Nick Boldt Assignee: Max Rydahl Andersen Attachments: Screenshot- JBoss Developer Studio 2.0.0.CR1.png Actually, it says "gij" but on my monitor the text is cut off and it looks like a q, not a g. Perhaps we could rework this as follows: "JBoss Developer Studio requires a Java 5 or later runtime. Gnu Java (gij) is not supported; Open JDK 6 is recommended. Choose the Java VM to use with JBoss Developer Studio. ( ) Default Java VM (defined by PATH) ( ) Alternate Java VM (user-defined)" Of course that assumes that JDBS *does in fact support JDK6*, and that we'd like to encourage people to use the latest and greatest Open JDK [1] (offered OOTB in Fedora 9 and later [2]), rather than letting them pick Sun, IBM, or BEA's JDKs. [1] http://openjdk.java.net/ [2] http://fedoraproject.org/wiki/JavaFAQ Also, does the installer check if the version of java used to run it is a compatible one? For example, will the installer run with 1.4, or with blackdown or gij, but require that JBDS itself use 5.0+? And, since this selection is a prereq before JBDS will work at all, should this page be step 1, not 4? -- 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, 6 months

2
11
0 / 0

[JBoss JIRA] Created: (JBDS-854) Testing examples with TestNG plugin fails

by Martin Gencur (JIRA)

Testing examples with TestNG plugin fails ----------------------------------------- Key: JBDS-854 URL: https://jira.jboss.org/jira/browse/JBDS-854 Project: JBoss Developer Studio Issue Type: Bug Components: seam Affects Versions: 2.1.0 Reporter: Martin Gencur The bug is present in N200908281758-H140 build (the same result on windows and linux) When testing examples from seam with TestNG plugin in JBDS the test always throws java.lang.AssertionError. For example: in the booking example when running BookingTest.java with TestNG plugin, the test ends up with: FAILED: testBookHotel java.lang.AssertionError: javax.el.PropertyNotFoundException: Target Unreachable, identifier 'hotelSearch' resolved to null at org.jboss.seam.mock.AbstractSeamTest$Request.onException(AbstractSeamTest.java:455) at org.jboss.seam.mock.AbstractSeamTest$Request$2.doFilter(AbstractSeamTest.java:504) at org.jboss.seam.servlet.SeamFilter$FilterChainImpl.doFilter(SeamFilter.java:83) at org.jboss.seam.web.LoggingFilter.doFilter(LoggingFilter.java:60) at org.jboss.seam.servlet.SeamFilter$FilterChainImpl.doFilter(SeamFilter.java:69) at org.jboss.seam.web.IdentityFilter.doFilter(IdentityFilter.java:40) at org.jboss.seam.servlet.SeamFilter$FilterChainImpl.doFilter(SeamFilter.java:69) at org.jboss.seam.web.MultipartFilter.doFilter(MultipartFilter.java:90) at org.jboss.seam.servlet.SeamFilter$FilterChainImpl.doFilter(SeamFilter.java:69) at org.jboss.seam.web.ExceptionFilter.doFilter(ExceptionFilter.java:64) at org.jboss.seam.servlet.SeamFilter$FilterChainImpl.doFilter(SeamFilter.java:69) at org.jboss.seam.web.RedirectFilter.doFilter(RedirectFilter.java:45) at org.jboss.seam.servlet.SeamFilter$FilterChainImpl.doFilter(SeamFilter.java:69) at org.jboss.seam.servlet.SeamFilter.doFilter(SeamFilter.java:158) at org.jboss.seam.mock.AbstractSeamTest$Request.run(AbstractSeamTest.java:491) at org.jboss.seam.mock.AbstractSeamTest$FacesRequest.run(AbstractSeamTest.java:862) at org.jboss.seam.example.booking.test.BookingTest.testBookHotel(BookingTest.java:66) Caused by: javax.el.PropertyNotFoundException: Target Unreachable, identifier 'hotelSearch' resolved to null at org.jboss.el.parser.AstValue.getTarget(AstValue.java:38) at org.jboss.el.parser.AstValue.setValue(AstValue.java:83) at org.jboss.el.ValueExpressionImpl.setValue(ValueExpressionImpl.java:249) at org.jboss.seam.mock.AbstractSeamTest$Request.setValue(AbstractSeamTest.java:430) at org.jboss.seam.example.booking.test.BookingTest$2.updateModelValues(BookingTest.java:47) at org.jboss.seam.mock.AbstractSeamTest$Request.updateModelValuesPhase(AbstractSeamTest.java:670) at org.jboss.seam.mock.AbstractSeamTest$Request.emulateJsfLifecycle(AbstractSeamTest.java:592) at org.jboss.seam.mock.AbstractSeamTest$Request.access$100(AbstractSeamTest.java:177) at org.jboss.seam.mock.AbstractSeamTest$Request$2.doFilter(AbstractSeamTest.java:497) ... 37 more ... Removed 22 stack frames Another example: seam todo example ends up with: FAILED: testTodo java.lang.AssertionError: javax.el.PropertyNotFoundException: Target Unreachable, identifier 'login' resolved to null at org.jboss.seam.mock.AbstractSeamTest$Request.onException(AbstractSeamTest.java:455) at org.jboss.seam.mock.AbstractSeamTest$Request$2.doFilter(AbstractSeamTest.java:504) at org.jboss.seam.servlet.SeamFilter$FilterChainImpl.doFilter(SeamFilter.java:83) at org.jboss.seam.web.LoggingFilter.doFilter(LoggingFilter.java:60) at org.jboss.seam.servlet.SeamFilter$FilterChainImpl.doFilter(SeamFilter.java:69) at org.jboss.seam.web.IdentityFilter.doFilter(IdentityFilter.java:40) at org.jboss.seam.servlet.SeamFilter$FilterChainImpl.doFilter(SeamFilter.java:69) at org.jboss.seam.web.MultipartFilter.doFilter(MultipartFilter.java:90) at org.jboss.seam.servlet.SeamFilter$FilterChainImpl.doFilter(SeamFilter.java:69) at org.jboss.seam.web.ExceptionFilter.doFilter(ExceptionFilter.java:64) at org.jboss.seam.servlet.SeamFilter$FilterChainImpl.doFilter(SeamFilter.java:69) at org.jboss.seam.web.RedirectFilter.doFilter(RedirectFilter.java:45) at org.jboss.seam.servlet.SeamFilter$FilterChainImpl.doFilter(SeamFilter.java:69) at org.jboss.seam.servlet.SeamFilter.doFilter(SeamFilter.java:158) at org.jboss.seam.mock.AbstractSeamTest$Request.run(AbstractSeamTest.java:491) at org.jboss.seam.mock.AbstractSeamTest$FacesRequest.run(AbstractSeamTest.java:862) at org.jboss.seam.example.todo.test.TodoTest.testTodo(TodoTest.java:42) Caused by: javax.el.PropertyNotFoundException: Target Unreachable, identifier 'login' resolved to null at org.jboss.el.parser.AstValue.getTarget(AstValue.java:38) at org.jboss.el.parser.AstValue.setValue(AstValue.java:83) at org.jboss.el.ValueExpressionImpl.setValue(ValueExpressionImpl.java:249) at org.jboss.seam.mock.AbstractSeamTest$Request.setValue(AbstractSeamTest.java:430) at org.jboss.seam.example.todo.test.TodoTest$1.updateModelValues(TodoTest.java:26) at org.jboss.seam.mock.AbstractSeamTest$Request.updateModelValuesPhase(AbstractSeamTest.java:670) at org.jboss.seam.mock.AbstractSeamTest$Request.emulateJsfLifecycle(AbstractSeamTest.java:592) at org.jboss.seam.mock.AbstractSeamTest$Request.access$100(AbstractSeamTest.java:177) at org.jboss.seam.mock.AbstractSeamTest$Request$2.doFilter(AbstractSeamTest.java:497) ... 37 more ... Removed 22 stack frames Last example: seambay example ends up with: FAILED: testCreateAuction java.lang.AssertionError at org.jboss.seam.example.seambay.test.AuctionTest$1.invokeApplication(AuctionTest.java:26) at org.jboss.seam.mock.AbstractSeamTest$Request.invokeApplicationPhase(AbstractSeamTest.java:646) at org.jboss.seam.mock.AbstractSeamTest$Request.emulateJsfLifecycle(AbstractSeamTest.java:595) at org.jboss.seam.mock.AbstractSeamTest$Request.access$100(AbstractSeamTest.java:177) at org.jboss.seam.mock.AbstractSeamTest$Request$2.doFilter(AbstractSeamTest.java:497) at org.jboss.seam.servlet.SeamFilter$FilterChainImpl.doFilter(SeamFilter.java:83) at org.jboss.seam.web.LoggingFilter.doFilter(LoggingFilter.java:60) at org.jboss.seam.servlet.SeamFilter$FilterChainImpl.doFilter(SeamFilter.java:69) at org.jboss.seam.web.IdentityFilter.doFilter(IdentityFilter.java:40) at org.jboss.seam.servlet.SeamFilter$FilterChainImpl.doFilter(SeamFilter.java:69) at org.jboss.seam.web.MultipartFilter.doFilter(MultipartFilter.java:90) at org.jboss.seam.servlet.SeamFilter$FilterChainImpl.doFilter(SeamFilter.java:69) at org.jboss.seam.web.ExceptionFilter.doFilter(ExceptionFilter.java:64) at org.jboss.seam.servlet.SeamFilter$FilterChainImpl.doFilter(SeamFilter.java:69) at org.jboss.seam.web.RedirectFilter.doFilter(RedirectFilter.java:45) at org.jboss.seam.servlet.SeamFilter$FilterChainImpl.doFilter(SeamFilter.java:69) at org.jboss.seam.servlet.SeamFilter.doFilter(SeamFilter.java:158) at org.jboss.seam.mock.AbstractSeamTest$Request.run(AbstractSeamTest.java:491) at org.jboss.seam.mock.AbstractSeamTest$FacesRequest.run(AbstractSeamTest.java:862) at org.jboss.seam.example.seambay.test.AuctionTest.testCreateAuction(AuctionTest.java:28) ... Removed 22 stack frames -- 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, 6 months

2
11
0 / 0

[JBoss JIRA] Created: (JBIDE-5393) BPEL validation errors in hello_world_header_ode riftsaw quickstart sample

by Gary Brown (JIRA)

BPEL validation errors in hello_world_header_ode riftsaw quickstart sample -------------------------------------------------------------------------- Key: JBIDE-5393 URL: https://jira.jboss.org/jira/browse/JBIDE-5393 Project: Tools (JBoss Tools) Issue Type: Bug Components: bpm Reporter: Gary Brown Error occurred when importing the hello_world_header_ode riftsaw quickstart sample into Eclipse. This one is because the copy has an ODE extension, to define the header attribute. Not sure what the situation is with supporting ODE extensions, but in the short term, it might be good if we could atleast change this error to a warning, if the copy defines the header attribute? The from-spec of "<wsdl:message "HelloMessage">" is not compatible with to-spec of "<xs:simpleType "string">" HelloWorld.bpel /Quickstart_bpel_hello_world_header_ode/bpelContent line 58 BPEL Validation Marker -- 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, 6 months

2
4
0 / 0

[JBoss JIRA] Created: (JBIDE-3891) Add JUnit tests for org.jboss.tools.common.verification.ui.vrules.preferences

by Denis Golovin (JIRA)

Add JUnit tests for org.jboss.tools.common.verification.ui.vrules.preferences ----------------------------------------------------------------------------- Key: JBIDE-3891 URL: https://jira.jboss.org/jira/browse/JBIDE-3891 Project: Tools (JBoss Tools) Issue Type: Task Components: common Affects Versions: 3.0.0.GA Reporter: Denis Golovin Assignee: Denis Golovin Fix For: 3.1.0 1. Create est plug-ins for common.verification 2. Create test suites 3. Include test suites into test builder build.properties -- 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, 6 months

1
5
0 / 0

[JBoss JIRA] Created: (JBIDE-5416) Allow META-INF directory location to be moved

by David Thompson (JIRA)

Allow META-INF directory location to be moved --------------------------------------------- Key: JBIDE-5416 URL: https://jira.jboss.org/jira/browse/JBIDE-5416 Project: Tools (JBoss Tools) Issue Type: Feature Request Components: core Affects Versions: 3.1.0.M4 Environment: All versions Reporter: David Thompson We use JBoss Tools on projects that have been created using seamgen. Seamgen puts all of its persistence and hibernate config files in the following Project/resources/META-INF. However, JBoss Tools is hardcoded to look for these files in src/hot/META-INF. If the META-INF location could be set in the org.jboss.tools.seam.core.prefs file, then we could easily have the validation working for our environment (seamgen). Everything else is configurable and is working like a dream. -- 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, 6 months

2
8
0 / 0

[JBoss JIRA] Created: (JBIDE-5315) Smooks Run As... Odd exception when testing Java Mapping task

by Brian Fitzpatrick (JIRA)

Smooks Run As... Odd exception when testing Java Mapping task ------------------------------------------------------------- Key: JBIDE-5315 URL: https://jira.jboss.org/jira/browse/JBIDE-5315 Project: Tools (JBoss Tools) Issue Type: Bug Components: smooks Affects Versions: 3.1.0.CR1 Reporter: Brian Fitzpatrick Assignee: Tom Fennelly Fix For: 3.1.0.GA Testing an Input task wired to a Java Mapping task I get this... (No errors/warnings in Problems view indicating issues exist.) Exception in thread "main" org.milyn.SmooksException: Failed to apply processing unit [org.milyn.javabean.ext.WireOnElementChecker] to [org:milyn:smooks:unknowndoc:/smooks-resource-list/jb:bindings/jb:wiring]. at org.milyn.delivery.dom.SmooksDOMFilter.processVisitorException(SmooksDOMFilter.java:818) at org.milyn.delivery.dom.SmooksDOMFilter.access$800(SmooksDOMFilter.java:134) at org.milyn.delivery.dom.SmooksDOMFilter$ElementProcessor.processMapping(SmooksDOMFilter.java:762) at org.milyn.delivery.dom.SmooksDOMFilter$ElementProcessor.process(SmooksDOMFilter.java:704) at org.milyn.delivery.dom.SmooksDOMFilter$ElementProcessor.access$000(SmooksDOMFilter.java:660) at org.milyn.delivery.dom.SmooksDOMFilter.filter(SmooksDOMFilter.java:389) at org.milyn.delivery.dom.SmooksDOMFilter.doFilter(SmooksDOMFilter.java:245) at org.milyn.delivery.dom.SmooksDOMFilter.doFilter(SmooksDOMFilter.java:223) at org.milyn.Smooks._filter(Smooks.java:470) at org.milyn.Smooks.filterSource(Smooks.java:448) at org.milyn.cdr.XMLConfigDigester.digestExtendedResourceConfig(XMLConfigDigester.java:479) at org.milyn.cdr.XMLConfigDigester.digestV11XSDValidatedConfig(XMLConfigDigester.java:264) at org.milyn.cdr.XMLConfigDigester.digestConfigRecursively(XMLConfigDigester.java:150) at org.milyn.cdr.XMLConfigDigester.digestConfig(XMLConfigDigester.java:116) at org.milyn.cdr.SmooksResourceConfigurationStore.registerResources(SmooksResourceConfigurationStore.java:211) at org.milyn.Smooks.addConfigurations(Smooks.java:288) at org.milyn.Smooks.addConfigurations(Smooks.java:260) at org.milyn.Smooks.<init>(Smooks.java:125) at org.jboss.tools.smooks.launch.SmooksLauncher.main(SmooksLauncher.java:68) Caused by: org.milyn.cdr.SmooksConfigurationException: The bindings attribute 'createOnElement' and wiring attribute 'wireOnElement' are both not set. One of them must at least be set. If the result of this binding should be a new populated Object then you need to set the 'createOnElement' bindings attribute. If you want to update an existing object in the bean context then you must set the 'wireOnElement' attribute. at org.milyn.javabean.ext.WireOnElementChecker.visitBefore(WireOnElementChecker.java:38) at org.milyn.delivery.dom.SmooksDOMFilter$ElementProcessor.processMapping(SmooksDOMFilter.java:756) ... 16 more -- 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, 6 months

1
2
0 / 0

[JBoss JIRA] Created: (JBIDE-5210) Complains during adding JSF capabilities

by Jiri Peterka (JIRA)

Complains during adding JSF capabilities ---------------------------------------- Key: JBIDE-5210 URL: https://jira.jboss.org/jira/browse/JBIDE-5210 Project: Tools (JBoss Tools) Issue Type: Bug Affects Versions: 3.1.0.CR1 Reporter: Jiri Peterka Priority: Minor Fix For: 3.1.0.GA Steps: 1. Create JSF kickstart project 2. Remove JSF Capabilities - removing JSF without problem) is done 3. When adding JSF capabilities, there is complain it's already deployed Expected behaviour: No complains during adding or removing JSF Capabilities. If adding jsf capabilities requires undeployed project, then during removing jsf capabilities jsf project should be undeployed -- 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, 6 months

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