March 2012 - jbosstools-issues - Jboss List Archives

[JBoss JIRA] (JBIDE-11253) Fix JSF project templates to avoid warnings on the web.xml

by Alexey Kazakov (JIRA)

Alexey Kazakov created JBIDE-11253: -------------------------------------- Summary: Fix JSF project templates to avoid warnings on the web.xml Key: JBIDE-11253 URL: https://issues.jboss.org/browse/JBIDE-11253 Project: Tools (JBoss Tools) Issue Type: Bug Components: JSF Affects Versions: 3.3.0.Beta1 Reporter: Alexey Kazakov Assignee: Viacheslav Kabanovich Fix For: 3.3.0.Beta2 1. Create JSF 2 KickStart project 2. Open web.xml 3. There are a few warning messages like: file name references to default.htm that does not exist in web content. Let's remove all the <welcom-file> elements which reference to missing resources from this project template. So there shouldnot be any problems in web.xml for a brand new project. -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.jboss.org/secure/ContactAdministrators!default.jspa For more information on JIRA, see: http://www.atlassian.com/software/jira

14 years

2
2
0 / 0

[JBoss JIRA] (JBIDE-10926) Propertysheet for JSF 2.0 HTML component 'messages' shows wrong options

by Vimal Kansal (JIRA)

Vimal Kansal created JBIDE-10926: ------------------------------------ Summary: Propertysheet for JSF 2.0 HTML component 'messages' shows wrong options Key: JBIDE-10926 URL: https://issues.jboss.org/browse/JBIDE-10926 Project: Tools (JBoss Tools) Issue Type: Bug Reporter: Vimal Kansal JSF 2.0 html component 'messages' has attribute called 'layout' for which 2 options are 'table' and 'list' whereas the property editor shows the options as 'horizontal' and 'verticle' -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.jboss.org/secure/ContactAdministrators!default.jspa For more information on JIRA, see: http://www.atlassian.com/software/jira

14 years

5
6
0 / 0

[JBoss JIRA] (JBIDE-11345) Materialize Library : wrong default materialization output folder for webapps

by Fred Bricon (JIRA)

Fred Bricon created JBIDE-11345: ----------------------------------- Summary: Materialize Library : wrong default materialization output folder for webapps Key: JBIDE-11345 URL: https://issues.jboss.org/browse/JBIDE-11345 Project: Tools (JBoss Tools) Issue Type: Bug Components: common/jst/core Affects Versions: 3.3.0.Beta1 Reporter: Fred Bricon Assignee: Alexey Kazakov Fix For: 3.3.0.Beta2 Burr's JBDSWFK demo showed the materialize library feature uses a wrong default output folder for webapps : It defaults to src/main/webapp/lib instead of src/main/webapp/WEB-INF/lib. That renders the converted webapp unusable at runtime. -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.jboss.org/secure/ContactAdministrators!default.jspa For more information on JIRA, see: http://www.atlassian.com/software/jira

14 years

3
8
0 / 0

[JBoss JIRA] (JBIDE-11189) should enable the "Web Browser" menu in JBoss perspective

by Max Rydahl Andersen (JIRA)

Max Rydahl Andersen created JBIDE-11189: ------------------------------------------- Summary: should enable the "Web Browser" menu in JBoss perspective Key: JBIDE-11189 URL: https://issues.jboss.org/browse/JBIDE-11189 Project: Tools (JBoss Tools) Issue Type: Bug Components: common/jst/core Reporter: Max Rydahl Andersen Assignee: Alexey Kazakov Priority: Minor Fix For: 3.3.0.Beta2 I think it make sense to enable the "Window > Web Browser" menu in JBoss perspective. This will allow easy switching between what browser "run as.." and other operations uses. -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.jboss.org/secure/ContactAdministrators!default.jspa For more information on JIRA, see: http://www.atlassian.com/software/jira

14 years

4
3
0 / 0

[JBoss JIRA] (JBIDE-11385) Invalid thread access in CDICoreValidator

by Daniel Azarov (JIRA)

Daniel Azarov created JBIDE-11385: ------------------------------------- Summary: Invalid thread access in CDICoreValidator Key: JBIDE-11385 URL: https://issues.jboss.org/browse/JBIDE-11385 Project: Tools (JBoss Tools) Issue Type: Bug Components: CDI Affects Versions: 3.3.0.Beta1 Reporter: Daniel Azarov Assignee: Alexey Kazakov {code} org.jboss.tools.common.validation.JBTValidationException: Invalid thread access at org.jboss.tools.common.validation.ValidatorManager.validateInJob(ValidatorManager.java:101) at org.eclipse.wst.validation.internal.operations.ValidatorJob.run(ValidatorJob.java:78) at org.eclipse.core.internal.jobs.Worker.run(Worker.java:54) Caused by: org.eclipse.swt.SWTException: Invalid thread access at org.eclipse.swt.SWT.error(SWT.java:4282) at org.eclipse.swt.SWT.error(SWT.java:4197) at org.eclipse.swt.SWT.error(SWT.java:4168) at org.eclipse.swt.widgets.Widget.error(Widget.java:466) at org.eclipse.swt.widgets.Widget.checkWidget(Widget.java:404) at org.eclipse.swt.widgets.Widget.getData(Widget.java:492) at org.eclipse.ui.forms.DetailsPart.getCurrentPage(DetailsPart.java:135) at org.eclipse.ui.forms.DetailsPart.isDirty(DetailsPart.java:165) at org.eclipse.ui.forms.ManagedForm.isDirty(ManagedForm.java:272) at org.eclipse.ui.forms.editor.FormPage.isDirty(FormPage.java:231) at org.eclipse.pde.internal.ui.editor.PDEFormEditor.computeDirtyState(PDEFormEditor.java:623) at org.eclipse.pde.internal.ui.editor.PDEFormEditor.isDirty(PDEFormEditor.java:617) at org.eclipse.ui.internal.EditorManager.collectDirtyEditors(EditorManager.java:294) at org.eclipse.ui.internal.EditorManager.getDirtyEditors(EditorManager.java:587) at org.eclipse.ui.internal.WorkbenchPage.getDirtyEditors(WorkbenchPage.java:2153) at org.jboss.tools.common.util.EclipseUIUtil.getDirtyFiles(EclipseUIUtil.java:86) at org.jboss.tools.common.validation.ValidationErrorManager.init(ValidationErrorManager.java:105) at org.jboss.tools.common.validation.ValidationErrorManager.init(ValidationErrorManager.java:90) at org.jboss.tools.cdi.internal.core.validation.CDICoreValidator.init(CDICoreValidator.java:267) at org.jboss.tools.cdi.internal.core.validation.CDICoreValidator.validate(CDICoreValidator.java:292) at org.jboss.tools.common.validation.ValidatorManager.validate(ValidatorManager.java:117) at org.jboss.tools.common.validation.ValidatorManager.validateInJob(ValidatorManager.java:81) ... 2 more {code} -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.jboss.org/secure/ContactAdministrators!default.jspa For more information on JIRA, see: http://www.atlassian.com/software/jira

14 years

3
5
0 / 0

[JBoss JIRA] Created: (JBIDE-9283) JPA: Add hibernate @Type composite to JPA Details view

by Dmitry Geraskov (JIRA)

JPA: Add hibernate @Type composite to JPA Details view ------------------------------------------------------ Key: JBIDE-9283 URL: https://issues.jboss.org/browse/JBIDE-9283 Project: Tools (JBoss Tools) Issue Type: Feature Request Components: Hibernate Affects Versions: 3.3.0.M3 Reporter: Dmitry Geraskov Assignee: Dmitry Geraskov Attachments: type_composite.PNG There is also a composite in JPA Details view which should be extended. See attachment. -- This message is automatically generated by JIRA. For more information on JIRA, see: http://www.atlassian.com/software/jira

14 years

3
7
0 / 0

[JBoss JIRA] Created: (JBIDE-9290) Automatically install JAX-RS facet when RESTEasy dependency is added to the project

by Xavier Coulon (JIRA)

Automatically install JAX-RS facet when RESTEasy dependency is added to the project ------------------------------------------------------------------------------------ Key: JBIDE-9290 URL: https://issues.jboss.org/browse/JBIDE-9290 Project: Tools (JBoss Tools) Issue Type: Feature Request Components: maven Affects Versions: 3.3.0.M2 Reporter: Xavier Coulon Assignee: Fred Bricon Automatically install the JAX-RS Facet and the JAX-RS Builder when a dependency with groupId "org.jboss.resteasy" is added to the project's pom.xml -- This message is automatically generated by JIRA. For more information on JIRA, see: http://www.atlassian.com/software/jira

14 years

5
16
0 / 0

[JBoss JIRA] Created: (JBIDE-9310) JBoss tools does not take AS 6's jsf.deployer into account

by arjan tijms (JIRA)

JBoss tools does not take AS 6's jsf.deployer into account ---------------------------------------------------------- Key: JBIDE-9310 URL: https://issues.jboss.org/browse/JBIDE-9310 Project: Tools (JBoss Tools) Issue Type: Bug Reporter: arjan tijms In JBoss AS 6, one can change which JSF implementation JBoss AS uses by editing /deployers/jsf.deployer/META-INF/jsf-integration-deployer-jboss-beans.xml. JBoss bundles Mojarra 1.2, 2.0 and MyFaces 2.0 by default. However, if one changes this, JBoss tools keeps putting the two hardcoded libs in /deployers/jsf.deployer/Mojarra-2.0/jsf-libs on the IDE's lookup path. This means that stepping through JSF source code is totally broken then. A workaround is to copy the libs from the other configuration to /deployers/jsf.deployer/Mojarra-2.0/jsf-libs and rename them to jsf-api-2.0.3-b05.jar and jsf-impl-2.0.3-b05.jar. This works, but there is something unsettling of having e.g. the 2.1.2 libs called 2.0.3 just for the sake of the ability to debug. -- This message is automatically generated by JIRA. For more information on JIRA, see: http://www.atlassian.com/software/jira

14 years

7
9
0 / 0

[JBoss JIRA] Created: (JBIDE-9375) JPA: validate @ForeignKey inverseName for ManyToMany mapping

by Dmitry Geraskov (JIRA)

JPA: validate @ForeignKey inverseName for ManyToMany mapping ------------------------------------------------------------ Key: JBIDE-9375 URL: https://issues.jboss.org/browse/JBIDE-9375 Project: Tools (JBoss Tools) Issue Type: Feature Request Components: Hibernate Affects Versions: 3.3.0.M2 Reporter: Dmitry Geraskov Assignee: Dmitry Geraskov Fix For: 3.3.0.M3 @ForignKey annotations can be used in OneToMany, ManyToOne, and OneToOne relationships, ManyToMany relationships. Inverse name should be validated only in ManyToMany relationships at owner side (not owner side has mappedBy attribute). Test case: 1. Create JPA project with Hibernate platform 2. Create 2 Entities with many to many reference 3. Add @ForeignKey(name="x", inverseName="") to both sides Check that error appeared and only on the owning size. -- This message is automatically generated by JIRA. For more information on JIRA, see: http://www.atlassian.com/software/jira

14 years

3
6
0 / 0

[JBoss JIRA] Created: (JBIDE-9510) Add openshift express capabilities to AS7 server adapter

by Andre Dietisheim (JIRA)

Add openshift express capabilities to AS7 server adapter -------------------------------------------------------- Key: JBIDE-9510 URL: https://issues.jboss.org/browse/JBIDE-9510 Project: Tools (JBoss Tools) Issue Type: Feature Request Components: JBossAS Affects Versions: 3.3.0.M3 Reporter: Andre Dietisheim Assignee: Andre Dietisheim Fix For: 3.3.0.M3 Bascially you can already use eclipse and the AS7 server adapter to work with Openshift Express. The whole workflow is pretty much rough though and we need to improve that. We want to add ease of use so that deploying to Openshift Express gets as easy as possible. -- This message is automatically generated by JIRA. For more information on JIRA, see: http://www.atlassian.com/software/jira

14 years

7
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 March 2012