[JBoss JIRA] Created: (JBAS-4683) The 4.2 dtds are not configured in the default schema resolver
by Scott M Stark (JIRA)
The 4.2 dtds are not configured in the default schema resolver
--------------------------------------------------------------
Key: JBAS-4683
URL: http://jira.jboss.com/jira/browse/JBAS-4683
Project: JBoss Application Server
Issue Type: Bug
Security Level: Public (Everyone can see)
Components: XML services
Reporter: Scott M Stark
Assigned To: Alexey Loubyansky
Fix For: JBossAS-5.0.0.Beta3
Trying to deploy a descriptor using a 4.2 id is failing. The schema resolver known dtds needs to be updated to include the 4.2 versions, and these need to be added.
I have the following jboss-web.xml:
+++
<!DOCTYPE jboss-web PUBLIC "-//JBoss//DTD Web Service Reference 4.2//EN"
"http://www.jboss.org/j2ee/dtd/jboss-web_4_2.dtd">
<jboss-web>
<!-- Uncomment the security-domain to enable security. You will
need to edit the htmladaptor login configuration to setup the
login modules used to authentication users.
<security-domain>java:/jaas/jmx-console</security-domain>
-->
</jboss-web>
+++
It causes the following error:
+++
Caused by: org.jboss.xb.binding.JBossXBException: Failed to parse
source:
vfsfile:/home/jfclere/jbossas_head/build/output/jboss-5.0.0.Beta3/server/default/deploy/jmx-console.war/WEB-INF/jboss-web.xml@3,12
at
org.jboss.xb.binding.parser.sax.SaxJBossXBParser.parse(SaxJBossXBParser.java:184)
at
org.jboss.xb.binding.UnmarshallerImpl.unmarshal(UnmarshallerImpl.java:186)
at
org.jboss.deployers.vfs.spi.deployer.ObjectModelFactoryDeployer.parse(ObjectModelFactoryDeployer.java:120)
... 22 more
Caused by: org.xml.sax.SAXException: Element type "jboss-web" must be
declared. @
vfsfile:/home/jfclere/jbossas_head/build/output/jboss-5.0.0.Beta3/server/default/deploy/jmx-console.war/WEB-INF/jboss-web.xml[3,12]
at
org.jboss.xb.binding.parser.sax.SaxJBossXBParser$MetaDataErrorHandler.error(SaxJBossXBParser.java:427)
at org.apache.xerces.util.ErrorHandlerWrapper.error(Unknown Source)
at org.apache.xerces.impl.XMLErrorReporter.reportError(Unknown
Source)
at org.apache.xerces.impl.XMLErrorReporter.reportError(Unknown
Source)
+++
--
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
18 years, 10 months
[JBoss JIRA] Created: (JBAS-4705) org.jboss.varia.scheduler.Scheduler
by Rafael Codina Tormo (JIRA)
org.jboss.varia.scheduler.Scheduler
-----------------------------------
Key: JBAS-4705
URL: http://jira.jboss.com/jira/browse/JBAS-4705
Project: JBoss Application Server
Issue Type: Bug
Security Level: Public (Everyone can see)
Affects Versions: JBossAS-4.0.4.GA
Reporter: Rafael Codina Tormo
Priority: Critical
I am currently implementing MBeans to schedule several classes. For that purpose, I am using the javax.management.timer.Timer class as timer.
Here you can see an exemple:
Code:
<mbean code="javax.management.timer.Timer"
name="app.timer:service=Scheduler">
</mbean>
<mbean code="org.jboss.varia.scheduler.Scheduler"
name="app.timer:service=TheScheduler">
<attribute name="StartAtStartup">true</attribute>
<attribute name="SchedulableClass">myClass</attribute>
<attribute name="SchedulableArgumentTypes">MyTypes</attribute>
<attribute name="SchedulableArguments">MyArgs</attribute>
<attribute name="InitialStartDate">01/01/1970 22:00</attribute>
<attribute name="SchedulePeriod">86400000</attribute>
<attribute name="InitialRepetitions">-1</attribute>
<depends>app.timer:service=Scheduler</depends>
</mbean>
The execution of the class takes 15 minutes (it finishes at 22:15), which makes the second execution start at 22:15 the following day, whereas we need it to be started at 22:00.
--
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
18 years, 10 months
[JBoss JIRA] Created: (BPEL-277) message parts with the atribute element won't be accepted by bpel
by Felipe (JIRA)
message parts with the atribute element won't be accepted by bpel
-----------------------------------------------------------------
Key: BPEL-277
URL: http://jira.jboss.com/jira/browse/BPEL-277
Project: JBoss jBPM BPEL
Issue Type: Bug
Security Level: Public (Everyone can see)
Affects Versions: jBPM BPEL 1.1 beta 3
Environment: Running Java sdk 1.5.0_11, Jboss AS 4.0.5 GA and ant 1.7 in SunOs 5.9
Reporter: Felipe
Assigned To: Alejandro Guizar
Wsdl specification allows the use of the attribute element or type to refer to the XSD definition of the part (Cf. http://www.w3.org/TR/2001/NOTE-wsdl-20010315.html#_messages )
However, when using the following definitions:
<element name="EE">
<complexType>
<sequence>
<element name="usuario" type="xsd:string"/>
<element name="sistema" type="xsd:string"/>
</sequence>
</complexType>
</element>
<wsdl:message name="pruebaE">
<wsdl:part name="entrada" element="tns1:EE"/>
</wsdl:message>
<variable name="entradaPruebaE" messageType="BA:pruebaE"/>
<copy>
<from variable="nombres" />
<to variable="entradaPruebaElectrica" part="entrada" query="/entrada/usuario"/>
</copy>
It will throw the following exception:
2007-08-28 14:45:28,291 DEBUG [org.jbpm.bpel.graph.scope.FaultActionHandler] handling fault: org.jbpm.bpel.gra
ph.exe.ScopeInstance@1f8ab0d[name=<null>,token=/,state=performingPrimaryActivity,id=0]
org.jbpm.bpel.graph.exe.BpelFaultException: org.jbpm.bpel.graph.exe.FaultInstance@4a1535[name={http://schemas.
xmlsoap.org/ws/2004/03/business-process/}selectionFailure,id=0]
at org.jbpm.bpel.sublang.xpath.XPathEvaluator.createNode(XPathEvaluator.java:100)
at org.jbpm.bpel.sublang.xpath.XPathEvaluator.selectOrCreateNodes(XPathEvaluator.java:79)
In the addressed part of XPathEvaluator, the following can be read:
if (!(node instanceof Element)) {
// cannot create node for a non-element parent
throw new BpelFaultException(BpelConstants.FAULT_SELECTION_FAILURE);
}
This won't happen when using a type especification.
--
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
18 years, 10 months