[Design of JBoss Web Services] - Error loading Web Services
by sacramentojoe
I have downloaded JBoss AS 4.0.5. I'm on JDK 1.5. I downloaded the jbossws-1.0.4.GA. I followed the install directions in the install.txt.
I get the following error during startup. I'm new to J2EE and App Servers so I don't even know where to start.
Thank you in advance for your assistance.
--- MBeans waiting for other MBeans ---
ObjectName: jboss.beans:service=JBossBeanDeployment,name='jbossws.beans'
State: FAILED
Reason: org.jboss.deployment.DeploymentException: Cannot start AbstractKernelD
eployment@ed65e0{name=file:/C:/Program Files/jboss/server/default/deploy/jbossws
/jbossws.beans/META-INF/jboss-beans.xml installed=true beans=[AbstractBeanMetaDa
ta@1bb9533{name=ServiceEndpointManager bean=org.jboss.ws.server.ServiceEndpointM
anager properties=[serviceEndpointInvokerMDB, serviceEndpointInvokerJSE, service
EndpointInvokerEJB3, alwaysModifySOAPAddress, serviceEndpointInvokerEJB21, webSe
rviceHost] constructor=null}, AbstractBeanMetaData@406b09{name=ServiceEndpointDe
ployer bean=org.jboss.ws.deployment.ServiceEndpointDeployer properties=[serviceE
ndpointManager] constructor=null}, AbstractBeanMetaData@1332b63{name=ServiceEndp
ointPublisher bean=org.jboss.ws.integration.jboss.JBossServiceEndpointPublisher
properties=[serviceEndpointServlet, serviceEndpointDeployer] constructor=null},
AbstractBeanMetaData@657c7b{name=JMSMessageDispatcher bean=org.jboss.ws.integrat
ion.jboss.jms.JMSMessageDispatcher properties= constructor=null}, AbstractBeanMe
taData@cf7fda{name=SubscriptionManager bean=org.jboss.ws.eventing.mgmt.Subscript
ionManager properties=[defaultLeaseTimeMins, maxLeaseTimeMins] constructor=null}
, AbstractBeanMetaData@d2f5f1{name=ServerConfig bean=org.jboss.ws.integration.jb
oss.ServerConfigImpl properties= constructor=null}, AbstractBeanMetaData@10c276{
name=KernelLocator bean=org.jboss.ws.server.KernelLocator properties= constructo
r=null}]}; - nested throwable: (java.lang.IllegalStateException: Incompletely de
ployed:
*** DEPLOYMENTS IN ERROR:
SubscriptionManager -> org.jboss.joinpoint.spi.JoinpointException: Property defa
ultLeaseTimeMins not found for AbstractBeanInfo(a)12bbe6b{name=org.jboss.ws.eventi
ng.mgmt.SubscriptionManager classInfo= properties=[completedTaskCount, largestPo
olSize, activeCount, eventKeepAlive, class, maxPoolSize, maximumPoolSize, corePo
olSize] methods=[, , , , , , , , , , , , , , , , , , , , , , , , , , , , , , , ,
, , , , , , , , ] constructors=[] events=}
ServiceEndpointManager -> javax.management.InstanceAlreadyExistsException: jboss
.ws:service=ServiceEndpointManager already registered.
JMSMessageDispatcher -> java.lang.ClassNotFoundException: No ClassLoaders found
for: org.jboss.ws.integration.jboss.jms.JMSMessageDispatcher
*** DEPLOYMENTS MISSING DEPENDENCIES:
ServiceEndpointPublisher -> ServiceEndpointDeployer{Configured:Instantiated}
ServiceEndpointDeployer -> ServiceEndpointManager{Configured:**ERROR**}
)
--- MBEANS THAT ARE THE ROOT CAUSE OF THE PROBLEM ---
ObjectName: jboss.beans:service=JBossBeanDeployment,name='jbossws.beans'
State: FAILED
Reason: org.jboss.deployment.DeploymentException: Cannot start AbstractKernelD
eployment@ed65e0{name=file:/C:/Program Files/jboss/server/default/deploy/jbossws
/jbossws.beans/META-INF/jboss-beans.xml installed=true beans=[AbstractBeanMetaDa
ta@1bb9533{name=ServiceEndpointManager bean=org.jboss.ws.server.ServiceEndpointM
anager properties=[serviceEndpointInvokerMDB, serviceEndpointInvokerJSE, service
EndpointInvokerEJB3, alwaysModifySOAPAddress, serviceEndpointInvokerEJB21, webSe
rviceHost] constructor=null}, AbstractBeanMetaData@406b09{name=ServiceEndpointDe
ployer bean=org.jboss.ws.deployment.ServiceEndpointDeployer properties=[serviceE
ndpointManager] constructor=null}, AbstractBeanMetaData@1332b63{name=ServiceEndp
ointPublisher bean=org.jboss.ws.integration.jboss.JBossServiceEndpointPublisher
properties=[serviceEndpointServlet, serviceEndpointDeployer] constructor=null},
AbstractBeanMetaData@657c7b{name=JMSMessageDispatcher bean=org.jboss.ws.integrat
ion.jboss.jms.JMSMessageDispatcher properties= constructor=null}, AbstractBeanMe
taData@cf7fda{name=SubscriptionManager bean=org.jboss.ws.eventing.mgmt.Subscript
ionManager properties=[defaultLeaseTimeMins, maxLeaseTimeMins] constructor=null}
, AbstractBeanMetaData@d2f5f1{name=ServerConfig bean=org.jboss.ws.integration.jb
oss.ServerConfigImpl properties= constructor=null}, AbstractBeanMetaData@10c276{
name=KernelLocator bean=org.jboss.ws.server.KernelLocator properties= constructo
r=null}]}; - nested throwable: (java.lang.IllegalStateException: Incompletely de
ployed:
*** DEPLOYMENTS IN ERROR:
SubscriptionManager -> org.jboss.joinpoint.spi.JoinpointException: Property defa
ultLeaseTimeMins not found for AbstractBeanInfo(a)12bbe6b{name=org.jboss.ws.eventi
ng.mgmt.SubscriptionManager classInfo= properties=[completedTaskCount, largestPo
olSize, activeCount, eventKeepAlive, class, maxPoolSize, maximumPoolSize, corePo
olSize] methods=[, , , , , , , , , , , , , , , , , , , , , , , , , , , , , , , ,
, , , , , , , , ] constructors=[] events=}
ServiceEndpointManager -> javax.management.InstanceAlreadyExistsException: jboss
.ws:service=ServiceEndpointManager already registered.
JMSMessageDispatcher -> java.lang.ClassNotFoundException: No ClassLoaders found
for: org.jboss.ws.integration.jboss.jms.JMSMessageDispatcher
*** DEPLOYMENTS MISSING DEPENDENCIES:
ServiceEndpointPublisher -> ServiceEndpointDeployer{Configured:Instantiated}
ServiceEndpointDeployer -> ServiceEndpointManager{Configured:**ERROR**}
)
10:52:36,844 INFO [Http11BaseProtocol] Starting Coyote HTTP/1.1 on http-0.0.0.0
-8080
10:52:36,969 INFO [ChannelSocket] JK: ajp13 listening on /0.0.0.0:8009
10:52:36,985 INFO [JkMain] Jk running ID=0 time=0/79 config=null
10:52:36,985 INFO [Server] JBoss (MX MicroKernel) [4.0.5.GA (build: CVSTag=Bran
ch_4_0 date=200610162339)] Started in 34s:672ms
10:55:30,625 ERROR [[/jbossws]] StandardWrapper.Throwable
org.jboss.kernel.spi.registry.KernelRegistryEntryNotFoundException: Entry not fo
und with name: ServiceEndpointManager
at org.jboss.kernel.plugins.registry.AbstractKernelRegistry.getEntry(Abs
tractKernelRegistry.java:99)
View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=4006502#4006502
Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=4006502
18 years
todays conf call is canceled because of the R&D call
by Thomas Diesler
Please catch up with me individually.
In line with overall priorities jbossws-1.2.0 has highest priority.
Heiko and I will be working on this. For the others it's still CTS
cheers
-thomas
--
xxxxxxxxxxxxxxxxxxxxxxxxxxxx
Thomas Diesler
Web Service Lead
JBoss, a division of Red Hat
xxxxxxxxxxxxxxxxxxxxxxxxxxxx
18 years
[Design of JBoss Web Services] - Re: @PortComponent replacement
by adrian＠jboss.org
"heiko.braun(a)jboss.com" wrote : While working on config issues i realized that the PortComponentAnnotation needed refactoring. It's now split into @WebContext and @EndpointConfig.
| The main reason for this was the distinction between client and server side annotations.
|
This change breaks the EJB3 testsuite
| [ejort@warjort ejb3]$ ./build.sh -f build-test.xml
| Buildfile: build-test.xml
| Overriding previous definition of reference to jboss.test.classpath
|
| init:
|
| compile-classes:
| [javac] Compiling 1124 source files to /home/ejort/jboss-head/ejb3/output/test-classes
| [javac] /home/ejort/jboss-head/ejb3/src/test/org/jboss/ejb3/test/regression/ejbthree440/model/MyResource.java:12: warning: unmappable character for encoding UTF8
| [javac] * @author Ortwin Gl?
| [javac] ^
| [javac] /home/ejort/jboss-head/ejb3/src/test/org/jboss/ejb3/test/jaxws/EndpointEJB.java:36: package org.jboss.ws.annotation does not exist
| [javac] import org.jboss.ws.annotation.PortComponent;
| [javac] ^
| [javac] /home/ejort/jboss-head/ejb3/src/test/org/jboss/ejb3/test/jaxws/unit/ContextEJBTestCase.java:37: package org.jboss.ws.metadata.wsdl does not exist
| [javac] import org.jboss.ws.metadata.wsdl.WSDLDefinitions;
| [javac] ^
| [javac] /home/ejort/jboss-head/ejb3/src/test/org/jboss/ejb3/test/jaxws/unit/ContextEJBTestCase.java:38: package org.jboss.ws.tools.wsdl does not exist
| [javac] import org.jboss.ws.tools.wsdl.WSDLDefinitionsFactory;
| [javac] ^
| [javac] /home/ejort/jboss-head/ejb3/src/test/org/jboss/ejb3/test/webservices/jsr181/EJB3Bean.java:25: package org.jboss.ws.annotation does not exist
| [javac] import org.jboss.ws.annotation.PortComponent;
| [javac] ^
| [javac] /home/ejort/jboss-head/ejb3/src/test/org/jboss/ejb3/test/webservices/jsr181/EndpointInterface.java:24: package org.jboss.ws.annotation does not exist
| [javac] import org.jboss.ws.annotation.PortComponent;
| [javac] ^
| [javac] /home/ejort/jboss-head/ejb3/src/test/org/jboss/ejb3/test/webservices/unit/JSR181TestCase.java:37: package org.jboss.ws.metadata.wsdl does not exist
| [javac] import org.jboss.ws.metadata.wsdl.WSDLDefinitions;
| [javac] ^
| [javac] /home/ejort/jboss-head/ejb3/src/test/org/jboss/ejb3/test/webservices/unit/JSR181TestCase.java:38: package org.jboss.ws.tools.wsdl does not exist
| [javac] import org.jboss.ws.tools.wsdl.WSDLDefinitionsFactory;
| [javac] ^
| [javac] /home/ejort/jboss-head/ejb3/src/test/org/jboss/ejb3/test/jaxws/EndpointEJB.java:39: cannot find symbol
| [javac] symbol: class PortComponent
| [javac] @PortComponent(contextRoot = "/jaxws-context", urlPattern = "/*")
| [javac] ^
| [javac] /home/ejort/jboss-head/ejb3/src/test/org/jboss/ejb3/test/webservices/jsr181/EJB3Bean.java:38: cannot find symbol
| [javac] symbol: class PortComponent
| [javac] @PortComponent(contextRoot="/jsr181", urlPattern="/*")
| [javac] ^
| [javac] /home/ejort/jboss-head/ejb3/src/test/org/jboss/ejb3/test/dd/web/servlets/SubjectFilter.java:76: warning: [deprecation] getActiveSubject() in org.jboss.security.AuthenticationManager has been deprecated
| [javac] Subject s0 = mgr.getActiveSubject();
| [javac] ^
| [javac] /home/ejort/jboss-head/ejb3/src/test/org/jboss/ejb3/test/jaxws/unit/ContextEJBTestCase.java:63: cannot find symbol
| [javac] symbol : class WSDLDefinitionsFactory
| [javac] location: class org.jboss.ejb3.test.jaxws.unit.ContextEJBTestCase
| [javac] WSDLDefinitionsFactory factory = WSDLDefinitionsFactory.newInstance();
| [javac] ^
| [javac] /home/ejort/jboss-head/ejb3/src/test/org/jboss/ejb3/test/jaxws/unit/ContextEJBTestCase.java:63: cannot find symbol
| [javac] symbol : variable WSDLDefinitionsFactory
| [javac] location: class org.jboss.ejb3.test.jaxws.unit.ContextEJBTestCase
| [javac] WSDLDefinitionsFactory factory = WSDLDefinitionsFactory.newInstance();
| [javac] ^
| [javac] /home/ejort/jboss-head/ejb3/src/test/org/jboss/ejb3/test/jaxws/unit/ContextEJBTestCase.java:64: cannot find symbol
| [javac] symbol : class WSDLDefinitions
| [javac] location: class org.jboss.ejb3.test.jaxws.unit.ContextEJBTestCase
| [javac] WSDLDefinitions wsdlDefinitions = factory.parse(wsdlURL);
| [javac] ^
| [javac] /home/ejort/jboss-head/ejb3/src/test/org/jboss/ejb3/test/standalone/unit/StandardTestCase.java:167: warning: non-varargs call of varargs method with inexact argument type for last parameter;
| [javac] cast to java.lang.Object for a varargs call
| [javac] cast to java.lang.Object[] for a non-varargs call and to suppress this warning
| [javac] Object testCase = constructor.newInstance(constructorParams);
| [javac] ^
| [javac] /home/ejort/jboss-head/ejb3/src/test/org/jboss/ejb3/test/standalone/unit/StandardTestCase.java:192: warning: non-varargs call of varargs method with inexact argument type for last parameter;
| [javac] cast to java.lang.Object for a varargs call
| [javac] cast to java.lang.Object[] for a non-varargs call and to suppress this warning
| [javac] Object testCase = constructor.newInstance(constructorParams);
| [javac] ^
| [javac] /home/ejort/jboss-head/ejb3/src/test/org/jboss/ejb3/test/webservices/unit/JSR181TestCase.java:106: cannot find symbol
| [javac] symbol : class WSDLDefinitionsFactory
| [javac] location: class org.jboss.ejb3.test.webservices.unit.JSR181TestCase
| [javac] WSDLDefinitionsFactory factory = WSDLDefinitionsFactory.newInstance();
| [javac] ^
| [javac] /home/ejort/jboss-head/ejb3/src/test/org/jboss/ejb3/test/webservices/unit/JSR181TestCase.java:106: cannot find symbol
| [javac] symbol : variable WSDLDefinitionsFactory
| [javac] location: class org.jboss.ejb3.test.webservices.unit.JSR181TestCase
| [javac] WSDLDefinitionsFactory factory = WSDLDefinitionsFactory.newInstance();
| [javac] ^
| [javac] /home/ejort/jboss-head/ejb3/src/test/org/jboss/ejb3/test/webservices/unit/JSR181TestCase.java:107: cannot find symbol
| [javac] symbol : class WSDLDefinitions
| [javac] location: class org.jboss.ejb3.test.webservices.unit.JSR181TestCase
| [javac] WSDLDefinitions wsdlDefinitions = factory.parse(wsdlURL);
| [javac] ^
| [javac] Note: Some input files use unchecked or unsafe operations.
| [javac] Note: Recompile with -Xlint:unchecked for details.
| [javac] 15 errors
| [javac] 4 warnings
|
| BUILD FAILED
| /home/ejort/jboss-head/ejb3/build-test.xml:347: Compile failed; see the compiler error output for details.
|
What is it with the webservices team that they can't resist refactoring code
and consequentially continually breaking the JBossAS build? :-)
View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=4005293#4005293
Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=4005293
18 years
WS-I Basic Profile & Other WS-* Status questions
by Burr Sutter
Hey guys,
I'm trying to update our slides on when various WS-* capabilities are
arriving. Please validate/comment on the following:
Already here
- WS-I Basic Profile 1.0 (or is it 1.1?)
- SOAP 1.2
- WSDL 2.0
- MTOM
- WS-Security 1.0
- WS-Addressing 1.0
- SAAJ 1.2
- WS-Eventing
- WS-Content
- XML Schema Part 1: Structures
- XML Schema Part 2: Data types
Coming soon (when?)
- JAX-WS 2.0 with JAXB 2.0
- WS-Security 1.1
18 years
[Design of JBoss Web Services] - Re: JBWS-1464 - Adding MTOM support to WSDL To Java - Design
by heiko.braun＠jboss.com
I would favour point (1). This is what i communicated to the users already. It's simple and fits the overall problem the best. There is many cases where
a) you dont know the exact mimetype
b) data is send inlined
c) you need to pass the content type along
DataHandler is the best chioce IMO.
Regarding Noel's considerations:
anonymous wrote :
| I see base64Binary data that should not be considered as attachment. It's a type that is often used for IDs. For exemple, you can have an operation with an ID as argument and an attachment as a result.
|
It's right what you are saying, but in the only (rare) case this becomes a problem is when users types contain base64 types that should be optimized and others that shouldnt at the same time. If this doesnt occur on the same payload then you easily turn off MTOM for that port.
On the otherhand, if you want to meet that rare case a treshold switch should be used to decide at runtime wether or not optimization should be done.
This is a good idea in many cases, because MTOM optimization does pay off only when data reaches several kb.
View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=4004817#4004817
Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=4004817
18 years
