-
1. Re: required jars for client configuration for JBoss SOA Platform Version 5.1.0.GA
rotemni Jan 9, 2012 4:14 AM (in response to rotemni)I had made several retries with other jars:
since our server includes EJB jars ( jboss-ejb3-common-client) -I had added more jars located at the client folder. the total list is:
concurrent.jar
jboss-ejb3-common-client.jar
jboss-ejb3-core-client.jar
jboss-ejb3-ext-api-impl.jar
jboss-ejb3-ext-api.jar
jboss-ejb3-proxy-clustered-client.jar
jboss-ejb3-proxy-impl-client.jar
jboss-ejb3-proxy-spi-client.jar
jboss-ejb3-security-client.jar
jboss-ejb3-vfs-spi.jar
jboss-javaee.jar
jboss-messaging-client.jar
jboss-system-client.jar
jbosscx-client.jar
jnp-client.jar
I have added the jars in the client folders under tomcat, and on a second retry out of tomcat- both retries rsulted the following error:
java.lang.NoClassDefFoundError: org/jboss/logging/Logger
at org.jnp.interfaces.NamingContext.<clinit>(NamingContext.java:181)
at org.jnp.interfaces.NamingContextFactory.getInitialContext(NamingContextFactory.java:55)
at javax.naming.spi.NamingManager.getInitialContext(Unknown Source)
at javax.naming.InitialContext.getDefaultInitCtx(Unknown Source)
at javax.naming.InitialContext.init(Unknown Source)
at javax.naming.InitialContext.<init>(Unknown Source)
at com.realops.adapter.jms.JMSActorAdapter.initialize(JMSActorAdapter.java:221)
at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
at sun.reflect.NativeMethodAccessorImpl.invoke(Unknown Source)
at sun.reflect.DelegatingMethodAccessorImpl.invoke(Unknown Source)
at java.lang.reflect.Method.invoke(Unknown Source)
at com.realops.common.util.proxy.ContextClassLoaderDecoratorFactory$IsolatedInvocationHandler.doInvoke(ContextClassLoaderDecoratorFactory.java:79)
at com.realops.common.util.proxy.AbstractInvocationHandler.invoke(AbstractInvocationHandler.java:89)
at $Proxy178.initialize(Unknown Source)
at com.realops.foundation.adapterframework.AdapterManager.startAdapter(AdapterManager.java:2027)
at com.realops.foundation.adapterframework.AdapterManager.loadAdapters(AdapterManager.java:813)
at com.realops.foundation.adapterframework.AdapterManager.doStart(AdapterManager.java:593)
at com.realops.foundation.component.Component.start(Component.java:228)
at com.realops.foundation.GridPeer.startComponent(GridPeer.java:864)
at com.realops.foundation.GridPeer.startComponent(GridPeer.java:1625)
at com.realops.foundation.GridPeer.startComponents(GridPeer.java:1672)
at com.realops.foundation.GridPeer.start(GridPeer.java:704)
at com.realops.foundation.DefaultServerManager$UserGridPeerStartupTask.run(DefaultServerManager.java:1856)
at java.util.concurrent.Executors$RunnableAdapter.call(Unknown Source)
at java.util.concurrent.FutureTask$Sync.innerRun(Unknown Source)
at java.util.concurrent.FutureTask.run(Unknown Source)
at java.util.concurrent.ThreadPoolExecutor$Worker.runTask(Unknown Source)
at java.util.concurrent.ThreadPoolExecutor$Worker.run(Unknown Source)
at java.lang.Thread.run(Unknown Source)
Caused by: java.lang.ClassNotFoundException: org.jboss.logging.Logger
at org.apache.catalina.loader.WebappClassLoader.loadClass(WebappClassLoader.java:1645)
at org.apache.catalina.loader.WebappClassLoader.loadClass(WebappClassLoader.java:1491)
any idea ?
-
2. Re: required jars for client configuration for JBoss SOA Platform Version 5.1.0.GA
tcunning Jan 10, 2012 1:40 PM (in response to rotemni)Hi rotem,
From your stack trace, it looks like it is missing jboss-logging-spi.jar (I'm assuming you are using JBoss AS 5.1.0.GA?)
If you want a project to work off of, try this :
https://anonsvn.jboss.org/repos/labs/labs/jbossesb/workspace/dbevenius/remote-service-invoker
If you are using ESB 4.9 or 4.10, you probably want to use the version of the juddi JARs (and their dependencies) that shipped with 4.9 or 4.10.
-
3. Re: required jars for client configuration for JBoss SOA Platform Version 5.1.0.GA
rotemni Jan 11, 2012 4:06 AM (in response to tcunning)Tom,
thanks for your suggestions- but I still recieve errors. Moreover, I couldn't activate the client at all when I tried using the jars located in the link
The client (I am obligated to use this specific client) consists on the following jars:
abdera-client-1.0-20090105.215721-1.jar
abdera-core-1.0-20090105.215721-1.jar
abdera-i18n-1.0-20090105.215721-1.jar
abdera-parser-1.0-20090105.215721-1.jar
activation-1.1.jar
activeio-core-3.1.2.jar
activemq-core-5.4.2.jar
activemq-pool-5.4.2.jar
activemq-protobuf-1.1.jar
adapter-protocol-7.6.02.00.jar
agent-7.6.02.00.jar
annotations-1.3.2.jar
antlr-2.7.6.jar
aopalliance-1.0.jar
api-7.6.02.00.jar
aspectjrt-1.6.2.jar
axiom-api-1.2.2.jar
axiom-impl-1.2.2.jar
axis-1.4.jar
axis-jaxrpc-1.4.jar
axis-wsdl4j-1.5.1.jar
axis2-codegen-1.1.1.jar
axis2-kernel-1.1.1.jar
axis2-saaj-1.1.1.jar
axis2-tools-1.1.1.jar
axis2-xmlbeans-1.1.1.jar
backport-util-concurrent-3.1.jar
bcprov-jdk16-140.jar
bmclog4j-1.0.0.0.jar
bootstrap-7.6.02.00.jar
c3p0-0.9.1.2.jar
common-2.2.3.jar
common-7.6.02.00.jar
commons-beanutils-1.7.0.jar
commons-beanutils-core-1.7.0.jar
commons-codec-1.3.jar
commons-collections-3.1.jar
commons-configuration-1.5.jar
commons-daemon-1.0.1.jar
commons-dbcp-1.2.1.jar
commons-digester-1.8.1.jar
commons-discovery-0.2.jar
commons-el-1.0.jar
commons-fileupload-1.0.jar
commons-httpclient-3.1-rc1.jar
commons-io-1.3.2.jar
commons-lang-2.3.jar
commons-logging-1.1.1.jar
commons-logging-api-1.1.jar
commons-net-1.3.0.jar
commons-pool-1.4.jar
commons-validator-1.3.1.jar
concurrent-1.3.4.jar
config-descriptor-7.6.02.00.jar
conversion-jmx-7.6.02.00.jar
deploy-schema-7.6.02.00.jar
derby-10.6.2.1.jar
dom4j-1.6.1.jar
ecore-2.2.3.jar
ecore-change-2.2.3.jar
ecore-xmi-2.2.3.jar
ehcache-1.5.0.jar
ejb3-persistence-1.0.2.GA.jar
embedder-6.0.jar
FastInfoset-1.2.2.jar
foundation-7.6.02.00.jar
geronimo-activation_1.0.2_spec-1.1.jar
geronimo-j2ee-management_1.1_spec-1.0.1.jar
geronimo-jms_1.1_spec-1.1.1.jar
geronimo-jta_1.0.1B_spec-1.0.1.jar
geronimo-stax-api_1.0_spec-1.0.1.jar
grid-framework-7.6.02.00.jar
hibernate-annotations-3.4.0.GA.jar
hibernate-commons-annotations-3.1.0.GA.jar
hibernate-core-3.3.1.GA.jar
hibernate-validator-3.1.0.CR2.jar
i18n-7.6.02.00.jar
jargs-1.0.jar
jasypt-1.5.jar
javassist-3.4.GA.jar
jaxb-api-2.1.jar
jaxb-impl-2.1.7.jar
jaxen-1.1.2.jar
jaxws-api-2.1.jar
jaxws-rt-2.1.4.jar
jaxws-spring-1.8.jar
jboss-sunxacml-2.0.4.jar
jboss-xacml-2.0.4.jar
jcip-annotations-1.0.jar
jcl-over-slf4j-1.5.6.jar
jdom-1.0.jar
jdtcore-2.1.0.jar
joda-time-1.5.2.jar
jsf-api-1.2_12.jar
jsf-impl-1.2_12.jar
jsr107cache-1.0.jar
jsr181-api-1.0-MR1.jar
jsr250-api-1.0.jar
jsr305-1.3.2.jar
jstl-1.2.jar
jta-1.1.jar
jxta-2.3.6.jar
kahadb-5.4.2.jar
log4j-1.2.15.jar
mail-1.4.1.jar
mimepull-1.2.jar
models-7.6.02.00.jar
not-yet-commons-ssl-0.3.9.jar
opensaml-2.1.0.jar
openuddi-client-1.4.jar
openws-1.1.0.jar
org.mortbay.jetty-4.2.27.jar
oro-2.0.8.jar
persistence-api-1.0.jar
quartz-1.6.5.jar
relaxngDatatype-1.0.jar
repository-api-7.6.02.00.jar
repository-client-7.6.02.00.jar
repository-schema-7.6.02.00.jar
resolver-2.9.1.jar
resolver-20050927.jar
resources-7.6.02.00.jar
richfaces-api-3.3.2.SR1.jar
richfaces-impl-3.3.2.SR1.jar
richfaces-ui-3.3.2.SR1.jar
saaj-api-1.3.jar
saaj-impl-1.3.jar
saxpath-1.0-FCS.jar
security-common-7.6.02.00.jar
serializer-2.9.1.jar
sjsxp-1.0.1.jar
slf4j-api-1.5.6.jar
slf4j-log4j12-1.5.6.jar
spring-2.5.4.jar
spring-aop-2.5.4.jar
spring-beans-2.5.4.jar
spring-context-2.5.4.jar
spring-context-support-2.5.4.jar
spring-core-2.5.4.jar
spring-jdbc-2.5.4.jar
spring-jms-2.5.4.jar
spring-oxm-1.5.2.jar
spring-oxm-tiger-1.5.2.jar
spring-security-acl-2.0.3.jar
spring-security-core-2.0.3.jar
spring-security-core-tiger-2.0.3.jar
spring-security-taglibs-2.0.3.jar
spring-support-2.0.8.jar
spring-tx-2.5.4.jar
spring-web-2.5.4.jar
spring-ws-1.5.2.jar
spring-xml-1.5.2.jar
stax-api-1.0.1.jar
stax-api-1.0.jar
stax-ex-1.2.jar
streambuffer-0.8.jar
sun-xacml-2.0.jar
tidy-1.7.jar
tomahawk-1.1.6.jar
tuscany-sdo-api-r2.1-1.1.1.jar
tuscany-sdo-impl-1.1.1.jar
tuscany-sdo-lib-1.1.1.jar
utilities-7.6.02.00.jar
velocity-1.5.jar
whirlycache-1.0.2.jar
ws-orchestrator-7.6.02.00.jar
wsdl4j-1.6.1.jar
wsdl4j-qname-1.6.1.jar
wstx-asl-3.2.1.jar
xalan-2.7.1.jar
xbean-2.2.0.jar
xbean-spring-2.7.jar
xercesImpl-2.9.1.jar
xml-apis-1.3.03.jar
xml-apis-2.9.1.jar
xml-security-1.4.1.jar
xmldsig-1.0.jar
XmlSchema-1.3.2.jar
xmlsec-2.0.jar
xmltooling-1.0.1.jar
xsd-2.2.3.jar
xsom-20070515.jar
xws-security-3.0.jarthe server client jars includes the following jars:
activation.jar
antlr.jar
commons-codec-1.3.jar
commons-httpclient-3.1.jar
commons-logging.jar
concurrent.jar
ejb3-persistence.jar
FastInfoset.jar
getopt.jar
hibernate-annotations.jar
hibernate-commons-annotations.jar
hibernate-core.jar
hibernate-validator.jar
hornetq-core-client.jar
hornetq-jms-client.jar
jacorb.jar
javassist.jar
jaxb-api.jar
jaxb-impl.jar
jaxb-xjc.jar
jaxws-rt.jar
jaxws-tools.jar
jboss-aop-client.jar
jboss-appclient.jar
jboss-aspect-jdk50-client.jar
jboss-client.jar
jboss-common-core.jar
jboss-deployers-client-spi.jar
jboss-deployers-client.jar
jboss-deployers-core-spi.jar
jboss-deployers-core.jar
jboss-deployers-vfs-spi.jar
jboss-deployers-vfs.jar
jboss-deployment.jar
jboss-ejb3-common-client.jar
jboss-ejb3-core-client.jar
jboss-ejb3-ext-api-impl.jar
jboss-ejb3-ext-api.jar
jboss-ejb3-proxy-clustered-client.jar
jboss-ejb3-proxy-impl-client.jar
jboss-ejb3-proxy-spi-client.jar
jboss-ejb3-security-client.jar
jboss-ejb3-vfs-spi.jar
jboss-ha-client.jar
jboss-ha-legacy-client.jar
jboss-iiop-client.jar
jboss-integration.jar
jboss-j2se.jar
jboss-jaspi-api.jar
jboss-javaee.jar
jboss-jsr77-client.jar
jboss-logging-jdk.jar
jboss-logging-log4j.jar
jboss-logging-spi.jar
jboss-mdr.jar
jboss-messaging-client.jar
jboss-metadata.jar
jboss-profileservice-client.jar
jboss-remoting.jar
jboss-security-spi.jar
jboss-serialization.jar
jboss-srp-client.jar
jboss-system-client.jar
jboss-system-jmx-client.jar
jboss-xml-binding.jar
jbossall-client.jar
jbosscx-client.jar
jbossjmx-ant.jar
jbossjts-integration.jar
jbossjts-jacorb.jar
jbossjts.jar
jbosssx-as-client.jar
jbosssx-client.jar
jbossws-common.jar
jbossws-framework.jar
jbossws-jboss50.jar
jbossws-native-client.jar
jbossws-native-core.jar
jbossws-native-jaxrpc.jar
jbossws-native-jaxws-ext.jar
jbossws-native-jaxws.jar
jbossws-native-saaj.jar
jbossws-spi.jar
jettison.jar
jmx-client.jar
jmx-invoker-adaptor-client.jar
jnp-client.jar
log4j.jar
logkit.jar
mail.jar
netty.jar
riftsaw-tools-2.1.5.Final.jar
riftsaw-utils-2.1.5.Final.jar
scout-1.2.2.jar
slf4j-api.jar
slf4j-jboss-logging.jar
stax-api.jar
stax-ex.jar
streambuffer.jar
trove.jar
wsdl4j.jar
wstx.jar
xmlsec.jarI am looking for the right combination of jars from jboss that will allow me to use this specific client. could you help me at this issue?
thanks
-
4. Re: required jars for client configuration for JBoss SOA Platform Version 5.1.0.GA
tcunning Jan 11, 2012 12:54 PM (in response to rotemni)rotem,
What version of JBoss ESB are you using? I'll give you an example for whatever version you need.
--Tom
-
5. Re: required jars for client configuration for JBoss SOA Platform Version 5.1.0.GA
rotemni Jan 11, 2012 1:36 PM (in response to tcunning)Hi Tom
unfortunely, I don't know the exact version (some one else installtion... he isn't available right now ) - I think it is 4.8, but iam not sure
where can find the version xml for the ESB ?
-
6. Re: required jars for client configuration for JBoss SOA Platform Version 5.1.0.GA
rotemni Jan 11, 2012 1:48 PM (in response to rotemni)I will be able to keep on working on the issue (and have certain version numbers) only from tommorow - can you please give me instructions for both 4.8 and 4.9.
thanks !
-
7. Re: required jars for client configuration for JBoss SOA Platform Version 5.1.0.GA
tcunning Jan 11, 2012 10:24 PM (in response to rotemni)That's a little much - can we square away the version number that you are using first? What version of juddi-core JAR do you see in ./server/default/deploy/jbossesb-registry.sar?
-
8. Re: required jars for client configuration for JBoss SOA Platform Version 5.1.0.GA
rotemni Jan 12, 2012 2:40 AM (in response to tcunning)The version is juddi-core-3.0.4 .
-
9. Re: required jars for client configuration for JBoss SOA Platform Version 5.1.0.GA
rotemni Jan 12, 2012 9:40 AM (in response to rotemni)Tom,
after more researching in the issue it seems the Problem is related to JBOSS messaging, since it is the Direct interface my client is using to the ESB
thanks for your help so far,
Rotem