October 2015 - jbosstools-issues - Jboss List Archives

[JBoss JIRA] (JBIDE-17859) XML validation error for a web service configuration XML file in a Seam project

by Thomas Haskes (JIRA)

[ https://issues.jboss.org/browse/JBIDE-17859?page=com.atlassian.jira.plugi... ] Thomas Haskes commented on JBIDE-17859: --------------------------------------- For others that are looking for a solution this may be useful. I had the same problem described above in eclipse, but the solution of adding the aforementioned attributes did not work for me. Adding the attributes made the error disappear, but then my ear would not deploy anymore, stating the error "Unexpected element: handler-chains" while deploying. Adding the following attributes worked though, the error in eclipse disappeard, ant the ear did deploy again: {code:xml} <handler-chains xmlns="http://java.sun.com/xml/ns/javaee" xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance" xmlns:jaxb="http://java.sun.com/xml/ns/jaxb" xsi:schemaLocation="http://java.sun.com/xml/ns/javaee http://java.sun.com/xml/ns/javaee/javaee_web_services_metadata_handler_2_..."> {code} I found that solution here: http://stackoverflow.com/questions/27903735/cannot-find-declaration-of-el... > XML validation error for a web service configuration XML file in a Seam project > ------------------------------------------------------------------------------- > > Key: JBIDE-17859 > URL: https://issues.jboss.org/browse/JBIDE-17859 > Project: Tools (JBoss Tools) > Issue Type: Bug > Components: upstream > Environment: JBDS 8.0.0.Beta3 > Reporter: Ron Šmeral > Assignee: Viacheslav Kabanovich > Fix For: 4.2.0.CR1 > > > {noformat} > cvc-elt.1: Cannot find the declaration of element 'handler-chains'. > soap-handlers.xml > /seambay-ejb/src/main/resources/org/jboss/seam/example/seambay > line 2 > XML Problem > {noformat} > The file is valid and satisfies the webservices schema in the javaee namespace: http://www.oracle.com/webfolder/technetwork/jsc/xml/ns/javaee/javaee_web_...: > {code:xml} > <?xml version="1.0" encoding="UTF-8"?> > <handler-chains xmlns="http://java.sun.com/xml/ns/javaee"> > <handler-chain> > <handler> > <handler-name>SOAP Request Handler</handler-name> > <handler-class>org.jboss.seam.webservice.SOAPRequestHandler</handler-class> > </handler> > </handler-chain> > </handler-chains> > {code} -- This message was sent by Atlassian JIRA (v6.4.11#64026)

10 years, 5 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-20990) Add "CDK Server" for start/stop for the CDK

by Max Rydahl Andersen (JIRA)

[ https://issues.jboss.org/browse/JBIDE-20990?page=com.atlassian.jira.plugi... ] Max Rydahl Andersen commented on JBIDE-20990: --------------------------------------------- sorry, not following how this relate to this ? > Add "CDK Server" for start/stop for the CDK > ------------------------------------------- > > Key: JBIDE-20990 > URL: https://issues.jboss.org/browse/JBIDE-20990 > Project: Tools (JBoss Tools) > Issue Type: Feature Request > Components: server > Reporter: Max Rydahl Andersen > Assignee: Rob Stryker > > We want to be able to start/stop CDK easily. > Current suggestion is to use a server entry in server view that can start/stop vagrant by simply knowing its file location would be a good start. > note: the vagrant image might already be running so just need to be able to take care of that. -- This message was sent by Atlassian JIRA (v6.4.11#64026)

10 years, 5 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-21005) Node location should point to the node executable file instead of the parent folder of it

by Ilya Buziuk (JIRA)

[ https://issues.jboss.org/browse/JBIDE-21005?page=com.atlassian.jira.plugi... ] Ilya Buziuk commented on JBIDE-21005: ------------------------------------- Yeah, this is a good idea indeed. Actually I was also thinking about this enhancement. Basically, my plan in firstly make initial npm contribution to jst and after that fix this and other (if any) usability issues in one go for node / npm / bower > Node location should point to the node executable file instead of the parent folder of it > ----------------------------------------------------------------------------------------- > > Key: JBIDE-21005 > URL: https://issues.jboss.org/browse/JBIDE-21005 > Project: Tools (JBoss Tools) > Issue Type: Enhancement > Components: javascript, javascript-bower > Affects Versions: 4.3.0.Final > Reporter: Alexey Kazakov > Assignee: Ilya Buziuk > Fix For: 4.4.0.Alpha1 > > > Window->Preferences->Java Script tools->Node > It's confusing that "Node Location" in that preference page is actually references to the parent folder of the executable node file. I would expect "/usr/bin/nodejs" or "C:/.../node.exe" in that field. > IMO it's confusing and actually not very flexible. Why wouldn't let users to select the executable file itself? > WDYT? -- This message was sent by Atlassian JIRA (v6.4.11#64026)

10 years, 5 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-21003) Update target platform for linxtools.docker.ui to include https://bugs.eclipse.org/bugs/show_bug.cgi?id=480308

by Xavier Coulon (JIRA)

[ https://issues.jboss.org/browse/JBIDE-21003?page=com.atlassian.jira.plugi... ] Xavier Coulon commented on JBIDE-21003: --------------------------------------- [~akazakov] Docker Tools 1.2.0 is what we plan for end of year, so yes, it is targetting Eclipse Mars. I'm not sure there'll be a full release of Linux Tools (4.2.0) or just the Docker tooling component. > Update target platform for linxtools.docker.ui to include https://bugs.eclipse.org/bugs/show_bug.cgi?id=480308 > -------------------------------------------------------------------------------------------------------------- > > Key: JBIDE-21003 > URL: https://issues.jboss.org/browse/JBIDE-21003 > Project: Tools (JBoss Tools) > Issue Type: Bug > Components: target-platform > Affects Versions: 4.3.x > Reporter: Jeff Cantrill > Assignee: Nick Boldt > Fix For: 4.3.1.Beta1, 4.4.0.Alpha1 > > > *Reason:* update linuxtools.docker to expose ImageSearch wizard > *Project page/sources:* https://bugs.eclipse.org/bugs/show_bug.cgi?id=480308 > *Version:* .... > *License and owner:* ... > *Original p2 repo:* http://third-party-vendor.com/path/to/updates-site/ > *JBoss mirror:* Leave empty > *Include Sources:* Yes > *Affected JBoss Tools components:* jbosstools-openshift > *Include in JBDS:* Yes > *Type of dependency:* distribution > *List of bundles added/removed:* > {code} > suggested diff on the .target files > {code} > If applicable: > *non-p2 repository:* ... > *non-p2 ids:* ... -- This message was sent by Atlassian JIRA (v6.4.11#64026)

10 years, 5 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-21008) [origin_intservice_49] Can not add/edit service port

by Chunyun Chen (JIRA)

[ https://issues.jboss.org/browse/JBIDE-21008?page=com.atlassian.jira.plugi... ] Chunyun Chen updated JBIDE-21008: --------------------------------- Environment: OpenShift 3 Tools: 3.1.0.Beta1-v20151016-1836-B52 OS: Fedora 17 was:OpenShift 3 Tools: 3.1.0.Beta1-v20151016-1836-B52 > [origin_intservice_49] Can not add/edit service port > ---------------------------------------------------- > > Key: JBIDE-21008 > URL: https://issues.jboss.org/browse/JBIDE-21008 > Project: Tools (JBoss Tools) > Issue Type: Bug > Components: openshift > Affects Versions: 4.3.1.Beta1 > Environment: OpenShift 3 Tools: 3.1.0.Beta1-v20151016-1836-B52 > OS: Fedora 17 > Reporter: Chunyun Chen > Labels: app, openshift_v3 > Attachments: service_port_screenshot.png > > > It can not add/edit service port on "Services & Routing settings" wizard. -- This message was sent by Atlassian JIRA (v6.4.11#64026)

10 years, 5 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-21008) [origin_intservice_49] Can not add/edit service port

by Chunyun Chen (JIRA)

Chunyun Chen created JBIDE-21008: ------------------------------------ Summary: [origin_intservice_49] Can not add/edit service port Key: JBIDE-21008 URL: https://issues.jboss.org/browse/JBIDE-21008 Project: Tools (JBoss Tools) Issue Type: Bug Components: openshift Affects Versions: 4.3.1.Beta1 Environment: OpenShift 3 Tools: 3.1.0.Beta1-v20151016-1836-B52 Reporter: Chunyun Chen Attachments: service_port_screenshot.png It can not add/edit service port on "Services & Routing settings" wizard. -- This message was sent by Atlassian JIRA (v6.4.11#64026)

10 years, 5 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-21007) Do not display OpenShift v2/v3 but rather OpenShift 2/3

by Marián Labuda (JIRA)

Marián Labuda created JBIDE-21007: ------------------------------------- Summary: Do not display OpenShift v2/v3 but rather OpenShift 2/3 Key: JBIDE-21007 URL: https://issues.jboss.org/browse/JBIDE-21007 Project: Tools (JBoss Tools) Issue Type: Bug Components: openshift Affects Versions: 4.3.0.CR1 Reporter: Fred Bricon Assignee: Nick Boldt Fix For: 4.3.1.Beta1, 4.4.0.Alpha1 [~sspeiche] mentioned today we should not display OpenShift v2/v3 but rather OpenShift 2/3. Need to change all strings in jbosstools-openshift codebase and the JBoss Central connectors (cc [~nickboldt]) -- This message was sent by Atlassian JIRA (v6.4.11#64026)

10 years, 5 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-21007) Do not display OpenShift v2/v3 but rather OpenShift 2/3

by Marián Labuda (JIRA)

[ https://issues.jboss.org/browse/JBIDE-21007?page=com.atlassian.jira.plugi... ] Marián Labuda updated JBIDE-21007: ---------------------------------- Fix Version/s: (was: 4.3.1.Beta1) > Do not display OpenShift v2/v3 but rather OpenShift 2/3 > ------------------------------------------------------- > > Key: JBIDE-21007 > URL: https://issues.jboss.org/browse/JBIDE-21007 > Project: Tools (JBoss Tools) > Issue Type: Bug > Components: openshift > Affects Versions: 4.3.0.CR1 > Reporter: Fred Bricon > Assignee: Nick Boldt > Fix For: 4.4.0.Alpha1 > > > [~sspeiche] mentioned today we should not display OpenShift v2/v3 but rather OpenShift 2/3. Need to change all strings in jbosstools-openshift codebase and the JBoss Central connectors (cc [~nickboldt]) -- This message was sent by Atlassian JIRA (v6.4.11#64026)

10 years, 5 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-21007) Do not display OpenShift v2/v3 but rather OpenShift 2/3

by Marián Labuda (JIRA)

[ https://issues.jboss.org/browse/JBIDE-21007?page=com.atlassian.jira.plugi... ] Marián Labuda resolved JBIDE-21007. ----------------------------------- Resolution: Done > Do not display OpenShift v2/v3 but rather OpenShift 2/3 > ------------------------------------------------------- > > Key: JBIDE-21007 > URL: https://issues.jboss.org/browse/JBIDE-21007 > Project: Tools (JBoss Tools) > Issue Type: Bug > Components: openshift > Affects Versions: 4.3.0.CR1 > Reporter: Fred Bricon > Assignee: Nick Boldt > Fix For: 4.4.0.Alpha1 > > > [~sspeiche] mentioned today we should not display OpenShift v2/v3 but rather OpenShift 2/3. Need to change all strings in jbosstools-openshift codebase and the JBoss Central connectors (cc [~nickboldt]) -- This message was sent by Atlassian JIRA (v6.4.11#64026)

10 years, 5 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-20565) Do not display OpenShift v2/v3 but rather OpenShift 2/3

by Marián Labuda (JIRA)

[ https://issues.jboss.org/browse/JBIDE-20565?page=com.atlassian.jira.plugi... ] Marián Labuda updated JBIDE-20565: ---------------------------------- Fix Version/s: (was: 4.4.0.Alpha1) > Do not display OpenShift v2/v3 but rather OpenShift 2/3 > ------------------------------------------------------- > > Key: JBIDE-20565 > URL: https://issues.jboss.org/browse/JBIDE-20565 > Project: Tools (JBoss Tools) > Issue Type: Bug > Components: openshift > Affects Versions: 4.3.0.CR1 > Reporter: Fred Bricon > Assignee: Nick Boldt > Fix For: 4.3.1.Beta1 > > > [~sspeiche] mentioned today we should not display OpenShift v2/v3 but rather OpenShift 2/3. Need to change all strings in jbosstools-openshift codebase and the JBoss Central connectors (cc [~nickboldt]) -- This message was sent by Atlassian JIRA (v6.4.11#64026)

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