[JBoss JIRA] (WFLY-4336) Cannot run testsuite if an application holds port 8080 open
by Fedor Gavrilov (Jira)
[ https://issues.jboss.org/browse/WFLY-4336?page=com.atlassian.jira.plugin.... ]
Fedor Gavrilov updated WFLY-4336:
---------------------------------
Attachment: 11861.patch
> 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: Enhancement
> Components: Test Suite
> Affects Versions: 9.0.0.Alpha1
> Reporter: Michael Musgrove
> Assignee: Fedor Gavrilov
> Priority: Optional
> Fix For: Awaiting Volunteers
>
> Attachments: 11861.patch
>
>
> 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
(v7.12.1#712002)
5 years, 5 months
[JBoss JIRA] (DROOLS-3447) Remove "DMN Asset" dependency from TitledAttachmentFileWidget
by Gabriele Cardosi (Jira)
Gabriele Cardosi created DROOLS-3447:
----------------------------------------
Summary: Remove "DMN Asset" dependency from TitledAttachmentFileWidget
Key: DROOLS-3447
URL: https://issues.jboss.org/browse/DROOLS-3447
Project: Drools
Issue Type: Bug
Components: Scenario Simulation and Testing
Reporter: Gabriele Cardosi
Assignee: Gabriele Cardosi
Currently, TitledAttachmentFileWidget use ProjectAssetsQuery to retrieve the "dmn" files.
Implicitly, this means that *if* (for whatever reason) dmn editor is disabled, the dmn file are not retrieved. Wording differently, this creates an implicit dependency between scenariosimulation and dmn editor.
Fix it so that TitledAttachmentFileWidget could find dmn files regardless of dmn editor.
Look at left dock that shows all the files of the project.
--
This message was sent by Atlassian Jira
(v7.12.1#712002)
5 years, 5 months
[JBoss JIRA] (WFLY-3313) Websocket Auth - Container is not aware of the Principal
by Darran Lofthouse (Jira)
[ https://issues.jboss.org/browse/WFLY-3313?page=com.atlassian.jira.plugin.... ]
Darran Lofthouse reassigned WFLY-3313:
--------------------------------------
Assignee: Darran Lofthouse (was: Stuart Douglas)
> Websocket Auth - Container is not aware of the Principal
> --------------------------------------------------------
>
> Key: WFLY-3313
> URL: https://issues.jboss.org/browse/WFLY-3313
> Project: WildFly
> Issue Type: Bug
> Components: EJB, Security, Web (Undertow), Web Sockets
> Affects Versions: 8.1.0.CR1, 10.0.0.Final, 15.0.0.Final
> Reporter: Markus D
> Assignee: Darran Lofthouse
> Priority: Major
> Attachments: websocket-different-principals-ejb-vs-socket.png, websocket-endpoint-security.war
>
>
> The Websocket is protected by the web.xml. The session object of the callback object correctly returns the principal.
> When an EJB is called the callerPrincipal is always anonymous.
> @Resource
> private SessionContext ctx;
> Principal callerPrincipal = ctx.getCallerPrincipal();
> Running thread here:
> https://community.jboss.org/thread/240617
> Shouldn't the principal be propagated to the EJB container when a websocket callback method triggered?
--
This message was sent by Atlassian Jira
(v7.12.1#712002)
5 years, 5 months