April 2016 - jbosstools-issues - Jboss List Archives

[JBoss JIRA] (JBIDE-20415) Runtime download hyperlink not working from New Server dialog on Mac - upstream

by Rob Stryker (JIRA)

[ https://issues.jboss.org/browse/JBIDE-20415?page=com.atlassian.jira.plugi... ] Rob Stryker updated JBIDE-20415: -------------------------------- Fix Version/s: 4.4.x (was: 4.3.x) > Runtime download hyperlink not working from New Server dialog on Mac - upstream > ------------------------------------------------------------------------------- > > Key: JBIDE-20415 > URL: https://issues.jboss.org/browse/JBIDE-20415 > Project: Tools (JBoss Tools) > Issue Type: Bug > Components: server > Affects Versions: 4.3.0.Alpha2 > Reporter: Martin Malina > Assignee: Rob Stryker > Fix For: 4.4.x > > > When you go through Servers view -> New Server -> EAP 6.1 -> New Runtime and then click "Download and install runtime...", it won't do anything. > If you go through Preferences -> Server -> Runtime Environments -> Add -> EAP 6.1+ and then click the Download button, it will work. > This issue applies to both JBDS 8.1.0.GA and JBoss Tools 4.3.0.Alpha2 testing build, but I doubt we will be able to fix this for 4.2.x. -- This message was sent by Atlassian JIRA (v6.4.11#64026)

9 years, 11 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-20985) XML Schema validation fails when importing external schema

by Rob Stryker (JIRA)

[ https://issues.jboss.org/browse/JBIDE-20985?page=com.atlassian.jira.plugi... ] Rob Stryker updated JBIDE-20985: -------------------------------- Fix Version/s: 4.4.x (was: 4.3.x) > XML Schema validation fails when importing external schema > ---------------------------------------------------------- > > Key: JBIDE-20985 > URL: https://issues.jboss.org/browse/JBIDE-20985 > Project: Tools (JBoss Tools) > Issue Type: Bug > Components: upstream > Affects Versions: 4.2.3.Final > Reporter: Mustafa Musaji > Assignee: Rob Stryker > Priority: Critical > Fix For: 4.4.x > > Attachments: bean-service-quickstart.zip, simplerSYexample.zip > > > Product JIRA for upstream bug - https://bugs.eclipse.org/bugs/show_bug.cgi?id=315741 > This is to track the upstream bug in Eclipse that we need to pull in to JBDS at some point. -- This message was sent by Atlassian JIRA (v6.4.11#64026)

9 years, 11 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-19854) When Wildfly starts in debug mode occurs ClassNotFoundException with org.jboss.modules.Main

by Rob Stryker (JIRA)

[ https://issues.jboss.org/browse/JBIDE-19854?page=com.atlassian.jira.plugi... ] Rob Stryker reassigned JBIDE-19854: ----------------------------------- Assignee: Martin Malina > When Wildfly starts in debug mode occurs ClassNotFoundException with org.jboss.modules.Main > ------------------------------------------------------------------------------------------- > > Key: JBIDE-19854 > URL: https://issues.jboss.org/browse/JBIDE-19854 > Project: Tools (JBoss Tools) > Issue Type: Bug > Components: server > Environment: OS: Windows 8.1; Intel Core i3 540 3.07Ghz; 4GB DDR3 1333Mhz; Java Version 1.7.0_75; > Reporter: Giancarlo giulian > Assignee: Martin Malina > Labels: classnotfound, debug, debugging, jboss, main, wildfly > Fix For: 4.4.x > > Attachments: image2.png, image3.png, imagem1.png > > > This problem has recently begun, before that is it working in debug mode. Errors log are not created and doesn't appear in console output using Eclipse Luna. > Program Arguments: > {quote} > -mp "C:/wildfly-8.1/modules" -jaxpmodule javax.xml.jaxp-provider org.jboss.as.standalone -b localhost --server-config=standalone.xml -Djboss.server.base.dir=C:\wildfly-8.1\standalone > {quote} > VM Arguments: > {quote} > "-Dprogram.name=JBossTools: WildFly 8.1" -server -Xms64m -Xmx512m -XX:MaxPermSize=256m -Dorg.jboss.resolver.warning=true -Djava.net.preferIPv4Stack=true -Dsun.rmi.dgc.client.gcInterval=3600000 -Dsun.rmi.dgc.server.gcInterval=3600000 -Djboss.modules.system.pkgs=org.jboss.byteman -Djava.awt.headless=true "-Dorg.jboss.boot.log.file=C:/wildfly-8.1/standalone/log/boot.log" "-Dlogging.configuration=file:/C:/wildfly-8.1/standalone/configuration/logging.properties" "-Djboss.home.dir=C:/wildfly-8.1" -Dorg.jboss.logmanager.nocolor=true -Djboss.bind.address.management=localhost > {quote} > Images: > https://www.dropbox.com/s/g0hdwh1tz543q1p/imagem1.png > https://www.dropbox.com/s/ivpnd3ggaprtl2v/image2.png -- This message was sent by Atlassian JIRA (v6.4.11#64026)

9 years, 11 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-19854) When Wildfly starts in debug mode occurs ClassNotFoundException with org.jboss.modules.Main

by Rob Stryker (JIRA)

[ https://issues.jboss.org/browse/JBIDE-19854?page=com.atlassian.jira.plugi... ] Rob Stryker commented on JBIDE-19854: ------------------------------------- I cannot replicate in windows. Can you, [~mmalina]? If not we should probably close the issue. > When Wildfly starts in debug mode occurs ClassNotFoundException with org.jboss.modules.Main > ------------------------------------------------------------------------------------------- > > Key: JBIDE-19854 > URL: https://issues.jboss.org/browse/JBIDE-19854 > Project: Tools (JBoss Tools) > Issue Type: Bug > Components: server > Environment: OS: Windows 8.1; Intel Core i3 540 3.07Ghz; 4GB DDR3 1333Mhz; Java Version 1.7.0_75; > Reporter: Giancarlo giulian > Assignee: Martin Malina > Labels: classnotfound, debug, debugging, jboss, main, wildfly > Fix For: 4.4.x > > Attachments: image2.png, image3.png, imagem1.png > > > This problem has recently begun, before that is it working in debug mode. Errors log are not created and doesn't appear in console output using Eclipse Luna. > Program Arguments: > {quote} > -mp "C:/wildfly-8.1/modules" -jaxpmodule javax.xml.jaxp-provider org.jboss.as.standalone -b localhost --server-config=standalone.xml -Djboss.server.base.dir=C:\wildfly-8.1\standalone > {quote} > VM Arguments: > {quote} > "-Dprogram.name=JBossTools: WildFly 8.1" -server -Xms64m -Xmx512m -XX:MaxPermSize=256m -Dorg.jboss.resolver.warning=true -Djava.net.preferIPv4Stack=true -Dsun.rmi.dgc.client.gcInterval=3600000 -Dsun.rmi.dgc.server.gcInterval=3600000 -Djboss.modules.system.pkgs=org.jboss.byteman -Djava.awt.headless=true "-Dorg.jboss.boot.log.file=C:/wildfly-8.1/standalone/log/boot.log" "-Dlogging.configuration=file:/C:/wildfly-8.1/standalone/configuration/logging.properties" "-Djboss.home.dir=C:/wildfly-8.1" -Dorg.jboss.logmanager.nocolor=true -Djboss.bind.address.management=localhost > {quote} > Images: > https://www.dropbox.com/s/g0hdwh1tz543q1p/imagem1.png > https://www.dropbox.com/s/ivpnd3ggaprtl2v/image2.png -- This message was sent by Atlassian JIRA (v6.4.11#64026)

9 years, 11 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-19854) When Wildfly starts in debug mode occurs ClassNotFoundException with org.jboss.modules.Main

by Rob Stryker (JIRA)

[ https://issues.jboss.org/browse/JBIDE-19854?page=com.atlassian.jira.plugi... ] Rob Stryker updated JBIDE-19854: -------------------------------- Fix Version/s: 4.4.x (was: 4.3.x) > When Wildfly starts in debug mode occurs ClassNotFoundException with org.jboss.modules.Main > ------------------------------------------------------------------------------------------- > > Key: JBIDE-19854 > URL: https://issues.jboss.org/browse/JBIDE-19854 > Project: Tools (JBoss Tools) > Issue Type: Bug > Components: server > Environment: OS: Windows 8.1; Intel Core i3 540 3.07Ghz; 4GB DDR3 1333Mhz; Java Version 1.7.0_75; > Reporter: Giancarlo giulian > Assignee: Martin Malina > Labels: classnotfound, debug, debugging, jboss, main, wildfly > Fix For: 4.4.x > > Attachments: image2.png, image3.png, imagem1.png > > > This problem has recently begun, before that is it working in debug mode. Errors log are not created and doesn't appear in console output using Eclipse Luna. > Program Arguments: > {quote} > -mp "C:/wildfly-8.1/modules" -jaxpmodule javax.xml.jaxp-provider org.jboss.as.standalone -b localhost --server-config=standalone.xml -Djboss.server.base.dir=C:\wildfly-8.1\standalone > {quote} > VM Arguments: > {quote} > "-Dprogram.name=JBossTools: WildFly 8.1" -server -Xms64m -Xmx512m -XX:MaxPermSize=256m -Dorg.jboss.resolver.warning=true -Djava.net.preferIPv4Stack=true -Dsun.rmi.dgc.client.gcInterval=3600000 -Dsun.rmi.dgc.server.gcInterval=3600000 -Djboss.modules.system.pkgs=org.jboss.byteman -Djava.awt.headless=true "-Dorg.jboss.boot.log.file=C:/wildfly-8.1/standalone/log/boot.log" "-Dlogging.configuration=file:/C:/wildfly-8.1/standalone/configuration/logging.properties" "-Djboss.home.dir=C:/wildfly-8.1" -Dorg.jboss.logmanager.nocolor=true -Djboss.bind.address.management=localhost > {quote} > Images: > https://www.dropbox.com/s/g0hdwh1tz543q1p/imagem1.png > https://www.dropbox.com/s/ivpnd3ggaprtl2v/image2.png -- This message was sent by Atlassian JIRA (v6.4.11#64026)

9 years, 11 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-19453) Remote host information does not fit in the server editor

by Rob Stryker (JIRA)

[ https://issues.jboss.org/browse/JBIDE-19453?page=com.atlassian.jira.plugi... ] Rob Stryker commented on JBIDE-19453: ------------------------------------- I still can't replicate this. Pushing to later nad help-wanted > Remote host information does not fit in the server editor > --------------------------------------------------------- > > Key: JBIDE-19453 > URL: https://issues.jboss.org/browse/JBIDE-19453 > Project: Tools (JBoss Tools) > Issue Type: Bug > Components: server > Affects Versions: 4.2.3.Beta1 > Reporter: Martin Malina > Assignee: Rob Stryker > Priority: Minor > Labels: help_wanted > Fix For: LATER > > Attachments: remote-runtime-does-not-fit.png, server-editor-2.png, server-editor-linux.png > > > Today I noticed this. When I set up a remote server and then open it in the Server editor, the part under Server Behavior where it shows the remote host configuration (e.g. Remote Server Home) does not fix - it needs more space to the right, but it's hidden and there is no way to scroll to view it. > !remote-runtime-does-not-fit.png! > The same problem applies to both JBDS 8.1.0.Beta1 and JBDS 9.0.0.Alpha1. So you may want to clone this for 4.3.x. -- This message was sent by Atlassian JIRA (v6.4.11#64026)

9 years, 11 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-19453) Remote host information does not fit in the server editor

by Rob Stryker (JIRA)

[ https://issues.jboss.org/browse/JBIDE-19453?page=com.atlassian.jira.plugi... ] Rob Stryker updated JBIDE-19453: -------------------------------- Fix Version/s: LATER (was: 4.3.x) > Remote host information does not fit in the server editor > --------------------------------------------------------- > > Key: JBIDE-19453 > URL: https://issues.jboss.org/browse/JBIDE-19453 > Project: Tools (JBoss Tools) > Issue Type: Bug > Components: server > Affects Versions: 4.2.3.Beta1 > Reporter: Martin Malina > Assignee: Rob Stryker > Priority: Minor > Labels: help_wanted > Fix For: LATER > > Attachments: remote-runtime-does-not-fit.png, server-editor-2.png, server-editor-linux.png > > > Today I noticed this. When I set up a remote server and then open it in the Server editor, the part under Server Behavior where it shows the remote host configuration (e.g. Remote Server Home) does not fix - it needs more space to the right, but it's hidden and there is no way to scroll to view it. > !remote-runtime-does-not-fit.png! > The same problem applies to both JBDS 8.1.0.Beta1 and JBDS 9.0.0.Alpha1. So you may want to clone this for 4.3.x. -- This message was sent by Atlassian JIRA (v6.4.11#64026)

9 years, 11 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-19453) Remote host information does not fit in the server editor

by Rob Stryker (JIRA)

[ https://issues.jboss.org/browse/JBIDE-19453?page=com.atlassian.jira.plugi... ] Rob Stryker updated JBIDE-19453: -------------------------------- Labels: help_wanted (was: ) > Remote host information does not fit in the server editor > --------------------------------------------------------- > > Key: JBIDE-19453 > URL: https://issues.jboss.org/browse/JBIDE-19453 > Project: Tools (JBoss Tools) > Issue Type: Bug > Components: server > Affects Versions: 4.2.3.Beta1 > Reporter: Martin Malina > Assignee: Rob Stryker > Priority: Minor > Labels: help_wanted > Fix For: LATER > > Attachments: remote-runtime-does-not-fit.png, server-editor-2.png, server-editor-linux.png > > > Today I noticed this. When I set up a remote server and then open it in the Server editor, the part under Server Behavior where it shows the remote host configuration (e.g. Remote Server Home) does not fix - it needs more space to the right, but it's hidden and there is no way to scroll to view it. > !remote-runtime-does-not-fit.png! > The same problem applies to both JBDS 8.1.0.Beta1 and JBDS 9.0.0.Alpha1. So you may want to clone this for 4.3.x. -- This message was sent by Atlassian JIRA (v6.4.11#64026)

9 years, 11 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-16539) move pollthread mechanism into subsystem

by Rob Stryker (JIRA)

[ https://issues.jboss.org/browse/JBIDE-16539?page=com.atlassian.jira.plugi... ] Rob Stryker updated JBIDE-16539: -------------------------------- Fix Version/s: LATER (was: 4.3.x) > move pollthread mechanism into subsystem > ----------------------------------------- > > Key: JBIDE-16539 > URL: https://issues.jboss.org/browse/JBIDE-16539 > Project: Tools (JBoss Tools) > Issue Type: Task > Components: server > Reporter: Max Rydahl Andersen > Fix For: LATER > > > JBIDE-16533 revealed poll threads are handled via global static singleton - a less than perfect fit for the subsystem mechanism. -- This message was sent by Atlassian JIRA (v6.4.11#64026)

9 years, 11 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-20701) [eap7 quickstarts] Eclipse Errors validating jboss-ejb-security-interceptors quickstart

by Rob Stryker (JIRA)

[ https://issues.jboss.org/browse/JBIDE-20701?page=com.atlassian.jira.plugi... ] Rob Stryker updated JBIDE-20701: -------------------------------- Fix Version/s: 4.4.x (was: 4.3.x) > [eap7 quickstarts] Eclipse Errors validating jboss-ejb-security-interceptors quickstart > --------------------------------------------------------------------------------------- > > Key: JBIDE-20701 > URL: https://issues.jboss.org/browse/JBIDE-20701 > Project: Tools (JBoss Tools) > Issue Type: Sub-task > Components: server, upstream > Affects Versions: 4.3.0.CR1 > Reporter: Rob Stryker > Labels: xml_validation_quickstart_content, xml_validation_quickstarts_eap7, xml_validation_schema_error > Fix For: 4.4.x > > Attachments: 20529_security_interceptors_1.png > > > The above quickstart's file jboss-ejb3.xml indicates two errors. The first error seems to be a problem with the upstream / online schema, and I'm not sure if this is fixable in the quickstart or not. The second error may either be an error in the quickstart, or an error in the xsds, or, possibly, an error in eclipse validation. I am having trouble figuring out which. > *Error 1:* > Referenced file contains errors (jar:file:/home/rob/apps/eclipse/builds/mars_sr1_w_jbt/eclipse/plugins/ > org.jboss.tools.as.catalog_3.1.0.CR1-v20150911-0311-B31.jar!/schema/xsd/jboss-ejb3-spec-2_0.xsd). > Further details can be seen in attachment "20529_security_interceptors_1.png", > *Error 2:* > The current file in the quicksttarts has the following content: > {code} > <jee:assembly-descriptor> > <ci:container-interceptors> > <jee:interceptor-binding> > <ejb-name>IntermediateEJB</ejb-name> > <interceptor-class>org.jboss.as.quickstarts.ejb_security_interceptors.ServerSecurityInterceptor</interceptor-class> > </jee:interceptor-binding> > // removed 2nd for brevity > </ci:container-interceptors> > </jee:assembly-descriptor> > {code} > There are a few noted problems here. > 1) Validation insists that one jee:ejb-name element must live inside the container-interceptors but before the interceptor-binding. This basically means that that set of container-interceptors is only valid for one ejb. > 2) Validation also insists that ANOTHER jee:ejb-name ALSO live INSIDE the interceptor-binding > 3) If you have multiple interceptor bindings, only the first must have a jee:ejb-name OUTSIDE of it. > After a lot of spit-balling, the only valid xml I've managed to come up with that validates properly is: > {code} > <jee:assembly-descriptor> > <ci:container-interceptors> > <jee:ejb-name>IntermediateEJB</jee:ejb-name> > <ci:interceptor-binding> > <jee:ejb-name>IntermediateEJB</jee:ejb-name> > <jee:interceptor-class>org.jboss.as.quickstarts.ejb_security_interceptors.ServerSecurityInterceptor</jee:interceptor-class> > </ci:interceptor-binding> > </ci:container-interceptors> > <ci:container-interceptors> > <jee:ejb-name>SecuredEJB</jee:ejb-name> > <ci:interceptor-binding> > <jee:ejb-name>SecuredEJB</jee:ejb-name> > <jee:interceptor-class>org.jboss.as.quickstarts.ejb_security_interceptors.ServerSecurityInterceptor</jee:interceptor-class> > </ci:interceptor-binding> > </ci:container-interceptors> > </jee:assembly-descriptor> > {code} > You'll note there's a lot more namespacing going on in the elements, and that we now have two container-interceptors as opposed to one, because both are for different EJBs. You'll also note that the ejb-name must be declared twice, or else validation fails. This is most likely an error in the heirarchy / nesting of the xsd's, but I am not an expert in that regard. > So the above xml would be a good workaround for the quickstarts. Any other fix would require investigation of the xsd's by someone more qualified than I am. -- This message was sent by Atlassian JIRA (v6.4.11#64026)

9 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 April 2016