September 2009 - jbosstools-issues

[JBoss JIRA] Created: (JBIDE-4870) Support suggestions for JSF DataModel when created inline in seam

by Cody Lerum (JIRA)

Support suggestions for JSF DataModel when created inline in seam ----------------------------------------------------------------- Key: JBIDE-4870 URL: https://jira.jboss.org/jira/browse/JBIDE-4870 Project: Tools (JBoss Tools) Issue Type: Feature Request Components: Seam Affects Versions: 3.1.0.M3 Environment: Seam 2.2.0, Richfaces 3.3.1, Tools 3.1M3, Eclipse 3.5 Reporter: Cody Lerum Priority: Minor When editing an xhtml file if I create a rich:dataTable and use an object outjected via @DataModel then Tools will suggest the possible values for auto-completion. However, if I create the DataModel inline by wrapping a collection like this: <rich:dataTable id="banList" var="ban" value="#{dataModels.getDataModel(summaryBillingAccountNumber.billingAccountNumbers)}" "> .... </rich:dataTable> Then if I access the value "ban" through EL like <h:outputText value="#{ban.name}" /> the suggestions after I type "ban." are for the DataModel object not the ban object. It would be nice if the behavior was the same. -- 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

16 years, 1 month

2
2
0 / 0

[JBoss JIRA] Created: (JBIDE-4855) TestNG Tests don't work when the JBoss BIRT Integration facet is added to a Seam project

by Snjezana Peco (JIRA)

TestNG Tests don't work when the JBoss BIRT Integration facet is added to a Seam project ---------------------------------------------------------------------------------------- Key: JBIDE-4855 URL: https://jira.jboss.org/jira/browse/JBIDE-4855 Project: Tools (JBoss Tools) Issue Type: Bug Components: birt Affects Versions: 3.1.0.M2 Reporter: Snjezana Peco Assignee: Snjezana Peco Fix For: 3.1.0.M4 If you create a Seam 2.1.1.GA default project in JBDS 2.0.0.GA (ear project) and place jboss-birt.jar in the classpath and create a new Seam action, then go to your Project-Name-test and run the created test RunAs->TestNG Test the test throws an exception: FAILED CONFIGURATION: @BeforeSuite startSeam java.lang.RuntimeException: java.net.MalformedURLException: no !/ in spec at org.jboss.virtual.plugins.context.AbstractURLHandler.initCacheLastModified(AbstractURLHandler.java:76) at org.jboss.virtual.plugins.context.AbstractURLHandler.<init>(AbstractURLHandler.java:65) at org.jboss.virtual.plugins.context.jar.SynthenticDirEntryHandler.<init>(SynthenticDirEntryHandler.java:72) at org.jboss.virtual.plugins.context.jar.AbstractJarHandler.buildParents(AbstractJarHandler.java:244) at org.jboss.virtual.plugins.context.jar.AbstractJarHandler.initJarFile(AbstractJarHandler.java:179) at org.jboss.virtual.plugins.context.jar.JarHandler.<init>(JarHandler.java:63) at org.jboss.virtual.plugins.context.jar.JarContext.createVirtualFileHandler(JarContext.java:85) at org.jboss.virtual.plugins.context.jar.JarContext.<init>(JarContext.java:58) at org.jboss.virtual.plugins.context.jar.JarContextFactory.getVFS(JarContextFactory.java:51) at org.jboss.virtual.VFS.getVFS(VFS.java:132) at org.jboss.virtual.VFS.getRoot(VFS.java:146) at org.jboss.embedded.DeploymentGroup.getVirtualFile(DeploymentGroup.java:175) at org.jboss.embedded.DeploymentGroup.add(DeploymentGroup.java:165) at org.jboss.embedded.DeploymentGroup.addBaseResource(DeploymentGroup.java:369) at org.jboss.embedded.DeploymentGroup.addResourceBases(DeploymentGroup.java:398) at org.jboss.embedded.Bootstrap.deployResourceBases(Bootstrap.java:288) at org.jboss.seam.mock.EmbeddedBootstrap.startAndDeployResources(EmbeddedBootstrap.java:15) at org.jboss.seam.mock.AbstractSeamTest.startJbossEmbeddedIfNecessary(AbstractSeamTest.java:1024) at org.jboss.seam.mock.AbstractSeamTest.startSeam(AbstractSeamTest.java:915) at org.jboss.seam.mock.SeamTest.startSeam(SeamTest.java:58) Caused by: java.net.MalformedURLException: no !/ in spec at java.net.URL.<init>(URL.java:601) at java.net.URL.<init>(URL.java:464) at java.net.URL.<init>(URL.java:413) at java.net.JarURLConnection.parseSpecs(JarURLConnection.java:161) at java.net.JarURLConnection.<init>(JarURLConnection.java:144) at sun.net.www.protocol.jar.JarURLConnection.<init>(JarURLConnection.java:61) at sun.net.www.protocol.jar.Handler.openConnection(Handler.java:24) at java.net.URL.openConnection(URL.java:943) at org.jboss.virtual.plugins.context.AbstractURLHandler.initCacheLastModified(AbstractURLHandler.java:72) ... 34 more ... Removed 15 stack frames SKIPPED CONFIGURATION: @BeforeClass setupClass SKIPPED CONFIGURATION: @BeforeMethod begin SKIPPED CONFIGURATION: @AfterMethod end SKIPPED CONFIGURATION: @AfterClass cleanupClass SKIPPED: test_actionMethod -- 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

16 years, 1 month

2
2
0 / 0

[JBoss JIRA] Created: (JBIDE-4200) Change qualifiers on zips and jars to support Milestones and RCs instead of Alphas, Betas, CRs, GA

by Nick Boldt (JIRA)

Change qualifiers on zips and jars to support Milestones and RCs instead of Alphas, Betas, CRs, GA -------------------------------------------------------------------------------------------------- Key: JBIDE-4200 URL: https://jira.jboss.org/jira/browse/JBIDE-4200 Project: Tools (JBoss Tools) Issue Type: Bug Components: Build/Releng Affects Versions: 3.1.0.M1 Reporter: Nick Boldt Priority: Minor Jars and zips currently look like 3.1.0.Alpha1-yyyymmddHHMM-H### To support a more Eclipse-like naming convention involving milestones, we need to switch to: 3.1.0.vyyyymmddHHMM-PP-H###-T Where PP = phase, eg., M1, H### = Hudson build number, and T = type, eg., N, I, S, or R. (Only N and R are currently supported.) This will guarantee that regardless of where a build is produced (ie., in whatever phase) it can always be installed onto an older version because the qualifier will always increase w/ time, regardless of additional suffixes. -- 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

16 years, 1 month

3
18
0 / 0

[JBoss JIRA] Created: (JBIDE-3506) Add JSF Capabilities Dialog doesn't pick up server runtime from selected Dynamic Web Project

by Denis Golovin (JIRA)

Add JSF Capabilities Dialog doesn't pick up server runtime from selected Dynamic Web Project -------------------------------------------------------------------------------------------- Key: JBIDE-3506 URL: https://jira.jboss.org/jira/browse/JBIDE-3506 Project: Tools (JBoss Tools) Issue Type: Bug Affects Versions: 3.0.0.cr1 Reporter: Denis Golovin Assignee: Denis Golovin Fix For: 3.1.0 It should get runtime from selected project if it is Dynamic Web Project -- 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

16 years, 1 month

2
8
0 / 0

[JBoss JIRA] Created: (JBIDE-4690) Add Maven Portlet library provider

by Snjezana Peco (JIRA)

Add Maven Portlet library provider ---------------------------------- Key: JBIDE-4690 URL: https://jira.jboss.org/jira/browse/JBIDE-4690 Project: Tools (JBoss Tools) Issue Type: Sub-task Components: maven, Portal Affects Versions: 3.1.0.M2 Reporter: Snjezana Peco Assignee: Snjezana Peco Fix For: 3.1.0.M3 -- 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

16 years, 1 month

1
2
0 / 0

[JBoss JIRA] Created: (JBIDE-4833) Reduce a number of jars in org.jboss.tools.jst.jsp.test\projects.

by Alexey Kazakov (JIRA)

Reduce a number of jars in org.jboss.tools.jst.jsp.test\projects. ----------------------------------------------------------------- Key: JBIDE-4833 URL: https://jira.jboss.org/jira/browse/JBIDE-4833 Project: Tools (JBoss Tools) Issue Type: Task Components: QA Affects Versions: 3.1.0.M3 Reporter: Alexey Kazakov Assignee: Victor Rubezhny Fix For: 3.1.0.M4 There is not any need to have such many copies of the same jars for these projects. Please remove unnessary files and copy needed jars from one place instead of having many copies in SVN. -- 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

16 years, 1 month

2
1
0 / 0

[JBoss JIRA] Created: (JBDS-848) Updatesite has bad naming/versions/categorizations

by Max Rydahl Andersen (JIRA)

Updatesite has bad naming/versions/categorizations -------------------------------------------------- Key: JBDS-848 URL: https://jira.jboss.org/jira/browse/JBDS-848 Project: JBoss Developer Studio Issue Type: Bug Components: Build Affects Versions: 2.1.0 Reporter: Max Rydahl Andersen Assignee: Nick Boldt Priority: Blocker Fix For: 2.1.0 See attached image. This is when updating JBDS 2.0.0.GA to JBDS 2.1. "JBoss Developer Studio" is already installed and it has version 3.0.2. I guess 3.0.2 is a sideeffect of richfaces build determining the version. But ignoring that part Developer Studio should be updated to a newer version to accomodate for updated branding right ? Furthermore TPTP is not put under the "supporting" category forcing installation of TPTP if selecting the main node. And JBoss BIRT are not supposed to be in here. -- 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

16 years, 1 month

2
4
0 / 0

[JBoss JIRA] Created: (JBIDE-4848) The Content Assist doesn't show proposals for the attribute names (The issue is found by org.jboss.tools.jst.jsp.test.ca.JsfJspJbide1717Test.testJstJspJbide1717() JUnit Test Case)

by Victor Rubezhny (JIRA)

The Content Assist doesn't show proposals for the attribute names (The issue is found by org.jboss.tools.jst.jsp.test.ca.JsfJspJbide1717Test.testJstJspJbide1717() JUnit Test Case) ----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- Key: JBIDE-4848 URL: https://jira.jboss.org/jira/browse/JBIDE-4848 Project: Tools (JBoss Tools) Issue Type: Bug Components: jsp/jsf/xml source editing Affects Versions: 3.1.0.M3 Reporter: Victor Rubezhny Assignee: Victor Rubezhny Fix For: 3.1.0.M3, 3.1.0.M4 The issue is found by org.jboss.tools.jst.jsp.test.ca.JsfJspJbide1717Test.testJstJspJbide1717() JUnit Test Case. The Content Assist doesn't show proposals for the attribute names. TEST CASE: EXECUTE: Create a jsf kickstart project EXECUTE: Open /pages/greeting.jsp file in JSP Text Editor EXETUCE: Find the <h:outputText ...> tag in the text and insert the following text right before this place: <h:outputText value="#{msg.greeting}" | /> Note: Do not type in the "|"-character, just put the cursor into this position. EXECUTE: Put the cursor in the position noted above (the cursor must be rounded with two space-chars) and press Ctrl-Space to invoke the CA. ASSERT: the attribute name proposals are shown (except the names of existing attributes) -- 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

16 years, 1 month

2
2
0 / 0

[JBoss JIRA] Created: (JBIDE-4861) Remove old KB plug-ins from build and SVN.

by Alexey Kazakov (JIRA)

Remove old KB plug-ins from build and SVN. ------------------------------------------ Key: JBIDE-4861 URL: https://jira.jboss.org/jira/browse/JBIDE-4861 Project: Tools (JBoss Tools) Issue Type: Task Components: Cleanup, common Reporter: Alexey Kazakov Assignee: Alexey Kazakov Fix For: 3.1.0.M4 Old KB plug-in is not used any more. So let's remove it. -- 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

16 years, 1 month

1
1
0 / 0

[JBoss JIRA] Created: (JBIDE-4802) Undeclared dependency from o.j.t.common.model to o.j.t.jsf.ui

by Daniel Serodio (JIRA)

Undeclared dependency from o.j.t.common.model to o.j.t.jsf.ui ------------------------------------------------------------- Key: JBIDE-4802 URL: https://jira.jboss.org/jira/browse/JBIDE-4802 Project: Tools (JBoss Tools) Issue Type: Bug Components: Build/Releng Affects Versions: LATER Environment: Eclipse Galileo (Reporting package from EPP) on Windows XP SP3 and Sun Java 1.6.0_16-b01 Reporter: Daniel Serodio I installed only the Hibernate support from JBoss Tools, since it's all that I need, but when I started Eclipse for the first time after install, I got the following error from the org.jboss.tools.common.model: eclipse.buildId=I20090611-1540 java.version=1.6.0_16 java.vendor=Sun Microsystems Inc. BootLoader constants: OS=win32, ARCH=x86, WS=win32, NL=pt_BR Framework arguments: -product org.eclipse.epp.package.reporting.product Command-line arguments: -os win32 -ws win32 -arch x86 -product org.eclipse.epp.package.reporting.product Info Thu Aug 20 16:01:19 BRT 2009 ClassLoaderUtil:activate: Cannot find required plugin org.jboss.tools.jsf.ui Besides not being declared in the plugin descriptor (otherwise I wouln't have been able to install it), a "model" package depending on a UI package smells like cyclic dependency... -- 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

16 years, 1 month

4
9
0 / 0

2025

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

2009

2008

2007

2006

jbosstools-issues September 2009