January 2012 - jbosstools-issues - Jboss List Archives

[JBoss JIRA] (JBIDE-10475) AS7 examples from JBoss Central such as helloworld do not have a targeted runtime after import

by Rob Stryker (Created) (JIRA)

AS7 examples from JBoss Central such as helloworld do not have a targeted runtime after import ---------------------------------------------------------------------------------------------- Key: JBIDE-10475 URL: https://issues.jboss.org/browse/JBIDE-10475 Project: Tools (JBoss Tools) Issue Type: Bug Components: project-examples Affects Versions: 3.3.0.M5 Reporter: Rob Stryker Assignee: Snjezana Peco Fix For: 3.3.0.Beta1 As described by Martin: When I try to create one of the examples with AS 7.1 installed, it doesn't complain about anything and simply creates the project. But when you go to "Project -> Properties -> Targeted runtimes" no runtime is checked. The 7.1 runtime should be automatically checked, right? --- I did some digging and found that none of the fixes in project examples add the facet runtime as a primary runtime object to the project. In my environment, after importing the hello-world example via JBoss Central, the only "fix" that is != null is WTPRuntimeFix. This fix, however, seems heavily targeted to ESB fixes, and not to generic projects such as hello-world. What I'm noting is that on line 94, the project has no primary runtime set yet. Therefore, it slips into the correcting of the esb section, where it does nothing. I'm attaching a patch which attempts to fix this logic. It isolates the code to check for whether esb is required. Then it ensures that the proper facet-runtime is added regardless of whether one exists on the project already. The patch is not 100%, though, because I commented out two lines, calling fixNonFacetedEsbProject. I commented these lines out because by this point in the code, we have already guaranteed the project IS faceted. I am confident this code is correct, but I admit I do not know all the usecases and so cannot guarantee it. A test on your part would prove very helpful -- 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 months

4
3
0 / 0

[JBoss JIRA] (JBIDE-10421) "output directory" is shown on the project example wizard before even choosing a project

by Max Rydahl Andersen (Created) (JIRA)

"output directory" is shown on the project example wizard before even choosing a project ---------------------------------------------------------------------------------------- Key: JBIDE-10421 URL: https://issues.jboss.org/browse/JBIDE-10421 Project: Tools (JBoss Tools) Issue Type: Bug Components: project-examples Reporter: Max Rydahl Andersen Assignee: Snjezana Peco Priority: Blocker Fix For: 3.3.0.Beta1 when using the project examples wizard there is now a "output directory' field shown long before I actually choose which example to use. This is taking up alot of space and is not relevant to show here - should be shown when the project gets actually checked out. -- 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 months

7
8
0 / 0

[JBoss JIRA] Created: (JBIDE-8651) Revert workaround for wrong implementation of WTP's ElementImpl.getAttribute(String)

by Yahor Radtsevich (JIRA)

Revert workaround for wrong implementation of WTP's ElementImpl.getAttribute(String) ------------------------------------------------------------------------------------ Key: JBIDE-8651 URL: https://issues.jboss.org/browse/JBIDE-8651 Project: Tools (JBoss Tools) Issue Type: Task Components: Visual Page Editor core Affects Versions: 3.3.0.M1 Reporter: Yahor Radtsevich Assignee: Yahor Radtsevich Fix For: 3.3.x Workaround for JBIDE-8649 (https://bugs.eclipse.org/272378 ) should be reverted when this propblen is fixed on WTP. -- This message is automatically generated by JIRA. For more information on JIRA, see: http://www.atlassian.com/software/jira

14 years, 2 months

2
3
0 / 0

[JBoss JIRA] (JBIDE-10645) Validate servlet name 'javax.ws.rs.core.Application' or any subtype

by Xavier Coulon (JIRA)

Xavier Coulon created JBIDE-10645: ------------------------------------- Summary: Validate servlet name 'javax.ws.rs.core.Application' or any subtype Key: JBIDE-10645 URL: https://issues.jboss.org/browse/JBIDE-10645 Project: Tools (JBoss Tools) Issue Type: Bug Components: JSF Affects Versions: 3.3.0.M5 Reporter: Xavier Coulon Assignee: Alexey Kazakov The 'JAX-RS Application' is the top level fragment of the URI Path Templates of the JAX-RS Endpoints. One way to configure it is in the webapp's deployment descriptor, with something like this: {code} <web-app version="2.4" xmlns="http://java.sun.com/xml/ns/j2ee" xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance" xsi:schemaLocation="http://java.sun.com/xml/ns/j2ee http://java.sun.com/xml/ns/j2ee/web-app_2_4.xsd"> <servlet-mapping> <servlet-name>javax.ws.rs.core.Application</servlet-name> <url-pattern>/*</url-pattern> </servlet-mapping> </web-app> {code} see [JBossAS 7 / JAX-RS docs here|https://docs.jboss.org/author/display/AS7/Java+API+for+RESTful+Web+S...] Hélas, the web.xml validator reports an error (or a warning) with the following message {quote} servlet-name references to javax.ws.rs.core.Application that is not a servlet {quote} For sure, the validation level could be set to ignore, but could this JAX-RS specific rule be implemented by default ? -- 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 months

3
14
0 / 0

[JBoss JIRA] (JBIDE-10685) Restart Forge When Default Runtime Preference Changes

by Koen Aers (JIRA)

Koen Aers created JBIDE-10685: --------------------------------- Summary: Restart Forge When Default Runtime Preference Changes Key: JBIDE-10685 URL: https://issues.jboss.org/browse/JBIDE-10685 Project: Tools (JBoss Tools) Issue Type: Task Components: forge Reporter: Koen Aers Assignee: Koen Aers Fix For: 3.3.0.Beta1 As the Forge runtime is now decoupled from the Forge view. The Forge view will use the default runtime as indicated by the Forge preferences. It follows that the runtime needs to be restarted when this default changes. -- 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 months

1
1
0 / 0

[JBoss JIRA] (JBDS-1985) Synchronizing a VDB takes too long in 7.4.2

by Max Rydahl Andersen (JIRA)

[ https://issues.jboss.org/browse/JBDS-1985?page=com.atlassian.jira.plugin.... ] Max Rydahl Andersen updated JBDS-1985: -------------------------------------- Fix Version/s: 4.1.2.GA (was: 4.1.x) > Synchronizing a VDB takes too long in 7.4.2 > ------------------------------------------- > > Key: JBDS-1985 > URL: https://issues.jboss.org/browse/JBDS-1985 > Project: Developer Studio (JBoss Developer Studio) > Issue Type: Support Patch > Security Level: Public(Everyone can see) > Components: teiid > Affects Versions: 4.1.1.GA > Reporter: Johnathon Lee > Assignee: Barry LaFond > Fix For: 4.1.2.GA > > Attachments: JBDS1985.upversion.patch.txt, org.teiid.designer.core.patch, org.teiid.designer.dqp.patch, org.teiid.designer.vdb.patch, org.teiid.designer.vdb.test.patch, org.teiid.designer.vdb.ui.patch, TEIIDDES-1200-7.4.2-Patch-A.zip, TEIIDDES_1200.zip, UdfManager.java.patch, UdfUiPlugin.java.patch, VdbUtil.java.patch > > > Synchronizing a big VDB in version 7.4.2 (JBDS 4.1.1) takes 30 minutes versus 2 minutes in 7.1.1 (JBDS 4.1.0) > Investigating/debug noted 2 areas. > 1) New UdfManager is not caching a FunctionLibrary and each SQL validation is creating a new instance. (needs a fix) > 2) Synchronizing a VDB is hammering the ChecksumUtil.computeChecksum() during the VDB's resource build processing > 3) PreviewManager is using a new Vdb() object to determine if "preview = true" and version #. However, it's heavy weight and currently the Vdb() is registering for events, but is not being Unregistered. -- 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 months

1
0
0 / 0

[JBoss JIRA] Created: (JBIDE-3574) JBoss Tools wizards have black borders around SWT controls

by Denis Golovin (JIRA)

JBoss Tools wizards have black borders around SWT controls ---------------------------------------------------------- Key: JBIDE-3574 URL: https://jira.jboss.org/jira/browse/JBIDE-3574 Project: Tools (JBoss Tools) Issue Type: Bug Affects Versions: 3.0.0.CR2 Reporter: Denis Golovin Assignee: Denis Golovin Fix For: 3.0.0.GA -- 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, 2 months

3
21
0 / 0

[JBoss JIRA] (JBIDE-10572) NullPointerException in ClassHyperlink

by Viacheslav Kabanovich (Created) (JIRA)

NullPointerException in ClassHyperlink -------------------------------------- Key: JBIDE-10572 URL: https://issues.jboss.org/browse/JBIDE-10572 Project: Tools (JBoss Tools) Issue Type: Bug Components: common/jst/core Affects Versions: 3.3.0.M5 Reporter: Viacheslav Kabanovich Assignee: Alexey Kazakov Fix For: 3.3.0.Beta1 Attachments: NPE.txt Now the exception can be obtained only in struts-config.xml, but faults in our code make it probable to appear more generally. EXECUTE: Create Struts KickStart project and open struts-config.xml EXECUTE: Create global exception {code} <exception className="/pages/greeting.jsp" key="a" path="/greeting.do" type="b"/> {code} where 'className' is deliberately assigned to an existing page path instead of a class name. EXECUTE: Call open-on options over word 'greeting' ASSERT: Two options appear: 1) open class 'greeting.jsp' 2) Open '/struts/WebContent/pages/greeting.jsp' with JBoss Tools JSP Editor EXECUTE: Call open-on options over symbol '/' FAILURE: null pointer exception; two options may still appear: 1) empty label 2) Open '/struts/WebContent/pages/greeting.jsp' with JBoss Tools JSP Editor I see the cause of the exception in difference of algorithm computing class name region in classes XMLClassHyperlinkPartitioner and ClassHyperlink. Partitioner returns attribute value with trimmed white spaces ant quote symbols. So, even if open-on is invoked over '/', partitioner creates instance of ClassHyperlink. But ClassHyperlink computes region more strictly, so that text contains only qualified Java name symbols. When open-on is invoked over '/', ClassHyperlink sets region to open to null. If there is no other hyperlink option, that may pass, but when several hyperlinks are detected, MultipleHyperlinkPresenter requests each for hyperlink text, and ClassHyperlink fails. In this case the other option is WST's WorkspaceFileHyperlink, it detects in any attribute values resource paths; if it starts to detect them in text nodes (and why not?), this issue will take place in faces-config.xml and web.xml, where class names are assigned as text nodes. This issue cannot be fixed just by preventing NPE, because open-on option with empty label may appear all the same. Solution is to let partitioner create instance of hyperlink only when hyperlink is capable to do its job. -- 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 months

5
10
0 / 0

[JBoss JIRA] (JBIDE-10411) could maven archetype wizard not provide some "ok" defaults for group and package name

by Max Rydahl Andersen (Created) (JIRA)

could maven archetype wizard not provide some "ok" defaults for group and package name --------------------------------------------------------------------------------------- Key: JBIDE-10411 URL: https://issues.jboss.org/browse/JBIDE-10411 Project: Tools (JBoss Tools) Issue Type: Bug Components: central, maven Reporter: Max Rydahl Andersen Assignee: Snjezana Peco Fix For: 3.3.0.M5 -- 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 months

6
10
0 / 0

[JBoss JIRA] (JBIDE-10423) Better icon for JBoss Central

by Alexey Kazakov (Created) (JIRA)

Better icon for JBoss Central ----------------------------- Key: JBIDE-10423 URL: https://issues.jboss.org/browse/JBIDE-10423 Project: Tools (JBoss Tools) Issue Type: Enhancement Components: central Reporter: Alexey Kazakov Assignee: Snjezana Peco The current icon is GIF and it doesn't look good on dark background. Let's change it to PNG with transparent background istead of white one. -- 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 months

5
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 January 2012