December 2017 - jboss-jira - Jboss List Archives

[JBoss JIRA] (JBRULES-3445) DSL expander expands lines in /* */comment block

by Mario Fusco (JIRA)

Mario Fusco created JBRULES-3445: ------------------------------------ Summary: DSL expander expands lines in /* */comment block Key: JBRULES-3445 URL: https://issues.jboss.org/browse/JBRULES-3445 Project: Drools Issue Type: Bug Security Level: Public (Everyone can see) Reporter: Mario Fusco Assignee: Mario Fusco When you comment some code in dslr file, the expander still tries to expand it. -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.jboss.org/secure/ContactAdministrators!default.jspa For more information on JIRA, see: http://www.atlassian.com/software/jira

3 weeks, 1 day

3
10
0 / 0

[JBoss JIRA] (WFLY-9644) Wildfly 11 can't deploy simple REST web service because it can't find javax.ws.rs.core.Application

by Dean Schulze (JIRA)

Dean Schulze created WFLY-9644: ---------------------------------- Summary: Wildfly 11 can't deploy simple REST web service because it can't find javax.ws.rs.core.Application Key: WFLY-9644 URL: https://issues.jboss.org/browse/WFLY-9644 Project: WildFly Issue Type: Bug Components: REST Affects Versions: 11.0.0.Final Environment: Ubuntu 16.04, JDK 1.8 Reporter: Dean Schulze Assignee: Alessio Soldano Simple JAX-RS .war file with an Application .class file (extends javax.ws.rs.core.Application) and one resource .class file. No web.xml file. Deploying gives this error: Cannot upload deployment: {"WFLYCTL0080: Failed services" => {"jboss.deployment.unit.pdfupload.POST_MODULE" => "WFLYSRV0153: Failed to process phase POST_MODULE of deployment \"pdfupload\" Caused by: org.jboss.as.server.deployment.DeploymentUnitProcessingException: WFLYRS0006: Could not load JAX-RS Application class Caused by: java.lang.ClassNotFoundException: pdf.upload.server.PdfUploadApplication from [Module \"deployment.pdfupload\" from Service Module Loader]"}} -- This message was sent by Atlassian JIRA (v7.5.0#75005)

7 years, 4 months

1
0
0 / 0

[JBoss JIRA] (WFCORE-3482) Remove deprecated org.jboss.as.controller.NoSuchResourceException

by Brian Stansberry (JIRA)

[ https://issues.jboss.org/browse/WFCORE-3482?page=com.atlassian.jira.plugi... ] Brian Stansberry updated WFCORE-3482: ------------------------------------- Priority: Minor (was: Major) > Remove deprecated org.jboss.as.controller.NoSuchResourceException > ----------------------------------------------------------------- > > Key: WFCORE-3482 > URL: https://issues.jboss.org/browse/WFCORE-3482 > Project: WildFly Core > Issue Type: Task > Components: Domain Management > Reporter: Brian Stansberry > Assignee: Brian Stansberry > Priority: Minor > Fix For: 4.0.0.Alpha6 > > > Class was deprecated in March 2015 and is not used in WildFly Core or in full WildFly. It was never something meant for use outside of the management kernel, so the odds any external extensions use it are low. -- This message was sent by Atlassian JIRA (v7.5.0#75005)

7 years, 4 months

1
0
0 / 0

[JBoss JIRA] (WFCORE-3482) Remove deprecated org.jboss.as.controller.NoSuchResourceException

by Brian Stansberry (JIRA)

Brian Stansberry created WFCORE-3482: ---------------------------------------- Summary: Remove deprecated org.jboss.as.controller.NoSuchResourceException Key: WFCORE-3482 URL: https://issues.jboss.org/browse/WFCORE-3482 Project: WildFly Core Issue Type: Task Components: Domain Management Reporter: Brian Stansberry Assignee: Brian Stansberry Fix For: 4.0.0.Alpha6 Class was deprecated in March 2015 and is not used in WildFly Core or in full WildFly. It was never something meant for use outside of the management kernel, so the odds any external extensions use it are low. -- This message was sent by Atlassian JIRA (v7.5.0#75005)

7 years, 4 months

1
0
0 / 0

[JBoss JIRA] (WFLY-9643) Getting Internal server error on exception if the rest service content type is "application/xml"

by Gopal krishna (JIRA)

[ https://issues.jboss.org/browse/WFLY-9643?page=com.atlassian.jira.plugin.... ] Gopal krishna updated WFLY-9643: -------------------------------- Description: We are getting Internal server error if any exception is thrown from spring interceptor when rest API header is set as "application/xml". This works if the rest API header is set as "application/json". we didnt see this issue in jboss 7 and WAS was: We are getting Internal server error if any exception is thrown from spring interceptor when rest API header is set as "application/xml". This works if the rest API header is set as "application/json". This didnt see this issue in jboss 7 and WAS > Getting Internal server error on exception if the rest service content type is "application/xml" > ------------------------------------------------------------------------------------------------ > > Key: WFLY-9643 > URL: https://issues.jboss.org/browse/WFLY-9643 > Project: WildFly > Issue Type: Bug > Components: Application Client > Reporter: Gopal krishna > Assignee: Stuart Douglas > Priority: Blocker > > We are getting Internal server error if any exception is thrown from spring interceptor when rest API header is set as "application/xml". This works if the rest API header is set as "application/json". > we didnt see this issue in jboss 7 and WAS -- This message was sent by Atlassian JIRA (v7.5.0#75005)

7 years, 4 months

1
0
0 / 0

[JBoss JIRA] (WFLY-9643) Getting Internal server error on exception if the rest service content type is "application/xml"

by Gopal krishna (JIRA)

Gopal krishna created WFLY-9643: ----------------------------------- Summary: Getting Internal server error on exception if the rest service content type is "application/xml" Key: WFLY-9643 URL: https://issues.jboss.org/browse/WFLY-9643 Project: WildFly Issue Type: Bug Components: Application Client Reporter: Gopal krishna Assignee: Stuart Douglas Priority: Blocker We are getting Internal server error if any exception is thrown from spring interceptor when rest API header is set as "application/xml". This works if the rest API header is set as "application/json". This didnt see this issue in jboss 7 and WAS -- This message was sent by Atlassian JIRA (v7.5.0#75005)

7 years, 4 months

1
0
0 / 0

[JBoss JIRA] (DROOLS-2201) DMN runtime typecheck not managed for context and DT output

by Matteo Mortari (JIRA)

[ https://issues.jboss.org/browse/DROOLS-2201?page=com.atlassian.jira.plugi... ] Matteo Mortari updated DROOLS-2201: ----------------------------------- Attachment: screenshot-2.png > DMN runtime typecheck not managed for context and DT output > ----------------------------------------------------------- > > Key: DROOLS-2201 > URL: https://issues.jboss.org/browse/DROOLS-2201 > Project: Drools > Issue Type: Bug > Components: dmn engine > Reporter: Matteo Mortari > Assignee: Matteo Mortari > Attachments: screenshot-1.png, screenshot-2.png > > > A Context result (last line) > and > A Decision Table output column > are not obliging to the configuration for runtime typecheck. -- This message was sent by Atlassian JIRA (v7.5.0#75005)

7 years, 4 months

1
0
0 / 0

[JBoss JIRA] (DROOLS-2201) DMN runtime typecheck not managed for context and DT output

by Matteo Mortari (JIRA)

[ https://issues.jboss.org/browse/DROOLS-2201?page=com.atlassian.jira.plugi... ] Matteo Mortari commented on DROOLS-2201: ---------------------------------------- Example for Context result !screenshot-2.png|thumbnail! > DMN runtime typecheck not managed for context and DT output > ----------------------------------------------------------- > > Key: DROOLS-2201 > URL: https://issues.jboss.org/browse/DROOLS-2201 > Project: Drools > Issue Type: Bug > Components: dmn engine > Reporter: Matteo Mortari > Assignee: Matteo Mortari > Attachments: screenshot-1.png, screenshot-2.png > > > A Context result (last line) > and > A Decision Table output column > are not obliging to the configuration for runtime typecheck. -- This message was sent by Atlassian JIRA (v7.5.0#75005)

7 years, 4 months

1
0
0 / 0

[JBoss JIRA] (DROOLS-2201) DMN runtime typecheck not managed for context and DT output

by Matteo Mortari (JIRA)

[ https://issues.jboss.org/browse/DROOLS-2201?page=com.atlassian.jira.plugi... ] Matteo Mortari updated DROOLS-2201: ----------------------------------- Attachment: screenshot-1.png > DMN runtime typecheck not managed for context and DT output > ----------------------------------------------------------- > > Key: DROOLS-2201 > URL: https://issues.jboss.org/browse/DROOLS-2201 > Project: Drools > Issue Type: Bug > Components: dmn engine > Reporter: Matteo Mortari > Assignee: Matteo Mortari > Attachments: screenshot-1.png > > > A Context result (last line) > and > A Decision Table output column > are not obliging to the configuration for runtime typecheck. -- This message was sent by Atlassian JIRA (v7.5.0#75005)

7 years, 4 months

1
0
0 / 0

[JBoss JIRA] (DROOLS-2201) DMN runtime typecheck not managed for context and DT output

by Matteo Mortari (JIRA)

[ https://issues.jboss.org/browse/DROOLS-2201?page=com.atlassian.jira.plugi... ] Matteo Mortari commented on DROOLS-2201: ---------------------------------------- Example for Decision Table output column: !screenshot-1.png|thumbnail! > DMN runtime typecheck not managed for context and DT output > ----------------------------------------------------------- > > Key: DROOLS-2201 > URL: https://issues.jboss.org/browse/DROOLS-2201 > Project: Drools > Issue Type: Bug > Components: dmn engine > Reporter: Matteo Mortari > Assignee: Matteo Mortari > Attachments: screenshot-1.png > > > A Context result (last line) > and > A Decision Table output column > are not obliging to the configuration for runtime typecheck. -- This message was sent by Atlassian JIRA (v7.5.0#75005)

7 years, 4 months

1
0
0 / 0

2025

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

2009

2008

2007

2006

jboss-jira December 2017