[JBoss JIRA] (WFLY-3657) Injection not working on JAXWS handlers specified with @HandlerChain on service endpoint interfaces
by Alessio Soldano (JIRA)
[ https://issues.jboss.org/browse/WFLY-3657?page=com.atlassian.jira.plugin.... ]
Alessio Soldano updated WFLY-3657:
----------------------------------
Fix Version/s: 9.0.0.Beta1
> Injection not working on JAXWS handlers specified with @HandlerChain on service endpoint interfaces
> ---------------------------------------------------------------------------------------------------
>
> Key: WFLY-3657
> URL: https://issues.jboss.org/browse/WFLY-3657
> Project: WildFly
> Issue Type: Bug
> Components: Web Services
> Affects Versions: 8.1.0.Final
> Environment: Ubuntu 12.04
> JDK 1.8.0_11
> Reporter: Thomas Kriechbaum
> Assignee: Alessio Soldano
> Fix For: 9.0.0.Beta1
>
> Attachments: jaxws-handler-war.zip, wildfly-test-soapui-project.xml
>
>
> According to the JavaEE spec JAXWS-handlers should support injection (@Inject, @EJB), @PostConstruct and @PreDestroy.
> In my test case (top-down approach, handler class is defined within *_handler.xml) @PostCunstruct works, but managed beans (CDI, EJB) are not injected via @Inject or @EJB.
> Possible workaround for EJBs: manual JNDI-lookup within @PostConstruct method. For CDI-managed beans you have to lookup the BeanManager and load the desired bean yourself.
> It seems, that this issue should have been addressed by WFLY-2362. But it is still does not work.
--
This message was sent by Atlassian JIRA
(v6.3.11#6341)
11 years, 2 months
[JBoss JIRA] (WFLY-3657) Injection not working on JAXWS handlers specified with @HandlerChain on service endpoint interfaces
by Alessio Soldano (JIRA)
[ https://issues.jboss.org/browse/WFLY-3657?page=com.atlassian.jira.plugin.... ]
Alessio Soldano commented on WFLY-3657:
---------------------------------------
I confirm this is a bug; basically, org.jboss.as.webservices.injection.WSHandlerChainAnnotationProcessor is not considering @HandlerChain annotation that could be on service endpoint interfaces referenced by @WebService(endpointInterface="..." ) on endpoint implementations.
This is covered by JSR-181 spec, section 4.6.1:
"The @HandlerChain annotation MAY be present on the endpoint interface and service
implementation bean. The service implementation bean’s @HandlerChain is used if
@HandlerChain is present on both."
> Injection not working on JAXWS handlers specified with @HandlerChain on service endpoint interfaces
> ---------------------------------------------------------------------------------------------------
>
> Key: WFLY-3657
> URL: https://issues.jboss.org/browse/WFLY-3657
> Project: WildFly
> Issue Type: Bug
> Components: Web Services
> Affects Versions: 8.1.0.Final
> Environment: Ubuntu 12.04
> JDK 1.8.0_11
> Reporter: Thomas Kriechbaum
> Assignee: Alessio Soldano
> Attachments: jaxws-handler-war.zip, wildfly-test-soapui-project.xml
>
>
> According to the JavaEE spec JAXWS-handlers should support injection (@Inject, @EJB), @PostConstruct and @PreDestroy.
> In my test case (top-down approach, handler class is defined within *_handler.xml) @PostCunstruct works, but managed beans (CDI, EJB) are not injected via @Inject or @EJB.
> Possible workaround for EJBs: manual JNDI-lookup within @PostConstruct method. For CDI-managed beans you have to lookup the BeanManager and load the desired bean yourself.
> It seems, that this issue should have been addressed by WFLY-2362. But it is still does not work.
--
This message was sent by Atlassian JIRA
(v6.3.11#6341)
11 years, 2 months
[JBoss JIRA] (WFLY-3657) Injection not working on JAXWS handlers specified with @HandlerChain on service endpoint interfaces
by Alessio Soldano (JIRA)
[ https://issues.jboss.org/browse/WFLY-3657?page=com.atlassian.jira.plugin.... ]
Alessio Soldano updated WFLY-3657:
----------------------------------
Summary: Injection not working on JAXWS handlers specified with @HandlerChain on service endpoint interfaces (was: JAXWS handlers do not support injection)
> Injection not working on JAXWS handlers specified with @HandlerChain on service endpoint interfaces
> ---------------------------------------------------------------------------------------------------
>
> Key: WFLY-3657
> URL: https://issues.jboss.org/browse/WFLY-3657
> Project: WildFly
> Issue Type: Bug
> Components: Web Services
> Affects Versions: 8.1.0.Final
> Environment: Ubuntu 12.04
> JDK 1.8.0_11
> Reporter: Thomas Kriechbaum
> Assignee: Alessio Soldano
> Attachments: jaxws-handler-war.zip, wildfly-test-soapui-project.xml
>
>
> According to the JavaEE spec JAXWS-handlers should support injection (@Inject, @EJB), @PostConstruct and @PreDestroy.
> In my test case (top-down approach, handler class is defined within *_handler.xml) @PostCunstruct works, but managed beans (CDI, EJB) are not injected via @Inject or @EJB.
> Possible workaround for EJBs: manual JNDI-lookup within @PostConstruct method. For CDI-managed beans you have to lookup the BeanManager and load the desired bean yourself.
> It seems, that this issue should have been addressed by WFLY-2362. But it is still does not work.
--
This message was sent by Atlassian JIRA
(v6.3.11#6341)
11 years, 2 months
[JBoss JIRA] (DROOLS-733) Unify Drools and jBPM execution servers
by Edson Tirelli (JIRA)
[ https://issues.jboss.org/browse/DROOLS-733?page=com.atlassian.jira.plugin... ]
Edson Tirelli updated DROOLS-733:
---------------------------------
Description:
This is a placeholder parent ticket for the merge of the code from Drools and jBPM execution servers into a single server.
The new server should be standalone, free of UI code, support remote interfaces, and comply to all requirements from both Drools and jBPM.
It should try to avoid the use of technologies that cause issues on different containers (like CDI), and be as lightweight as possible for cloud deployment.
Initial open questions include:
* support to databases and persistence: should this be a per-container configuration or per-kjar configuration?
* can a single deployment model be used for both drools and jbpm?
* how to apply the security model from jbpm?
* does the workbench need to continue to support remote REST calls for deployments or can it be moved completely out of it?
* workbench UI consolidation for exec servers
was:
This is a placeholder parent ticket for the merge of the code from Drools and jBPM execution servers into a single server.
The new server should be standalone, free of UI code, support remote interfaces, and comply to all requirements from both Drools and jBPM.
It should try to avoid the use of technologies that cause issues on different containers (like CDI), and be as lightweight as possible for cloud deployment.
Initial open questions include:
* support to databases and persistence: should this be a per-container configuration or per-kjar configuration?
* can a single deployment model be used for both drools and jbpm?
* how to apply the security model from jbpm?
* does the workbench need to continue to support remote REST calls for deployments or can it be moved completely out of it?
> Unify Drools and jBPM execution servers
> ---------------------------------------
>
> Key: DROOLS-733
> URL: https://issues.jboss.org/browse/DROOLS-733
> Project: Drools
> Issue Type: Feature Request
> Components: kie server
> Affects Versions: 6.2.0.Final
> Reporter: Edson Tirelli
> Assignee: Edson Tirelli
> Fix For: 6.3.0.Final
>
>
> This is a placeholder parent ticket for the merge of the code from Drools and jBPM execution servers into a single server.
> The new server should be standalone, free of UI code, support remote interfaces, and comply to all requirements from both Drools and jBPM.
> It should try to avoid the use of technologies that cause issues on different containers (like CDI), and be as lightweight as possible for cloud deployment.
> Initial open questions include:
> * support to databases and persistence: should this be a per-container configuration or per-kjar configuration?
> * can a single deployment model be used for both drools and jbpm?
> * how to apply the security model from jbpm?
> * does the workbench need to continue to support remote REST calls for deployments or can it be moved completely out of it?
> * workbench UI consolidation for exec servers
--
This message was sent by Atlassian JIRA
(v6.3.11#6341)
11 years, 2 months
[JBoss JIRA] (WFCORE-510) Fix filtering in domain mode
by Brian Stansberry (JIRA)
[ https://issues.jboss.org/browse/WFCORE-510?page=com.atlassian.jira.plugin... ]
Brian Stansberry reassigned WFCORE-510:
---------------------------------------
Assignee: ehsavoie Hugonnet (was: Brian Stansberry)
> Fix filtering in domain mode
> ----------------------------
>
> Key: WFCORE-510
> URL: https://issues.jboss.org/browse/WFCORE-510
> Project: WildFly Core
> Issue Type: Sub-task
> Components: Domain Management
> Reporter: Harald Pehl
> Assignee: ehsavoie Hugonnet
> Fix For: 1.0.0.Beta1
>
>
> The overall result for query operations in domain mode does not filter undefined results. Executing the following operation, will yield three results. However the last result needs to be filtered:
> {code}
> [domain@localhost:9990 /] /host=master/server-config=*:query(select=[name, status, auto-start], where={auto-start=>true})
> {
> "outcome" => "success",
> "result" => [
> {
> "address" => [
> ("host" => "master"),
> ("server-config" => "server-one")
> ],
> "outcome" => undefined,
> "result" => {
> "name" => "server-one",
> "status" => "STARTED",
> "auto-start" => true
> }
> },
> {
> "address" => [
> ("host" => "master"),
> ("server-config" => "server-two")
> ],
> "outcome" => undefined,
> "result" => {
> "name" => "server-two",
> "status" => "STARTED",
> "auto-start" => true
> }
> },
> {
> "address" => [
> ("host" => "master"),
> ("server-config" => "server-three")
> ],
> "outcome" => undefined,
> "result" => undefined
> }
> ],
> "server-groups" => undefined
> }
> {code}
--
This message was sent by Atlassian JIRA
(v6.3.11#6341)
11 years, 2 months
[JBoss JIRA] (WFCORE-510) Fix filtering in domain mode
by Brian Stansberry (JIRA)
[ https://issues.jboss.org/browse/WFCORE-510?page=com.atlassian.jira.plugin... ]
Brian Stansberry commented on WFCORE-510:
-----------------------------------------
No, I haven't looked at it. Is there a reason to believe the problem is outside the handling for the query op itself?
> Fix filtering in domain mode
> ----------------------------
>
> Key: WFCORE-510
> URL: https://issues.jboss.org/browse/WFCORE-510
> Project: WildFly Core
> Issue Type: Sub-task
> Components: Domain Management
> Reporter: Harald Pehl
> Assignee: Brian Stansberry
> Fix For: 1.0.0.Beta1
>
>
> The overall result for query operations in domain mode does not filter undefined results. Executing the following operation, will yield three results. However the last result needs to be filtered:
> {code}
> [domain@localhost:9990 /] /host=master/server-config=*:query(select=[name, status, auto-start], where={auto-start=>true})
> {
> "outcome" => "success",
> "result" => [
> {
> "address" => [
> ("host" => "master"),
> ("server-config" => "server-one")
> ],
> "outcome" => undefined,
> "result" => {
> "name" => "server-one",
> "status" => "STARTED",
> "auto-start" => true
> }
> },
> {
> "address" => [
> ("host" => "master"),
> ("server-config" => "server-two")
> ],
> "outcome" => undefined,
> "result" => {
> "name" => "server-two",
> "status" => "STARTED",
> "auto-start" => true
> }
> },
> {
> "address" => [
> ("host" => "master"),
> ("server-config" => "server-three")
> ],
> "outcome" => undefined,
> "result" => undefined
> }
> ],
> "server-groups" => undefined
> }
> {code}
--
This message was sent by Atlassian JIRA
(v6.3.11#6341)
11 years, 2 months
[JBoss JIRA] (DROOLS-733) Unify Drools and jBPM execution servers
by Edson Tirelli (JIRA)
Edson Tirelli created DROOLS-733:
------------------------------------
Summary: Unify Drools and jBPM execution servers
Key: DROOLS-733
URL: https://issues.jboss.org/browse/DROOLS-733
Project: Drools
Issue Type: Feature Request
Components: kie server
Affects Versions: 6.2.0.Final
Reporter: Edson Tirelli
Assignee: Edson Tirelli
Fix For: 6.3.0.Final
This is a placeholder parent ticket for the merge of the code from Drools and jBPM execution servers into a single server.
The new server should be standalone, free of UI code, support remote interfaces, and comply to all requirements from both Drools and jBPM.
It should try to avoid the use of technologies that cause issues on different containers (like CDI), and be as lightweight as possible for cloud deployment.
Initial open questions include:
* support to databases and persistence: should this be a per-container configuration or per-kjar configuration?
* can a single deployment model be used for both drools and jbpm?
* how to apply the security model from jbpm?
* does the workbench need to continue to support remote REST calls for deployments or can it be moved completely out of it?
--
This message was sent by Atlassian JIRA
(v6.3.11#6341)
11 years, 2 months
[JBoss JIRA] (WFLY-4324) While starting Jboss AS getting IllegalStateException.
by Tomaz Cerar (JIRA)
[ https://issues.jboss.org/browse/WFLY-4324?page=com.atlassian.jira.plugin.... ]
Tomaz Cerar commented on WFLY-4324:
-----------------------------------
see https://developer.jboss.org/message/919055#919055
> While starting Jboss AS getting IllegalStateException.
> ------------------------------------------------------
>
> Key: WFLY-4324
> URL: https://issues.jboss.org/browse/WFLY-4324
> Project: WildFly
> Issue Type: Bug
> Environment: Java with 1.8 v and JBOS 7
> Reporter: ANKUSH NIKHAR
>
> Hi,
> I am facing issue when I am trying to deploy web service on Jboss 7 and using jdk 1.8 version. Below are the sample log :
> This issue does not impact the processing of my code execution. Is this just warning or will it harm in future.
> I am migrating my project from jdk1.7 to 1.8.
> When I try to deploy WS with jdk1.7, I didn't get such error.
> 18:56:01,032 WARN [org.jboss.as.server.deployment] (MSC service thread 1-1) JBAS015852: Could not index class sun/applet/AppletPanel.class at /D:/Test Eclipse/Migration Eclipse/Mig Workspace/CDLibrary/CDLibrary-test/content/InMemory.war/WEB-INF/lib/tools.jar: java.lang.IllegalStateException: Unknown tag! pos=1006 poolCount = 1018
> at org.jboss.jandex.Indexer.processConstantPool(Indexer.java:606) [jandex-1.0.3.Final-redhat-2.jar:1.0.3.Final-redhat-2]
> at org.jboss.jandex.Indexer.index(Indexer.java:640) [jandex-1.0.3.Final-redhat-2.jar:1.0.3.Final-redhat-2]
> at org.jboss.as.server.deployment.annotation.ResourceRootIndexer.indexResourceRoot(ResourceRootIndexer.java:100) [jboss-as-server-7.4.0.Final-redhat-19.jar:7.4.0.Final-redhat-19]
> at org.jboss.as.server.deployment.annotation.AnnotationIndexProcessor.deploy(AnnotationIndexProcessor.java:51) [jboss-as-server-7.4.0.Final-redhat-19.jar:7.4.0.Final-redhat-19]
> at org.jboss.as.server.deployment.DeploymentUnitPhaseService.start(DeploymentUnitPhaseService.java:159) [jboss-as-server-7.4.0.Final-redhat-19.jar:7.4.0.Final-redhat-19]
> at org.jboss.msc.service.ServiceControllerImpl$StartTask.startService(ServiceControllerImpl.java:1980) [jboss-msc-1.1.5.Final-redhat-1.jar:1.1.5.Final-redhat-1]
> at org.jboss.msc.service.ServiceControllerImpl$StartTask.run(ServiceControllerImpl.java:1913) [jboss-msc-1.1.5.Final-redhat-1.jar:1.1.5.Final-redhat-1]
> at java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1142) [rt.jar:1.8.0_31]
> at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:617) [rt.jar:1.8.0_31]
> at java.lang.Thread.run(Thread.java:745) [rt.jar:1.8.0_31]
--
This message was sent by Atlassian JIRA
(v6.3.11#6341)
11 years, 2 months
[JBoss JIRA] (WFCORE-510) Fix filtering in domain mode
by Heiko Braun (JIRA)
[ https://issues.jboss.org/browse/WFCORE-510?page=com.atlassian.jira.plugin... ]
Heiko Braun commented on WFCORE-510:
------------------------------------
[~brian.stansberry] any update on this?
> Fix filtering in domain mode
> ----------------------------
>
> Key: WFCORE-510
> URL: https://issues.jboss.org/browse/WFCORE-510
> Project: WildFly Core
> Issue Type: Sub-task
> Components: Domain Management
> Reporter: Harald Pehl
> Assignee: Brian Stansberry
> Fix For: 1.0.0.Beta1
>
>
> The overall result for query operations in domain mode does not filter undefined results. Executing the following operation, will yield three results. However the last result needs to be filtered:
> {code}
> [domain@localhost:9990 /] /host=master/server-config=*:query(select=[name, status, auto-start], where={auto-start=>true})
> {
> "outcome" => "success",
> "result" => [
> {
> "address" => [
> ("host" => "master"),
> ("server-config" => "server-one")
> ],
> "outcome" => undefined,
> "result" => {
> "name" => "server-one",
> "status" => "STARTED",
> "auto-start" => true
> }
> },
> {
> "address" => [
> ("host" => "master"),
> ("server-config" => "server-two")
> ],
> "outcome" => undefined,
> "result" => {
> "name" => "server-two",
> "status" => "STARTED",
> "auto-start" => true
> }
> },
> {
> "address" => [
> ("host" => "master"),
> ("server-config" => "server-three")
> ],
> "outcome" => undefined,
> "result" => undefined
> }
> ],
> "server-groups" => undefined
> }
> {code}
--
This message was sent by Atlassian JIRA
(v6.3.11#6341)
11 years, 2 months