November 2015 - jbosstools-issues

[JBoss JIRA] (JBIDE-21060) Upgrade Forge Runtime to 2.20.1.Final

by George Gastaldi (JIRA)

[ https://issues.jboss.org/browse/JBIDE-21060?page=com.atlassian.jira.plugi... ] George Gastaldi resolved JBIDE-21060. ------------------------------------- Resolution: Done Labels: new_and_noteworthy (was: ) > Upgrade Forge Runtime to 2.20.1.Final > ------------------------------------- > > Key: JBIDE-21060 > URL: https://issues.jboss.org/browse/JBIDE-21060 > Project: Tools (JBoss Tools) > Issue Type: Component Upgrade > Components: forge > Affects Versions: 4.3.0.Final > Reporter: George Gastaldi > Assignee: George Gastaldi > Labels: new_and_noteworthy > Fix For: 4.4.0.Alpha1 > > -- This message was sent by Atlassian JIRA (v6.4.11#64026)

10 years, 5 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-21060) Upgrade Forge Runtime to 2.20.1.Final

by George Gastaldi (JIRA)

George Gastaldi created JBIDE-21060: --------------------------------------- Summary: Upgrade Forge Runtime to 2.20.1.Final Key: JBIDE-21060 URL: https://issues.jboss.org/browse/JBIDE-21060 Project: Tools (JBoss Tools) Issue Type: Component Upgrade Components: forge Affects Versions: 4.3.0.Final Reporter: George Gastaldi Assignee: George Gastaldi Fix For: 4.4.0.Alpha1 -- This message was sent by Atlassian JIRA (v6.4.11#64026)

10 years, 5 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-21057) Web Services Tester locks up when editing

by Andrej Podhradsky (JIRA)

[ https://issues.jboss.org/browse/JBIDE-21057?page=com.atlassian.jira.plugi... ] Andrej Podhradsky commented on JBIDE-21057: ------------------------------------------- I'm able to reproduce it also on macosx 10.11 with Oracle JDK 1.8.0_60 > Web Services Tester locks up when editing > ------------------------------------------ > > Key: JBIDE-21057 > URL: https://issues.jboss.org/browse/JBIDE-21057 > Project: Tools (JBoss Tools) > Issue Type: Bug > Components: webservices > Affects Versions: 4.2.3.Final > Environment: Mac setup: > • OS X 10.9.4 > • JBDS 8.1.0.GA-v20150327-1349-B467 > • Fuse Tooling 7.2.3.v20151008-1250-H108-CR2 > • Switchyard 2.0.1v20150923-1505-H19-CR1 > • JRE 1.7.0_25-b15 > Reporter: Jane Murphey > Assignee: Brian Fitzpatrick > Priority: Critical > Attachments: OSX_WebServicTesterHang.rtf > > > When using the tree view in the Web Service Tester to edit request message values, the entire workbench freezes. Nothing appears in the error log and I have been unable to reproduce in a Windows environment. > Will get a simpler reproducible case, but am posting what [~jmurphey] has documented so far. -- This message was sent by Atlassian JIRA (v6.4.11#64026)

10 years, 5 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-15671) WildFly / EAP domain mode management UI

by Rob Stryker (JIRA)

[ https://issues.jboss.org/browse/JBIDE-15671?page=com.atlassian.jira.plugi... ] Rob Stryker updated JBIDE-15671: -------------------------------- Fix Version/s: LATER (was: 4.2.x) > WildFly / EAP domain mode management UI > --------------------------------------- > > Key: JBIDE-15671 > URL: https://issues.jboss.org/browse/JBIDE-15671 > Project: Tools (JBoss Tools) > Issue Type: Feature Request > Components: server > Reporter: Ondrej Zizka > Assignee: Rob Stryker > Fix For: LATER > > Attachments: domainmodeinitialmockup.bmml, domainmodeinitialmockup.png > > > Max brought the topic of Domain mode management UI. > The domain mode needs a special treatment. > Logically it's a matrix, and calls for a matrix-like UI instead of a tree. > The structure would be similar to the pictures of domain mode in tutorials (TBD: link). > An inspiration may be taken from AS web console. > As a preliminary solution, a tree may be used, in which case it may omit host controllers which do not play much role in domain mode management, from the admin PoV. > The nodes would represent server groups, and their leaves would represent particular servers (JVMs). -- This message was sent by Atlassian JIRA (v6.4.11#64026)

10 years, 5 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-20996) DV 6.2 is shipped withou EAP. Can we do something about it in context of Download Runtime wizard?

by Rob Stryker (JIRA)

[ https://issues.jboss.org/browse/JBIDE-20996?page=com.atlassian.jira.plugi... ] Rob Stryker updated JBIDE-20996: -------------------------------- Fix Version/s: 4.4.0.Alpha1 > DV 6.2 is shipped withou EAP. Can we do something about it in context of Download Runtime wizard? > ------------------------------------------------------------------------------------------------- > > Key: JBIDE-20996 > URL: https://issues.jboss.org/browse/JBIDE-20996 > Project: Tools (JBoss Tools) > Issue Type: Enhancement > Components: runtime-detection > Affects Versions: 4.3.0.Final > Reporter: Radim Hopp > Fix For: 4.4.0.Alpha1 > > > It's great that now, with JBIDE-19852 and JBIDE-20769 resolved, one can download DV 6.2 using Download Runtimes wizard and have the installation path pre-filled. But the DV 6.2 installator requires EAP 6.4 already present on user's machine (and the installation path must point to its JBOSS_HOME). If user does not have EAP 6.4, he has to exit wizard, install EAP 6.4 and then download (again) and install DV 6.2. > Is there anything we could do to make this workflow easier. > Maybe at least tell user to install EAP 6.4 prior downloading DV 6.2? -- 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 Rob Stryker (JIRA)

[ https://issues.jboss.org/browse/JBIDE-20990?page=com.atlassian.jira.plugi... ] Rob Stryker updated JBIDE-20990: -------------------------------- Fix Version/s: 4.4.0.Alpha1 > 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 > Fix For: 4.4.0.Alpha1 > > > 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-21034) new Runtime detector fails to use default (ext-pt) enablement if user has previouslymodified enablement list

by Rob Stryker (JIRA)

[ https://issues.jboss.org/browse/JBIDE-21034?page=com.atlassian.jira.plugi... ] Rob Stryker updated JBIDE-21034: -------------------------------- Fix Version/s: 4.3.1.Beta1 > new Runtime detector fails to use default (ext-pt) enablement if user has previouslymodified enablement list > ------------------------------------------------------------------------------------------------------------ > > Key: JBIDE-21034 > URL: https://issues.jboss.org/browse/JBIDE-21034 > Project: Tools (JBoss Tools) > Issue Type: Bug > Components: runtime-detection > Affects Versions: 4.3.0.Final > Reporter: Rob Stryker > Fix For: 4.3.1.Beta1 > > > Small coding error causes a new runtime detector to not have its default enablement respected if a user has previously modified the enablement of any detector. -- This message was sent by Atlassian JIRA (v6.4.11#64026)

10 years, 5 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-20830) "src-resolve: Cannot resolve the name 'javaee:jboss-ejb-beanType'

by Rob Stryker (JIRA)

[ https://issues.jboss.org/browse/JBIDE-20830?page=com.atlassian.jira.plugi... ] Rob Stryker updated JBIDE-20830: -------------------------------- Fix Version/s: 4.3.1.Final (was: 4.3.0.Final) > "src-resolve: Cannot resolve the name 'javaee:jboss-ejb-beanType' > ----------------------------------------------------------------- > > Key: JBIDE-20830 > URL: https://issues.jboss.org/browse/JBIDE-20830 > Project: Tools (JBoss Tools) > Issue Type: Sub-task > Components: upstream > Reporter: The Alchemist > Assignee: Rob Stryker > Priority: Minor > Fix For: 4.3.1.Final > > Attachments: screenshot.png > > > h2. Offending ejb-jar.xml > If you have the following {{ejb-jar.xml}}, which I got from [this Wildfly Wiki page|https://docs.jboss.org/author/display/WFLY8/jboss-ejb3.xml+Reference]: > {code:xml} > <?xml version="1.0"?> > <jboss:ejb-jar xmlns:jboss="http://www.jboss.com/xml/ns/javaee" > xmlns="http://java.sun.com/xml/ns/javaee" > xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance" > xmlns:s="urn:security:1.1" > xsi:schemaLocation="http://www.jboss.com/xml/ns/javaee http://www.jboss.org/j2ee/schema/jboss-ejb3-2_0.xsd http://java.sun.com/xml/ns/javaee http://java.sun.com/xml/ns/javaee/ejb-jar_3_1.xsd" > version="3.1" > impl-version="2.0"> > <enterprise-beans> > <message-driven> > <ejb-name>ReplyingMDB</ejb-name> > <ejb-class>org.jboss.as.test.integration.ejb.mdb.messagedestination.ReplyingMDB</ejb-class> > <activation-config> > <activation-config-property> > <activation-config-property-name>destination</activation-config-property-name> > <activation-config-property-value>java:jboss/mdbtest/messageDestinationQueue > </activation-config-property-value> > </activation-config-property> > </activation-config> > </message-driven> > </enterprise-beans> > <assembly-descriptor> > <s:security> > <ejb-name>DDMyDomainSFSB</ejb-name> > <s:security-domain>myDomain</s:security-domain> > <s:run-as-principal>myPrincipal</s:run-as-principal> > </s:security> > </assembly-descriptor> > </jboss:ejb-jar> > {code} > h2. Errors/Warnings > You'll get a few warnings: > !screenshot.png! > In the console: > {noformat} > Description Resource Path Location Type > Referenced file contains errors (jar:file:/Users/me/Applications/sts-bundle/STS.app/Contents/Eclipse/plugins/org.jboss.tools.as.catalog_3.1.0.Beta2-v20150723-0026-B29.jar!/schema/xsd/jboss-ejb3-2_0.xsd). For more information, right click on the message in the Problems View and select "Show Details..." jboss-ejb3.xml /my-project/src/main/resources/META-INF line 1 XML Problem > {noformat} > h2. Related issues > * https://bugzilla.redhat.com/show_bug.cgi?id=1193543 -- This message was sent by Atlassian JIRA (v6.4.11#64026)

10 years, 5 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-20830) "src-resolve: Cannot resolve the name 'javaee:jboss-ejb-beanType'

by Rob Stryker (JIRA)

[ https://issues.jboss.org/browse/JBIDE-20830?page=com.atlassian.jira.plugi... ] Rob Stryker updated JBIDE-20830: -------------------------------- Fix Version/s: 4.4.0.Final (was: 4.3.0.Final) > "src-resolve: Cannot resolve the name 'javaee:jboss-ejb-beanType' > ----------------------------------------------------------------- > > Key: JBIDE-20830 > URL: https://issues.jboss.org/browse/JBIDE-20830 > Project: Tools (JBoss Tools) > Issue Type: Sub-task > Components: upstream > Reporter: The Alchemist > Assignee: Rob Stryker > Priority: Minor > Fix For: 4.3.0.Final > > Attachments: screenshot.png > > > h2. Offending ejb-jar.xml > If you have the following {{ejb-jar.xml}}, which I got from [this Wildfly Wiki page|https://docs.jboss.org/author/display/WFLY8/jboss-ejb3.xml+Reference]: > {code:xml} > <?xml version="1.0"?> > <jboss:ejb-jar xmlns:jboss="http://www.jboss.com/xml/ns/javaee" > xmlns="http://java.sun.com/xml/ns/javaee" > xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance" > xmlns:s="urn:security:1.1" > xsi:schemaLocation="http://www.jboss.com/xml/ns/javaee http://www.jboss.org/j2ee/schema/jboss-ejb3-2_0.xsd http://java.sun.com/xml/ns/javaee http://java.sun.com/xml/ns/javaee/ejb-jar_3_1.xsd" > version="3.1" > impl-version="2.0"> > <enterprise-beans> > <message-driven> > <ejb-name>ReplyingMDB</ejb-name> > <ejb-class>org.jboss.as.test.integration.ejb.mdb.messagedestination.ReplyingMDB</ejb-class> > <activation-config> > <activation-config-property> > <activation-config-property-name>destination</activation-config-property-name> > <activation-config-property-value>java:jboss/mdbtest/messageDestinationQueue > </activation-config-property-value> > </activation-config-property> > </activation-config> > </message-driven> > </enterprise-beans> > <assembly-descriptor> > <s:security> > <ejb-name>DDMyDomainSFSB</ejb-name> > <s:security-domain>myDomain</s:security-domain> > <s:run-as-principal>myPrincipal</s:run-as-principal> > </s:security> > </assembly-descriptor> > </jboss:ejb-jar> > {code} > h2. Errors/Warnings > You'll get a few warnings: > !screenshot.png! > In the console: > {noformat} > Description Resource Path Location Type > Referenced file contains errors (jar:file:/Users/me/Applications/sts-bundle/STS.app/Contents/Eclipse/plugins/org.jboss.tools.as.catalog_3.1.0.Beta2-v20150723-0026-B29.jar!/schema/xsd/jboss-ejb3-2_0.xsd). For more information, right click on the message in the Problems View and select "Show Details..." jboss-ejb3.xml /my-project/src/main/resources/META-INF line 1 XML Problem > {noformat} > h2. Related issues > * https://bugzilla.redhat.com/show_bug.cgi?id=1193543 -- This message was sent by Atlassian JIRA (v6.4.11#64026)

10 years, 5 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-20830) "src-resolve: Cannot resolve the name 'javaee:jboss-ejb-beanType'

by Rob Stryker (JIRA)

[ https://issues.jboss.org/browse/JBIDE-20830?page=com.atlassian.jira.plugi... ] Rob Stryker updated JBIDE-20830: -------------------------------- Fix Version/s: 4.3.0.Final (was: 4.4.0.Final) > "src-resolve: Cannot resolve the name 'javaee:jboss-ejb-beanType' > ----------------------------------------------------------------- > > Key: JBIDE-20830 > URL: https://issues.jboss.org/browse/JBIDE-20830 > Project: Tools (JBoss Tools) > Issue Type: Sub-task > Components: upstream > Reporter: The Alchemist > Assignee: Rob Stryker > Priority: Minor > Fix For: 4.3.0.Final > > Attachments: screenshot.png > > > h2. Offending ejb-jar.xml > If you have the following {{ejb-jar.xml}}, which I got from [this Wildfly Wiki page|https://docs.jboss.org/author/display/WFLY8/jboss-ejb3.xml+Reference]: > {code:xml} > <?xml version="1.0"?> > <jboss:ejb-jar xmlns:jboss="http://www.jboss.com/xml/ns/javaee" > xmlns="http://java.sun.com/xml/ns/javaee" > xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance" > xmlns:s="urn:security:1.1" > xsi:schemaLocation="http://www.jboss.com/xml/ns/javaee http://www.jboss.org/j2ee/schema/jboss-ejb3-2_0.xsd http://java.sun.com/xml/ns/javaee http://java.sun.com/xml/ns/javaee/ejb-jar_3_1.xsd" > version="3.1" > impl-version="2.0"> > <enterprise-beans> > <message-driven> > <ejb-name>ReplyingMDB</ejb-name> > <ejb-class>org.jboss.as.test.integration.ejb.mdb.messagedestination.ReplyingMDB</ejb-class> > <activation-config> > <activation-config-property> > <activation-config-property-name>destination</activation-config-property-name> > <activation-config-property-value>java:jboss/mdbtest/messageDestinationQueue > </activation-config-property-value> > </activation-config-property> > </activation-config> > </message-driven> > </enterprise-beans> > <assembly-descriptor> > <s:security> > <ejb-name>DDMyDomainSFSB</ejb-name> > <s:security-domain>myDomain</s:security-domain> > <s:run-as-principal>myPrincipal</s:run-as-principal> > </s:security> > </assembly-descriptor> > </jboss:ejb-jar> > {code} > h2. Errors/Warnings > You'll get a few warnings: > !screenshot.png! > In the console: > {noformat} > Description Resource Path Location Type > Referenced file contains errors (jar:file:/Users/me/Applications/sts-bundle/STS.app/Contents/Eclipse/plugins/org.jboss.tools.as.catalog_3.1.0.Beta2-v20150723-0026-B29.jar!/schema/xsd/jboss-ejb3-2_0.xsd). For more information, right click on the message in the Problems View and select "Show Details..." jboss-ejb3.xml /my-project/src/main/resources/META-INF line 1 XML Problem > {noformat} > h2. Related issues > * https://bugzilla.redhat.com/show_bug.cgi?id=1193543 -- 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 November 2015