[JBoss JIRA] (DROOLS-4694) [DMN Designer] BC DOs as DMN DTs - Create import action into the UI
by Jozef Marko (Jira)
[ https://issues.jboss.org/browse/DROOLS-4694?page=com.atlassian.jira.plugi... ]
Jozef Marko updated DROOLS-4694:
--------------------------------
Attachment: do-not-pick-fields.webm
> [DMN Designer] BC DOs as DMN DTs - Create import action into the UI
> -------------------------------------------------------------------
>
> Key: DROOLS-4694
> URL: https://issues.jboss.org/browse/DROOLS-4694
> Project: Drools
> Issue Type: Task
> Components: DMN Editor
> Reporter: Guilherme Gomes
> Assignee: Daniel José dos Santos
> Priority: Major
> Labels: drools-tools
> Attachments: do-not-pick-fields.webm
>
>
> Consume the service provided by DROOLS-4680 and create Data Types in the UI.
> ⚠️ Notice:
> - Respect the nesting logic
> - Use the data types manager for creating type (just like the "Add" button)
> - The new data types must be added in the end of the list
> - If a Data Type with the same name already exists, remove it, and add the new one.
> h2. Manual Scenarios
> - No fields in data object (/)
> - Nested data objects, more than 5 levels
> - Class B extends Class A
> - Classes added as dependencies
> - Classes from different package than dmn
> - Collection fields
> - simple/built in type java types fields
> - static fields
> - Import, rename original java class, import again
> - Import, delete import, import
> - Import, add field in original java class, import
> - Import, change field type in original class, import
> - Import, import
> - Import, pick also types needed for fields
> - Import, do not pick types needed for fields (x)
> - Use imported type in dmn, test scenario
--
This message was sent by Atlassian Jira
(v7.13.8#713008)
6 years, 8 months
[JBoss JIRA] (DROOLS-4694) [DMN Designer] BC DOs as DMN DTs - Create import action into the UI
by Jozef Marko (Jira)
[ https://issues.jboss.org/browse/DROOLS-4694?page=com.atlassian.jira.plugi... ]
Jozef Marko updated DROOLS-4694:
--------------------------------
Description:
Consume the service provided by DROOLS-4680 and create Data Types in the UI.
⚠️ Notice:
- Respect the nesting logic
- Use the data types manager for creating type (just like the "Add" button)
- The new data types must be added in the end of the list
- If a Data Type with the same name already exists, remove it, and add the new one.
h2. Manual Scenarios
- No fields in data object (/)
- Nested data objects, more than 5 levels
- Class B extends Class A
- Classes added as dependencies
- Classes from different package than dmn
- Collection fields
- simple/built in type java types fields
- static fields
- Import, rename original java class, import again
- Import, delete import, import
- Import, add field in original java class, import
- Import, change field type in original class, import
- Import, import
- Import, pick also types needed for fields
- Import, do not pick types needed for fields (x) [^do-not-pick-fields.webm]
- Use imported type in dmn, test scenario
was:
Consume the service provided by DROOLS-4680 and create Data Types in the UI.
⚠️ Notice:
- Respect the nesting logic
- Use the data types manager for creating type (just like the "Add" button)
- The new data types must be added in the end of the list
- If a Data Type with the same name already exists, remove it, and add the new one.
h2. Manual Scenarios
- No fields in data object (/)
- Nested data objects, more than 5 levels
- Class B extends Class A
- Classes added as dependencies
- Classes from different package than dmn
- Collection fields
- simple/built in type java types fields
- static fields
- Import, rename original java class, import again
- Import, delete import, import
- Import, add field in original java class, import
- Import, change field type in original class, import
- Import, import
- Import, pick also types needed for fields
- Import, do not pick types needed for fields (x)
- Use imported type in dmn, test scenario
> [DMN Designer] BC DOs as DMN DTs - Create import action into the UI
> -------------------------------------------------------------------
>
> Key: DROOLS-4694
> URL: https://issues.jboss.org/browse/DROOLS-4694
> Project: Drools
> Issue Type: Task
> Components: DMN Editor
> Reporter: Guilherme Gomes
> Assignee: Daniel José dos Santos
> Priority: Major
> Labels: drools-tools
> Attachments: do-not-pick-fields.webm
>
>
> Consume the service provided by DROOLS-4680 and create Data Types in the UI.
> ⚠️ Notice:
> - Respect the nesting logic
> - Use the data types manager for creating type (just like the "Add" button)
> - The new data types must be added in the end of the list
> - If a Data Type with the same name already exists, remove it, and add the new one.
> h2. Manual Scenarios
> - No fields in data object (/)
> - Nested data objects, more than 5 levels
> - Class B extends Class A
> - Classes added as dependencies
> - Classes from different package than dmn
> - Collection fields
> - simple/built in type java types fields
> - static fields
> - Import, rename original java class, import again
> - Import, delete import, import
> - Import, add field in original java class, import
> - Import, change field type in original class, import
> - Import, import
> - Import, pick also types needed for fields
> - Import, do not pick types needed for fields (x) [^do-not-pick-fields.webm]
> - Use imported type in dmn, test scenario
--
This message was sent by Atlassian Jira
(v7.13.8#713008)
6 years, 8 months
[JBoss JIRA] (DROOLS-4694) [DMN Designer] BC DOs as DMN DTs - Create import action into the UI
by Jozef Marko (Jira)
[ https://issues.jboss.org/browse/DROOLS-4694?page=com.atlassian.jira.plugi... ]
Jozef Marko updated DROOLS-4694:
--------------------------------
Description:
Consume the service provided by DROOLS-4680 and create Data Types in the UI.
⚠️ Notice:
- Respect the nesting logic
- Use the data types manager for creating type (just like the "Add" button)
- The new data types must be added in the end of the list
- If a Data Type with the same name already exists, remove it, and add the new one.
h2. Manual Scenarios
- No fields in data object (/)
- Nested data objects, more than 5 levels
- Class B extends Class A
- Classes added as dependencies
- Classes from different package than dmn
- Collection fields
- simple/built in type java types fields
- static fields
- Import, rename original java class, import again
- Import, delete import, import
- Import, add field in original java class, import
- Import, change field type in original class, import
- Import, import
- Import, pick also types needed for fields
- Import, do not pick types needed for fields (x)
- Use imported type in dmn, test scenario
was:
Consume the service provided by DROOLS-4680 and create Data Types in the UI.
⚠️ Notice:
- Respect the nesting logic
- Use the data types manager for creating type (just like the "Add" button)
- The new data types must be added in the end of the list
- If a Data Type with the same name already exists, remove it, and add the new one.
h2. Manual Scenarios
- No fields in data object (/)
- Nested data objects, more than 5 levels
- Class B extends Class A
- Classes added as dependencies
- Classes from different package than dmn
- Collection fields
- simple/built in type java types fields
- static fields
- Import, rename original java class, import again
- Import, delete import, import
- Import, add field in original java class, import
- Import, change field type in original class, import
- Import, import
- Import, pick also types needed for fields
- Import, do not pick types needed for fields
- Use imported type in dmn, test scenario
> [DMN Designer] BC DOs as DMN DTs - Create import action into the UI
> -------------------------------------------------------------------
>
> Key: DROOLS-4694
> URL: https://issues.jboss.org/browse/DROOLS-4694
> Project: Drools
> Issue Type: Task
> Components: DMN Editor
> Reporter: Guilherme Gomes
> Assignee: Daniel José dos Santos
> Priority: Major
> Labels: drools-tools
>
> Consume the service provided by DROOLS-4680 and create Data Types in the UI.
> ⚠️ Notice:
> - Respect the nesting logic
> - Use the data types manager for creating type (just like the "Add" button)
> - The new data types must be added in the end of the list
> - If a Data Type with the same name already exists, remove it, and add the new one.
> h2. Manual Scenarios
> - No fields in data object (/)
> - Nested data objects, more than 5 levels
> - Class B extends Class A
> - Classes added as dependencies
> - Classes from different package than dmn
> - Collection fields
> - simple/built in type java types fields
> - static fields
> - Import, rename original java class, import again
> - Import, delete import, import
> - Import, add field in original java class, import
> - Import, change field type in original class, import
> - Import, import
> - Import, pick also types needed for fields
> - Import, do not pick types needed for fields (x)
> - Use imported type in dmn, test scenario
--
This message was sent by Atlassian Jira
(v7.13.8#713008)
6 years, 8 months
[JBoss JIRA] (DROOLS-4694) [DMN Designer] BC DOs as DMN DTs - Create import action into the UI
by Jozef Marko (Jira)
[ https://issues.jboss.org/browse/DROOLS-4694?page=com.atlassian.jira.plugi... ]
Jozef Marko updated DROOLS-4694:
--------------------------------
Description:
Consume the service provided by DROOLS-4680 and create Data Types in the UI.
⚠️ Notice:
- Respect the nesting logic
- Use the data types manager for creating type (just like the "Add" button)
- The new data types must be added in the end of the list
- If a Data Type with the same name already exists, remove it, and add the new one.
h2. Manual Scenarios
- No fields in data object (/)
- Nested data objects, more than 5 levels
- Class B extends Class A
- Classes added as dependencies
- Classes from different package than dmn
- Collection fields
- simple/built in type java types fields
- static fields
- Import, rename original java class, import again
- Import, delete import, import
- Import, add field in original java class, import
- Import, change field type in original class, import
- Import, import
- Import, pick also types needed for fields
- Import, do not pick types needed for fields
- Use imported type in dmn, test scenario
was:
Consume the service provided by DROOLS-4680 and create Data Types in the UI.
⚠️ Notice:
- Respect the nesting logic
- Use the data types manager for creating type (just like the "Add" button)
- The new data types must be added in the end of the list
- If a Data Type with the same name already exists, remove it, and add the new one.
h2. Manual Scenarios
- No fields in data object
- Nested data objects, more than 5 levels
- Class B extends Class A
- Classes added as dependencies
- Classes from different package than dmn
- Collection fields
- simple/built in type java types fields
- static fields
- Import, rename original java class, import again
- Import, delete import, import
- Import, add field in original java class, import
- Import, change field type in original class, import
- Import, import
- Import, pick also types needed for fields
- Import, do not pick types needed for fields
- Use imported type in dmn, test scenario
> [DMN Designer] BC DOs as DMN DTs - Create import action into the UI
> -------------------------------------------------------------------
>
> Key: DROOLS-4694
> URL: https://issues.jboss.org/browse/DROOLS-4694
> Project: Drools
> Issue Type: Task
> Components: DMN Editor
> Reporter: Guilherme Gomes
> Assignee: Daniel José dos Santos
> Priority: Major
> Labels: drools-tools
>
> Consume the service provided by DROOLS-4680 and create Data Types in the UI.
> ⚠️ Notice:
> - Respect the nesting logic
> - Use the data types manager for creating type (just like the "Add" button)
> - The new data types must be added in the end of the list
> - If a Data Type with the same name already exists, remove it, and add the new one.
> h2. Manual Scenarios
> - No fields in data object (/)
> - Nested data objects, more than 5 levels
> - Class B extends Class A
> - Classes added as dependencies
> - Classes from different package than dmn
> - Collection fields
> - simple/built in type java types fields
> - static fields
> - Import, rename original java class, import again
> - Import, delete import, import
> - Import, add field in original java class, import
> - Import, change field type in original class, import
> - Import, import
> - Import, pick also types needed for fields
> - Import, do not pick types needed for fields
> - Use imported type in dmn, test scenario
--
This message was sent by Atlassian Jira
(v7.13.8#713008)
6 years, 8 months
[JBoss JIRA] (DROOLS-4694) [DMN Designer] BC DOs as DMN DTs - Create import action into the UI
by Jozef Marko (Jira)
[ https://issues.jboss.org/browse/DROOLS-4694?page=com.atlassian.jira.plugi... ]
Jozef Marko updated DROOLS-4694:
--------------------------------
Description:
Consume the service provided by DROOLS-4680 and create Data Types in the UI.
⚠️ Notice:
- Respect the nesting logic
- Use the data types manager for creating type (just like the "Add" button)
- The new data types must be added in the end of the list
- If a Data Type with the same name already exists, remove it, and add the new one.
h2. Manual Scenarios
- No fields in data object
- Nested data objects, more than 5 levels
- Class B extends Class A
- Classes added as dependencies
- Classes from different package than dmn
- Collection fields
- simple/built in type java types fields
- static fields
- Import, rename original java class, import again
- Import, delete import, import
- Import, add field in original java class, import
- Import, change field type in original class, import
- Import, import
- Import, pick also types needed for fields
- Import, do not pick types needed for fields
- Use imported type in dmn, test scenario
was:
Consume the service provided by DROOLS-4680 and create Data Types in the UI.
⚠️ Notice:
- Respect the nesting logic
- Use the data types manager for creating type (just like the "Add" button)
- The new data types must be added in the end of the list
- If a Data Type with the same name already exists, remove it, and add the new one.
h2. Manual Scenarios
- No fields in data object
- Nested data objects, more than 5 levels
- Class B extends Class A
- Classes added as dependencies
- Collection fields
- simple/built in type java types fields
- static fields
- Import, rename original java class, import again
- Import, delete import, import
- Import, add field in original java class, import
- Import, change field type in original class, import
- Import, import
- Import, pick also types needed for fields
- Import, do not pick types needed for fields
- Use imported type in dmn, test scenario
> [DMN Designer] BC DOs as DMN DTs - Create import action into the UI
> -------------------------------------------------------------------
>
> Key: DROOLS-4694
> URL: https://issues.jboss.org/browse/DROOLS-4694
> Project: Drools
> Issue Type: Task
> Components: DMN Editor
> Reporter: Guilherme Gomes
> Assignee: Daniel José dos Santos
> Priority: Major
> Labels: drools-tools
>
> Consume the service provided by DROOLS-4680 and create Data Types in the UI.
> ⚠️ Notice:
> - Respect the nesting logic
> - Use the data types manager for creating type (just like the "Add" button)
> - The new data types must be added in the end of the list
> - If a Data Type with the same name already exists, remove it, and add the new one.
> h2. Manual Scenarios
> - No fields in data object
> - Nested data objects, more than 5 levels
> - Class B extends Class A
> - Classes added as dependencies
> - Classes from different package than dmn
> - Collection fields
> - simple/built in type java types fields
> - static fields
> - Import, rename original java class, import again
> - Import, delete import, import
> - Import, add field in original java class, import
> - Import, change field type in original class, import
> - Import, import
> - Import, pick also types needed for fields
> - Import, do not pick types needed for fields
> - Use imported type in dmn, test scenario
--
This message was sent by Atlassian Jira
(v7.13.8#713008)
6 years, 8 months
[JBoss JIRA] (DROOLS-4694) [DMN Designer] BC DOs as DMN DTs - Create import action into the UI
by Jozef Marko (Jira)
[ https://issues.jboss.org/browse/DROOLS-4694?page=com.atlassian.jira.plugi... ]
Jozef Marko updated DROOLS-4694:
--------------------------------
Description:
Consume the service provided by DROOLS-4680 and create Data Types in the UI.
⚠️ Notice:
- Respect the nesting logic
- Use the data types manager for creating type (just like the "Add" button)
- The new data types must be added in the end of the list
- If a Data Type with the same name already exists, remove it, and add the new one.
h2. Manual Scenarios
- No fields in data object
- Nested data objects, more than 5 levels
- Class B extends Class A
- Classes added as dependencies
- Collection fields
- simple/built in type java types fields
- static fields
- Import, rename original java class, import again
- Import, delete import, import
- Import, add field in original java class, import
- Import, change field type in original class, import
- Import, import
- Import, pick also types needed for fields
- Import, do not pick types needed for fields
- Use imported type in dmn, test scenario
was:
Consume the service provided by DROOLS-4680 and create Data Types in the UI.
⚠️ Notice:
- Respect the nesting logic
- Use the data types manager for creating type (just like the "Add" button)
- The new data types must be added in the end of the list
- If a Data Type with the same name already exists, remove it, and add the new one.
h2. Manual Scenarios
- No fields in data object
- Nested data objects, more than 5 levels
- Class B extends Class A
- Classes added as dependencies
- Collection fields
- simple/built in type java types fields
- static fields
- Import, rename original java class, import again
- Import, delete import, import
- Import, add field in original java class, import
- Import, change field type in original class, import
- Import, import
- Import, pick also types needed for fields
- Import, do not pick types needed for fields
> [DMN Designer] BC DOs as DMN DTs - Create import action into the UI
> -------------------------------------------------------------------
>
> Key: DROOLS-4694
> URL: https://issues.jboss.org/browse/DROOLS-4694
> Project: Drools
> Issue Type: Task
> Components: DMN Editor
> Reporter: Guilherme Gomes
> Assignee: Daniel José dos Santos
> Priority: Major
> Labels: drools-tools
>
> Consume the service provided by DROOLS-4680 and create Data Types in the UI.
> ⚠️ Notice:
> - Respect the nesting logic
> - Use the data types manager for creating type (just like the "Add" button)
> - The new data types must be added in the end of the list
> - If a Data Type with the same name already exists, remove it, and add the new one.
> h2. Manual Scenarios
> - No fields in data object
> - Nested data objects, more than 5 levels
> - Class B extends Class A
> - Classes added as dependencies
> - Collection fields
> - simple/built in type java types fields
> - static fields
> - Import, rename original java class, import again
> - Import, delete import, import
> - Import, add field in original java class, import
> - Import, change field type in original class, import
> - Import, import
> - Import, pick also types needed for fields
> - Import, do not pick types needed for fields
> - Use imported type in dmn, test scenario
--
This message was sent by Atlassian Jira
(v7.13.8#713008)
6 years, 8 months
[JBoss JIRA] (DROOLS-4694) [DMN Designer] BC DOs as DMN DTs - Create import action into the UI
by Jozef Marko (Jira)
[ https://issues.jboss.org/browse/DROOLS-4694?page=com.atlassian.jira.plugi... ]
Jozef Marko updated DROOLS-4694:
--------------------------------
Description:
Consume the service provided by DROOLS-4680 and create Data Types in the UI.
⚠️ Notice:
- Respect the nesting logic
- Use the data types manager for creating type (just like the "Add" button)
- The new data types must be added in the end of the list
- If a Data Type with the same name already exists, remove it, and add the new one.
h2. Manual Scenarios
- No fields in data object
- Nested data objects, more than 5 levels
- Class B extends Class A
- Classes added as dependencies
- Collection fields
- simple/built in type java types fields
- static fields
- Import, rename original java class, import again
- Import, delete import, import
- Import, add field in original java class, import
- Import, change field type in original class, import
- Import, import
- Import, pick also types needed for fields
- Import, do not pick types needed for fields
was:
Consume the service provided by DROOLS-4680 and create Data Types in the UI.
⚠️ Notice:
- Respect the nesting logic
- Use the data types manager for creating type (just like the "Add" button)
- The new data types must be added in the end of the list
- If a Data Type with the same name already exists, remove it, and add the new one.
> [DMN Designer] BC DOs as DMN DTs - Create import action into the UI
> -------------------------------------------------------------------
>
> Key: DROOLS-4694
> URL: https://issues.jboss.org/browse/DROOLS-4694
> Project: Drools
> Issue Type: Task
> Components: DMN Editor
> Reporter: Guilherme Gomes
> Assignee: Daniel José dos Santos
> Priority: Major
> Labels: drools-tools
>
> Consume the service provided by DROOLS-4680 and create Data Types in the UI.
> ⚠️ Notice:
> - Respect the nesting logic
> - Use the data types manager for creating type (just like the "Add" button)
> - The new data types must be added in the end of the list
> - If a Data Type with the same name already exists, remove it, and add the new one.
> h2. Manual Scenarios
> - No fields in data object
> - Nested data objects, more than 5 levels
> - Class B extends Class A
> - Classes added as dependencies
> - Collection fields
> - simple/built in type java types fields
> - static fields
> - Import, rename original java class, import again
> - Import, delete import, import
> - Import, add field in original java class, import
> - Import, change field type in original class, import
> - Import, import
> - Import, pick also types needed for fields
> - Import, do not pick types needed for fields
--
This message was sent by Atlassian Jira
(v7.13.8#713008)
6 years, 8 months
[JBoss JIRA] (WFLY-4409) java.lang.ArrayStoreException: sun.reflect.annotation.TypeNotPresentExceptionProxy. It's not clear what's the reason of the problem from the log
by anand gunasekaran (Jira)
[ https://issues.jboss.org/browse/WFLY-4409?page=com.atlassian.jira.plugin.... ]
anand gunasekaran commented on WFLY-4409:
-----------------------------------------
Hi, I am too facing this same issues. Please guide me.
> java.lang.ArrayStoreException: sun.reflect.annotation.TypeNotPresentExceptionProxy. It's not clear what's the reason of the problem from the log
> ------------------------------------------------------------------------------------------------------------------------------------------------
>
> Key: WFLY-4409
> URL: https://issues.jboss.org/browse/WFLY-4409
> Project: WildFly
> Issue Type: Bug
> Affects Versions: 8.2.0.Final
> Reporter: Alexandr Sokolov
> Assignee: Stuart Douglas
> Priority: Major
> Fix For: 9.0.0.Beta1
>
>
> In the log during the application server startup we see in the log file:
> {code}
> [0m[31m15:10:25,997 ERROR [org.jboss.msc.service.fail] (MSC service thread 1-1) MSC000001: Failed to start service jboss.deployment.subunit."mms.ear"."webservices.jar".POST_MODULE: org.jboss.msc.service.StartException in service jboss.deployment.subunit."mms.ear"."webservices.jar".POST_MODULE: JBAS018733: Failed to process phase POST_MODULE of subdeployment "webservices.jar" of deployment "mms.ear"
> at org.jboss.as.server.deployment.DeploymentUnitPhaseService.start(DeploymentUnitPhaseService.java:166) [wildfly-server-8.2.0.Final.jar:8.2.0.Final]
> at org.jboss.msc.service.ServiceControllerImpl$StartTask.startService(ServiceControllerImpl.java:1948) [jboss-msc-1.2.2.Final.jar:1.2.2.Final]
> at org.jboss.msc.service.ServiceControllerImpl$StartTask.run(ServiceControllerImpl.java:1881) [jboss-msc-1.2.2.Final.jar:1.2.2.Final]
> at java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1142) [rt.jar:1.8.0_25]
> at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:617) [rt.jar:1.8.0_25]
> at java.lang.Thread.run(Thread.java:745) [rt.jar:1.8.0_25]
> Caused by: java.lang.ArrayStoreException: sun.reflect.annotation.TypeNotPresentExceptionProxy
> at sun.reflect.annotation.AnnotationParser.parseClassArray(AnnotationParser.java:724) [rt.jar:1.8.0_25]
> at sun.reflect.annotation.AnnotationParser.parseArray(AnnotationParser.java:531) [rt.jar:1.8.0_25]
> at sun.reflect.annotation.AnnotationParser.parseMemberValue(AnnotationParser.java:355) [rt.jar:1.8.0_25]
> at sun.reflect.annotation.AnnotationParser.parseAnnotation2(AnnotationParser.java:286) [rt.jar:1.8.0_25]
> at sun.reflect.annotation.AnnotationParser.parseAnnotations2(AnnotationParser.java:120) [rt.jar:1.8.0_25]
> at sun.reflect.annotation.AnnotationParser.parseAnnotations(AnnotationParser.java:72) [rt.jar:1.8.0_25]
> at java.lang.Class.createAnnotationData(Class.java:3513) [rt.jar:1.8.0_25]
> at java.lang.Class.annotationData(Class.java:3502) [rt.jar:1.8.0_25]
> at java.lang.Class.getAnnotation(Class.java:3407) [rt.jar:1.8.0_25]
> at org.jboss.as.ejb3.deployment.processors.BusinessViewAnnotationProcessor.getRemoteBusinessInterfaces(BusinessViewAnnotationProcessor.java:148)
> at org.jboss.as.ejb3.deployment.processors.BusinessViewAnnotationProcessor.processViewAnnotations(BusinessViewAnnotationProcessor.java:116)
> at org.jboss.as.ejb3.deployment.processors.BusinessViewAnnotationProcessor.deploy(BusinessViewAnnotationProcessor.java:90)
> at org.jboss.as.server.deployment.DeploymentUnitPhaseService.start(DeploymentUnitPhaseService.java:159) [wildfly-server-8.2.0.Final.jar:8.2.0.Final]
> ... 5 more
> ...
> [0m[31m15:10:27,315 ERROR [org.jboss.as.controller.management-operation] (management-handler-thread - 4) JBAS014613: Operation ("deploy") failed - address: ([("deployment" => "mms.ear")]) - failure description: {
> "JBAS014671: Failed services" => {"jboss.deployment.subunit.\"mms.ear\".\"webservices.jar\".POST_MODULE" => "org.jboss.msc.service.StartException in service jboss.deployment.subunit.\"mms.ear\".\"webservices.jar\".POST_MODULE: JBAS018733: Failed to process phase POST_MODULE of subdeployment \"webservices.jar\" of deployment \"mms.ear\"
> Caused by: java.lang.ArrayStoreException: sun.reflect.annotation.TypeNotPresentExceptionProxy"},
> "JBAS014771: Services with missing/unavailable dependencies" => [
> "jboss.deployment.unit.\"mms.ear\".weld.weldClassIntrospector is missing [jboss.deployment.unit.\"mms.ear\".beanmanager]",
> "jboss.naming.context.java.comp.mms.wp.TemplateVariableService.Validator is missing [jboss.naming.context.java.comp.mms.wp.TemplateVariableService]",
> "jboss.naming.context.java.comp.mms.configuration.GenericDao.InAppClientContainer is missing [jboss.naming.context.java.comp.mms.configuration.GenericDao]",
> "jboss.naming.context.java.comp.mms.mmsServiceEJB.MMSMagnoliaSSOService.ORB is missing [jboss.naming.context.java.comp.mms.mmsServiceEJB.MMSMagnoliaSSOService]",
> ...
> {code}
> From this output it's not clear what exactly is absent in the ear file.
> Could you refactor logging for this error. In order to display which exactly annotation was not found.
--
This message was sent by Atlassian Jira
(v7.13.8#713008)
6 years, 8 months
[JBoss JIRA] (WFLY-12777) Stateful bean with @StatefulTimeout value -1 should not timeout or removed
by Cheng Fang (Jira)
[ https://issues.jboss.org/browse/WFLY-12777?page=com.atlassian.jira.plugin... ]
Cheng Fang commented on WFLY-12777:
-----------------------------------
It could be caused by {{org.jboss.as.ejb3.cache.simple.SimpleCache}} when converting the stateful timeout vqalue to duration, and therefore incorrectly scheduled it for timeout.
> Stateful bean with @StatefulTimeout value -1 should not timeout or removed
> --------------------------------------------------------------------------
>
> Key: WFLY-12777
> URL: https://issues.jboss.org/browse/WFLY-12777
> Project: WildFly
> Issue Type: Bug
> Components: EJB
> Affects Versions: 19.0.0.Beta1
> Reporter: Cheng Fang
> Assignee: Cheng Fang
> Priority: Major
> Fix For: 19.0.0.Beta1
>
>
> Stateful bean with @StatefulTimeout value -1 should not timeout or removed.
> A value of -1 means the bean will never be removed due to timeout. When running with the latest WildFly snapshot (2019-11-11), such a stateful bean was unexpectedly timed out and removed.
> {code:java}
> @Stateful
> @StatefulTimeout(value = -1, unit=TimeUnit.DAYS)
> @AccessTimeout(value=StatefulTimeoutIF.TIMEOUT_DAYS, unit=TimeUnit.DAYS)
> @Local(StatefulTimeoutIF.class)
> public class Minus1TimeoutBean {
> ...
> }
> {code}
--
This message was sent by Atlassian Jira
(v7.13.8#713008)
6 years, 8 months
[JBoss JIRA] (WFLY-12777) Stateful bean with @StatefulTimeout value -1 should not timeout or removed
by Cheng Fang (Jira)
[ https://issues.jboss.org/browse/WFLY-12777?page=com.atlassian.jira.plugin... ]
Cheng Fang updated WFLY-12777:
------------------------------
Description:
Stateful bean with @StatefulTimeout value -1 should not timeout or removed.
A value of -1 means the bean will never be removed due to timeout. When running with the latest WildFly snapshot (2019-11-11), such a stateful bean was unexpectedly timed out and removed.
{code:java}
@Stateful
@StatefulTimeout(value = -1, unit=TimeUnit.DAYS)
@AccessTimeout(value=StatefulTimeoutIF.TIMEOUT_DAYS, unit=TimeUnit.DAYS)
@Local(StatefulTimeoutIF.class)
public class Minus1TimeoutBean {
...
}
{code}
was:Stateful bean with @StatefulTimeout value -1 should not timeout or removed
> Stateful bean with @StatefulTimeout value -1 should not timeout or removed
> --------------------------------------------------------------------------
>
> Key: WFLY-12777
> URL: https://issues.jboss.org/browse/WFLY-12777
> Project: WildFly
> Issue Type: Bug
> Components: EJB
> Affects Versions: 19.0.0.Beta1
> Reporter: Cheng Fang
> Assignee: Cheng Fang
> Priority: Major
> Fix For: 19.0.0.Beta1
>
>
> Stateful bean with @StatefulTimeout value -1 should not timeout or removed.
> A value of -1 means the bean will never be removed due to timeout. When running with the latest WildFly snapshot (2019-11-11), such a stateful bean was unexpectedly timed out and removed.
> {code:java}
> @Stateful
> @StatefulTimeout(value = -1, unit=TimeUnit.DAYS)
> @AccessTimeout(value=StatefulTimeoutIF.TIMEOUT_DAYS, unit=TimeUnit.DAYS)
> @Local(StatefulTimeoutIF.class)
> public class Minus1TimeoutBean {
> ...
> }
> {code}
--
This message was sent by Atlassian Jira
(v7.13.8#713008)
6 years, 8 months