November 2010 - jbosstools-issues

[JBoss JIRA] Created: (JBIDE-7120) Server supplied JBossWS Runtime should be set as default

by Lukas Jungmann (JIRA)

Server supplied JBossWS Runtime should be set as default -------------------------------------------------------- Key: JBIDE-7120 URL: https://jira.jboss.org/browse/JBIDE-7120 Project: Tools (JBoss Tools) Issue Type: Feature Request Components: Webservices Affects Versions: 3.1.1 Reporter: Lukas Jungmann Assignee: Brian Fitzpatrick -create a new dynamic web project -set target runtime to some JBossAS server -modify project facets to contain JBoss Web Services Core => at this point user cannot simply finish the wizard - he is forced to click at least 3x 'next' to choose the JBossWS runtime he wants to use. I believe that in most cases it will be the one provided by the server, so setting it by default (and allowing user to change it if he'd like to) would simplify and speed up project creation process. -- 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

15 years, 4 months

3
5
0 / 0

[JBoss JIRA] Created: (JBIDE-2663) Bring an editing possibility to visual part of VPE

by Maxim Areshkau (JIRA)

Bring an editing possibility to visual part of VPE -------------------------------------------------- Key: JBIDE-2663 URL: https://jira.jboss.org/jira/browse/JBIDE-2663 Project: Tools (JBoss Tools) Issue Type: Feature Request Components: Visual Page Editor Affects Versions: 2.0.0.GA Reporter: Maxim Areshkau Assignee: Maxim Areshkau Fix For: 3.0.0.beta1 Bring an editing possibility to visual part of VPE. For example the slider has two values the min and the max. We should be able to edit this values in visual part. Because: it is the visual page *editor*. -- 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

15 years, 4 months

3
11
0 / 0

[JBoss JIRA] Created: (JBIDE-3798) VPE - I get mesage box - every time when I open some jsp

by Vitali Yemialyanchyk (JIRA)

VPE - I get mesage box - every time when I open some jsp -------------------------------------------------------- Key: JBIDE-3798 URL: https://jira.jboss.org/jira/browse/JBIDE-3798 Project: Tools (JBoss Tools) Issue Type: Feature Request Components: Visual Page Editor core Affects Versions: 3.0.0.CR2 Reporter: Vitali Yemialyanchyk Assignee: Maxim Areshkau Priority: Minor Attachments: screenshot-1.jpg open jsp with Visual/Source tab - get message; switch to source tab - ok; switch to Visual/Source tab - get message; -- 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

15 years, 4 months

6
19
0 / 0

[JBoss JIRA] Created: (JBIDE-6539) Fix failed tests after moving to Eclipse 3.6 and XR 1.9.2

by Denis Maliarevich (JIRA)

Fix failed tests after moving to Eclipse 3.6 and XR 1.9.2 --------------------------------------------------------- Key: JBIDE-6539 URL: https://jira.jboss.org/browse/JBIDE-6539 Project: Tools (JBoss Tools) Issue Type: Bug Components: Visual Page Editor core Affects Versions: 3.2.0.M1 Reporter: Denis Maliarevich Assignee: Denis Maliarevich Fix For: 3.2.0.M2 Fix failed tests after moving to Eclipse 3.6 and XR 1.9.2. -- 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

15 years, 4 months

5
9
0 / 0

[JBoss JIRA] Created: (JBIDE-7011) Mavenized Seam Web project can't be created using m2eclipse 0.11

by Snjezana Peco (JIRA)

Mavenized Seam Web project can't be created using m2eclipse 0.11 ---------------------------------------------------------------- Key: JBIDE-7011 URL: https://jira.jboss.org/browse/JBIDE-7011 Project: Tools (JBoss Tools) Issue Type: Bug Components: maven Affects Versions: 3.2.0.M1 Reporter: Snjezana Peco Assignee: Snjezana Peco Fix For: 3.2.0.Beta The m2eclipse Java configurator ignores compiler setting in a parent project and uses the default setting (1.4) which causes an error when creating a Java facet >= 5.0/1.5. -- 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

15 years, 4 months

3
10
0 / 0

[JBoss JIRA] Created: (JBDS-1343) ModeShape plugin needs to have its modeshape client jar replaced with the SOA-P ER3 build

by Dan Florian (JIRA)

ModeShape plugin needs to have its modeshape client jar replaced with the SOA-P ER3 build ----------------------------------------------------------------------------------------- Key: JBDS-1343 URL: https://jira.jboss.org/browse/JBDS-1343 Project: Developer Studio (JBoss Developer Studio) Issue Type: Task Components: Modeshape Reporter: Dan Florian Assignee: Dan Florian Priority: Blocker Fix For: 4.0.0.Beta1 The current ModeShape rest client jar is out-of-date. It needs to be replaced by the modeshape-client.jar being built from SOA-P. Note, the rest client jar is being replace by a different client jar that contains both the rest client and jdbc client interfaces. -- 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

15 years, 4 months

4
15
0 / 0

[JBoss JIRA] Created: (JBIDE-6984) Upgrade ModeShape Plugin To Use The Latest ModeShape JDBC Jar (Currently 2.2)

by Dan Florian (JIRA)

Upgrade ModeShape Plugin To Use The Latest ModeShape JDBC Jar (Currently 2.2) ----------------------------------------------------------------------------- Key: JBIDE-6984 URL: https://jira.jboss.org/browse/JBIDE-6984 Project: Tools (JBoss Tools) Issue Type: Task Components: modeshape Affects Versions: 3.2.0.M1 Reporter: Dan Florian Fix For: 3.2.0.Beta The ModeShape JBT plugin is currently using a manually built ModeShape project REST client jar with dependencies based on a ModeShape 2.1 snapshot release. A ModeShape JDBC jar is being built automatically by ModeShape and contains all the dependencies that the ModeShape JBT plugin needs except net.jcip.annotations. Also the ModeShape JDBC jar is significantly smaller in size. The net.jcip.annotations library is also being used by Teiid Designer so that library needs to be available from a common location within JBT and another ticket will be written to address that. Having the ModeShape JBT plugin use the JDBC jar may also benefit Teiid Designer as users of Designer may want to also use the ModeShape JDBC driver. -- 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

15 years, 4 months

2
5
0 / 0

[JBoss JIRA] Created: (JBIDE-7116) BPEL Editor not seeing message structure when imported into WSDL

by Jeff DeLong (JIRA)

BPEL Editor not seeing message structure when imported into WSDL ---------------------------------------------------------------- Key: JBIDE-7116 URL: https://jira.jboss.org/browse/JBIDE-7116 Project: Tools (JBoss Tools) Issue Type: Bug Components: bpel Affects Versions: 3.2.0.M2 Environment: JBTools3.2Beta1 Eclipse 3.6 on Mac Reporter: Jeff DeLong I have a WSDL generated from Savara. It looks like this: <wsdl:definitions name="PolicyQuoteProcessService" targetNamespace="http://www.pi4soa.org/PolicyQuote" xmlns:wsdl="http://schemas.xmlsoap.org/wsdl/" xmlns:tns="http://www.pi4soa.org/PolicyQuote" xmlns:pcs="http://www.example.org/policyQuoteCalculationService" xmlns:pol="http://www.example.org/policyQuote" xmlns:pes="http://www.example.org/policyQuoteEntityService" xmlns:xsd="http://www.w3.org/2001/XMLSchema" xmlns:cred="http://creditagency.com/creditCheck" xmlns:pps="http://www.example.org/policyQuoteProcessService" xmlns:soap="http://schemas.xmlsoap.org/wsdl/soap/" xmlns:dmv="http://dmv.com/drivingRecord"> <types xmlns="http://schemas.xmlsoap.org/wsdl/"> <schema xmlns="http://www.w3.org/2001/XMLSchema"> <import namespace="http://www.example.org/policyQuote" schemaLocation="../schema/policyQuote.xsd"/> <import namespace="http://creditagency.com/creditCheck" schemaLocation="../schema/creditCheck.xsd"/> <import namespace="http://dmv.com/drivingRecord" schemaLocation="../schema/drivingRecord.xsd"/> </schema> </types> <wsdl:message name="receivePolicyQuoteRequest"> <wsdl:part name="content" element="pol:policyQuote"> </wsdl:part> </wsdl:message> ... Where policyQuote schema is imported. When I create a Variable in the BPEL Editor, it does not see the structure of the message. This is a big problem, since with out the message details it is impossible to do Assign / Copy. I will attach the project. -- 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

15 years, 4 months

4
16
0 / 0

[JBoss JIRA] Created: (JBIDE-7767) tests broken in 7.1 branch

by Nick Boldt (JIRA)

tests broken in 7.1 branch -------------------------- Key: JBIDE-7767 URL: https://jira.jboss.org/browse/JBIDE-7767 Project: Tools (JBoss Tools) Issue Type: Bug Components: teiid Affects Versions: 3.2.0.Beta2 Reporter: Nick Boldt Assignee: Barry LaFond [ERROR] The project org.jboss.tools:tests.all:0.0.1-SNAPSHOT (/mnt/hudson_workspace/workspace/jbosstools-teiid-designer-7.1_stable_branch/sources/tests/pom.xml) has 2 errors [ERROR] 'modules.module[5]' specifies duplicate child module org.teiid.designer.core.test @ line 20, column 11 [ERROR] 'modules.module[29]' specifies duplicate child module org.teiid.designer.vdb.test @ line 44, column 11 http://hudson.qa.jboss.com/hudson/job/jbosstools-teiid-designer-7.1_stabl... Not sure what's amiss here, but have a look at the poms mentioned above and see what's causing the duplicate. -- This message is automatically generated by JIRA. - For more information on JIRA, see: http://www.atlassian.com/software/jira

15 years, 4 months

3
2
0 / 0

[JBoss JIRA] Created: (JBIDE-6398) SeamValidatorsAllTests fail intermittently on slaves soa4-rhel5-x86_64, vmg19-rhel5-x86, vmg18-rhel5-x86_64 for both JBT & JBDS builds

by Nick Boldt (JIRA)

SeamValidatorsAllTests fail intermittently on slaves soa4-rhel5-x86_64, vmg19-rhel5-x86, vmg18-rhel5-x86_64 for both JBT & JBDS builds -------------------------------------------------------------------------------------------------------------------------------------- Key: JBIDE-6398 URL: https://jira.jboss.org/browse/JBIDE-6398 Project: Tools (JBoss Tools) Issue Type: Bug Components: testing Affects Versions: 3.1.1 Reporter: Nick Boldt Not sure why these tests appear here: http://hudson.qa.jboss.com/hudson/view/DevStudio/job/devstudio-nightly-3.... (vmg20-rhel5-x86) Then disappear (failed? disabled? missing?) for all builds since. And, similarly: http://hudson.qa.jboss.com/hudson/view/DevStudio/job/jbosstools-nightly-3... (soa6-rhel5-x86_64) http://hudson.qa.jboss.com/hudson/view/DevStudio/job/jbosstools-nightly-3... (soa6-rhel5-x86_64) http://hudson.qa.jboss.com/hudson/view/DevStudio/job/jbosstools-nightly-3... (vmg20-rhel5-x86) But once again disappear (failed? disabled? missing?) for these builds: #109, 110, 111 (soa4-rhel5-x86_64, vmg19-rhel5-x86, vmg18-rhel5-x86_64) I wonder if the problem is one of configuration of the slaves (bad config? low ram? low disk?) or that the tests are too greedy/misconfigured? -- 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

15 years, 4 months

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 November 2010