[JBoss JIRA] (WFLY-11242) Provide builtin ParamConverter* classes for multi valued params
by James Perkins (Jira)
[ https://issues.jboss.org/browse/WFLY-11242?page=com.atlassian.jira.plugin... ]
James Perkins updated WFLY-11242:
---------------------------------
Fix Version/s: (was: 15.0.0.CR1)
> Provide builtin ParamConverter* classes for multi valued params
> ---------------------------------------------------------------
>
> Key: WFLY-11242
> URL: https://issues.jboss.org/browse/WFLY-11242
> Project: WildFly
> Issue Type: Feature Request
> Reporter: Marek Kopecký
> Assignee: Ron Sigal
> Priority: Major
>
> This is follow up for RESTEASY-1746 and RESTEASY-1566. In these feature jiras, users needs to prepare custom ParamConverter* classes in deployment.
> This feature should provide builtin ParamConverter* universal classes.
> Some PoC is in [this commit|https://github.com/marekkopecky/Resteasy/commit/08e0eb6de206085593...]
> Suitable annotations for end-point can parametrize converter behaviour. [~ron_sigal]'s proposal:
> {noformat}Maybe annotations in
> > public <T> ParamConverter<T> getConverter(Class<T> rawType, Type genericType, Annotation[] annotations;
> could be used to generalize. E.g.,
> public Response conversion1(@QueryParam @Separator("&") List<MultiValueParamBuiltinMyObject1> q);
> Even more general could be something like
> public Response conversion1(@QueryParam @MultiSyntax(<regular expression/>) List<MultiValueParamBuiltinMyObject1> q) {{noformat}
--
This message was sent by Atlassian Jira
(v7.12.1#712002)
6 years, 10 months
[JBoss JIRA] (WFCORE-4132) LogManager stops any logging output after changing "encoding" attribute to file-handler
by James Perkins (Jira)
[ https://issues.jboss.org/browse/WFCORE-4132?page=com.atlassian.jira.plugi... ]
James Perkins commented on WFCORE-4132:
---------------------------------------
This will require an upgrade to {{org.jboss.logmanager:jboss-logmanager:2.2.0.Final}}.
> LogManager stops any logging output after changing "encoding" attribute to file-handler
> ---------------------------------------------------------------------------------------
>
> Key: WFCORE-4132
> URL: https://issues.jboss.org/browse/WFCORE-4132
> Project: WildFly Core
> Issue Type: Bug
> Components: Logging
> Reporter: Masafumi Miura
> Assignee: James Perkins
> Priority: Major
>
> When setting "encoding" attribute on the file handler (file-handler, periodic-rotating-file-handler, size-rotating-file-handler, and periodic-size-rotating-file-handler) in CLI, LogManager throw the following error message in the console log and stops any logging output to the file-handler.
> Note that the stack trace below "org.jboss.logmanager.Logger.logRaw(Logger.java:850)" can differ. It looks like this error just happens on the first logging output after the configuration change.
> Even after executing ":reload" the instance via CLI, no log message are output to the file-handler. The instance needs to restart to output the file-handler.
> {code}
> LogManager error of type FLUSH_FAILURE: Error on flush
> java.io.IOException: Stream Closed
> at java.io.FileOutputStream.writeBytes(Native Method)
> at java.io.FileOutputStream.write(FileOutputStream.java:326)
> at java.io.BufferedOutputStream.flushBuffer(BufferedOutputStream.java:82)
> at java.io.BufferedOutputStream.flush(BufferedOutputStream.java:140)
> at org.jboss.logmanager.handlers.UninterruptibleOutputStream.flush(UninterruptibleOutputStream.java:110)
> at sun.nio.cs.StreamEncoder.implFlush(StreamEncoder.java:297)
> at sun.nio.cs.StreamEncoder.flush(StreamEncoder.java:141)
> at java.io.OutputStreamWriter.flush(OutputStreamWriter.java:229)
> at java.io.BufferedWriter.flush(BufferedWriter.java:254)
> at org.jboss.logmanager.handlers.WriterHandler.safeFlush(WriterHandler.java:170)
> at org.jboss.logmanager.handlers.WriterHandler.flush(WriterHandler.java:139)
> at org.jboss.logmanager.ExtHandler.doPublish(ExtHandler.java:105)
> at org.jboss.logmanager.handlers.WriterHandler.doPublish(WriterHandler.java:67)
> at org.jboss.logmanager.ExtHandler.publish(ExtHandler.java:77)
> at org.jboss.logmanager.LoggerNode.publish(LoggerNode.java:333)
> at org.jboss.logmanager.LoggerNode.publish(LoggerNode.java:341)
> at org.jboss.logmanager.LoggerNode.publish(LoggerNode.java:341)
> at org.jboss.logmanager.LoggerNode.publish(LoggerNode.java:341)
> at org.jboss.logmanager.LoggerNode.publish(LoggerNode.java:341)
> at org.jboss.logmanager.LoggerNode.publish(LoggerNode.java:341)
> at org.jboss.logmanager.Logger.logRaw(Logger.java:850)
> at org.jboss.logmanager.Logger.log(Logger.java:802)
> at org.jboss.logging.JBossLogManagerLogger.doLogf(JBossLogManagerLogger.java:53)
> at org.jboss.logging.Logger.logf(Logger.java:2398)
> at org.jboss.as.mail.extension.MailLogger_$logger.unboundMailSession(MailLogger_$logger.java:42)
> at org.jboss.as.mail.extension.MailSessionAdd$1.handleEvent(MailSessionAdd.java:150)
> at org.jboss.msc.service.ServiceControllerImpl$LifecycleListenerTask.execute(ServiceControllerImpl.java:1857)
> at org.jboss.msc.service.ServiceControllerImpl$ControllerTask.run(ServiceControllerImpl.java:1556)
> at org.jboss.threads.ContextClassLoaderSavingRunnable.run(ContextClassLoaderSavingRunnable.java:35)
> at org.jboss.threads.EnhancedQueueExecutor.safeRun(EnhancedQueueExecutor.java:1985)
> at org.jboss.threads.EnhancedQueueExecutor$ThreadBody.doRunTask(EnhancedQueueExecutor.java:1487)
> at org.jboss.threads.EnhancedQueueExecutor$ThreadBody.run(EnhancedQueueExecutor.java:1364)
> at java.lang.Thread.run(Thread.java:748)
> {code}
--
This message was sent by Atlassian Jira
(v7.12.1#712002)
6 years, 10 months
[JBoss JIRA] (DROOLS-3393) Please review scenario error cell text for legibility/accessibility.
by Liz Clayton (Jira)
[ https://issues.jboss.org/browse/DROOLS-3393?page=com.atlassian.jira.plugi... ]
Liz Clayton commented on DROOLS-3393:
-------------------------------------
p.s. [~kkufova] [~bdellasc] Please advise also if you think the error state needs a redundant cue of some sort (icon, bolded cell border...), rather than relying on color alone. Thanks!
> Please review scenario error cell text for legibility/accessibility.
> ---------------------------------------------------------------------
>
> Key: DROOLS-3393
> URL: https://issues.jboss.org/browse/DROOLS-3393
> Project: Drools
> Issue Type: Task
> Components: Scenario Simulation and Testing
> Reporter: Liz Clayton
> Assignee: Klara Kufova
> Priority: Major
> Labels: ScenarioSimulation, UX, UXTeam
> Attachments: Screen Shot 2018-11-30 at 11.59.32 AM.png, Screen Shot 2018-11-30 at 12.05.50 PM.png, Screenshot from 2018-11-30 17-11-43.png
>
>
> [~kkufova] [~bdellasc]
> I noticed that the error text is a little "fuzzy" looking, the edges aren't very sharp and I was concerned that it might not be legible. I asked Danielle about the specs for it and it's the same size just bolded.
> I did an online accessibility text using the following tool, with our current hex values: https://webaim.org/resources/contrastchecker/. It failed for level 3 compliance, but I'm not sure we need to shoot for that or not? I tried the darker PatternFly red color "#8b0000" and it passed at all levels, even at smaller sizes.
> I'm wondering if we could use the darker red, in the non-bolded font? And if so, perhaps the text would be a little bit more legible.
> Just wanted to ask about this, please let me know what you think.
--
This message was sent by Atlassian Jira
(v7.12.1#712002)
6 years, 10 months
[JBoss JIRA] (DROOLS-3049) [DMN Designer] NameAndDataTypeEditorViewImpl needs to hide if the User navigates to the Data Type dialog
by Guilherme Carreiro (Jira)
[ https://issues.jboss.org/browse/DROOLS-3049?page=com.atlassian.jira.plugi... ]
Guilherme Carreiro updated DROOLS-3049:
---------------------------------------
Labels: drools-tools (was: )
> [DMN Designer] NameAndDataTypeEditorViewImpl needs to hide if the User navigates to the Data Type dialog
> ---------------------------------------------------------------------------------------------------------
>
> Key: DROOLS-3049
> URL: https://issues.jboss.org/browse/DROOLS-3049
> Project: Drools
> Issue Type: Bug
> Components: DMN Editor
> Affects Versions: 7.12.0.Final
> Reporter: Michael Anstis
> Assignee: Guilherme Carreiro
> Priority: Minor
> Labels: drools-tools
>
> The {{NameAndDataTypeEditorViewImpl}} contains a link to the "Data Type Dialog". When this is clicked on the dialog is displayed and the _source_ {{Popover}} remains visible. When the User clicks on the dialog a mouse event is detected that is not _over_ the {{Popover}} and it closes. The proposal is to close the {{Popover}} if the User clicks on the link to the "Data Type Dialog".
--
This message was sent by Atlassian Jira
(v7.12.1#712002)
6 years, 10 months
[JBoss JIRA] (DROOLS-3049) [DMN Designer] NameAndDataTypeEditorViewImpl needs to hide if the User navigates to the Data Type dialog
by Guilherme Carreiro (Jira)
[ https://issues.jboss.org/browse/DROOLS-3049?page=com.atlassian.jira.plugi... ]
Guilherme Carreiro updated DROOLS-3049:
---------------------------------------
Sprint: 2018 Week 48-50
> [DMN Designer] NameAndDataTypeEditorViewImpl needs to hide if the User navigates to the Data Type dialog
> ---------------------------------------------------------------------------------------------------------
>
> Key: DROOLS-3049
> URL: https://issues.jboss.org/browse/DROOLS-3049
> Project: Drools
> Issue Type: Bug
> Components: DMN Editor
> Affects Versions: 7.12.0.Final
> Reporter: Michael Anstis
> Assignee: Guilherme Carreiro
> Priority: Minor
>
> The {{NameAndDataTypeEditorViewImpl}} contains a link to the "Data Type Dialog". When this is clicked on the dialog is displayed and the _source_ {{Popover}} remains visible. When the User clicks on the dialog a mouse event is detected that is not _over_ the {{Popover}} and it closes. The proposal is to close the {{Popover}} if the User clicks on the link to the "Data Type Dialog".
--
This message was sent by Atlassian Jira
(v7.12.1#712002)
6 years, 10 months
[JBoss JIRA] (DROOLS-3030) [DMN Designer] Expand / Collapse all
by Guilherme Carreiro (Jira)
[ https://issues.jboss.org/browse/DROOLS-3030?page=com.atlassian.jira.plugi... ]
Guilherme Carreiro resolved DROOLS-3030.
----------------------------------------
Resolution: Done
> [DMN Designer] Expand / Collapse all
> ------------------------------------
>
> Key: DROOLS-3030
> URL: https://issues.jboss.org/browse/DROOLS-3030
> Project: Drools
> Issue Type: Task
> Components: DMN Editor
> Affects Versions: 7.12.0.Final
> Reporter: Jozef Marko
> Assignee: Guilherme Carreiro
> Priority: Major
> Labels: UX, drools-tools
>
> User should have possibility to easily expand / collapse all data types in the *manage custom data type* dialog.
> h2. Manual acceptance test
> - Expand
> -- All collapsed initially
> -- Something collapsed initially, something expanded already
> -- All expanded already
> - Collapse
> -- All expanded initially
> -- Something expanded initially, something collapsed already
> -- All collapsed already
> - No error warning in browser console log
--
This message was sent by Atlassian Jira
(v7.12.1#712002)
6 years, 10 months