[JBoss JIRA] (WFCORE-4294) The xxx.conf.bat files do not set java.awt.headless=true
by Marek Kopecký (Jira)
[ https://issues.jboss.org/browse/WFCORE-4294?page=com.atlassian.jira.plugi... ]
Marek Kopecký commented on WFCORE-4294:
---------------------------------------
I'm not able to reproduce original issue from WFLY-4270. Anyway, sh + bat + ps1 scripts should be unified, but java.awt.headless is used just in sh:
{noformat}
[mkopecky@dhcp-10-40-5-71 bin]$ grep -Ri java.awt.headless
domain.conf: JAVA_OPTS="$JAVA_OPTS -Djboss.modules.system.pkgs=$JBOSS_MODULES_SYSTEM_PKGS -Djava.awt.headless=true"
appclient.conf: JAVA_OPTS="$JAVA_OPTS -Djboss.modules.system.pkgs=$JBOSS_MODULES_SYSTEM_PKGS -Djava.awt.headless=true"
standalone.conf: JAVA_OPTS="$JAVA_OPTS -Djboss.modules.system.pkgs=$JBOSS_MODULES_SYSTEM_PKGS -Djava.awt.headless=true"
[mkopecky@dhcp-10-40-5-71 bin]$
{noformat}
> The xxx.conf.bat files do not set java.awt.headless=true
> --------------------------------------------------------
>
> Key: WFCORE-4294
> URL: https://issues.jboss.org/browse/WFCORE-4294
> Project: WildFly Core
> Issue Type: Bug
> Components: Scripts
> Affects Versions: 8.0.0.Beta3
> Reporter: Brian Stansberry
> Priority: Major
>
> The standalone.conf and domain.comf files include -Djava.awt.headless=true in the default JAVA_OPTS but its not there in the Windows scripts.
--
This message was sent by Atlassian Jira
(v7.12.1#712002)
6 years, 9 months
[JBoss JIRA] (WFLY-11651) Add method parameter check in jaxrs apps
by Marek Kopecký (Jira)
[ https://issues.jboss.org/browse/WFLY-11651?page=com.atlassian.jira.plugin... ]
Marek Kopecký updated WFLY-11651:
---------------------------------
Affects Version/s: 15.0.0.Final
> Add method parameter check in jaxrs apps
> ----------------------------------------
>
> Key: WFLY-11651
> URL: https://issues.jboss.org/browse/WFLY-11651
> Project: WildFly
> Issue Type: Bug
> Components: REST
> Affects Versions: 15.0.0.Final, 16.0.0.Beta1
> Reporter: R Searls
> Assignee: R Searls
> Priority: Critical
> Attachments: RESTEASY-2062.zip
>
>
> The jaxrs 2.1 spec section 3.2 require resource method parameters be checked at deployment time of errors handling @DefaultValue annotations. This must be added in wfly because
> resteasy is not called until the first client request.
> Testing
> Build and deploy attached app to wildfly.
> Before code fix deployment should be successful.
> Running app with cmd: curl "http://localhost:8080/jaxrs-wf/a?param=2"
> should fail.
> After code fix deployment should fail with detailed msg.
--
This message was sent by Atlassian Jira
(v7.12.1#712002)
6 years, 9 months
[JBoss JIRA] (SWSQE-585) Documentation
by Filip Brychta (Jira)
Filip Brychta created SWSQE-585:
-----------------------------------
Summary: Documentation
Key: SWSQE-585
URL: https://issues.jboss.org/browse/SWSQE-585
Project: Kiali QE
Issue Type: Sub-task
Reporter: Filip Brychta
Assignee: Michael Foley
Document everything related to PSI which relates to our team:
* initial request tickets
* rover group, how to login, how to update rover group
* service user account
* custom images
* ...
--
This message was sent by Atlassian Jira
(v7.12.1#712002)
6 years, 9 months
[JBoss JIRA] (SWSQE-584) Create rover group and pair it with istioci project
by Filip Brychta (Jira)
Filip Brychta created SWSQE-584:
-----------------------------------
Summary: Create rover group and pair it with istioci project
Key: SWSQE-584
URL: https://issues.jboss.org/browse/SWSQE-584
Project: Kiali QE
Issue Type: Sub-task
Reporter: Filip Brychta
Assignee: Filip Brychta
There's a change in the authentication process in the new environment. In CI-RHOS we have used only local authentication and most teams only used shared account to login to the environment. In PSI (Upshift) we switched to LDAP authentication, thus you use your Kerberos credentials to log in to the system. What we do during the initial setup is paring of the Rover group name with the particular project and then it's up to Rover group admins to manage people who should be able to access the resources in PSI. That's why we need the Rover group name from you.
When creating a Rover group please give it a different name than your LDAP group. Ambiguity could be a potential problem.
--
This message was sent by Atlassian Jira
(v7.12.1#712002)
6 years, 9 months