December 2012 - jbosstools-issues

[JBoss JIRA] (JBIDE-11121) Generate target platforms for JBT/JBDS SOA Tooling which include: JBT/JBDS Core TP + last stable Core milestone

by Nick Boldt (JIRA)

Nick Boldt created JBIDE-11121: ---------------------------------- Summary: Generate target platforms for JBT/JBDS SOA Tooling which include: JBT/JBDS Core TP + last stable Core milestone Key: JBIDE-11121 URL: https://issues.jboss.org/browse/JBIDE-11121 Project: Tools (JBoss Tools) Issue Type: Bug Components: SOA Tooling Affects Versions: 3.3.0.Beta1-soa Reporter: Nick Boldt Assignee: Douglas Palmer Fix For: 3.3.0.Beta1-soa Generate target platforms for JBT/JBDS SOA Tooling which include: 1. JBT Core TP + last stable JBT Core milestone. 2. JBDS Core TP + last stable JBDS Core milestone. Then, all SOA Component jobs should be rekeyed to use these new TPs when building instead of the JBT/JBDS Core ones. This includes Drools, which currently builds against Helios instead of Indigo, and Savara, which has requirements which are not as yet in the JBT/JBDS Core TPs (eg., GMF and Graphiti). -- 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

13 years, 4 months

6
22
0 / 0

[JBoss JIRA] (JBDS-2413) remove all references to staging site just before GA

by Nick Boldt (JIRA)

Nick Boldt created JBDS-2413: -------------------------------- Summary: remove all references to staging site just before GA Key: JBDS-2413 URL: https://issues.jboss.org/browse/JBDS-2413 Project: Developer Studio (JBoss Developer Studio) Issue Type: Bug Security Level: Public (Everyone can see) Components: Build, central Affects Versions: 6.0.0.CR1 Reporter: Nick Boldt Assignee: Nick Boldt Priority: Blocker Fix For: 6.0.0.CR1 Need to s#/6.0-staging/#/6.0/#g in JBDS SVN tree so we publish pointing at the correct URLs. -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira

13 years, 4 months

1
3
0 / 0

[JBoss JIRA] (JBDS-2426) Fail to build sources (missing sources/extras)

by Mickael Istria (JIRA)

Mickael Istria created JBDS-2426: ------------------------------------ Summary: Fail to build sources (missing sources/extras) Key: JBDS-2426 URL: https://issues.jboss.org/browse/JBDS-2426 Project: Developer Studio (JBoss Developer Studio) Issue Type: Bug Security Level: Public (Everyone can see) Components: Build Affects Versions: 6.1.0.Alpha1 Reporter: Mickael Istria Assignee: Nick Boldt Priority: Blocker Fix For: 6.1.0.Alpha1 See http://jenkins.mw.lab.eng.bos.redhat.com/hudson/job/devstudio-6.0_trunk.u... Source build fails because sources/extras folder is missing. -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira

13 years, 4 months

2
2
0 / 0

[JBoss JIRA] (JBIDE-13251) Prepare JBT Central for 4.0.0.Final

by Nick Boldt (JIRA)

Nick Boldt created JBIDE-13251: ---------------------------------- Summary: Prepare JBT Central for 4.0.0.Final Key: JBIDE-13251 URL: https://issues.jboss.org/browse/JBIDE-13251 Project: Tools (JBoss Tools) Issue Type: Bug Components: central, project-examples Affects Versions: 4.0.0.CR1 Reporter: Nick Boldt Assignee: Nick Boldt Fix For: 4.0.0.Final These files in the jbosstools-central repo need to be tweaked in prep for Final release, so they'll point at http://download.jboss.org/jbosstools/updates/stable/juno/ instead of http://download.jboss.org/jbosstools/updates/development/juno/ {quote} ./central/plugins/org.jboss.tools.central.discovery/plugin.xml ./central/README.Central.milestone.testing.txt ./examples/plugins/org.jboss.tools.project.examples/pom.xml ./examples/plugins/org.jboss.tools.project.examples/src/org/jboss/tools/project/examples/configurators/DefaultJBossCentralConfigurator.java {quote} -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira

13 years, 4 months

1
3
0 / 0

[JBoss JIRA] (JBIDE-13247) Inadequate content of web.xml in new created CDI project

by Tomas Remes (JIRA)

Tomas Remes created JBIDE-13247: ----------------------------------- Summary: Inadequate content of web.xml in new created CDI project Key: JBIDE-13247 URL: https://issues.jboss.org/browse/JBIDE-13247 Project: Tools (JBoss Tools) Issue Type: Bug Components: CDI Affects Versions: 4.0.0.CR1 Environment: JBDS 6.0.0.CR1c Reporter: Tomas Remes Assignee: Alexey Kazakov Priority: Minor Create new CDI Web project in JBDS 6.0.0.CR1c and you'll get following web.xml: {noformat} <welcome-file-list> <welcome-file>index.html</welcome-file> <welcome-file>index.htm</welcome-file> <welcome-file>index.jsp</welcome-file> <welcome-file>default.html</welcome-file> <welcome-file>default.htm</welcome-file> <welcome-file>default.jsp</welcome-file> </welcome-file-list> <servlet> <servlet-name>Faces Servlet</servlet-name> <servlet-class>javax.faces.webapp.FacesServlet</servlet-class> <load-on-startup>1</load-on-startup> </servlet> <servlet-mapping> <servlet-name>Faces Servlet</servlet-name> <url-pattern>*.seam</url-pattern> </servlet-mapping> {noformat} IMHO there should be no ".seam" url pattern since that has nothing to do with Seam. Probably jsf would be better. Second thing is that there are no files like those specified in welcome list section. So it generates unnecessary warnings and would be better to remove it or generate these files along with project generation. -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira

13 years, 4 months

2
3
0 / 0

[JBoss JIRA] (JBIDE-13242) Seam 2.3: seam-gen generated project, JBDS reports missing files referenced from view-id in pages.xml

by Marek Novotny (JIRA)

Marek Novotny created JBIDE-13242: ------------------------------------- Summary: Seam 2.3: seam-gen generated project, JBDS reports missing files referenced from view-id in pages.xml Key: JBIDE-13242 URL: https://issues.jboss.org/browse/JBIDE-13242 Project: Tools (JBoss Tools) Issue Type: Feature Request Components: Seam 2 Affects Versions: 4.0.0.Beta2 Environment: Seam.2.3.0, JBDS 5.0.1.GA or JBDS 6.0.0.Beta2a Reporter: Marek Novotny Assignee: Alexey Kazakov After importing and building a Seam 2.3 seam-gen generated project in JBDS, it reports missing files referenced from view-id in pages.xml and in somEntity.page.xml files. This works OK for a Seam project created in JBDS and for a Maven project imported to JBDS. How reproducible: Import a seam-gen generated EAR project, check pages.xml. Steps to Reproduce: 1. Create a seam-gen EAR project. 2. Import into JBDS. 3. Open pages.xml, make a change (to trigger build). Actual results: On lines referencing a view-id, like <redirect view-id="/home.xhtml"/> JBDS shows an error saying: Cannot find target resource: "/home.xhtml" -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira

13 years, 4 months

2
1
0 / 0

[JBoss JIRA] (JBIDE-13243) Create Recursive XML Text Source Test

by Andrej Podhradsky (JIRA)

Andrej Podhradsky created JBIDE-13243: ----------------------------------------- Summary: Create Recursive XML Text Source Test Key: JBIDE-13243 URL: https://issues.jboss.org/browse/JBIDE-13243 Project: Tools (JBoss Tools) Issue Type: Task Environment: Teiid Designer 8.x Reporter: Andrej Podhradsky Assignee: Andrej Podhradsky The test will include: <ul> <li>Importing an XML schema</li> <li>Modeling recursive XML documents</li> <li>Setting up a connection to a text source</li> <li>Using the TEXTTABLE function to access the data in a relational fashion</li> <li>Creating and deploying a VDB</li> <li>Executing queries that return XML documents</li> </ul> -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira

13 years, 4 months

1
1
0 / 0

[JBoss JIRA] (JBIDE-13250) Wrong connection pre-selected when creating server adapter for application

by Stefan Bunciak (JIRA)

Stefan Bunciak created JBIDE-13250: -------------------------------------- Summary: Wrong connection pre-selected when creating server adapter for application Key: JBIDE-13250 URL: https://issues.jboss.org/browse/JBIDE-13250 Project: Tools (JBoss Tools) Issue Type: Bug Components: JBossAS/Servers, openshift Affects Versions: 4.0.0.CR1 Reporter: Stefan Bunciak Assignee: Andre Dietisheim Priority: Critical Attachments: wcon1.png, wcon2.png, wcon3.png -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira

13 years, 4 months

2
6
0 / 0

[JBoss JIRA] (JBIDE-12592) El is not revalidated in java comments

by Alexey Kazakov (JIRA)

Alexey Kazakov created JBIDE-12592: -------------------------------------- Summary: El is not revalidated in java comments Key: JBIDE-12592 URL: https://issues.jboss.org/browse/JBIDE-12592 Project: Tools (JBoss Tools) Issue Type: Bug Components: common/jst/core Affects Versions: 4.0.0.Alpha1 Environment: Juno Reporter: Alexey Kazakov Assignee: Alexey Kazakov Fix For: 4.0.0.Alpha2 1. Create the following class: {code} package test; import javax.enterprise.inject.Produces; import javax.inject.Named; public class Bean_Broken { public void foo() { String s = "#{string.ss}"; String s2 = "#{string.ss}"; } @Named @Produces public String string() { return ""; } } {code} 2. Both ELs are marked as a problem 3. Copy String s2 = "#{string.ss}"; 4. Delete it. 5. Past String s2 = "#{string.ss}"; 6. There is no validation problem on the second EL. 7. Add " " to the second string: String s2 = "#{string.ss} "; 8. The EL has a problem annotation now. -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira

13 years, 4 months

2
5
0 / 0

[JBoss JIRA] (JBIDE-13249) Improve MDB support

by Clebert Suconic (JIRA)

Clebert Suconic created JBIDE-13249: --------------------------------------- Summary: Improve MDB support Key: JBIDE-13249 URL: https://issues.jboss.org/browse/JBIDE-13249 Project: Tools (JBoss Tools) Issue Type: Feature Request Components: ejb3 Reporter: Clebert Suconic Assignee: Rob Stryker I have recently tried creating an MDB and it seems out of date. It's not adding any annotations and not asking the user for any parameters. You could do something like this: - Ask what provider is going to be used... Ask what's the queue name to be used What Resource Adapter's name. (It would be great if you could inspect the server being used here for the RA's names. Each hornetq pooled connection factory will be a resource adapter name BTW). What Queue Name you could also provide additional activation properties by either selecting a list of providers. Or even better you could inspect the list of available activation properties, so it would be more generic. -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira

13 years, 4 months

1
0
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 December 2012