October 2013 - jbosstools-issues - Jboss List Archives

[JBoss JIRA] (JBIDE-14618) Generating SOAP message via WISE takes a long time

by Brian Fitzpatrick (JIRA)

[ https://issues.jboss.org/browse/JBIDE-14618?page=com.atlassian.jira.plugi... ] Brian Fitzpatrick commented on JBIDE-14618: ------------------------------------------- Bumping to 4.2.x and will look into this moving forward > Generating SOAP message via WISE takes a long time > -------------------------------------------------- > > Key: JBIDE-14618 > URL: https://issues.jboss.org/browse/JBIDE-14618 > Project: Tools (JBoss Tools) > Issue Type: Enhancement > Components: webservices > Affects Versions: 4.1.0.Beta1 > Reporter: Jaroslav Jankovič > Assignee: Brian Fitzpatrick > Fix For: 4.2.x > > Attachments: JBIDE-14618.jpg > > > In "Select WSDL" dialog, after entering url of SOAP WS and confirming it with OK button, a "Progress Information" dialog appears because of waiting for WISE call. This dialog, I think, is very user unfriendly and in previous versions it was quite faster. In this point of view, Beta1 is worse than Alpha builds. -- 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

12 years, 6 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-13785) Improve the current WS Tester

by Brian Fitzpatrick (JIRA)

[ https://issues.jboss.org/browse/JBIDE-13785?page=com.atlassian.jira.plugi... ] Brian Fitzpatrick updated JBIDE-13785: -------------------------------------- Fix Version/s: LATER (was: 4.1.x) > Improve the current WS Tester > ----------------------------- > > Key: JBIDE-13785 > URL: https://issues.jboss.org/browse/JBIDE-13785 > Project: Tools (JBoss Tools) > Issue Type: Enhancement > Components: webservices > Affects Versions: 4.1.0.Final > Reporter: Xavier Coulon > Assignee: Brian Fitzpatrick > Fix For: LATER > > Attachments: binary-button-icon.png, hierarchical-layout-button-icon.png, JAX-RS Tester.bmml, JAX-RS Tester.bmml, JAX-RS Tester.bmml, JAX-RS Tester.bmml, JAX-RS Tester.bmml, JAX-RS Tester.bmml, JAX-RS Tester.bmml, JAX-RS Tester.png, jax-ws-tester-mockup.bmml, jax-ws-tester-mockup.bmml, jax-ws-tester-mockup.png, properties-button-icon.png, run-button-icon.png, save-button-icon.png, web-button-icon.png, wsdl-button-icon.png > > > Improving the current WebService Tester view, mayb splitting the current tester that supports both SOAP and REST styles into 2 separate viewers (with maybe a common code base). > Some ideas: > - removing some unnecessary options in the SOAP Tester (ex: HTTP Methods), > - adding embedded XML and JSON Editors to edit the request / response entities, > - generate request entity skeletons from the expected java class -- 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

12 years, 6 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-13280) Generate Arquillian test code from endpoints

by Brian Fitzpatrick (JIRA)

[ https://issues.jboss.org/browse/JBIDE-13280?page=com.atlassian.jira.plugi... ] Brian Fitzpatrick updated JBIDE-13280: -------------------------------------- Assignee: Xavier Coulon (was: Brian Fitzpatrick) > Generate Arquillian test code from endpoints > -------------------------------------------- > > Key: JBIDE-13280 > URL: https://issues.jboss.org/browse/JBIDE-13280 > Project: Tools (JBoss Tools) > Issue Type: Feature Request > Components: webservices > Affects Versions: 4.0.0.Final > Reporter: Xavier Coulon > Assignee: Xavier Coulon > Fix For: 4.1.x > > > Generate Arquillian JAX-RS test skeleton from: > - Endpoints in the Project Explorer, > - Java Methods > - Wizard > Client API could be based on: > - Apache HTTP Client > - Jersey / RESTEasy (custom) Client API > - JAX-RS 2.0 (standardized) Client API > This implies that some Maven dependencies may need to be added into the project. > Optionally, > {code} > @Deployment > public static JavaArchive createDeployment() { > ... > } > {code} > could be filled with required dependencies. -- 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

12 years, 6 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-13280) Generate Arquillian test code from endpoints

by Brian Fitzpatrick (JIRA)

[ https://issues.jboss.org/browse/JBIDE-13280?page=com.atlassian.jira.plugi... ] Brian Fitzpatrick updated JBIDE-13280: -------------------------------------- Fix Version/s: 4.2.x (was: 4.1.x) > Generate Arquillian test code from endpoints > -------------------------------------------- > > Key: JBIDE-13280 > URL: https://issues.jboss.org/browse/JBIDE-13280 > Project: Tools (JBoss Tools) > Issue Type: Feature Request > Components: webservices > Affects Versions: 4.0.0.Final > Reporter: Xavier Coulon > Assignee: Xavier Coulon > Fix For: 4.2.x > > > Generate Arquillian JAX-RS test skeleton from: > - Endpoints in the Project Explorer, > - Java Methods > - Wizard > Client API could be based on: > - Apache HTTP Client > - Jersey / RESTEasy (custom) Client API > - JAX-RS 2.0 (standardized) Client API > This implies that some Maven dependencies may need to be added into the project. > Optionally, > {code} > @Deployment > public static JavaArchive createDeployment() { > ... > } > {code} > could be filled with required dependencies. -- 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

12 years, 6 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-14618) Generating SOAP message via WISE takes a long time

by Brian Fitzpatrick (JIRA)

[ https://issues.jboss.org/browse/JBIDE-14618?page=com.atlassian.jira.plugi... ] Brian Fitzpatrick updated JBIDE-14618: -------------------------------------- Fix Version/s: 4.2.x (was: 4.1.x) > Generating SOAP message via WISE takes a long time > -------------------------------------------------- > > Key: JBIDE-14618 > URL: https://issues.jboss.org/browse/JBIDE-14618 > Project: Tools (JBoss Tools) > Issue Type: Enhancement > Components: webservices > Affects Versions: 4.1.0.Beta1 > Reporter: Jaroslav Jankovič > Assignee: Brian Fitzpatrick > Fix For: 4.2.x > > Attachments: JBIDE-14618.jpg > > > In "Select WSDL" dialog, after entering url of SOAP WS and confirming it with OK button, a "Progress Information" dialog appears because of waiting for WISE call. This dialog, I think, is very user unfriendly and in previous versions it was quite faster. In this point of view, Beta1 is worse than Alpha builds. -- 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

12 years, 6 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-15647) Compile errors when building arquillian with Luna target platform

by Snjezana Peco (JIRA)

[ https://issues.jboss.org/browse/JBIDE-15647?page=com.atlassian.jira.plugi... ] Snjezana Peco commented on JBIDE-15647: --------------------------------------- {code} which internal API would you remove that others in JBT uses ? {code} No one component uses arquillian. I have meant we can't use the same JBT code for Luna and Kepler because the most of our components (arquillian, central, project examples, maven, portlet, hibernate, archives, server, common, foundation, openshift... ) use internal Eclipse API. {quote} dont you mean stop using interal api or ? {quote} I mean we should stop using internal API whenever it is possible to do that. {quote} btw. this change sounds to me Eclipse are making public API internal between Kepler and Luna ? {quote} No, they aren't making public API internal. The org.eclipse.osgi.framework.adaptor.BundleClassLoader class has been internal API and is renamed in Luna. However, it seems the RuntimeProcess class (JBIDE-15649 - forge) has been changed although it is a public API. Forge doesn't use internal API. {quote} That should be trivial to do dynamic test instead of hardcoded version ? {quote} I have removed the BundleClassLoader class because the Arquillian classloader isn't used within an Eclipse bundle. Now, the arquillian component builds against the Kepler and/or Luna target. > Compile errors when building arquillian with Luna target platform > ----------------------------------------------------------------- > > Key: JBIDE-15647 > URL: https://issues.jboss.org/browse/JBIDE-15647 > Project: Tools (JBoss Tools) > Issue Type: Bug > Components: testing-tools > Affects Versions: 4.2.x > Reporter: Snjezana Peco > Assignee: Snjezana Peco > Priority: Blocker > Fix For: 4.2.0.Alpha1 > > > When building the arquillian component with Luna TP(tpc.version=4.40.0.Alpha1-SNAPSHOT) there are the following compile errors: > {code} > [ERROR] import org.eclipse.osgi.framework.adaptor.BundleClassLoader; > [ERROR] ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^ > [ERROR] The import org.eclipse.osgi.framework.adaptor cannot be resolved > [ERROR] > ... > [ERROR] || tmp instanceof BundleClassLoader) > [ERROR] ^^^^^^^^^^^^^^^^^ > [ERROR] BundleClassLoader cannot be resolved to a type > {code} > The errors are caused by the change of OSGi internals. > The org.eclipse.osgi.framework.adaptor package and the BundleClassloader class have been removed from Luna. > The changes aren't compatible with the previous Eclipse versions, so we need a separate branch for Luna. -- 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

12 years, 6 months

1
0
0 / 0

[JBoss JIRA] (JBDS-2790) "JBoss Tools" themes should not be part of JBDS

by Mickael Istria (JIRA)

[ https://issues.jboss.org/browse/JBDS-2790?page=com.atlassian.jira.plugin.... ] Mickael Istria commented on JBDS-2790: -------------------------------------- I locally tried to re-build the JBDS feature and p2 repo without reference to the theme feature. Then I enabled the nice "JBoss Tools - Red" theme, restarted, and then added this site as a software source to JBDS 7.1.0.Alpha2 and run "Checked for Updates". After the restart of my application, the Feature was updated, the theme bundle was removed and the theme was back to the cold default one without issue. So it appears to be totally safe to remove the theme feature from product definition in 7.1 and 8.0, except for people who prefer the Red or Blue themes... > "JBoss Tools" themes should not be part of JBDS > ----------------------------------------------- > > Key: JBDS-2790 > URL: https://issues.jboss.org/browse/JBDS-2790 > Project: Developer Studio (JBoss Developer Studio) > Issue Type: Bug > Security Level: Public(Everyone can see) > Components: central > Affects Versions: 6.0.1.GA, 7.0.1.GA > Reporter: Max Rydahl Andersen > Assignee: Mickael Istria > > "JBoss Tools" themes seem to be included in JBDS even though JBDS-2631 was rejected and not supposed to be included. > Now users are reporting issues on them in JBDS-2781 and JBDS-2782 we'll need to decide what to with them. > My suggestion is we remove them in JBDS 8 and if a missing theme does not affect a user having already used these themes I suggest we remove them in JBDS 7.1 too. > Thus setting suggested release target to 7.1 but if investigation shows it will hurt update path then at least remove them in 8.0. > WDYT ? -- 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

12 years, 6 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-15656) package-info.java in managed package in persistence.xml causes StackOverflowError

by Koen Aers (JIRA)

[ https://issues.jboss.org/browse/JBIDE-15656?page=com.atlassian.jira.plugi... ] Koen Aers updated JBIDE-15656: ------------------------------ Assignee: Koen Aers > package-info.java in managed package in persistence.xml causes StackOverflowError > --------------------------------------------------------------------------------- > > Key: JBIDE-15656 > URL: https://issues.jboss.org/browse/JBIDE-15656 > Project: Tools (JBoss Tools) > Issue Type: Bug > Components: hibernate > Affects Versions: 4.1.0.Final > Reporter: Fred Bricon > Assignee: Koen Aers > Priority: Blocker > Fix For: 4.1.1.Beta1 > > > A customer reported stackoverflow errors occuring when importing one of his maven projects. > After investigation, it appears the SO is caused by HibernatePackageInfoImpl > {noformat} > java.lang.StackOverflowError > at org.eclipse.core.runtime.Path.computeSegmentCount(Path.java:450) > at org.eclipse.core.runtime.Path.computeSegments(Path.java:467) > at org.eclipse.core.runtime.Path.initialize(Path.java:602) > at org.eclipse.core.runtime.Path.<init>(Path.java:163) > at org.eclipse.jdt.internal.core.PackageFragment.resource(PackageFragment.java:326) > at org.eclipse.jdt.internal.core.CompilationUnit.resource(CompilationUnit.java:894) > at org.eclipse.jdt.internal.core.Openable.getResource(Openable.java:453) > at org.eclipse.jpt.common.core.internal.resource.java.source.SourceCompilationUnit.getFile(SourceCompilationUnit.java:95) > at org.eclipse.jpt.common.core.internal.resource.java.AbstractJavaResourceModel.getFile(AbstractJavaResourceModel.java:98) > at org.jboss.tools.hibernate.jpt.core.internal.context.java.HibernatePackageInfoImpl.validate(HibernatePackageInfoImpl.java:238) > at org.jboss.tools.hibernate.jpt.core.internal.context.java.HibernatePackageInfoImpl.validate(HibernatePackageInfoImpl.java:245) > at org.jboss.tools.hibernate.jpt.core.internal.context.java.HibernatePackageInfoImpl.validate(HibernatePackageInfoImpl.java:245) > {noformat} > The simplest setup to reproduce involves creating a JPA project (Hibernate Platform 2), and adding the following files : > {code:title=persistence.xml } > <?xml version="1.0" encoding="UTF-8"?> > <persistence version="2.0" xmlns="http://java.sun.com/xml/ns/persistence" xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance" xsi:schemaLocation="http://java.sun.com/xml/ns/persistence http://java.sun.com/xml/ns/persistence/persistence_2_0.xsd"> > <persistence-unit name="jpa"> > <class>foo.bar.model</class> > </persistence-unit> > </persistence> > {code} > {code:title=package-info.java} > package foo.bar.model; > {code} -- 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

12 years, 6 months

1
0
0 / 0

[JBoss JIRA] (JBTIS-186) ModeShape sometimes doesn't publish all models of Teiid VDB

by RH Bugzilla Integration (JIRA)

[ https://issues.jboss.org/browse/JBTIS-186?page=com.atlassian.jira.plugin.... ] RH Bugzilla Integration commented on JBTIS-186: ----------------------------------------------- Van Halbert <vhalbert(a)redhat.com> changed the Status of [bug 1017684|https://bugzilla.redhat.com/show_bug.cgi?id=1017684] from NEW to CLOSED > ModeShape sometimes doesn't publish all models of Teiid VDB > ----------------------------------------------------------- > > Key: JBTIS-186 > URL: https://issues.jboss.org/browse/JBTIS-186 > Project: JBoss Tools Integration Stack > Issue Type: Bug > Security Level: Public(Everyone can see) > Components: modeshape > Affects Versions: 4.1.3 > Environment: Ubuntu 12.04, JBTIS 4.1.3.Beta4, DV 6.0.0.ER2, sun jdk 1.6 > Reporter: Lucie Fabrikova > Assignee: Lucie Fabrikova > Attachments: BooksMode.vdb > > > If I publish a teiid VDB with relational models .xmi in given environment, sometimes some (or all) of the models are not published. -- 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

12 years, 6 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-15598) Environmental Variable API interface

by Andre Dietisheim (JIRA)

[ https://issues.jboss.org/browse/JBIDE-15598?page=com.atlassian.jira.plugi... ] Andre Dietisheim commented on JBIDE-15598: ------------------------------------------ both PRs were merged into upstream master. > Environmental Variable API interface > ------------------------------------ > > Key: JBIDE-15598 > URL: https://issues.jboss.org/browse/JBIDE-15598 > Project: Tools (JBoss Tools) > Issue Type: Sub-task > Components: openshift > Reporter: Martes Wigglesworth > Assignee: Andre Dietisheim > Priority: Blocker > Fix For: 4.1.1.Beta1, 4.2.0.Alpha1 > > > API calls to OpenShift for use with the JBDS OpenShift plugin's environmental variables interface. -- 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

12 years, 6 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 October 2013