January 2013 - jboss-jira - Jboss List Archives

[JBoss JIRA] (JBMETA-363) Validation errors with "jboss-web_7_0.xsd

by Wolfgang Knauf (JIRA)

Wolfgang Knauf created JBMETA-363: ------------------------------------- Summary: Validation errors with "jboss-web_7_0.xsd Key: JBMETA-363 URL: https://issues.jboss.org/browse/JBMETA-363 Project: JBoss Metadata Issue Type: Bug Security Level: Public (Everyone can see) Components: web Affects Versions: 7.0.5 Environment: Eclipse Reporter: Wolfgang Knauf Assignee: Jean-Frederic Clere I tried to create a "jboss-web.xml" file based on the "jboss-web_7_1.xsd" As this is not uploaded to the web up to now, I created it with a schema location pointing to my local JBoss 7.2.0Alpha1 snapshot: <?xml version="1.0" encoding="UTF-8"?> <jboss-web xmlns="http://www.jboss.com/xml/ns/javaee" xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance" xsi:schemaLocation="http://www.jboss.com/xml/ns/javaee file:///C:/Temp/jboss-as-7.2.0.Alpha1-SNAPSHOT/docs/schema/jboss-web_7_0.xsd" version="7.0"> ... </jboss-web> Eclipse shows validation errors in the XSD file. The first on is: sch-props-correct.2: A schema cannot contain two global components with the same name; this schema contains two occurences of 'http://java.sun.com/xml/ns/javaee,descriptionGroup' (occurs in javaee_6.xsd, line 88) And a lot more of those. The file was created as part of https://issues.jboss.org/browse/AS7-1262 - and the one who created it found the same validation error. It seems the fix is quite simple: "jboss-web_7_0.xsd" contains this import: <xsd:import namespace="http://java.sun.com/xml/ns/javaee" schemaLocation="web-app_3_0.xsd"/> Change it to: <xsd:import namespace="http://java.sun.com/xml/ns/javaee" schemaLocation="http://java.sun.com/xml/ns/javaee/web-app_3_0.xsd"/> The reason seems to be: "jboss-web_7_0.xsd" imports "jboss-common_6-0.xsd", and this one imports "javaee_6.xsd" with a full schema location. The "web-app_3_0.xsd" in "jboss-web_7_0.xsd" has a local schema location, thus the "javaee_6.xsd" import in "web-app_3_0.xsd" points also to local. And this seems to cause a duplicate import of the file. (might also be an Eclipse valiation bug) -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira

11 years, 11 months

1
0
0 / 0

[JBoss JIRA] (DROOLS-20) Compilation exception gets eaten by MVEL

by Mario Fusco (JIRA)

[ https://issues.jboss.org/browse/DROOLS-20?page=com.atlassian.jira.plugin.... ] Mario Fusco resolved DROOLS-20. ------------------------------- Resolution: Done fixed with mvel 2.1.4 > Compilation exception gets eaten by MVEL > ---------------------------------------- > > Key: DROOLS-20 > URL: https://issues.jboss.org/browse/DROOLS-20 > Project: Drools > Issue Type: Feature Request > Security Level: Public(Everyone can see) > Reporter: Geoffrey De Smet > Assignee: Mario Fusco > Priority: Critical > > To reproduce: > - open planner, run the CloudBalancingApp, load a dataset and click button solve. This will work. > - Now open drools-planner-examples/src/main/resources/org/drools/planner/examples/cloudbalancing/solver/cloudBalancingScoreRules.drl > - At line 114, change > {code} > IntConstraintOccurrence(constraintType = ... > {code} > into > {code} > IntConstraintOccurrence(ConstraintType = ... > {code} > (so change only the case of the first letter of constraintType > - Run the CloudBalancingApp, load a dataset and click button solve. It will fail with this exception (which is not the real exception): > {code} > org.kie.runtime.rule.ConsequenceException: Exception executing consequence for rule "computerCost" in org.drools.planner.examples.cloudbalancing.solver: java.lang.NullPointerException > at org.drools.runtime.rule.impl.DefaultConsequenceExceptionHandler.handleException(DefaultConsequenceExceptionHandler.java:39) ~[drools-core-6.0.0-SNAPSHOT.jar:6.0.0-SNAPSHOT] > ... > Caused by: java.lang.NullPointerException: null > at java.lang.String.<init>(String.java:168) ~[na:1.7.0_09] > at org.mvel2.util.ErrorUtil.rewriteIfNeeded(ErrorUtil.java:12) ~[mvel2-2.1.3.Final.jar:na] > at org.mvel2.compiler.ExpressionCompiler._compile(ExpressionCompiler.java:302) ~[mvel2-2.1.3.Final.jar:na] > at org.mvel2.compiler.ExpressionCompiler.compile(ExpressionCompiler.java:62) ~[mvel2-2.1.3.Final.jar:na] > at org.mvel2.MVEL.compileExpression(MVEL.java:810) ~[mvel2-2.1.3.Final.jar:na] > at org.drools.base.mvel.MVELCompilationUnit.compile(MVELCompilationUnit.java:435) ~[drools-core-6.0.0-SNAPSHOT.jar:6.0.0-SNAPSHOT] > at org.drools.base.mvel.MVELCompilationUnit.getCompiledExpression(MVELCompilationUnit.java:238) ~[drools-core-6.0.0-SNAPSHOT.jar:6.0.0-SNAPSHOT] > at org.drools.rule.constraint.MvelConstraint.createMvelConditionEvaluator(MvelConstraint.java:205) ~[drools-core-6.0.0-SNAPSHOT.jar:6.0.0-SNAPSHOT] > at org.drools.rule.constraint.MvelConstraint.evaluate(MvelConstraint.java:189) ~[drools-core-6.0.0-SNAPSHOT.jar:6.0.0-SNAPSHOT] > at org.drools.rule.constraint.MvelConstraint.isAllowed(MvelConstraint.java:156) ~[drools-core-6.0.0-SNAPSHOT.jar:6.0.0-SNAPSHOT] > at org.drools.reteoo.AlphaNode.assertObject(AlphaNode.java:143) ~[drools-core-6.0.0-SNAPSHOT.jar:6.0.0-SNAPSHOT] > at org.drools.reteoo.CompositeObjectSinkAdapter.doPropagateAssertObject(CompositeObjectSinkAdapter.java:498) ~[drools-core-6.0.0-SNAPSHOT.jar:6.0.0-SNAPSHOT] > at org.drools.reteoo.CompositeObjectSinkAdapter.propagateAssertObject(CompositeObjectSinkAdapter.java:383) ~[drools-core-6.0.0-SNAPSHOT.jar:6.0.0-SNAPSHOT] > at org.drools.reteoo.ObjectTypeNode.assertObject(ObjectTypeNode.java:232) ~[drools-core-6.0.0-SNAPSHOT.jar:6.0.0-SNAPSHOT] > at org.drools.reteoo.EntryPointNode.assertObject(EntryPointNode.java:244) ~[drools-core-6.0.0-SNAPSHOT.jar:6.0.0-SNAPSHOT] > at org.drools.common.NamedEntryPoint.insert(NamedEntryPoint.java:352) ~[drools-core-6.0.0-SNAPSHOT.jar:6.0.0-SNAPSHOT] > at org.drools.beliefsystem.simple.SimpleBeliefSystem.insert(SimpleBeliefSystem.java:49) ~[drools-core-6.0.0-SNAPSHOT.jar:6.0.0-SNAPSHOT] > at org.drools.common.TruthMaintenanceSystem.addLogicalDependency(TruthMaintenanceSystem.java:150) ~[drools-core-6.0.0-SNAPSHOT.jar:6.0.0-SNAPSHOT] > at org.drools.common.TruthMaintenanceSystem.addLogicalDependency(TruthMaintenanceSystem.java:121) ~[drools-core-6.0.0-SNAPSHOT.jar:6.0.0-SNAPSHOT] > at org.drools.common.NamedEntryPoint.insert(NamedEntryPoint.java:227) ~[drools-core-6.0.0-SNAPSHOT.jar:6.0.0-SNAPSHOT] > at org.drools.common.AbstractWorkingMemory.insert(AbstractWorkingMemory.java:822) ~[drools-core-6.0.0-SNAPSHOT.jar:6.0.0-SNAPSHOT] > at org.drools.base.DefaultKnowledgeHelper.insertLogical(DefaultKnowledgeHelper.java:255) ~[drools-core-6.0.0-SNAPSHOT.jar:6.0.0-SNAPSHOT] > at org.drools.base.DefaultKnowledgeHelper.insertLogical(DefaultKnowledgeHelper.java:220) ~[drools-core-6.0.0-SNAPSHOT.jar:6.0.0-SNAPSHOT] > at org.drools.base.DefaultKnowledgeHelper.insertLogical(DefaultKnowledgeHelper.java:215) ~[drools-core-6.0.0-SNAPSHOT.jar:6.0.0-SNAPSHOT] > at org.drools.planner.examples.cloudbalancing.solver.Rule_computerCost_eb2dbb0704b64ca3a554fbda80ff54ab.defaultConsequence(Rule_computerCost_eb2dbb0704b64ca3a554fbda80ff54ab.java:7) ~[na:na] > at org.drools.planner.examples.cloudbalancing.solver.Rule_computerCost_eb2dbb0704b64ca3a554fbda80ff54abDefaultConsequenceInvokerGenerated.evaluate(Unknown Source) ~[na:na] > at org.drools.planner.examples.cloudbalancing.solver.Rule_computerCost_eb2dbb0704b64ca3a554fbda80ff54abDefaultConsequenceInvoker.evaluate(Unknown Source) ~[na:na] > at org.drools.common.DefaultAgenda.fireActivation(DefaultAgenda.java:1421) ~[drools-core-6.0.0-SNAPSHOT.jar:6.0.0-SNAPSHOT] > ... 21 common frames omitted > {code} -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira

11 years, 11 months

1
0
0 / 0

[JBoss JIRA] (AS7-5350) CliArgumentsTestCase.testWrongControler always fails on windows

by Alexey Loubyansky (JIRA)

[ https://issues.jboss.org/browse/AS7-5350?page=com.atlassian.jira.plugin.s... ] Alexey Loubyansky resolved AS7-5350. ------------------------------------ Fix Version/s: 7.2.0.Alpha1 Resolution: Done Fixed. > CliArgumentsTestCase.testWrongControler always fails on windows > --------------------------------------------------------------- > > Key: AS7-5350 > URL: https://issues.jboss.org/browse/AS7-5350 > Project: Application Server 7 > Issue Type: Bug > Components: CLI > Affects Versions: 7.1.2.Final (EAP), 7.2.0.Alpha1 > Environment: Windows > Reporter: Tomaz Cerar > Assignee: Alexey Loubyansky > Fix For: 7.2.0.Alpha1 > > > org.jboss.as.test.integration.management.cli.CliArgumentsTestCase.testWrongControler consistently fails on windows. > jenkins build where it can be seen > http://lightning.mw.lab.eng.bos.redhat.com/jenkins/job/as7-master-windows... -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira

11 years, 11 months

1
0
0 / 0

[JBoss JIRA] (AS7-6392) standalone.sh / domain.sh does not support overriding jboss.server.base.dir, log and config dir in CYGWIN

by Brian Stansberry (JIRA)

[ https://issues.jboss.org/browse/AS7-6392?page=com.atlassian.jira.plugin.s... ] Brian Stansberry reassigned AS7-6392: ------------------------------------- Assignee: (was: Brian Stansberry) If you have a patch for this that you know will reliably work (i.e. doesn't require an unusual cygwin environment), please submit a pull request. > standalone.sh / domain.sh does not support overriding jboss.server.base.dir, log and config dir in CYGWIN > --------------------------------------------------------------------------------------------------------- > > Key: AS7-6392 > URL: https://issues.jboss.org/browse/AS7-6392 > Project: Application Server 7 > Issue Type: Bug > Components: Scripts > Affects Versions: 7.1.3.Final (EAP) > Reporter: Tom Fonteyne > > There is a check on linux, so a cygwin system will not execute this block: > if $linux; then > # consolidate the server and command line opts > CONSOLIDATED_OPTS="$JAVA_OPTS $SERVER_OPTS" > # process the standalone options > for var in $CONSOLIDATED_OPTS > do > case $var in > -Djboss.server.base.dir=*) > JBOSS_BASE_DIR=`readlink -m ${var#*=}` > ... -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira

11 years, 11 months

1
0
0 / 0

[JBoss JIRA] (AS7-6390) Problem with jboss versions of xerces and xalan: XML Parsing Error: duplicate attribute in wsdl definitions

by Brian Stansberry (JIRA)

[ https://issues.jboss.org/browse/AS7-6390?page=com.atlassian.jira.plugin.s... ] Brian Stansberry updated AS7-6390: ---------------------------------- Component/s: Web Services > Problem with jboss versions of xerces and xalan: XML Parsing Error: duplicate attribute in wsdl definitions > ----------------------------------------------------------------------------------------------------------- > > Key: AS7-6390 > URL: https://issues.jboss.org/browse/AS7-6390 > Project: Application Server 7 > Issue Type: Bug > Components: Web Services > Affects Versions: 7.1.1.Final > Reporter: Michael Vetter > > We are using a feature (SimpleWsdl11Definition) of spring ws (version 1.5.9) to serve wsdl files to the browser or to a client. > Our wsdl file has custom namespace prefixes like this: > <wsdl:definitions xmlns:wsdl="http://schemas.xmlsoap.org/wsdl/" xmlns:bsf="http:/... > > It works in JBoss 5.1 and eap 6.0.0 but with JBoss 7.1.1 or the current 7.2 snapshot I get the following error when I enter the wsdl URL in the browser: > XML Parsing Error: duplicate attribute > Location: http://localhost:8080/sc-webservices/service/loginServiceWS.wsdl > Line Number 1, Column 671:<?xml version="1.0" encoding="UTF-8"?><wsdl:definitions xmlns:wsdl="http://schemas.xmlsoap.org/wsdl/" xmlns:bsf="http:// > The wsdl served to the browser contains duplicates of the custom namespace prefixes defined in the original wsdl file packaged in a war inside an ear. > While debugging I only saw classes from jboss versions of xerces and xalan parsing the wsdl and serving the result to the client. -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira

11 years, 11 months

1
0
0 / 0

[JBoss JIRA] (AS7-6389) Integrate prunsrv.exe for OOTB Windows service

by Brian Stansberry (JIRA)

[ https://issues.jboss.org/browse/AS7-6389?page=com.atlassian.jira.plugin.s... ] Brian Stansberry commented on AS7-6389: --------------------------------------- Nicklas, my scheduling this for 7.3 was meant to indicate that it's fine for that release, if you're up for that. It's too late for 7.2. > Integrate prunsrv.exe for OOTB Windows service > ---------------------------------------------- > > Key: AS7-6389 > URL: https://issues.jboss.org/browse/AS7-6389 > Project: Application Server 7 > Issue Type: Enhancement > Components: Scripts > Affects Versions: 7.2.0.Alpha1 > Environment: Windows > Reporter: Nicklas Karlsson > Assignee: Nicklas Karlsson > Fix For: 7.3.0.Alpha1 > > > It would be nice to provide pre-configured scripts for running JBoss as a service on Windows. Tomaž Cerar hinted that the prunsrv.exe in use for EAP should also be used for the community version -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira

11 years, 11 months

1
0
0 / 0

[JBoss JIRA] (AS7-6389) Integrate prunsrv.exe for OOTB Windows service

by Brian Stansberry (JIRA)

[ https://issues.jboss.org/browse/AS7-6389?page=com.atlassian.jira.plugin.s... ] Brian Stansberry updated AS7-6389: ---------------------------------- Fix Version/s: 7.3.0.Alpha1 > Integrate prunsrv.exe for OOTB Windows service > ---------------------------------------------- > > Key: AS7-6389 > URL: https://issues.jboss.org/browse/AS7-6389 > Project: Application Server 7 > Issue Type: Enhancement > Components: Scripts > Affects Versions: 7.2.0.Alpha1 > Environment: Windows > Reporter: Nicklas Karlsson > Assignee: Nicklas Karlsson > Fix For: 7.3.0.Alpha1 > > > It would be nice to provide pre-configured scripts for running JBoss as a service on Windows. Tomaž Cerar hinted that the prunsrv.exe in use for EAP should also be used for the community version -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira

11 years, 11 months

1
0
0 / 0

[JBoss JIRA] (AS7-6408) Can't configure JGroups subsystem with CLI script in 7.2.0.Alpha1-SNAPSHOT

by Tomaz Cerar (JIRA)

[ https://issues.jboss.org/browse/AS7-6408?page=com.atlassian.jira.plugin.s... ] Tomaz Cerar commented on AS7-6408: ---------------------------------- Yeah fix also addresses that. news is that you now have both :add-protocol and :add-transport operations that replace that lists that had in :add() operation but in any case I would modify your script to something like that: {noformat} # Configuring jGroups batch /extension=org.jboss.as.clustering.jgroups:add run-batch batch /subsystem=jgroups:add(default-stack=udp) # protocols is a list of string now. I have to configure socket-bindings later /subsystem=jgroups/stack=udp:add() /subsystem=jgroups/stack=udp:add-transport("type"=>"UDP","socket-binding"=>"jgroups-udp") /subsystem=jgroups/stack=udp:add-protocol("type"=>"FD_SOCK","socket-binding"=>"jgroups-udp-fd") ... (other protocols)... /subsystem=jgroups/stack=tcp:add() /subsystem=jgroups/stack=udp:add-transport("type"=>"TCP","socket-binding"=>"jgroups-tcp") /subsystem=jgroups/stack=udp:add-protocol("type"=>"MPING","socket-binding"=>"jgroups-mping") /subsystem=jgroups/stack=udp:add-protocol("type"=>"pbcast.NAKACK2") ... (other protocols)... run-batch {noformat} > Can't configure JGroups subsystem with CLI script in 7.2.0.Alpha1-SNAPSHOT > --------------------------------------------------------------------------- > > Key: AS7-6408 > URL: https://issues.jboss.org/browse/AS7-6408 > Project: Application Server 7 > Issue Type: Bug > Components: Clustering > Affects Versions: 7.2.0.Alpha1 > Environment: Git checkout of JBossAS 7.2.0.ALPHA1 from today (28/Jan/2013) > Reporter: Bernd Koecke > Assignee: Tomaz Cerar > Attachments: standalone-ha-jgroups.cli, standalone-jgroups-fragment.xml > > > When I try to configure extension and subsystem JGroups with a CLI script, the attribute "protocols" of the stack=tcp- or stack=udp-node contains the list of configured protocols twice. The result is that the list of protocols is doubled in the standalone.xml. But having a protocol twice in one stack results in an error at next server startup. I will attach the CLI script and the resulting XML fragment. > When I shutdown the server, remove the doubled second part of each protocol list, the server comes up and all is working fine. But I can't configure it only with a CLI script. -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira

11 years, 11 months

1
0
0 / 0

[JBoss JIRA] (DROOLS-22) Drools index files are getting created out of control and consume all of the hard drive space

by Jyothi Alapati (JIRA)

[ https://issues.jboss.org/browse/DROOLS-22?page=com.atlassian.jira.plugin.... ] Jyothi Alapati updated DROOLS-22: --------------------------------- Issue Type: Bug (was: Feature Request) > Drools index files are getting created out of control and consume all of the hard drive space > --------------------------------------------------------------------------------------------- > > Key: DROOLS-22 > URL: https://issues.jboss.org/browse/DROOLS-22 > Project: Drools > Issue Type: Bug > Security Level: Public(Everyone can see) > Reporter: Jyothi Alapati > Assignee: Mark Proctor > Attachments: repository.xml, workspace.xml > > > Drools index files are getting created out of control and consume all of the hard drive space. It used to consume 20MB for index files, but in this case, it consumed 5GB of hard disk space and stopped working. > Note: Deleting the old index files except the latest solved this problem, but we want this to be prevented, instead of deleting the index files manually. -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira

11 years, 11 months

1
0
0 / 0

[JBoss JIRA] (AS7-6388) @Resource injection of Datasource on clustered SFSB fails with serialization error

by Paul Ferraro (JIRA)

[ https://issues.jboss.org/browse/AS7-6388?page=com.atlassian.jira.plugin.s... ] Paul Ferraro updated AS7-6388: ------------------------------ Git Pull Request: (was: https://github.com/jbossas/jboss-as/pull/3933) > @Resource injection of Datasource on clustered SFSB fails with serialization error > ---------------------------------------------------------------------------------- > > Key: AS7-6388 > URL: https://issues.jboss.org/browse/AS7-6388 > Project: Application Server 7 > Issue Type: Bug > Components: Clustering > Affects Versions: 7.1.3.Final (EAP) > Reporter: Paul Ferraro > Assignee: Paul Ferraro > Fix For: 7.2.0.Alpha1 > > > See JBPAPP6-1762 for details. -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira

11 years, 11 months

1
0
0 / 0

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

2009

2008

2007

2006

jboss-jira January 2013