May 2015 - jbosstools-issues - Jboss List Archives

[JBoss JIRA] (JBIDE-19605) Avoid need for multiple javax.servlet

by Brian Fitzpatrick (JIRA)

[ https://issues.jboss.org/browse/JBIDE-19605?page=com.atlassian.jira.plugi... ] Brian Fitzpatrick commented on JBIDE-19605: ------------------------------------------- [~xcoulon] I haven't made the changes to actually remove those lines from the MANIFEST.MF file yet. :) What versions of the repo should I target this for? > Avoid need for multiple javax.servlet > ------------------------------------- > > Key: JBIDE-19605 > URL: https://issues.jboss.org/browse/JBIDE-19605 > Project: Tools (JBoss Tools) > Issue Type: Enhancement > Components: target-platform, webservices > Affects Versions: 4.3.0.Alpha2 > Reporter: Mickael Istria > Assignee: Brian Fitzpatrick > Fix For: LATER > > Attachments: org.jboss.tools.ws.jaxrs.core.internal.metamodel.builder.JavaElement11ChangedProcessingTestCase.txt, org.jboss.tools.ws.jaxrs.core.internal.metamodel.builder.JaxrsMetamodelChangedProcessorTestCase.txt, org.jboss.tools.ws.jaxrs.core.internal.metamodel.builder.ResourceChangedProcessingTestCase.txt, org.jboss.tools.ws.jaxrs.core.internal.metamodel.domain.Jaxrs11ElementFactoryTestCase.txt, org.jboss.tools.ws.jaxrs.core.internal.metamodel.domain.Jaxrs20EndpointTestCase.txt > > > We currently use 2 different version of javax.servlet bundle. We'd rather decide on sticking to 1. > {code} > On 04/15/2015 11:56 PM, Nick Boldt wrote: > > Just wondering if anyone knows WHY we include javax.servlet 3.0.0 and > > 3.1.0 in JBDS. > > More importantly... SHOULD we be including both? Or can we just include > > 3.1.0 and drop 3.0.0? > I have JBDS installed from installer, which basically ran a p2 director. And I get jetty 3.0.0 and jetty 3.1.0. Than means that while resolving what to installed, p2 has to keep both versions of javax.servlet. That's definitely a sign that our dependency chain currently need both (or p2 wouldn't have installed both). > So I've tried the ultimate test: > $ cd jbdevstudio-9.0.0.Alpha2/studio > $ rm plugins/javax.servlet_3.0.0* > $ ./jbdevstudio > And saw > !ENTRY org.jboss.tools.ws.ui 4 0 2015-04-16 10:35:49.110 > !MESSAGE FrameworkEvent ERROR > !STACK 0 > org.osgi.framework.BundleException: Could not resolve module: org.jboss.tools.ws.ui [967] > Unresolved requirement: Import-Package: javax.servlet; version="[2.4.0,3.0.0)" > at org.eclipse.osgi.container.Module.start(Module.java:434) > at org.eclipse.osgi.container.ModuleContainer$ContainerStartLevel.incStartLevel(ModuleContainer.java:1582) > at org.eclipse.osgi.container.ModuleContainer$ContainerStartLevel.incStartLevel(ModuleContainer.java:1561) > at org.eclipse.osgi.container.ModuleContainer$ContainerStartLevel.doContainerStartLevel(ModuleContainer.java:1533) > at org.eclipse.osgi.container.ModuleContainer$ContainerStartLevel.dispatchEvent(ModuleContainer.java:1476) > at org.eclipse.osgi.container.ModuleContainer$ContainerStartLevel.dispatchEvent(ModuleContainer.java:1) > at org.eclipse.osgi.framework.eventmgr.EventManager.dispatchEvent(EventManager.java:230) > at org.eclipse.osgi.framework.eventmgr.EventManager$EventThread.run(EventManager.java:340) > Fun thing is that the javax.servlet_3.0.0 actually exports packages in version 2.6.0, whereas javax.servlet_3.1.0 exports them in version 3.1.0. > {code} -- This message was sent by Atlassian JIRA (v6.3.15#6346)

10 years, 11 months

1
0
0 / 0

[JBoss JIRA] (JBDS-3411) have installer build actually use M6 p2 product build

by Martin Malina (JIRA)

[ https://issues.jboss.org/browse/JBDS-3411?page=com.atlassian.jira.plugin.... ] Martin Malina commented on JBDS-3411: ------------------------------------- And not to forget: Now that it's (hopefully) all fixed, we will need to verify also the other things described by Nick and Denis above: {quote} Some previous functionality is affected and should be verified: 1. Installation layout is not changed for windows and linux, so $ {target-dir} /studio should have the same structure with plugins/features/about/etc sub-folders; 2. Installation layout is changed for Mac OS X and all eclipse related artifacts plugins/features/about/etc are moved inside $INSTALL_PATH/studio/jbdevstudio.app; 3. Adding selected jvm location to jbdevstudio.ini file; 4. Installation with EAP discovers $INSTALL_PATH/runtimes/jboss-eap/ as a runtime after first start. {quote} {quote} can it be installed? do both the standalone and EAP version work? OSX freezing / being slow {quote} > have installer build actually use M6 p2 product build > ----------------------------------------------------- > > Key: JBDS-3411 > URL: https://issues.jboss.org/browse/JBDS-3411 > Project: Developer Studio (JBoss Developer Studio) > Issue Type: Bug > Components: build, installer, updatesite > Reporter: Max Rydahl Andersen > Assignee: Denis Golovin > Priority: Critical > Fix For: 9.0.0.Beta1 > > > talking with [~prapicault] I learned that since M6 the following changes are required for proper working p2 product/osx build: > {code} > <products> > <product> > ... > <rootFolders> > <macosx>MyProduct.app</macosx> > </rootFolders> > </product> > {code} > And to use tycho 0.23-snapshot -- This message was sent by Atlassian JIRA (v6.3.15#6346)

10 years, 11 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-19785) CordovaSim does not work with cordova-android-4.0.0

by Ilya Buziuk (JIRA)

[ https://issues.jboss.org/browse/JBIDE-19785?page=com.atlassian.jira.plugi... ] Ilya Buziuk updated JBIDE-19785: -------------------------------- Sprint: Sprint #3 May 2015 > CordovaSim does not work with cordova-android-4.0.0 > --------------------------------------------------- > > Key: JBIDE-19785 > URL: https://issues.jboss.org/browse/JBIDE-19785 > Project: Tools (JBoss Tools) > Issue Type: Bug > Components: cordovasim > Affects Versions: 4.3.0.Alpha2 > Reporter: Ilya Buziuk > Assignee: Ilya Buziuk > Priority: Critical > Fix For: 4.3.0.Beta1 > > > The upstream issues: > - https://issues.apache.org/jira/browse/RIPPLE-82 > - https://issues.apache.org/jira/browse/CB-8971 > Basically, need to wait for republication of all affected platforms (this release would be broken for both Ripple and CordovaSim) -- This message was sent by Atlassian JIRA (v6.3.15#6346)

10 years, 11 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-19687) Web Service wizard buttons act strangely if an error occurs creating CXF service

by Max Rydahl Andersen (JIRA)

[ https://issues.jboss.org/browse/JBIDE-19687?page=com.atlassian.jira.plugi... ] Max Rydahl Andersen commented on JBIDE-19687: --------------------------------------------- removed "workaround" label and instead set the "workaround avaiable" flag + text and marked for 4.3.x in case actual upstream bug gets fixed. > Web Service wizard buttons act strangely if an error occurs creating CXF service > -------------------------------------------------------------------------------- > > Key: JBIDE-19687 > URL: https://issues.jboss.org/browse/JBIDE-19687 > Project: Tools (JBoss Tools) > Issue Type: Bug > Components: webservices > Affects Versions: 4.3.0.Alpha2 > Environment: Fedora 20 x64, openjdk 1.7.0_75 > Reporter: Jan Richter > Assignee: Brian Fitzpatrick > Labels: upstream > Fix For: 4.3.x > > Attachments: errorMessage > > > Trying to create a bottom up Apache CXF web service. If after the "Apache CXF Wbe Service Java2WS Configuration" step an error occurs, the "back" and "next" buttons stop behaving in the expected fashion. > So far I've found these cases: > - The back button will loop through the last 3 pages of the wizard, while pressing "next" on any of these pages will return you to the first page. > - You can return with the back button, but pressing next will open an error dialog with the same message as the original error. -- This message was sent by Atlassian JIRA (v6.3.15#6346)

10 years, 11 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-19687) Web Service wizard buttons act strangely if an error occurs creating CXF service

by Max Rydahl Andersen (JIRA)

[ https://issues.jboss.org/browse/JBIDE-19687?page=com.atlassian.jira.plugi... ] Max Rydahl Andersen updated JBIDE-19687: ---------------------------------------- Workaround Description: workaround to get past this by adding "targetNamespace" as an element in the WebService annotation: {code} package org.jboss.samples.webservices; import javax.jws.WebMethod; import javax.jws.WebService; @WebService(targetNamespace = "http://jboss.org/wsdl") public class HelloWorld { @WebMethod() public String sayHello(String name) { System.out.println("Hello: " + name); return "Hello " + name + "!"; } } {code} Workaround: Workaround Exists > Web Service wizard buttons act strangely if an error occurs creating CXF service > -------------------------------------------------------------------------------- > > Key: JBIDE-19687 > URL: https://issues.jboss.org/browse/JBIDE-19687 > Project: Tools (JBoss Tools) > Issue Type: Bug > Components: webservices > Affects Versions: 4.3.0.Alpha2 > Environment: Fedora 20 x64, openjdk 1.7.0_75 > Reporter: Jan Richter > Assignee: Brian Fitzpatrick > Labels: upstream > Fix For: 4.3.x > > Attachments: errorMessage > > > Trying to create a bottom up Apache CXF web service. If after the "Apache CXF Wbe Service Java2WS Configuration" step an error occurs, the "back" and "next" buttons stop behaving in the expected fashion. > So far I've found these cases: > - The back button will loop through the last 3 pages of the wizard, while pressing "next" on any of these pages will return you to the first page. > - You can return with the back button, but pressing next will open an error dialog with the same message as the original error. -- This message was sent by Atlassian JIRA (v6.3.15#6346)

10 years, 11 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-19687) Web Service wizard buttons act strangely if an error occurs creating CXF service

by Max Rydahl Andersen (JIRA)

[ https://issues.jboss.org/browse/JBIDE-19687?page=com.atlassian.jira.plugi... ] Max Rydahl Andersen updated JBIDE-19687: ---------------------------------------- Labels: upstream (was: upstream workaround) > Web Service wizard buttons act strangely if an error occurs creating CXF service > -------------------------------------------------------------------------------- > > Key: JBIDE-19687 > URL: https://issues.jboss.org/browse/JBIDE-19687 > Project: Tools (JBoss Tools) > Issue Type: Bug > Components: webservices > Affects Versions: 4.3.0.Alpha2 > Environment: Fedora 20 x64, openjdk 1.7.0_75 > Reporter: Jan Richter > Assignee: Brian Fitzpatrick > Labels: upstream > Fix For: 4.3.x > > Attachments: errorMessage > > > Trying to create a bottom up Apache CXF web service. If after the "Apache CXF Wbe Service Java2WS Configuration" step an error occurs, the "back" and "next" buttons stop behaving in the expected fashion. > So far I've found these cases: > - The back button will loop through the last 3 pages of the wizard, while pressing "next" on any of these pages will return you to the first page. > - You can return with the back button, but pressing next will open an error dialog with the same message as the original error. -- This message was sent by Atlassian JIRA (v6.3.15#6346)

10 years, 11 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-19687) Web Service wizard buttons act strangely if an error occurs creating CXF service

by Max Rydahl Andersen (JIRA)

[ https://issues.jboss.org/browse/JBIDE-19687?page=com.atlassian.jira.plugi... ] Max Rydahl Andersen updated JBIDE-19687: ---------------------------------------- Fix Version/s: 4.3.x (was: 4.3.0.Final) > Web Service wizard buttons act strangely if an error occurs creating CXF service > -------------------------------------------------------------------------------- > > Key: JBIDE-19687 > URL: https://issues.jboss.org/browse/JBIDE-19687 > Project: Tools (JBoss Tools) > Issue Type: Bug > Components: webservices > Affects Versions: 4.3.0.Alpha2 > Environment: Fedora 20 x64, openjdk 1.7.0_75 > Reporter: Jan Richter > Assignee: Brian Fitzpatrick > Labels: upstream > Fix For: 4.3.x > > Attachments: errorMessage > > > Trying to create a bottom up Apache CXF web service. If after the "Apache CXF Wbe Service Java2WS Configuration" step an error occurs, the "back" and "next" buttons stop behaving in the expected fashion. > So far I've found these cases: > - The back button will loop through the last 3 pages of the wizard, while pressing "next" on any of these pages will return you to the first page. > - You can return with the back button, but pressing next will open an error dialog with the same message as the original error. -- This message was sent by Atlassian JIRA (v6.3.15#6346)

10 years, 11 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-19785) CordovaSim does not work with cordova-android-4.0.0

by Ilya Buziuk (JIRA)

[ https://issues.jboss.org/browse/JBIDE-19785?page=com.atlassian.jira.plugi... ] Ilya Buziuk updated JBIDE-19785: -------------------------------- Issue Type: Bug (was: Feature Request) > CordovaSim does not work with cordova-android-4.0.0 > --------------------------------------------------- > > Key: JBIDE-19785 > URL: https://issues.jboss.org/browse/JBIDE-19785 > Project: Tools (JBoss Tools) > Issue Type: Bug > Components: cordovasim > Affects Versions: 4.3.0.Alpha2 > Reporter: Ilya Buziuk > Assignee: Ilya Buziuk > Priority: Critical > Fix For: 4.3.0.Beta1 > > > The upstream issues: > - https://issues.apache.org/jira/browse/RIPPLE-82 > - https://issues.apache.org/jira/browse/CB-8971 > Basically, need to wait for republication for all affected platforms (this release would be broken for both Ripple and CordovaSim) -- This message was sent by Atlassian JIRA (v6.3.15#6346)

10 years, 11 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-19785) CordovaSim does not work with cordova-android-4.0.0

by Ilya Buziuk (JIRA)

[ https://issues.jboss.org/browse/JBIDE-19785?page=com.atlassian.jira.plugi... ] Ilya Buziuk updated JBIDE-19785: -------------------------------- Description: The upstream issues: - https://issues.apache.org/jira/browse/RIPPLE-82 - https://issues.apache.org/jira/browse/CB-8971 Basically, need to wait for republication of all affected platforms (this release would be broken for both Ripple and CordovaSim) was: The upstream issues: - https://issues.apache.org/jira/browse/RIPPLE-82 - https://issues.apache.org/jira/browse/CB-8971 Basically, need to wait for republication for all affected platforms (this release would be broken for both Ripple and CordovaSim) > CordovaSim does not work with cordova-android-4.0.0 > --------------------------------------------------- > > Key: JBIDE-19785 > URL: https://issues.jboss.org/browse/JBIDE-19785 > Project: Tools (JBoss Tools) > Issue Type: Bug > Components: cordovasim > Affects Versions: 4.3.0.Alpha2 > Reporter: Ilya Buziuk > Assignee: Ilya Buziuk > Priority: Critical > Fix For: 4.3.0.Beta1 > > > The upstream issues: > - https://issues.apache.org/jira/browse/RIPPLE-82 > - https://issues.apache.org/jira/browse/CB-8971 > Basically, need to wait for republication of all affected platforms (this release would be broken for both Ripple and CordovaSim) -- This message was sent by Atlassian JIRA (v6.3.15#6346)

10 years, 11 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-19785) CordovaSim does not work with cordova-android-4.0.0

by Ilya Buziuk (JIRA)

Ilya Buziuk created JBIDE-19785: ----------------------------------- Summary: CordovaSim does not work with cordova-android-4.0.0 Key: JBIDE-19785 URL: https://issues.jboss.org/browse/JBIDE-19785 Project: Tools (JBoss Tools) Issue Type: Feature Request Components: cordovasim Affects Versions: 4.3.0.Alpha2 Reporter: Ilya Buziuk Assignee: Ilya Buziuk Priority: Critical Fix For: 4.3.0.Beta1 The upstream issues: - https://issues.apache.org/jira/browse/RIPPLE-82 - https://issues.apache.org/jira/browse/CB-8971 Basically, need to wait for republication for all affected platforms (this release would be broken for both Ripple and CordovaSim) -- This message was sent by Atlassian JIRA (v6.3.15#6346)

10 years, 11 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 May 2015