January 2016 - jbosstools-issues - Jboss List Archives

[JBoss JIRA] (JBDS-3560) Arbitrary remote code execution with InvokerTransformer (COLLECTIONS-580)

by Alexey Kazakov (JIRA)

[ https://issues.jboss.org/browse/JBDS-3560?page=com.atlassian.jira.plugin.... ] Alexey Kazakov updated JBDS-3560: --------------------------------- Fix Version/s: 9.1.0.CR1 (was: 9.1.0.Beta2) > Arbitrary remote code execution with InvokerTransformer (COLLECTIONS-580) > ------------------------------------------------------------------------- > > Key: JBDS-3560 > URL: https://issues.jboss.org/browse/JBDS-3560 > Project: Developer Studio (JBoss Developer Studio) > Issue Type: Bug > Components: upstream > Affects Versions: 8.1.0.GA, 9.0.0.GA, 10.0.0.Alpha1 > Reporter: Nick Boldt > Assignee: Nick Boldt > Fix For: 9.1.0.CR1, 10.0.0.Alpha1 > > Attachments: apache-commons-collections-in-JBDS7,8,9,10.png, apache-commons-collections-in-JBDS7,8,9,10_refs1.png, apache-commons-collections-in-JBDS7,8,9,10_refs10.png, apache-commons-collections-in-JBDS7,8,9,10_refs7.png, apache-commons-collections-in-JBDS7,8,9,10_refs8-IS-fuse.png, apache-commons-collections-in-JBDS7,8,9,10_refs8.png, apache-commons-collections-in-JBDS7,8,9,10_refs9.png, orbit.R20150519210750_vs_I20151117200049.log.txt, orbit.R20150519210750_vs_I20151117200049.log_onlyLatest.txt > > > This is a container issue to wrap & track https://issues.apache.org/jira/browse/COLLECTIONS-580 > Problem is that JBDS 9 (and probably 8 and 10 too) include org.apache.commons.collections 3.2.0.v2013030210310, which is affected by COLLECTIONS-580 - Arbitrary remote code execution with InvokerTransformer -- This message was sent by Atlassian JIRA (v6.4.11#64026)

10 years, 5 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-18497) Importing PicketLink quickstart raises error

by Rob Stryker (JIRA)

[ https://issues.jboss.org/browse/JBIDE-18497?page=com.atlassian.jira.plugi... ] Rob Stryker updated JBIDE-18497: -------------------------------- Fix Version/s: 4.4.0.Alpha1 (was: 4.3.1.Beta2) > Importing PicketLink quickstart raises error > -------------------------------------------- > > Key: JBIDE-18497 > URL: https://issues.jboss.org/browse/JBIDE-18497 > Project: Tools (JBoss Tools) > Issue Type: Sub-task > Components: server > Affects Versions: 4.2.0.CR1 > Environment: JBDS 8.0.CR1 > Java 1.7 - OpenJDK > RHEL6 > Reporter: Len DiMaggio > Assignee: Rob Stryker > Labels: upstream, xml_validation_quickstarts_redirect > Fix For: 4.4.0.Alpha1 > > > Steps to recreate issue: > * Dowload, unzip EAP quickstarts from - http://www.jboss.org/quickstarts/eap > * Install JBDS8.0.CR1 > * Import-> Existing Maven Projects - select the quickstart > The error is: > jboss-picketlink-sts > Referenced file contains errors (http://www.jboss.com/ws-security/schema/jboss-ws-security_1_0.xsd). For more information, right click on the message in the Problems View and select "Show Details..." jboss-wsse-server.xml /jboss-picketlink-sts/src/main/webapp/WEB-INF line 1 XML Problem -- This message was sent by Atlassian JIRA (v6.4.11#64026)

10 years, 5 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-20536) Several quickstarts fail; jboss-ejb3-2_0.xsd cannot resolve jboss elements

by Rob Stryker (JIRA)

[ https://issues.jboss.org/browse/JBIDE-20536?page=com.atlassian.jira.plugi... ] Rob Stryker updated JBIDE-20536: -------------------------------- Fix Version/s: 4.4.0.Alpha1 (was: 4.3.1.Beta2) > Several quickstarts fail; jboss-ejb3-2_0.xsd cannot resolve jboss elements > --------------------------------------------------------------------------- > > Key: JBIDE-20536 > URL: https://issues.jboss.org/browse/JBIDE-20536 > Project: Tools (JBoss Tools) > Issue Type: Sub-task > Components: server, upstream > Reporter: Rob Stryker > Labels: xml_validation_quickstarts_eap7, xml_validation_quickstarts_wildfly, xml_validation_schema_error > Fix For: 4.4.0.Alpha1 > > > Several errors fail with the following error message: > Referenced file contains errors (file:/home/rob/code/fuseide/fuseide/targetplatform/target/org.fusesource.ide.targetplatform.target.repo/../../../../../jbtools/github/jbosstools-server/as/plugins/org.jboss.tools.as.catalog/schema/xsd/jboss-ejb3-2_0.xsd). For more information, right click on the message in the Problems View and select "Show Details..." > The schema seems to fail to resolve any elements that have 'jboss' in them, for example: > {code} > <xs:element name="enterprise-beans" type="javaee:jboss-enterprise-beansType"/> > {code} > When looking at the entire xsd space, I see no attempt to reference or import any remote schema or any jboss schema url or namespace. > The offending schema file is here: > {code}<xs:schema xmlns:xs="http://www.w3.org/2001/XMLSchema" > targetNamespace="http://www.jboss.com/xml/ns/javaee" > xmlns="http://www.jboss.com/xml/ns/javaee" > xmlns:javaee="http://java.sun.com/xml/ns/javaee" > elementFormDefault="qualified" > attributeFormDefault="unqualified" > version="2.0"> >  >  > <xs:import namespace="http://java.sun.com/xml/ns/javaee"/> > <xs:element name="ejb" type="javaee:jboss-ejb-beanType"/> > <xs:element name="ejb-jar" type="javaee:jboss-ejb-jarType"/> > <xs:element name="enterprise-beans" type="javaee:jboss-enterprise-beansType"/> > <xs:element name="destination-jndi-name" type="xs:string" /> > <xs:element name="distinct-name" type="xs:string"> > <xs:annotation> > <xs:documentation> > The distinct-name for this EJB module. > </xs:documentation> > </xs:annotation> > </xs:element> > </xs:schema> > {code} > Perhaps I'm not understanding xml enough, but I kinda agree with the validator here, in that there's no clear way to resolve any of the jboss-* elements. -- This message was sent by Atlassian JIRA (v6.4.11#64026)

10 years, 5 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-20538) wildfly-ejb-multi-server-app-one-ejb quickstart upstream schema error

by Rob Stryker (JIRA)

[ https://issues.jboss.org/browse/JBIDE-20538?page=com.atlassian.jira.plugi... ] Rob Stryker updated JBIDE-20538: -------------------------------- Fix Version/s: 4.4.0.Alpha1 (was: 4.3.1.Beta2) > wildfly-ejb-multi-server-app-one-ejb quickstart upstream schema error > --------------------------------------------------------------------- > > Key: JBIDE-20538 > URL: https://issues.jboss.org/browse/JBIDE-20538 > Project: Tools (JBoss Tools) > Issue Type: Sub-task > Components: server > Reporter: Rob Stryker > Labels: xml_validation_schema_error > Fix For: 4.4.0.Alpha1 > > > Root cause here seems to be that the xsd on the web url http://www.jboss.org/schema/jbossas/jboss-ejb3-spec-2_0.xsd has a schemaLocation=jboss-ejb3-2_0.xsd relative path -- 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.Alpha1 (was: 4.3.1.Beta2) > "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.4.0.Alpha1 > > 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-21340) Deploy from existing project git constraints are too stringent

by Fred Bricon (JIRA)

[ https://issues.jboss.org/browse/JBIDE-21340?page=com.atlassian.jira.plugi... ] Fred Bricon edited comment on JBIDE-21340 at 1/20/16 3:35 PM: -------------------------------------------------------------- Fixed in master / 4.3.x. Now only a warning shows up if no HTTP(S)-based git remote is defined. Git-dirty projects are now allowed. Enforcing the Git source property will be implemented later, via JBIDE-21490 was (Author: fbricon): Fixed in master / 4.3.x. Now only a warning shows up if no HTTP(S)-based git remote is defined. Git-dirty projects are now allowed > Deploy from existing project git constraints are too stringent > -------------------------------------------------------------- > > Key: JBIDE-21340 > URL: https://issues.jboss.org/browse/JBIDE-21340 > Project: Tools (JBoss Tools) > Issue Type: Bug > Components: openshift > Affects Versions: 4.3.1.Beta1 > Reporter: Fred Bricon > Assignee: Andre Dietisheim > Fix For: 4.3.1.Beta2 > > > There are currently 2 constraints when deploying ane existing project to OpenShift 3 that are really really annoying: > - if the project is shared with git but dirty, you can't proceed with project deployment on openshift. This constraint is completely unnecessary and should be lifted > - if the project was cloned using git/ssh protocol, it can't be deployed directly (http(s) is required). This should actually just be a warning, the user can modify the git url to use http(s) in the next page -- This message was sent by Atlassian JIRA (v6.4.11#64026)

10 years, 5 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-21468) Delete project menu entry is not enabled to delete a project

by Fred Bricon (JIRA)

[ https://issues.jboss.org/browse/JBIDE-21468?page=com.atlassian.jira.plugi... ] Fred Bricon resolved JBIDE-21468. --------------------------------- Assignee: Fred Bricon (was: Jeff Cantrill) Resolution: Done Fixed in master / 4.3.x > Delete project menu entry is not enabled to delete a project > ------------------------------------------------------------ > > Key: JBIDE-21468 > URL: https://issues.jboss.org/browse/JBIDE-21468 > Project: Tools (JBoss Tools) > Issue Type: Bug > Components: openshift > Affects Versions: 4.3.1.Beta1 > Reporter: Jeff Cantrill > Assignee: Fred Bricon > Labels: openshift_deployment_view > Fix For: 4.3.1.Beta2 > > -- This message was sent by Atlassian JIRA (v6.4.11#64026)

10 years, 5 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-20480) Explorer, Manage Project wizard: Unable to delete projects

by Fred Bricon (JIRA)

[ https://issues.jboss.org/browse/JBIDE-20480?page=com.atlassian.jira.plugi... ] Fred Bricon resolved JBIDE-20480. --------------------------------- Resolution: Done This has been fixed as part of the new explorer work. In master / 4.3.x > Explorer, Manage Project wizard: Unable to delete projects > ---------------------------------------------------------- > > Key: JBIDE-20480 > URL: https://issues.jboss.org/browse/JBIDE-20480 > Project: Tools (JBoss Tools) > Issue Type: Bug > Components: openshift > Affects Versions: 4.3.0.CR1 > Reporter: Jeff Cantrill > Assignee: Jeff Cantrill > Labels: explorer, manage_projects_wizard, openshift_v3 > Fix For: 4.3.1.Beta2 > > Attachments: screenshot-1.png > > > Unable to delete projects from either right click or the manage projects. > !screenshot-1.png! -- This message was sent by Atlassian JIRA (v6.4.11#64026)

10 years, 5 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-21453) Server Adapter: use rsync flag instead of local filtered-copy

by Fred Bricon (JIRA)

[ https://issues.jboss.org/browse/JBIDE-21453?page=com.atlassian.jira.plugi... ] Fred Bricon updated JBIDE-21453: -------------------------------- Fix Version/s: 4.3.1.CR1 (was: 4.3.1.Beta2) > Server Adapter: use rsync flag instead of local filtered-copy > ------------------------------------------------------------- > > Key: JBIDE-21453 > URL: https://issues.jboss.org/browse/JBIDE-21453 > Project: Tools (JBoss Tools) > Issue Type: Enhancement > Components: openshift > Affects Versions: 4.3.1.Beta1 > Reporter: Andre Dietisheim > Fix For: 4.3.1.CR1 > > > With https://github.com/openshift/origin/issues/6143 *oc rsync* now allows specific white-listed flag to be used. > Our current implementation works around this by doing a local copy where excluded bits are filtered (not copied). We need to use exclusion flags if available. -- This message was sent by Atlassian JIRA (v6.4.11#64026)

10 years, 5 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-21486) HTML5 Project and Java EE Web Project in the Getting Started tab do not allow clicking

by Alexey Kazakov (JIRA)

[ https://issues.jboss.org/browse/JBIDE-21486?page=com.atlassian.jira.plugi... ] Alexey Kazakov reassigned JBIDE-21486: -------------------------------------- Assignee: Konstantin Marmalyukov (was: Radim Hopp) [~kmarmaliykov] could you please take a look? > HTML5 Project and Java EE Web Project in the Getting Started tab do not allow clicking > --------------------------------------------------------------------------------------- > > Key: JBIDE-21486 > URL: https://issues.jboss.org/browse/JBIDE-21486 > Project: Tools (JBoss Tools) > Issue Type: Bug > Components: central > Affects Versions: 4.3.1.Beta1 > Reporter: Supriya Bharadwaj > Assignee: Konstantin Marmalyukov > Fix For: 4.3.1.CR1, 4.4.0.Alpha1 > > > I have downloaded Red Hat JBoss Developer Studio 9.1.0 Beta 1 Installer with EAP from the Customer Portal (https://access.redhat.com/jbossnetwork/restricted/listSoftware.html?produ...). > In the Getting Started tab, if I hover the mouse over HTML5 Project and Java EE Web Project, the display keeps moving and does not allow me to click these two project types. A possible bug? -- 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 January 2016