September 2011 - jbosstools-issues

[JBoss JIRA] Created: (JBIDE-9311) Implementation of the publisher has undesirable side-effect possibilities

by Rob Stryker (JIRA)

Implementation of the publisher has undesirable side-effect possibilities ------------------------------------------------------------------------- Key: JBIDE-9311 URL: https://issues.jboss.org/browse/JBIDE-9311 Project: Tools (JBoss Tools) Issue Type: Task Components: JBossAS Reporter: Rob Stryker Assignee: Rob Stryker Some parts of the publishing code create a callback handler on "/" in the constructor. This leads an implementation of makeDirIfRequired to potentially attempt to create folders above the server home or targeted deployment directory when they should not be able to do this. In some circumstances, attempts to create the root folder are made. This should not be occurring. -- This message is automatically generated by JIRA. For more information on JIRA, see: http://www.atlassian.com/software/jira

14 years, 7 months

1
2
0 / 0

[JBoss JIRA] Created: (JBIDE-8946) Unable to remove jBPM runtime

by Martin Malina (JIRA)

Unable to remove jBPM runtime ----------------------------- Key: JBIDE-8946 URL: https://issues.jboss.org/browse/JBIDE-8946 Project: Tools (JBoss Tools) Issue Type: Bug Components: runtimes Affects Versions: 3.2.1.M1 Environment: Mac OS X 10.6 Snow Leopard jbdevstudio-product-macosx-cocoa-4.1.0.v201105091943R-H400-M1.jar Reporter: Martin Malina Assignee: Snjezana Peco When you add SOA-P 5.1, it will add a jBPM runtime among other things. It's not possible to remove this runtime. All other runtimes, including Seam and Drools, can be removed without a problem. -- This message is automatically generated by JIRA. For more information on JIRA, see: http://www.atlassian.com/software/jira

14 years, 7 months

5
15
0 / 0

[JBoss JIRA] Updated: (JBDS-1819) Configure SOA-P quickstarts to be run OOTB in JBDS 4.1.1 with SOA-P 5.2

by Max Rydahl Andersen (JIRA)

[ https://issues.jboss.org/browse/JBDS-1819?page=com.atlassian.jira.plugin.... ] Max Rydahl Andersen updated JBDS-1819: -------------------------------------- Description: Need to ensure there are sample ESB quickstarts available to run cleanly with SOA-P 5.2 on JBDS 4.1.1 Was: Need to verify that all JBDS supplied sample ESB quickstarts run cleanly with SOA-P 5.2 on JBDS 4.1.1 Was: This subject comes up now and then - it would be very useful to new users to have the full set of SOA-P quickstarts configured to run OOTB from JBDS. was: Changed to: Need to verify that all JBDS supplied sample ESB quickstarts run cleanly with SOA-P 5.2 on JBDS 4.1.1 Was: This subject comes up now and then - it would be very useful to new users to have the full set of SOA-P quickstarts configured to run OOTB from JBDS. > Configure SOA-P quickstarts to be run OOTB in JBDS 4.1.1 with SOA-P 5.2 > ----------------------------------------------------------------------- > > Key: JBDS-1819 > URL: https://issues.jboss.org/browse/JBDS-1819 > Project: Developer Studio (JBoss Developer Studio) > Issue Type: Task > Security Level: Public(Everyone can see) > Components: SOA Platform > Affects Versions: 4.1.0.CR3 > Reporter: Len DiMaggio > Assignee: Brian Fitzpatrick > Fix For: 4.1.1.Final > > Attachments: bfitzpat_examples.png, product_examples.png, runtimes.png > > > Need to ensure there are sample ESB quickstarts available to run cleanly with SOA-P 5.2 on JBDS 4.1.1 > Was: > Need to verify that all JBDS supplied sample ESB quickstarts run cleanly with SOA-P 5.2 on JBDS 4.1.1 > Was: > This subject comes up now and then - it would be very useful to new users to have the full set of SOA-P quickstarts configured to run OOTB from JBDS. -- This message is automatically generated by JIRA. For more information on JIRA, see: http://www.atlassian.com/software/jira

14 years, 7 months

1
0
0 / 0

[JBoss JIRA] Created: (JBIDE-9676) NullPointer exception in SingleDeployableWorkspaceListener when project is closed in workspace

by Fisheye JIRA Integration (JIRA)

NullPointer exception in SingleDeployableWorkspaceListener when project is closed in workspace ---------------------------------------------------------------------------------------------- Key: JBIDE-9676 URL: https://issues.jboss.org/browse/JBIDE-9676 Project: Tools (JBoss Tools) Issue Type: Sub-task Affects Versions: 3.2.1.M1, 3.3.0.M1 Reporter: Fisheye JIRA Integration Fix For: 3.3.0.Final Created by Denis Golovin from Crucible comment on SingleDeployableWorkspaceListener.java line 44 https://source.jboss.org/cru/REV-JBIDE-4#c157 : Documentation for getDelta() says: {quote}Returns a resource delta, rooted at the workspace, describing the set of changes that happened to resources in the workspace. Returns null if not applicable to this type of event. Returns: the resource delta, or null if not applicable{quote} so potential NPE in this line -- This message is automatically generated by JIRA. For more information on JIRA, see: http://www.atlassian.com/software/jira

14 years, 7 months

1
0
0 / 0

[JBoss JIRA] Created: (JBIDE-9219) Split up continuous and test builds for SOA/JBDS split

by Brian Fitzpatrick (JIRA)

Split up continuous and test builds for SOA/JBDS split ------------------------------------------------------ Key: JBIDE-9219 URL: https://issues.jboss.org/browse/JBIDE-9219 Project: Tools (JBoss Tools) Issue Type: Sub-task Components: bpel, bpm, drools, esb, jbpm, modeshape, pi4soa, Savara, smooks, teiid Affects Versions: 3.3.0.M1 Reporter: Brian Fitzpatrick Assignee: Nick Boldt Fix For: 3.3.0.M2 This arose in an e-mail from Nick: "Should we be splitting the cont's and test builds apart so they don't include the SOA components in the Core builds? Realize that I split up the aggregate + JBDS update site builds, but not the all-in-one tests job or the "does everything compile?" jobs." I think the answer is "yes" we need to do these things. The upside is that it should speed up the component builds on both sides of the equation. The downside is that it means more work for Nick and/or Doug. -- This message is automatically generated by JIRA. For more information on JIRA, see: http://www.atlassian.com/software/jira

14 years, 7 months

3
33
0 / 0

[JBoss JIRA] Created: (JBIDE-9029) publish SOA Tooling aggregate nightly / milestone sites onto download.jboss.org

by Nick Boldt (JIRA)

publish SOA Tooling aggregate nightly / milestone sites onto download.jboss.org ------------------------------------------------------------------------------- Key: JBIDE-9029 URL: https://issues.jboss.org/browse/JBIDE-9029 Project: Tools (JBoss Tools) Issue Type: Sub-task Components: updatesite Affects Versions: 3.3.0.M2 Reporter: Nick Boldt Assignee: Nick Boldt I assume we'll do something like: Core: http://download.jboss.org/jbosstools/updates/nightly/trunk SOA Tooling: http://download.jboss.org/jbosstools/updates/nightly/soa-tooling/trunk And, for the next milestone: Core: http://download.jboss.org/jbosstools/updates/development/indigo/ SOA Tooling: http://download.jboss.org/jbosstools/updates/development/soa-tooling/indigo/ And, once it's available in JBDS, we'll composite the sites together here: http://devstudio.jboss.com/updates/5.0/staging/ and http://devstudio.jboss.com/updates/5.0/ Does that make sense? -- This message is automatically generated by JIRA. For more information on JIRA, see: http://www.atlassian.com/software/jira

14 years, 7 months

3
18
0 / 0

[JBoss JIRA] Created: (JBIDE-9193) Wrong line number in OpenOn for injection of bean declared in seam config.

by Alexey Kazakov (JIRA)

Wrong line number in OpenOn for injection of bean declared in seam config. -------------------------------------------------------------------------- Key: JBIDE-9193 URL: https://issues.jboss.org/browse/JBIDE-9193 Project: Tools (JBoss Tools) Issue Type: Bug Components: cdi (jsr-299) Affects Versions: 3.3.0.M2 Reporter: Alexey Kazakov Assignee: Viacheslav Kabanovich Fix For: 3.3.0.M3 Attachments: screen.png EXECUTE: Create CDI project with Seam Config support EXECUTE: Add the following files to the project: {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:Resource> <s:Produces/> <r:SalesQualifier/> <value>Text</value> </r:Resource> </beans> {code} {code} package org.example.reports; import javax.inject.Inject; public class Report { public @Inject @SalesQualifier Resource path; } {code} {code} package org.example.reports; public class Resource { } {code} EXECUTE: Ctrl+Click on public @Inject @SalesQualifier Resource path; FAILURE: There is "Open Resource in beans.xml at line 6. ASSERT: There is "Open Resource in beans.xml at line 7. -- This message is automatically generated by JIRA. For more information on JIRA, see: http://www.atlassian.com/software/jira

14 years, 7 months

2
3
0 / 0

[JBoss JIRA] Created: (JBIDE-9186) Seam Config XML: Incremental validation does not work

by Alexey Kazakov (JIRA)

Seam Config XML: Incremental validation does not work ----------------------------------------------------- Key: JBIDE-9186 URL: https://issues.jboss.org/browse/JBIDE-9186 Project: Tools (JBoss Tools) Issue Type: Bug Components: cdi (jsr-299) Affects Versions: 3.3.0.M2 Reporter: Alexey Kazakov Assignee: Viacheslav Kabanovich Fix For: 3.3.x Suppose we have the following 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> <s:modifies/> </r:Report> </beans> {code} But no org.example.reports.Report in the project classpath. Seam config validation will mark <r:Report> as unknown type. That's correct. Create org.example.reports.Report class. The seam-config.xml should be re-validated and the problem marker disappear. -- This message is automatically generated by JIRA. For more information on JIRA, see: http://www.atlassian.com/software/jira

14 years, 7 months

3
3
0 / 0

[JBoss JIRA] Created: (JBIDE-6517) Resolve member values of annotations to qualified names, instead of reducing them to simple names

by Viacheslav Kabanovich (JIRA)

Resolve member values of annotations to qualified names, instead of reducing them to simple names ------------------------------------------------------------------------------------------------- Key: JBIDE-6517 URL: https://jira.jboss.org/browse/JBIDE-6517 Project: Tools (JBoss Tools) Issue Type: Bug Components: cdi (jsr-299) Reporter: Viacheslav Kabanovich Assignee: Viacheslav Kabanovich Fix For: 3.2.x Injection point @Inject @PayBy(FirstPaymentMethod.CASH) AsynchronousPaymentProcessor cashPaymentProcessor; should not accept bean @PayBy(SecondPaymentMethod.CASH) @ApplicationScoped class SecondPaymentProcessor implements AsynchronousPaymentProcessor {} Test in org.jboss.tools.cdi.core.test.tck.QualifierWithMembersTest.testQualifierCoincidingSimpleNameInInjectingBeanAndCoincidingSimpleNameInInjectedBeanResolved() should pass. -- 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, 7 months

3
6
0 / 0

[JBoss JIRA] Created: (JBIDE-9348) merge correlative bpel project examples to one bpel project example

by Feng Qian (JIRA)

merge correlative bpel project examples to one bpel project example ------------------------------------------------------------------- Key: JBIDE-9348 URL: https://issues.jboss.org/browse/JBIDE-9348 Project: Tools (JBoss Tools) Issue Type: Bug Components: bpel Affects Versions: 3.3.0.M2 Reporter: Feng Qian Assignee: Feng Qian Fix For: 3.3.0.M3 For now, there are some bpel project examples, one will call another. I found we can put them into one project example. Do it. -- This message is automatically generated by JIRA. For more information on JIRA, see: http://www.atlassian.com/software/jira

14 years, 7 months

5
13
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 September 2011