February 2015 - jboss-jira - Jboss List Archives

[JBoss JIRA] (WFLY-4247) Deployment fails if a web-fragment.xml references fragment name that's not present

by RH Bugzilla Integration (JIRA)

[ https://issues.jboss.org/browse/WFLY-4247?page=com.atlassian.jira.plugin.... ] RH Bugzilla Integration commented on WFLY-4247: ----------------------------------------------- Radim Hatlapatka <rhatlapa(a)redhat.com> changed the Status of [bug 1181854|https://bugzilla.redhat.com/show_bug.cgi?id=1181854] from ON_QA to VERIFIED > Deployment fails if a web-fragment.xml references fragment name that's not present > ---------------------------------------------------------------------------------- > > Key: WFLY-4247 > URL: https://issues.jboss.org/browse/WFLY-4247 > Project: WildFly > Issue Type: Bug > Components: Web (Undertow) > Affects Versions: 9.0.0.Alpha1 > Reporter: James Livingston > Assignee: Stuart Douglas > Fix For: 9.0.0.Beta1 > > > If you deploy a web application which has a web fragment with a relative ordering referring to a non-existent fragment, it will fail. This was reported for old JBossAS as JBAS-8767, Remy said the spec was not clear so he would ask, and them it was fixed for AS 6.0. > The reproducer WAR from JBAS-8767 fails to deploy on WildFly as well. I am unsure as to the result of the spec clarification on whether it should work, but since we fixed it for AS 6 it should probably be fixed in WF too. -- This message was sent by Atlassian JIRA (v6.3.11#6341)

11 years, 5 months

1
0
0 / 0

[JBoss JIRA] (DROOLS-709) fuse-bxms-integ list of build/release issues

by Geoffrey De Smet (JIRA)

Geoffrey De Smet created DROOLS-709: --------------------------------------- Summary: fuse-bxms-integ list of build/release issues Key: DROOLS-709 URL: https://issues.jboss.org/browse/DROOLS-709 Project: Drools Issue Type: Bug Reporter: Geoffrey De Smet Assignee: Edson Tirelli Priority: Blocker Here's a summary of the issues discussed in e-mail so we can track them. 1) fuse-bxms-integ violates Red Hat naming: We can't use a product name ("Fuse", "bxms") for community code. The repository contains community glue code between camel and kie, so for example "camel-kie-integ" would be better. Is drools-camel open source? If yes, then we want the community to be able to use it and report issues before we release the product version. 2) The artifacts of fuse-bxms-integ all still use the groupId "org.kie", but supposedly have their a different version numbering than org.kie's artifacts. 2 artifacts in the same groupId must use the exact same version numbering and release lifecycle! So the groupId must be changed before its released. 3) fuse-bxms-integ will use it's own version numbering, so it should not use kie's "6.2.0.Final" Either it uses a neutral number, such as "1.0.0.Final" or it defines a pattern based on it's kie and it's camel dependency. For example "6.2.0.Final-2.14.1.Final" (bad example, violates OSGi guidelines). Calling it "6.2.0.Final" is just asking for confusion and trouble, because productization scripts will presume it's 100% equal to the kie version. 4) Now one seems to have the faintest idea how we'll handle branching: think camel 2.14.x, camel 2.13.x, kie 6.2.x, camel 2.12.x, kie 6.1.x, ... 5) // Not valid 6) Renaming the java packages according to the new groupId/artifactId we will choose (as we did in the past with all other projects) and also fix the OSGi manifest and features.xml files accordingly. 7) migrating the optaplanner-camel module in the new integration project. Note: ge0ffrey will migrate optaplanner-camel after the other issues in this list are solved to avoid breaking users now. 8) It's artifacts are currently: - no longer extending droolsjbpm-parent(-with-dependencies) - no longer in the kie-bom and that the repo is no longer in our github organization or git-clone-others script, but it is part of our release. So it's already quite different than in 6.1. -- This message was sent by Atlassian JIRA (v6.3.11#6341)

11 years, 5 months

1
0
0 / 0

[JBoss JIRA] (WFLY-4336) Cannot run testsuite if an application holds port 8080 open

by Tomaz Cerar (JIRA)

[ https://issues.jboss.org/browse/WFLY-4336?page=com.atlassian.jira.plugin.... ] Tomaz Cerar commented on WFLY-4336: ----------------------------------- Why would be a requirement? for testsuite it is expected that runs on "clean" machine without other server software listening on different ports... > Cannot run testsuite if an application holds port 8080 open > ----------------------------------------------------------- > > Key: WFLY-4336 > URL: https://issues.jboss.org/browse/WFLY-4336 > Project: WildFly > Issue Type: Bug > Components: Test Suite > Affects Versions: 9.0.0.Alpha1 > Reporter: Michael Musgrove > > We run jobs on a Jenkins cluster where the master is also a slave. The master runs the web front end gui on port 8080. The default wildfly web profile uses the same port. I tried starting undertow on a different port but the testsuite has some hardcoded references to port 8080, for example: > testsuite/integration/src/test/xslt/changeIPAddresses.xsl > testsuite/integration/xts/src/test/java/org/jboss/as/test/xts/wsat/client/ATClient.java > testsuite/integration/xts/src/test/java/org/jboss/as/test/xts/wsba/coordinatorcompletion/client/BACoordinatorCompletionClient.java > testsuite/integration/xts/src/test/java/org/jboss/as/test/xts/wsba/participantcompletion/client/BAParticipantCompletionClient.java > The particular command I tried was: > {code} > ./tools/maven/bin/mvn -s tools/maven/conf/settings.xml test '-f' './testsuite/integration/xts/pom.xml' '-Pxts.integration.tests.profile' -Djboss.http.port=xxx > {code} -- This message was sent by Atlassian JIRA (v6.3.11#6341)

11 years, 5 months

1
0
0 / 0

[JBoss JIRA] (ELY-155) Condense Message IDs

by Darran Lofthouse (JIRA)

Darran Lofthouse created ELY-155: ------------------------------------ Summary: Condense Message IDs Key: ELY-155 URL: https://issues.jboss.org/browse/ELY-155 Project: WildFly Elytron Issue Type: Task Reporter: Darran Lofthouse Assignee: Darran Lofthouse Priority: Blocker Fix For: 1.0.0.Alpha1 This is a task to complete at the point of tagging, condense the message IDs to close any gaps in the numbering. -- This message was sent by Atlassian JIRA (v6.3.11#6341)

11 years, 5 months

1
0
0 / 0

[JBoss JIRA] (WFCORE-507) Unit test FileSystemDeploymentServiceUnitTestCase fails on IBM JDK

by RH Bugzilla Integration (JIRA)

[ https://issues.jboss.org/browse/WFCORE-507?page=com.atlassian.jira.plugin... ] RH Bugzilla Integration commented on WFCORE-507: ------------------------------------------------ Marek Kopecky <mkopecky(a)redhat.com> changed the Status of [bug 1182466|https://bugzilla.redhat.com/show_bug.cgi?id=1182466] from ON_QA to VERIFIED > Unit test FileSystemDeploymentServiceUnitTestCase fails on IBM JDK > -------------------------------------------------------------------- > > Key: WFCORE-507 > URL: https://issues.jboss.org/browse/WFCORE-507 > Project: WildFly Core > Issue Type: Bug > Components: Test Suite > Affects Versions: 1.0.0.Alpha15 > Reporter: Emmanuel Hugonnet > Assignee: Emmanuel Hugonnet > Priority: Trivial > Fix For: 1.0.0.Alpha16 > > > Always on IBM JDK org.jboss.as.server.deployment.scanner.FileSystemDeploymentServiceUnitTestCase.testNoUndeployment fails with: > - java.net.ConnectException: Connection refused > - java.lang.UnsupportedOperationException: cannot get the capability, performing dispose of the retransforming environment -- This message was sent by Atlassian JIRA (v6.3.11#6341)

11 years, 5 months

1
0
0 / 0

[JBoss JIRA] (WFLY-4337) Missing default configuration for allowed origins (CORS)

by Harald Pehl (JIRA)

[ https://issues.jboss.org/browse/WFLY-4337?page=com.atlassian.jira.plugin.... ] Harald Pehl closed WFLY-4337. ----------------------------- Resolution: Done Once WFCORE-535 is fixed, this one will be fixed automatically. > Missing default configuration for allowed origins (CORS) > -------------------------------------------------------- > > Key: WFLY-4337 > URL: https://issues.jboss.org/browse/WFLY-4337 > Project: WildFly > Issue Type: Bug > Components: Domain Management > Reporter: Harald Pehl > Assignee: Harald Pehl > Fix For: 9.0.0.Beta1 > > > This is the WildFly counterpart for WFCORE-535 -- This message was sent by Atlassian JIRA (v6.3.11#6341)

11 years, 5 months

1
0
0 / 0

[JBoss JIRA] (WFCORE-535) Missing default configuration for allowed origins (CORS)

by Darran Lofthouse (JIRA)

[ https://issues.jboss.org/browse/WFCORE-535?page=com.atlassian.jira.plugin... ] Darran Lofthouse commented on WFCORE-535: ----------------------------------------- I think a better solution would be an 'allow-same-origin' option otherwise there is going to be an additional attribute administrators need to update in parallel to their network configuration and bind address. > Missing default configuration for allowed origins (CORS) > -------------------------------------------------------- > > Key: WFCORE-535 > URL: https://issues.jboss.org/browse/WFCORE-535 > Project: WildFly Core > Issue Type: Bug > Components: Domain Management > Reporter: Harald Pehl > Assignee: Harald Pehl > Fix For: 1.0.0.Beta1 > > > WFCORE-302 adds support for CORS. However it's missing a default configuration for allowed origins. Without it the console does no longer work ootb. > The default list for allowed origins should at least contain > - http://127.0.0.1:9990 > - http://localhost:9990 -- This message was sent by Atlassian JIRA (v6.3.11#6341)

11 years, 5 months

1
0
0 / 0

[JBoss JIRA] (WFLY-4337) Missing default configuration for allowed origins (CORS)

by Harald Pehl (JIRA)

Harald Pehl created WFLY-4337: --------------------------------- Summary: Missing default configuration for allowed origins (CORS) Key: WFLY-4337 URL: https://issues.jboss.org/browse/WFLY-4337 Project: WildFly Issue Type: Bug Components: Domain Management Reporter: Harald Pehl Assignee: Harald Pehl Fix For: 9.0.0.Beta1 This is the WildFly counterpart for WFCORE-535 -- This message was sent by Atlassian JIRA (v6.3.11#6341)

11 years, 5 months

1
0
0 / 0

[JBoss JIRA] (WFCORE-535) Missing default configuration for allowed origins (CORS)

by Harald Pehl (JIRA)

Harald Pehl created WFCORE-535: ---------------------------------- Summary: Missing default configuration for allowed origins (CORS) Key: WFCORE-535 URL: https://issues.jboss.org/browse/WFCORE-535 Project: WildFly Core Issue Type: Bug Components: Domain Management Reporter: Harald Pehl Assignee: Harald Pehl Fix For: 1.0.0.Beta1 WFCORE-302 adds support for CORS. However it's missing a default configuration for allowed origins. Without it the console does no longer work ootb. The default list for allowed origins should at least contain - http://127.0.0.1:9990 - http://localhost:9990 -- This message was sent by Atlassian JIRA (v6.3.11#6341)

11 years, 5 months

1
0
0 / 0

[JBoss JIRA] (ELY-154) Session based DigestCredential support

by Darran Lofthouse (JIRA)

Darran Lofthouse created ELY-154: ------------------------------------ Summary: Session based DigestCredential support Key: ELY-154 URL: https://issues.jboss.org/browse/ELY-154 Project: WildFly Elytron Issue Type: Sub-task Components: Passwords Reporter: Darran Lofthouse Assignee: Darran Lofthouse Fix For: 1.0.0.Alpha1 DigestCredential but where additional information is included such as nonce and cnonce to create a credential applicable to a session. -- This message was sent by Atlassian JIRA (v6.3.11#6341)

11 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

jboss-jira February 2015