SwitchYard deployment on WildFly ok, but I can't see it in the SwitchYard-SubModule-Menue

[ubm]

Hi!

I tried all WildFly-8.x Versions with the bundle "switchyard-installer-wildfly-2.0.0.Final.zip".

For all of them the installation was no problem ... WildFly always is starting and the new

SwitchYard-SubMenues are visible.

When I compile and deploy an "new-and-empty SwitchYard project" I can see it

in the application server deployments section and in the SwitchYard submenue.

However, if I add at least one Java class to the project, the deployment disappears

from the SwitchYard submenue ... :-(

What's wrong?

Uwe

[rick_wagner]

Hi Uwe,

That's an interesting problem.  Here's an idea to try:

- Turn logging to 'DEBUG' for the org.switchyard category.

- Go through the first (empty application) scenario.  We'll be interested in what the log shows as you deployed the application.

- Now try to deploy the application that has a class.  Compare the log for this effort to the previous one.

Maybe something can be learned from that.  (Or maybe not.  But it's worth a try.)

Good luck,

Rick

[ubm]

Hi Rick,

many thanks for your reply. I splitted the diffs into 3

paragraphs ... using WildFly 8.1.0 in Domain-Mode

with currently only one node named "wildfly10" on

JDK8.

DEPLOYMENT OF EMPTY SWITCHYARD-PROJECT:

[Server:wildfly10]  [33m [0m [0m13:07:22,660 INFO  [org.jboss.as.server.deployment] (MSC service thread 1-3) JBAS015876: Starting deployment of "SY-Test-3-0.0.1-SNAPSHOT.jar" (runtime-name: "SY-Test-3-0.0.1-SNAPSHOT.jar") [0m

[Server:wildfly10]  [0m [0m13:07:22,689 INFO  [org.jboss.weld.deployer] (MSC service thread 1-16) JBAS016002: Processing weld deployment SY-Test-3-0.0.1-SNAPSHOT.jar [0m

[Server:wildfly10]  [0m [0m13:07:22,720 INFO  [org.jboss.weld.deployer] (MSC service thread 1-3) JBAS016005: Starting Services for CDI deployment: SY-Test-3-0.0.1-SNAPSHOT.jar [0m

[Server:wildfly10]  [0m [0m13:07:22,723 INFO  [org.switchyard] (MSC service thread 1-3) Deploying SwitchYard application 'SY-Test-3-0.0.1-SNAPSHOT.jar' [0m

[Server:wildfly10]  [0m [0m13:07:22,728 INFO  [org.jboss.weld.deployer] (MSC service thread 1-4) JBAS016008: Starting weld service for deployment SY-Test-3-0.0.1-SNAPSHOT.jar [0m

[Server:wildfly10]  [0m [33m13:07:22,951 WARN  [org.jboss.weld.Validator] (weld-worker-1) WELD-001473: javax.enterprise.inject.spi.Bean implementation org.switchyard.component.bean.internal.message.MessageBean@41b23cde declared a normal scope but does not implement javax.enterprise.inject.spi.PassivationCapable. It won't be possible to inject this bean into a bean with passivating scope (@SessionScoped, @ConversationScoped). This can be fixed by assigning the Bean implementation a unique id by implementing the PassivationCapable interface. [0m

[Server:wildfly10]  [33m [0m [33m13:07:22,951 WARN  [org.jboss.weld.Validator] (weld-worker-2) WELD-001473: javax.enterprise.inject.spi.Bean implementation org.switchyard.component.bean.internal.context.ContextBean@4962f11b declared a normal scope but does not implement javax.enterprise.inject.spi.PassivationCapable. It won't be possible to inject this bean into a bean with passivating scope (@SessionScoped, @ConversationScoped). This can be fixed by assigning the Bean implementation a unique id by implementing the PassivationCapable interface. [0m

[Server:wildfly10]  [33m [0m [33m13:07:22,951 WARN  [org.jboss.weld.Validator] (weld-worker-4) WELD-001473: javax.enterprise.inject.spi.Bean implementation org.switchyard.component.bean.internal.exchange.ExchangeBean@1fa1b852 declared a normal scope but does not implement javax.enterprise.inject.spi.PassivationCapable. It won't be possible to inject this bean into a bean with passivating scope (@SessionScoped, @ConversationScoped). This can be fixed by assigning the Bean implementation a unique id by implementing the PassivationCapable interface. [0m

[Server:wildfly10]  [33m [0m [33m13:07:22,955 WARN  [org.jboss.weld.Validator] (weld-worker-4) WELD-001473: javax.enterprise.inject.spi.Bean implementation org.switchyard.component.bean.deploy.BeanDeploymentMetaDataCDIBean@71ff24e5 declared a normal scope but does not implement javax.enterprise.inject.spi.PassivationCapable. It won't be possible to inject this bean into a bean with passivating scope (@SessionScoped, @ConversationScoped). This can be fixed by assigning the Bean implementation a unique id by implementing the PassivationCapable interface. [0m

[Server:wildfly10]  [33m [0m [0m13:07:22,986 INFO  [org.switchyard] (MSC service thread 1-1) Starting SwitchYard service [0m

[Server:wildfly10]  [0m [0m13:07:22,991 INFO  [org.switchyard.common.camel.SwitchYardCamelContextImpl] (MSC service thread 1-1) Apache Camel 2.0.0.Final (CamelContext: camel-6) is starting [0m

[Server:wildfly10]  [0m [0m13:07:22,991 INFO  [org.apache.camel.management.ManagedManagementStrategy] (MSC service thread 1-1) JMX is enabled [0m

[Server:wildfly10]  [0m [0m13:07:23,013 INFO  [org.apache.camel.impl.converter.DefaultTypeConverter] (MSC service thread 1-1) Loaded 220 type converters [0m

[Server:wildfly10]  [0m [0m13:07:23,026 INFO  [org.switchyard.common.camel.SwitchYardCamelContextImpl] (MSC service thread 1-1) AllowUseOriginalMessage is enabled. If access to the original message is not needed, then its recommended to turn this option off as it may improve performance. [0m

[Server:wildfly10]  [0m [0m13:07:23,026 INFO  [org.switchyard.common.camel.SwitchYardCamelContextImpl] (MSC service thread 1-1) StreamCaching is not in use. If using streams then its recommended to enable stream caching. See more details at http://camel.apache.org/stream-caching.html [0m

[Server:wildfly10]  [0m [0m13:07:23,027 INFO  [org.switchyard.common.camel.SwitchYardCamelContextImpl] (MSC service thread 1-1) Total 0 routes, of which 0 is started. [0m

[Server:wildfly10]  [0m [0m13:07:23,027 INFO  [org.switchyard.common.camel.SwitchYardCamelContextImpl] (MSC service thread 1-1) Apache Camel 2.0.0.Final (CamelContext: camel-6) started in 0.036 seconds [0m

[Server:wildfly10]  [0m [0m13:07:23,163 INFO  [org.jboss.as.server] (ServerService Thread Pool -- 113) JBAS018559: Deployed "SY-Test-3-0.0.1-SNAPSHOT.jar" (runtime-name : "SY-Test-3-0.0.1-SNAPSHOT.jar") [0m

UN-DEPLOYMENT OF EMPTY SWITCHYARD-PROJECT:

[Server:wildfly10]  [33m [0m [0m13:08:34,337 INFO  [org.switchyard.common.camel.SwitchYardCamelContextImpl] (MSC service thread 1-5) Apache Camel 2.0.0.Final (CamelContext: camel-6) is shutting down [0m

[Server:wildfly10]  [0m [0m13:08:34,340 INFO  [org.switchyard.common.camel.SwitchYardCamelContextImpl] (MSC service thread 1-5) Apache Camel 2.0.0.Final (CamelContext: camel-6) uptime 1 minute [0m

[Server:wildfly10]  [0m [0m13:08:34,340 INFO  [org.switchyard.common.camel.SwitchYardCamelContextImpl] (MSC service thread 1-5) Apache Camel 2.0.0.Final (CamelContext: camel-6) is shutdown in 0.003 seconds [0m

[Server:wildfly10]  [0m [0m13:08:34,342 INFO  [org.jboss.weld.deployer] (MSC service thread 1-11) JBAS016009: Stopping weld service for deployment SY-Test-3-0.0.1-SNAPSHOT.jar [0m

[Server:wildfly10]  [0m [0m13:08:34,363 INFO  [org.jboss.as.server.deployment] (MSC service thread 1-10) JBAS015877: Stopped deployment SY-Test-3-0.0.1-SNAPSHOT.jar (runtime-name: SY-Test-3-0.0.1-SNAPSHOT.jar) in 29ms [0m

[Server:wildfly10]  [0m [0m13:08:34,392 INFO  [org.jboss.as.server] (ServerService Thread Pool -- 114) JBAS018558: Undeployed "SY-Test-3-0.0.1-SNAPSHOT.jar" (runtime-name: "SY-Test-3-0.0.1-SNAPSHOT.jar") [0m

[Server:wildfly10]  [0m [0m13:08:34,392 INFO  [org.jboss.as.repository] (ServerService Thread Pool -- 114) JBAS014901: Content removed from location /data/soa/jboss/jboss-cluster/domain/servers/wildfly10/data/content/0a/3509aec403485acebf06d9ec23479faf328d46/content [0m

DEPLOYMENT OF SWITCHYARD-PROJECT WITH ONE BEAN:

[Server:wildfly10]  [0m [0m13:08:46,693 INFO  [org.jboss.as.server.deployment] (MSC service thread 1-12) JBAS015876: Starting deployment of "SY-Test-3-0.0.1-SNAPSHOT.jar" (runtime-name: "SY-Test-3-0.0.1-SNAPSHOT.jar") [0m

[Server:wildfly10]  [0m [0m13:08:46,721 INFO  [org.jboss.weld.deployer] (MSC service thread 1-8) JBAS016002: Processing weld deployment SY-Test-3-0.0.1-SNAPSHOT.jar [0m

[Server:wildfly10]  [0m [0m13:08:46,746 INFO  [org.jboss.weld.deployer] (MSC service thread 1-11) JBAS016005: Starting Services for CDI deployment: SY-Test-3-0.0.1-SNAPSHOT.jar [0m

[Server:wildfly10]  [0m [0m13:08:46,750 INFO  [org.switchyard] (MSC service thread 1-11) Deploying SwitchYard application 'SY-Test-3-0.0.1-SNAPSHOT.jar' [0m

[Server:wildfly10]  [0m [0m13:08:46,756 INFO  [org.jboss.weld.deployer] (MSC service thread 1-7) JBAS016008: Starting weld service for deployment SY-Test-3-0.0.1-SNAPSHOT.jar [0m

[Server:wildfly10]  [0m [33m13:08:46,977 WARN  [org.jboss.weld.Validator] (weld-worker-7) WELD-001473: javax.enterprise.inject.spi.Bean implementation org.switchyard.component.bean.deploy.BeanDeploymentMetaDataCDIBean@159d3423 declared a normal scope but does not implement javax.enterprise.inject.spi.PassivationCapable. It won't be possible to inject this bean into a bean with passivating scope (@SessionScoped, @ConversationScoped). This can be fixed by assigning the Bean implementation a unique id by implementing the PassivationCapable interface. [0m

[Server:wildfly10]  [33m [0m [33m13:08:46,986 WARN  [org.jboss.weld.Validator] (weld-worker-6) WELD-001473: javax.enterprise.inject.spi.Bean implementation org.switchyard.component.bean.internal.context.ContextBean@67d1b623 declared a normal scope but does not implement javax.enterprise.inject.spi.PassivationCapable. It won't be possible to inject this bean into a bean with passivating scope (@SessionScoped, @ConversationScoped). This can be fixed by assigning the Bean implementation a unique id by implementing the PassivationCapable interface. [0m

[Server:wildfly10]  [33m [0m [33m13:08:46,986 WARN  [org.jboss.weld.Validator] (weld-worker-5) WELD-001473: javax.enterprise.inject.spi.Bean implementation org.switchyard.component.bean.internal.message.MessageBean@1b91bad6 declared a normal scope but does not implement javax.enterprise.inject.spi.PassivationCapable. It won't be possible to inject this bean into a bean with passivating scope (@SessionScoped, @ConversationScoped). This can be fixed by assigning the Bean implementation a unique id by implementing the PassivationCapable interface. [0m

[Server:wildfly10]  [33m [0m [33m13:08:46,986 WARN  [org.jboss.weld.Validator] (weld-worker-6) WELD-001473: javax.enterprise.inject.spi.Bean implementation org.switchyard.component.bean.internal.exchange.ExchangeBean@3a11de8e declared a normal scope but does not implement javax.enterprise.inject.spi.PassivationCapable. It won't be possible to inject this bean into a bean with passivating scope (@SessionScoped, @ConversationScoped). This can be fixed by assigning the Bean implementation a unique id by implementing the PassivationCapable interface. [0m

[Server:wildfly10]  [33m [0m [0m13:08:46,992 INFO  [org.switchyard] (MSC service thread 1-16) Starting SwitchYard service [0m

[Server:wildfly10]  [0m [0m13:08:47,000 INFO  [org.switchyard.common.camel.SwitchYardCamelContextImpl] (MSC service thread 1-16) Apache Camel 2.0.0.Final (CamelContext: camel-7) is starting [0m

[Server:wildfly10]  [0m [0m13:08:47,001 INFO  [org.apache.camel.management.ManagedManagementStrategy] (MSC service thread 1-16) JMX is enabled [0m

[Server:wildfly10]  [0m [0m13:08:47,021 INFO  [org.apache.camel.impl.converter.DefaultTypeConverter] (MSC service thread 1-16) Loaded 220 type converters [0m

[Server:wildfly10]  [0m [0m13:08:47,034 INFO  [org.switchyard.common.camel.SwitchYardCamelContextImpl] (MSC service thread 1-16) AllowUseOriginalMessage is enabled. If access to the original message is not needed, then its recommended to turn this option off as it may improve performance. [0m

[Server:wildfly10]  [0m [0m13:08:47,034 INFO  [org.switchyard.common.camel.SwitchYardCamelContextImpl] (MSC service thread 1-16) StreamCaching is not in use. If using streams then its recommended to enable stream caching. See more details at http://camel.apache.org/stream-caching.html [0m

[Server:wildfly10]  [0m [0m13:08:47,035 INFO  [org.switchyard.common.camel.SwitchYardCamelContextImpl] (MSC service thread 1-16) Total 0 routes, of which 0 is started. [0m

[Server:wildfly10]  [0m [0m13:08:47,035 INFO  [org.switchyard.common.camel.SwitchYardCamelContextImpl] (MSC service thread 1-16) Apache Camel 2.0.0.Final (CamelContext: camel-7) started in 0.035 seconds [0m

[Server:wildfly10]  [0m [31m13:08:47,122 ERROR [stderr] (MSC service thread 1-16) Warning:  org.apache.xerces.jaxp.SAXParserImpl$JAXPSAXParser: Property 'http://www.oracle.com/xml/jaxp/properties/entityExpansionLimit' is not recognized. [0m

[Server:wildfly10]  [31m [0m [31m13:08:47,131 ERROR [stderr] (MSC service thread 1-16) Compiler warnings: [0m

[Server:wildfly10]  [31m [0m [31m13:08:47,132 ERROR [stderr] (MSC service thread 1-16)   WARNING:  'org.apache.xerces.jaxp.SAXParserImpl: Property 'http://javax.xml.XMLConstants/property/accessExternalDTD' is not recognized.' [0m

[Server:wildfly10]  [31m [0m [0m13:08:47,181 INFO  [org.jboss.as.server] (ServerService Thread Pool -- 114) JBAS018559: Deployed "SY-Test-3-0.0.1-SNAPSHOT.jar" (runtime-name : "SY-Test-3-0.0.1-SNAPSHOT.jar") [0m

Certainly the core error will be ...

WARNING:  'org.apache.xerces.jaxp.SAXParserImpl: Property 'http://javax.xml.XMLConstants/property/accessExternalDTD' is not recognized.'

... but I have no idea how I should deal with it :-(

Uwe

[ubm]

Hi Rick,

I've added now the interface "PassivationCapable" to my central bean.

In this scenario I'm able to deploy my SwitchYard-Project to the

WildFly8.1.0-ApplicationServer and I can use it!

Nevertheless nothing is shown under the SwitchYard-Menues!? :-(

Uwe