[esb-issues] [JBoss JIRA] Created: (JBESB-1258) helloworld_file_action QS throws 'max-millis-for-response' is not allowed to appear in element
Burr Sutter (JIRA)
jira-events at lists.jboss.org
Sat Oct 27 14:32:01 EDT 2007
helloworld_file_action QS throws 'max-millis-for-response' is not allowed to appear in element
----------------------------------------------------------------------------------------------
Key: JBESB-1258
URL: http://jira.jboss.com/jira/browse/JBESB-1258
Project: JBoss ESB
Issue Type: Bug
Security Level: Public (Everyone can see)
Components: Examples
Affects Versions: 4.2.1 IR2
Reporter: Burr Sutter
Assigned To: Mark Little
Fix For: 4.2.1 triage
Fails to deploy as a .esb archive (from SVN Trunk as of oct 27)
14:27:40,609 ERROR [XmlValidatorImpl] 1-ERROR-null-50:cvc-complex-type.3.2.2: At
tribute 'max-millis-for-response' is not allowed to appear in element 'fs-listen
er'.
14:27:40,640 WARN [ServiceController] Problem starting service jboss.esb:deploy
ment=Quickstart_helloworld_file_action.esb
java.lang.RuntimeException: java.lang.IllegalStateException: ESB file had valida
tion errors.
at org.jboss.soa.esb.listeners.config.Configuration.create(Configuration
.java:132)
at org.jboss.soa.esb.listeners.config.JBoss4ESBDeployment.startService(J
Boss4ESBDeployment.java:82)
at org.jboss.system.ServiceMBeanSupport.jbossInternalStart(ServiceMBeanS
upport.java:289)
at org.jboss.system.ServiceMBeanSupport.jbossInternalLifecycle(ServiceMB
eanSupport.java:245)
at sun.reflect.GeneratedMethodAccessor3.invoke(Unknown Source)
at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAcces
sorImpl.java:25)
at java.lang.reflect.Method.invoke(Method.java:585)
at org.jboss.mx.interceptor.ReflectedDispatcher.invoke(ReflectedDispatch
er.java:155)
at org.jboss.mx.server.Invocation.dispatch(Invocation.java:94)
at org.jboss.mx.server.Invocation.invoke(Invocation.java:86)
at org.jboss.mx.server.AbstractMBeanInvoker.invoke(AbstractMBeanInvoker.
java:264)
at org.jboss.mx.server.MBeanServerImpl.invoke(MBeanServerImpl.java:659)
at org.jboss.system.ServiceController$ServiceProxy.invoke(ServiceControl
ler.java:978)
at $Proxy0.start(Unknown Source)
at org.jboss.system.ServiceController.start(ServiceController.java:417)
at org.jboss.system.ServiceController.start(ServiceController.java:435)
at sun.reflect.GeneratedMethodAccessor9.invoke(Unknown Source)
at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAcces
sorImpl.java:25)
at java.lang.reflect.Method.invoke(Method.java:585)
at org.jboss.mx.interceptor.ReflectedDispatcher.invoke(ReflectedDispatch
er.java:155)
at org.jboss.mx.server.Invocation.dispatch(Invocation.java:94)
at org.jboss.mx.server.Invocation.invoke(Invocation.java:86)
at org.jboss.mx.server.AbstractMBeanInvoker.invoke(AbstractMBeanInvoker.
java:264)
at org.jboss.mx.server.MBeanServerImpl.invoke(MBeanServerImpl.java:659)
at org.jboss.mx.util.MBeanProxyExt.invoke(MBeanProxyExt.java:210)
at $Proxy4.start(Unknown Source)
at org.jboss.deployment.SARDeployer.start(SARDeployer.java:302)
--
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators: http://jira.jboss.com/jira/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira
More information about the esb-issues
mailing list