March 2012 - jbosstools-issues - Jboss List Archives

[JBoss JIRA] Created: (JBIDE-9087) Support of Bundles bean in CDI projects with Seam International module.

by Alexey Kazakov (JIRA)

Support of Bundles bean in CDI projects with Seam International module. ----------------------------------------------------------------------- Key: JBIDE-9087 URL: https://issues.jboss.org/browse/JBIDE-9087 Project: Tools (JBoss Tools) Issue Type: Feature Request Components: cdi (jsr-299) Reporter: Alexey Kazakov Assignee: Victor Rubezhny Fix For: 3.3.0.M3 EXECUTE: Import Seam-booking example (See http://seamframework.org/Seam3/Contribute for details how to get this example from Seam git repository. EXECUTE: Open src/main/webapp/home.xhtml ASSERT: Ctrl+Space for #{bundles.messages.|} should show proposals for messages_*.properties resource bundle. -- This message is automatically generated by JIRA. For more information on JIRA, see: http://www.atlassian.com/software/jira

14 years

5
9
0 / 0

[JBoss JIRA] Created: (JBIDE-9132) "Explore" on server in remote mode opens explorer that shows filesystem of local server

by Andre Dietisheim (JIRA)

"Explore" on server in remote mode opens explorer that shows filesystem of local server ---------------------------------------------------------------------------------------- Key: JBIDE-9132 URL: https://issues.jboss.org/browse/JBIDE-9132 Project: Tools (JBoss Tools) Issue Type: Bug Components: JBossAS Affects Versions: 3.3.0.M1 Reporter: Andre Dietisheim Assignee: Rob Stryker Fix For: 3.3.x -- This message is automatically generated by JIRA. For more information on JIRA, see: http://www.atlassian.com/software/jira

14 years

4
6
0 / 0

[JBoss JIRA] Created: (JBIDE-9187) Seam Config XML: OpenOn for <s:Inject/>

by Alexey Kazakov (JIRA)

Seam Config XML: OpenOn for <s:Inject/> --------------------------------------- Key: JBIDE-9187 URL: https://issues.jboss.org/browse/JBIDE-9187 Project: Tools (JBoss Tools) Issue Type: Feature Request Components: cdi (jsr-299) Reporter: Alexey Kazakov Assignee: Daniel Azarov Fix For: 3.3.x EXECUTE: Create CDI project with Seam Config support EXECUTE: Create org.example.Report class: {code} package org.example.reports; import javax.enterprise.inject.Produces; public class Report { public String filename; public String datasource; @Produces public String foo() { return "1"; } @Produces public String foo1() { return "2"; } } {code} EXECUTE: Add the following code to seam-beans.xml: {code} <?xml version="1.0" encoding="UTF-8"?> <beans xmlns="http://java.sun.com/xml/ns/javaee" xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance" xmlns:s="urn:java:ee" xmlns:r="urn:java:org.example.reports"> <r:Report> <r:datasource> <s:Inject/> </r:datasource> </r:Report> </beans> {code} EXECUTE: Ctrl+Click on <s:Inject/> ASSERT: The list of all the eligible beans appears. -- This message is automatically generated by JIRA. For more information on JIRA, see: http://www.atlassian.com/software/jira

14 years

3
5
0 / 0

[JBoss JIRA] Created: (JBIDE-9195) Filter for validation problem preferences

by Alexey Kazakov (JIRA)

Filter for validation problem preferences ----------------------------------------- Key: JBIDE-9195 URL: https://issues.jboss.org/browse/JBIDE-9195 Project: Tools (JBoss Tools) Issue Type: Feature Request Components: common Reporter: Alexey Kazakov Assignee: Viacheslav Kabanovich Fix For: 3.3.x It would be good to have some filter in our validation preferences pages like JDT has for compilation problem preferences. See the attached screenshot. -- This message is automatically generated by JIRA. For more information on JIRA, see: http://www.atlassian.com/software/jira

14 years

4
9
0 / 0

[JBoss JIRA] Created: (JBIDE-9203) Plain text value for translation is chosen wrongly when translating .jsp page via Externalize Selected String

by Vlado Pakan (JIRA)

Plain text value for translation is chosen wrongly when translating .jsp page via Externalize Selected String ------------------------------------------------------------------------------------------------------------- Key: JBIDE-9203 URL: https://issues.jboss.org/browse/JBIDE-9203 Project: Tools (JBoss Tools) Issue Type: Bug Components: Visual Page Editor core Affects Versions: 3.3.0.M2 Environment: Linux 32bit, Sun JDK 1.6.0_25, jbdevstudio-product-linux-gtk-5.0.0.v201106172137N-H681-M2. Reporter: Vlado Pakan Assignee: Yahor Radtsevich Fix For: 3.3.0.M3 1. Create JSF kick start project 2. Open hello.jsp page 3. Insert "Plain" text as shown on picture below and choose Externalize selected string toolbar button In the Externalize String dialog is set text "Plain" as Property value but together with special characters <EOL> !externalizestringdialog.png! 4. Choose next>, next>, OK. (Use default values) hello.jsp page look like this. <EOL> characters around "Plain" text were removed/replaced with reference to .properties file: !externalizestringresult.png! hello.properties has wrong contnent: !propertiesfile.png! -- This message is automatically generated by JIRA. For more information on JIRA, see: http://www.atlassian.com/software/jira

14 years

5
25
0 / 0

[JBoss JIRA] Created: (JBIDE-9244) Default bean Validation

by Viacheslav Kabanovich (JIRA)

Default bean Validation ----------------------- Key: JBIDE-9244 URL: https://issues.jboss.org/browse/JBIDE-9244 Project: Tools (JBoss Tools) Issue Type: Sub-task Components: cdi (jsr-299) Affects Versions: 3.3.0.M2 Reporter: Viacheslav Kabanovich Assignee: Viacheslav Kabanovich Fix For: 3.3.0.M3 1. Default producer fields are not supported on normal scoped beans. - it is a deployment error. 2. Two default beans with the same type and qualifiers is a deployment error. -- This message is automatically generated by JIRA. For more information on JIRA, see: http://www.atlassian.com/software/jira

14 years

10
18
0 / 0

[JBoss JIRA] Created: (JBIDE-7279) Provide support for JAX-WS 2.2 APIs

by Lukas Jungmann (JIRA)

Provide support for JAX-WS 2.2 APIs ----------------------------------- Key: JBIDE-7279 URL: https://jira.jboss.org/browse/JBIDE-7279 Project: Tools (JBoss Tools) Issue Type: Feature Request Components: Webservices Affects Versions: 3.2.0.Beta1 Reporter: Lukas Jungmann Assignee: Brian Fitzpatrick [this is to be checked against JBossAS 6.0M5 or newer] for a project which has target runtime set to JBossAS6/uses JBossWS 3.3.x -user should be allowed to set JAX-WS spec version in a top-down web service and web service client wizards to 2.2 -editor should not show errors for following generated type of constructor: public Info(WebServiceFeature ... features) { super(WSDL_LOCATION, SERVICE, features); } (in the other words editor/ide has to know about APIs from $JBOSS_HOME/lib/endorsed) -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: https://jira.jboss.org/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira

14 years

4
8
0 / 0

[JBoss JIRA] (JBIDE-10968) soa tooling build can't aggregate runtime.{drools, esb, jbpm}.detector unless they're on an upstream site

by Nick Boldt (JIRA)

Nick Boldt created JBIDE-10968: ---------------------------------- Summary: soa tooling build can't aggregate runtime.{drools,esb,jbpm}.detector unless they're on an upstream site Key: JBIDE-10968 URL: https://issues.jboss.org/browse/JBIDE-10968 Project: Tools (JBoss Tools) Issue Type: Bug Components: drools, esb, jbpm, runtime detection, SOA Tooling Affects Versions: 3.3.0.Beta1, 3.3.0.Beta1-soa Reporter: Nick Boldt Assignee: Douglas Palmer Fix For: 3.3.0.Beta1, 3.3.0.Beta1-soa Max, the issue is not that they need to exist on the soa side, it's that to BUILD the soa site, they need to exist upstream first. Thus, they would need to ALSO be on the JBT Core site as well as the JBT SOA site. Or else we need some other way to get them in there, like having them move from being part of Runtime to some other "Runtime-SOA" component which only SOA builds, downstream from Runtime and JBT Core aggregation. N On 02/20/2012 11:37 AM, Max Rydahl Andersen wrote: > please open jira on this - this is a technical issue on how runtime detection should work outofthebox. > > something SOA and Core engineering team need to coordinate on. > > but yes, since the runtime detectors rely on the soa stuff they need to exist on soa side of things. > > /max > > On Feb 20, 2012, at 7:32 AM, Nick Boldt wrote: > >> The JBT SOA Tooling aggregate [1] now sources from the upstream JBT Core site [2], and does NOT use the JBT Core composite staging site [3], only the JBT SOA Tooling one [4] so as to avoid getting a mismatched set of upstream plugins (eg., a newer Runtime component in staging vs. the last pulled nightly snapshot). >> >> However, this means that the build is failing because it can't find the org.jboss.tools.runtime.{drools,esb,jbpm}.detector.feature features, as they're *not currently published* to the JBT Core nightly site [2], only the composite [3] and the individual component's staging site [5]. This may be simply an oversight, or it was done intentionally because these detectors only make sense to be in the SOA Tooling site, not in Core. >> >> To solve this we should probably put these features into the JBT Aggregate site (albeit as hidden features). Then they can be found by the SOA Tooling jobs and categorized there. >> >> Does that make sense? >> >> [1] https://hudson.qa.jboss.com/hudson/job/jbosstools-3.3_stable_branch.soa-t... >> >> [2] http://download.jboss.org/jbosstools/updates/nightly/core/3.3.indigo/ >> >> [3] http://download.jboss.org/jbosstools/builds/staging/_composite_/core/3.3.... >> >> [4] http://download.jboss.org/jbosstools/builds/staging/_composite_/soa-tooli... >> >> [5] http://download.jboss.org/jbosstools/builds/staging/jbosstools-3.3_stable... -- 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

1
10
0 / 0

[JBoss JIRA] (JBIDE-11390) publish JBT test plugins to aggregate site so SOA can use them downstream

by Nick Boldt (JIRA)

Nick Boldt created JBIDE-11390: ---------------------------------- Summary: publish JBT test plugins to aggregate site so SOA can use them downstream Key: JBIDE-11390 URL: https://issues.jboss.org/browse/JBIDE-11390 Project: Tools (JBoss Tools) Issue Type: Sub-task Components: Build/Releng, SOA Tooling, testing, updatesite Affects Versions: 3.3.0.Beta1-SOA, 3.3.0.Beta3 Reporter: Nick Boldt Assignee: Nick Boldt Fix For: 3.3.0.Beta3 Builds like runtime-soa can't run tests because they depend on upstream plugins like org.jboss.tools.runtime.test, which is published to the staging composite but NOT to an aggregate site. {code:title=http://hudson.qa.jboss.com/hudson/view/DevStudio/view/DevStudio_Trunk/job/jbosstools-3.3_trunk.component--runtime-soa/16/console} [ERROR] Failed to execute goal org.eclipse.tycho:tycho-surefire-plugin:0.14.1:test (default-test) on project org.jboss.tools.runtime.soa.test: Cannot find test suite project with Bundle-SymbolicName org.jboss.tools.runtime.test -> [Help 1] {code} So, because SOA depends on our stable site (nightly or milestone) we need a place to put these plugins and features which is DIFFERENT from the webtools, core, soa & bottests sites. -- 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

1
15
0 / 0

[JBoss JIRA] (JBIDE-11188) JBoss Tools Model Update threw NPE

by Stevo Slavic (JIRA)

Stevo Slavic created JBIDE-11188: ------------------------------------ Summary: JBoss Tools Model Update threw NPE Key: JBIDE-11188 URL: https://issues.jboss.org/browse/JBIDE-11188 Project: Tools (JBoss Tools) Issue Type: Bug Affects Versions: 3.3.0.M5 Environment: eclipse 3.7 SR2 Reporter: Stevo Slavic Priority: Minor After refresh of project in workspace NPE got thrown: {noformat} !ENTRY org.eclipse.core.jobs 4 2 2012-03-07 09:56:26.722 !MESSAGE An internal error occurred during: "JBoss Tools Model Update". !STACK 0 java.lang.NullPointerException at org.jboss.tools.common.model.impl.XModelObjectImpl.getChildByPath(XModelObjectImpl.java:331) at org.jboss.tools.common.model.filesystems.impl.Libs.updateFileSystems(Libs.java:164) at org.jboss.tools.common.model.filesystems.impl.Libs.update(Libs.java:91) at org.jboss.tools.common.model.project.ext.AbstractClassPathMonitor.update(AbstractClassPathMonitor.java:63) at org.jboss.tools.jst.web.kb.internal.scanner.ClassPathMonitor$1.run(ClassPathMonitor.java:186) at org.jboss.tools.common.model.XJob.runInWorkspace(XJob.java:178) at org.eclipse.core.internal.resources.InternalWorkspaceJob.run(InternalWorkspaceJob.java:38) at org.eclipse.core.internal.jobs.Worker.run(Worker.java:54) {noformat} -- 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
11
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