[JBoss JIRA] (DROOLS-18) [Error: incompatible types in statement: boolean (compared from: class be.axi.planner.domain.Task)]
by Michiel Vermandel (JIRA)
[ https://issues.jboss.org/browse/DROOLS-18?page=com.atlassian.jira.plugin.... ]
Michiel Vermandel commented on DROOLS-18:
-----------------------------------------
Well I don't know.
Shouldn't that be supported in drl/mvel ?
I mean I used the "lead" in the sense of getLead() in drl and I used isLead() as pojo method in code.
In pojo you can of course have both getLead() and isLead().
Now I need to make a isLeader() or so... which is not nice.
I think it should be possible that the drl parcer matches the right method.
As the exception shows the parser knows that there is a type conflict, so maybe it could figure out as well that there is a second method that is the right one to use.
> [Error: incompatible types in statement: boolean (compared from: class be.axi.planner.domain.Task)]
> ---------------------------------------------------------------------------------------------------
>
> Key: DROOLS-18
> URL: https://issues.jboss.org/browse/DROOLS-18
> Project: Drools
> Issue Type: Bug
> Security Level: Public(Everyone can see)
> Environment: Windows 7 64Bit
> Java 1.7.0
> Drools-core 5.5.0.Final
> Drools-compiler 5.5.0.Final
> Mvel2 2.1.3.Final
> Reporter: Michiel Vermandel
> Assignee: Mario Fusco
> Priority: Critical
>
> In about one out of ten JUnit runs, I get a crash with stack trace.
> The process terminates immediately.
> Unit test output is 100% the same on successful runs.
> Stack trace:
> [Error: incompatible types in statement: boolean (compared from: class be.axi.planner.domain.Task)]
> [Near : {... this == lead ....}]
> ^
> [Line: 1, Column: 1]
> at org.mvel2.ast.BinaryOperation.<init>(BinaryOperation.java:84)
> at org.mvel2.util.CompilerTools.finalizePayload(CompilerTools.java:118)
> at org.mvel2.compiler.ExpressionCompiler._compile(ExpressionCompiler.java:287)
> at org.mvel2.compiler.ExpressionCompiler.compile(ExpressionCompiler.java:62)
> at org.mvel2.MVEL.compileExpression(MVEL.java:810)
> at org.drools.base.mvel.MVELCompilationUnit.compile(MVELCompilationUnit.java:435)
> at org.drools.base.mvel.MVELCompilationUnit.getCompiledExpression(MVELCompilationUnit.java:238)
> at org.drools.rule.constraint.MvelConstraint.createMvelConditionEvaluator(MvelConstraint.java:206)
> at org.drools.rule.constraint.MvelConstraint.evaluate(MvelConstraint.java:190)
> at org.drools.rule.constraint.MvelConstraint.isAllowed(MvelConstraint.java:157)
> at org.drools.reteoo.AlphaNode.assertObject(AlphaNode.java:137)
> at org.drools.reteoo.CompositeObjectSinkAdapter.doPropagateAssertObject(CompositeObjectSinkAdapter.java:497)
> at org.drools.reteoo.CompositeObjectSinkAdapter.propagateAssertObject(CompositeObjectSinkAdapter.java:382)
> at org.drools.reteoo.ObjectTypeNode.assertObject(ObjectTypeNode.java:235)
> at org.drools.reteoo.EntryPointNode.assertObject(EntryPointNode.java:240)
> at org.drools.common.NamedEntryPoint.insert(NamedEntryPoint.java:350)
> at org.drools.common.NamedEntryPoint.insert(NamedEntryPoint.java:311)
> at org.drools.common.AbstractWorkingMemory.insert(AbstractWorkingMemory.java:903)
> at org.drools.common.AbstractWorkingMemory.insert(AbstractWorkingMemory.java:847)
> at org.drools.planner.core.score.director.drools.DroolsScoreDirector.afterEntityAdded(DroolsScoreDirector.java:103)
> at org.drools.planner.core.heuristic.selector.variable.PlanningVariableWalker.moveIterator(PlanningVariableWalker.java:145)
> at org.drools.planner.core.constructionheuristic.greedyFit.decider.DefaultGreedyDecider.decideNextStep(DefaultGreedyDecider.java:74)
> at org.drools.planner.core.constructionheuristic.greedyFit.DefaultGreedyFitSolverPhase.solve(DefaultGreedyFitSolverPhase.java:65)
> at org.drools.planner.core.solver.DefaultSolver.runSolverPhases(DefaultSolver.java:190)
> at org.drools.planner.core.solver.DefaultSolver.solve(DefaultSolver.java:155)
> at be.axi.planner.app.InspectionSchedule.solve(InspectionSchedule.java:192)
> at be.axi.planner.testcore.AbstractPlanningTestClass.solve(AbstractPlanningTestClass.java:288)
> at be.axi.planner.testcore.AbstractPlanningTestClass.solve(AbstractPlanningTestClass.java:298)
> at be.axi.planner.testcore.AbstractPlanningTestClass.solve(AbstractPlanningTestClass.java:315)
> at be.axi.planner.TaskGroupingTest.communitySuccess02(TaskGroupingTest.java:289)
> 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 org.junit.runners.model.FrameworkMethod$1.runReflectiveCall(FrameworkMethod.java:44)
> at org.junit.internal.runners.model.ReflectiveCallable.run(ReflectiveCallable.java:15)
> at org.junit.runners.model.FrameworkMethod.invokeExplosively(FrameworkMethod.java:41)
> at org.junit.internal.runners.statements.InvokeMethod.evaluate(InvokeMethod.java:20)
> at org.junit.internal.runners.statements.RunBefores.evaluate(RunBefores.java:28)
> at org.junit.runners.BlockJUnit4ClassRunner.runNotIgnored(BlockJUnit4ClassRunner.java:79)
> at org.junit.runners.BlockJUnit4ClassRunner.runChild(BlockJUnit4ClassRunner.java:71)
> at org.junit.runners.BlockJUnit4ClassRunner.runChild(BlockJUnit4ClassRunner.java:49)
> at org.junit.runners.ParentRunner$3.run(ParentRunner.java:193)
> at org.junit.runners.ParentRunner$1.schedule(ParentRunner.java:52)
> at org.junit.runners.ParentRunner.runChildren(ParentRunner.java:191)
> at org.junit.runners.ParentRunner.access$000(ParentRunner.java:42)
> at org.junit.runners.ParentRunner$2.evaluate(ParentRunner.java:184)
> at org.junit.runners.ParentRunner.run(ParentRunner.java:236)
> at org.eclipse.jdt.internal.junit4.runner.JUnit4TestReference.run(JUnit4TestReference.java:50)
> at org.eclipse.jdt.internal.junit.runner.TestExecution.run(TestExecution.java:38)
> at org.eclipse.jdt.internal.junit.runner.RemoteTestRunner.runTests(RemoteTestRunner.java:467)
> at org.eclipse.jdt.internal.junit.runner.RemoteTestRunner.runTests(RemoteTestRunner.java:683)
> at org.eclipse.jdt.internal.junit.runner.RemoteTestRunner.run(RemoteTestRunner.java:390)
> at org.eclipse.jdt.internal.junit.runner.RemoteTestRunner.main(RemoteTestRunner.java:197)
--
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, 3 months
[JBoss JIRA] (AS7-6422) OptionsRoleMappingProvider cannot work on AS7
by Akram Ben Aissi (JIRA)
[ https://issues.jboss.org/browse/AS7-6422?page=com.atlassian.jira.plugin.s... ]
Akram Ben Aissi updated AS7-6422:
---------------------------------
> OptionsRoleMappingProvider cannot work on AS7
> ---------------------------------------------
>
> Key: AS7-6422
> URL: https://issues.jboss.org/browse/AS7-6422
> Project: Application Server 7
> Issue Type: Feature Request
> Components: Security
> Affects Versions: 7.1.2.Final (EAP), 7.1.3.Final (EAP)
> Reporter: Akram Ben Aissi
> Assignee: Anil Saldhana
>
> The OptionsRoleMappingProvider available in picketbox jars is intended to provided a simple way to map some toles to other roles.
> This case is usefull in many cases where you get roles from a system and want to map them to one or several JaaS Roles.
> However, OptionsRoleMappingProvider cannot be used in AS7 to map roles to groups because this provider contains an attribute Properties roleMaps which requires a Properties object to be initialized.
> A Properties object cannot be passed by AS7 configuration, so this provider cannot be used as is.
> Here is its required syntax according to picketbox documentation:
> {code:xml}
> <mapping-module code="org.jboss.security.mapping.providers.OptionsRoleMappingProvider"
> type="role">
> <module-option name="rolesMap" >
> <java:properties xmlns:java="urn:jboss:java-properties"
> xmlns:xs="http://www.w3.org/2001/XMLSchema-instance"
> xs:schemaLocation="urn:jboss:java-properties resource:java-properties_1_0.xsd">
> <java:property>
> <java:key>validuser</java:key>
> <java:value>AuthorizedUser,InternalUser</java:value>
> </java:property>
> </java:properties>
> </module-option>
> <module-option name="replaceRoles">false</module-option>
> </mapping-module>
> </mapping>
> {code}
> Such a syntax is not possible in AS7.
> Here is the incriminated code:
> {code:java}
> private Properties roleMapProperties = new Properties();
> /**
> * Specifies
> */
> private boolean REPLACE_ROLES = false;
>
> public void init(Map<String,Object> opt)
> {
> this.options = opt;
> if(options != null)
> {
> if(options.containsKey(REPLACE_ROLES_STRING))
> {
> REPLACE_ROLES = "true".equalsIgnoreCase((String)options.get(REPLACE_ROLES_STRING));
> }
> if(options.containsKey(ROLES_MAP))
> {
> roleMapProperties = (Properties)options.get(ROLES_MAP);
> }
> }
> }
> {code}
> As you can see, roleMapProperties is a Properties.
> But in AS7, options.get(ROLES_MAP) returns a String.
> So an adapter is required to make the AS match the contract, or another implemtation is required.
--
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, 3 months
[JBoss JIRA] (AS7-6422) OptionsRoleMappingProvider cannot work on AS7
by Akram Ben Aissi (JIRA)
[ https://issues.jboss.org/browse/AS7-6422?page=com.atlassian.jira.plugin.s... ]
Akram Ben Aissi updated AS7-6422:
---------------------------------
Description:
The OptionsRoleMappingProvider available in picketbox jars is intended to provided a simple way to map some toles to other roles.
This case is usefull in many cases where you get roles from a system and want to map them to one or several JaaS Roles.
However, OptionsRoleMappingProvider cannot be used in AS7 to map roles to groups because this provider contains an attribute Properties roleMaps which requires a Properties object to be initialized.
A Properties object cannot be passed by AS7 configuration, so this provider cannot be used as is.
Here is its required syntax according to picketbox documentation:
{code:xml}
<mapping-module code="org.jboss.security.mapping.providers.OptionsRoleMappingProvider"
type="role">
<module-option name="rolesMap" >
<java:properties xmlns:java="urn:jboss:java-properties"
xmlns:xs="http://www.w3.org/2001/XMLSchema-instance"
xs:schemaLocation="urn:jboss:java-properties resource:java-properties_1_0.xsd">
<java:property>
<java:key>validuser</java:key>
<java:value>AuthorizedUser,InternalUser</java:value>
</java:property>
</java:properties>
</module-option>
<module-option name="replaceRoles">false</module-option>
</mapping-module>
</mapping>
{code}
Such a syntax is not possible in AS7.
Here is the incriminated code:
{code:java}
private Properties roleMapProperties = new Properties();
/**
* Specifies
*/
private boolean REPLACE_ROLES = false;
public void init(Map<String,Object> opt)
{
this.options = opt;
if(options != null)
{
if(options.containsKey(REPLACE_ROLES_STRING))
{
REPLACE_ROLES = "true".equalsIgnoreCase((String)options.get(REPLACE_ROLES_STRING));
}
if(options.containsKey(ROLES_MAP))
{
roleMapProperties = (Properties)options.get(ROLES_MAP);
}
}
}
{code}
As you can see, roleMapProperties is a Properties.
But in AS7, options.get(ROLES_MAP) returns a String.
So an adapter is required to make the AS match the contract, or another implemtation is required.
was:
The OptionsRoleMappingProvider available in picketbox jars is intended to provided a simple way to map some toles to other roles.
This case is usefull in many cases where you get roles from a system and want to map them to one or several JaaS Roles.
However, OptionsRoleMappingProvider cannot be used in AS7 to map roles to groups because this provider contains an attribute Properties roleMaps which requires a Properties object to be initialized.
A Properties object cannot be passed by AS7 configuration, so this provider cannot be used as is.
Here is its required syntax according to picketbox documentation:
<mapping-module code="org.jboss.security.mapping.providers.OptionsRoleMappingProvider"
type="role">
<module-option name="rolesMap" >
<java:properties xmlns:java="urn:jboss:java-properties"
xmlns:xs="http://www.w3.org/2001/XMLSchema-instance"
xs:schemaLocation="urn:jboss:java-properties resource:java-properties_1_0.xsd">
<java:property>
<java:key>validuser</java:key>
<java:value>AuthorizedUser,InternalUser</java:value>
</java:property>
</java:properties>
</module-option>
<module-option name="replaceRoles">false</module-option>
</mapping-module>
</mapping>
Such a syntax is not possible in AS7.
Here is the incriminated code:
private Properties roleMapProperties = new Properties();
/**
* Specifies
*/
private boolean REPLACE_ROLES = false;
public void init(Map<String,Object> opt)
{
this.options = opt;
if(options != null)
{
if(options.containsKey(REPLACE_ROLES_STRING))
{
REPLACE_ROLES = "true".equalsIgnoreCase((String)options.get(REPLACE_ROLES_STRING));
}
if(options.containsKey(ROLES_MAP))
{
roleMapProperties = (Properties)options.get(ROLES_MAP);
}
}
}
As you can see, roleMapProperties is a Properties.
But in AS7, options.get(ROLES_MAP) returns a String.
So an adapter is required to make the AS match the contract, or another implemtation is required.
> OptionsRoleMappingProvider cannot work on AS7
> ---------------------------------------------
>
> Key: AS7-6422
> URL: https://issues.jboss.org/browse/AS7-6422
> Project: Application Server 7
> Issue Type: Feature Request
> Components: Security
> Affects Versions: 7.1.2.Final (EAP), 7.1.3.Final (EAP)
> Reporter: Akram Ben Aissi
> Assignee: Anil Saldhana
>
> The OptionsRoleMappingProvider available in picketbox jars is intended to provided a simple way to map some toles to other roles.
> This case is usefull in many cases where you get roles from a system and want to map them to one or several JaaS Roles.
> However, OptionsRoleMappingProvider cannot be used in AS7 to map roles to groups because this provider contains an attribute Properties roleMaps which requires a Properties object to be initialized.
> A Properties object cannot be passed by AS7 configuration, so this provider cannot be used as is.
> Here is its required syntax according to picketbox documentation:
> {code:xml}
> <mapping-module code="org.jboss.security.mapping.providers.OptionsRoleMappingProvider"
> type="role">
> <module-option name="rolesMap" >
> <java:properties xmlns:java="urn:jboss:java-properties"
> xmlns:xs="http://www.w3.org/2001/XMLSchema-instance"
> xs:schemaLocation="urn:jboss:java-properties resource:java-properties_1_0.xsd">
> <java:property>
> <java:key>validuser</java:key>
> <java:value>AuthorizedUser,InternalUser</java:value>
> </java:property>
> </java:properties>
> </module-option>
> <module-option name="replaceRoles">false</module-option>
> </mapping-module>
> </mapping>
> {code}
> Such a syntax is not possible in AS7.
> Here is the incriminated code:
> {code:java}
> private Properties roleMapProperties = new Properties();
> /**
> * Specifies
> */
> private boolean REPLACE_ROLES = false;
>
> public void init(Map<String,Object> opt)
> {
> this.options = opt;
> if(options != null)
> {
> if(options.containsKey(REPLACE_ROLES_STRING))
> {
> REPLACE_ROLES = "true".equalsIgnoreCase((String)options.get(REPLACE_ROLES_STRING));
> }
> if(options.containsKey(ROLES_MAP))
> {
> roleMapProperties = (Properties)options.get(ROLES_MAP);
> }
> }
> }
> {code}
> As you can see, roleMapProperties is a Properties.
> But in AS7, options.get(ROLES_MAP) returns a String.
> So an adapter is required to make the AS match the contract, or another implemtation is required.
--
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, 3 months
[JBoss JIRA] (AS7-6422) OptionsRoleMappingProvider cannot work on AS7
by Akram Ben Aissi (JIRA)
Akram Ben Aissi created AS7-6422:
------------------------------------
Summary: OptionsRoleMappingProvider cannot work on AS7
Key: AS7-6422
URL: https://issues.jboss.org/browse/AS7-6422
Project: Application Server 7
Issue Type: Feature Request
Components: Security
Affects Versions: 7.1.3.Final (EAP), 7.1.2.Final (EAP)
Reporter: Akram Ben Aissi
Assignee: Anil Saldhana
The OptionsRoleMappingProvider available in picketbox jars is intended to provided a simple way to map some toles to other roles.
This case is usefull in many cases where you get roles from a system and want to map them to one or several JaaS Roles.
However, OptionsRoleMappingProvider cannot be used in AS7 to map roles to groups because this provider contains an attribute Properties roleMaps which requires a Properties object to be initialized.
A Properties object cannot be passed by AS7 configuration, so this provider cannot be used as is.
Here is its required syntax according to picketbox documentation:
<mapping-module code="org.jboss.security.mapping.providers.OptionsRoleMappingProvider"
type="role">
<module-option name="rolesMap" >
<java:properties xmlns:java="urn:jboss:java-properties"
xmlns:xs="http://www.w3.org/2001/XMLSchema-instance"
xs:schemaLocation="urn:jboss:java-properties resource:java-properties_1_0.xsd">
<java:property>
<java:key>validuser</java:key>
<java:value>AuthorizedUser,InternalUser</java:value>
</java:property>
</java:properties>
</module-option>
<module-option name="replaceRoles">false</module-option>
</mapping-module>
</mapping>
Such a syntax is not possible in AS7.
Here is the incriminated code:
private Properties roleMapProperties = new Properties();
/**
* Specifies
*/
private boolean REPLACE_ROLES = false;
public void init(Map<String,Object> opt)
{
this.options = opt;
if(options != null)
{
if(options.containsKey(REPLACE_ROLES_STRING))
{
REPLACE_ROLES = "true".equalsIgnoreCase((String)options.get(REPLACE_ROLES_STRING));
}
if(options.containsKey(ROLES_MAP))
{
roleMapProperties = (Properties)options.get(ROLES_MAP);
}
}
}
As you can see, roleMapProperties is a Properties.
But in AS7, options.get(ROLES_MAP) returns a String.
So an adapter is required to make the AS match the contract, or another implemtation is required.
--
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, 3 months
[JBoss JIRA] (AS7-6420) spring-xml deployment fails without any error message given in latest snapshot
by jarkko rantavuori (JIRA)
[ https://issues.jboss.org/browse/AS7-6420?page=com.atlassian.jira.plugin.s... ]
jarkko rantavuori updated AS7-6420:
-----------------------------------
Description:
Today, 30.1.2013, I just got the latest snapshot from https://ci.jboss.org/jenkins/job/JBoss-AS-7.x-latest/lastSuccessfulBuild/... and tried to deploy my Spring framework on it. Spring-xml 2.10 component fails without any error message given, whereas the same jar deployed without issues in 18.12.2012 snapshot.
I tried to set set "JAVA_OPTS=%JAVA_OPTS% -Dorg.jboss.as.logging.per-deployment=false" to get an error message, but that did not help.
EDIT: this seems to be due to already having the deployment there. When you try to readd the same deployment, you get a red box saying deployment failed, but no error message anywhere.
was:
Today, 30.1.2013, I just got the latest snapshot from https://ci.jboss.org/jenkins/job/JBoss-AS-7.x-latest/lastSuccessfulBuild/... and tried to deploy my Spring framework on it. Spring-xml 2.10 component fails without any error message given, whereas the same jar deployed without issues in 18.12.2012 snapshot.
I tried to set set "JAVA_OPTS=%JAVA_OPTS% -Dorg.jboss.as.logging.per-deployment=false" to get an error message, but that did not help.
Jar is from Spring enterprise repository, containing OSGi metadata, so this might be OSGi related.
Steps to Reproduce:
Try to deploy attached spring-xml 2.10 component, downloaded from spring enterprise repository, in the JBoss AS7 snapshot installation (link as a comment). Using web-based admin console, red message "deployment failed" appears, but no reason is available in logs, System.out or UI.
Removing spring-ws deployment, again from admin console, makes spring-xml deployment appear in the admin console UI.
EDIT: or, just deploy any deployment through the admin console, but don't activate it. Try to add the same deployment again. Red box saying "deployment has failed" appears, but there is no details anywhere, not in UI, system.out or logs.
was:
Try to deploy attached spring-xml 2.10 component, downloaded from spring enterprise repository, in the JBoss AS7 snapshot installation (link as a comment). Using web-based admin console, red message "deployment failed" appears, but no reason is available in logs, System.out or UI.
Removing spring-ws deployment, again from admin console, makes spring-xml deployment appear in the admin console UI.
> spring-xml deployment fails without any error message given in latest snapshot
> ------------------------------------------------------------------------------
>
> Key: AS7-6420
> URL: https://issues.jboss.org/browse/AS7-6420
> Project: Application Server 7
> Issue Type: Bug
> Components: Console
> Affects Versions: 7.2.0.Alpha1
> Environment: Windows 7, 64-bit
> Reporter: jarkko rantavuori
> Assignee: Thomas Diesler
> Attachments: org.springframework.xml-2.1.0.RELEASE.jar
>
>
> Today, 30.1.2013, I just got the latest snapshot from https://ci.jboss.org/jenkins/job/JBoss-AS-7.x-latest/lastSuccessfulBuild/... and tried to deploy my Spring framework on it. Spring-xml 2.10 component fails without any error message given, whereas the same jar deployed without issues in 18.12.2012 snapshot.
> I tried to set set "JAVA_OPTS=%JAVA_OPTS% -Dorg.jboss.as.logging.per-deployment=false" to get an error message, but that did not help.
> EDIT: this seems to be due to already having the deployment there. When you try to readd the same deployment, you get a red box saying deployment failed, but no error message anywhere.
--
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, 3 months
[JBoss JIRA] (AS7-6420) spring-xml deployment fails without any error message given in latest snapshot
by jarkko rantavuori (JIRA)
[ https://issues.jboss.org/browse/AS7-6420?page=com.atlassian.jira.plugin.s... ]
jarkko rantavuori commented on AS7-6420:
----------------------------------------
Ok. I get now what is the problem.
- new management console only shows first 10 deployments
- if you deploy a 11th, you won't see it, so it is there as non-enabled without showing up on the ui
- when you notice it's not there you try to deploy again - it fails as it is already been deployed (just not showing up on the ui).
What needs to be done:
- show more than 10 deployments in http://localhost:9990/console/App.html :)
- if a deployment is already there and user tries to re-add the same deployment, give a meaningful error message.
I guess this defect is about giving a meaningful error message. I can open another one about showing more than 10 deployments.
> spring-xml deployment fails without any error message given in latest snapshot
> ------------------------------------------------------------------------------
>
> Key: AS7-6420
> URL: https://issues.jboss.org/browse/AS7-6420
> Project: Application Server 7
> Issue Type: Bug
> Components: OSGi, Server
> Affects Versions: 7.2.0.Alpha1
> Environment: Windows 7, 64-bit
> Reporter: jarkko rantavuori
> Assignee: Thomas Diesler
> Attachments: org.springframework.xml-2.1.0.RELEASE.jar
>
>
> Today, 30.1.2013, I just got the latest snapshot from https://ci.jboss.org/jenkins/job/JBoss-AS-7.x-latest/lastSuccessfulBuild/... and tried to deploy my Spring framework on it. Spring-xml 2.10 component fails without any error message given, whereas the same jar deployed without issues in 18.12.2012 snapshot.
> I tried to set set "JAVA_OPTS=%JAVA_OPTS% -Dorg.jboss.as.logging.per-deployment=false" to get an error message, but that did not help.
> Jar is from Spring enterprise repository, containing OSGi metadata, so this might be OSGi related.
--
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, 3 months
[JBoss JIRA] (JASSIST-183) API breakage: javassist.util.proxy.RuntimeSupport.findSuperMethod has changed signature
by Andrei Ivanov (JIRA)
[ https://issues.jboss.org/browse/JASSIST-183?page=com.atlassian.jira.plugi... ]
Andrei Ivanov commented on JASSIST-183:
---------------------------------------
Well, my project is a bit stuck on Seam 2.2.2 :(
And I think this issue can be easily fixed here by adding back that method so all other projects depending on this API will still work.
> API breakage: javassist.util.proxy.RuntimeSupport.findSuperMethod has changed signature
> ---------------------------------------------------------------------------------------
>
> Key: JASSIST-183
> URL: https://issues.jboss.org/browse/JASSIST-183
> Project: Javassist
> Issue Type: Bug
> Affects Versions: 3.17.0-GA, 3.17.1-GA
> Environment: Seam 2.2.2 / 2.3.0, Java 7u9
> Reporter: Andrei Ivanov
> Assignee: Shigeru Chiba
> Priority: Blocker
> Labels: regression
>
> Checking how some applications run with Java 7, I've tried to upgrade to the newly released Javassist just to notice Seam is no longer working:
> {noformat}
> java.lang.NoSuchMethodError: javassist.util.proxy.RuntimeSupport.findSuperMethod(Ljava/lang/Object;Ljava/lang/String;Ljava/lang/String;)Ljava/lang/reflect/Method;
> at OrderInitializer_$$_javassist_seam_0.writeReplace(OrderInitializer_$$_javassist_seam_0.java)
> at org.jboss.seam.Component.postConstructJavaBean(Component.java:1461)
> at org.jboss.seam.Component.postConstruct(Component.java:1379)
> at org.jboss.seam.Component.newInstance(Component.java:2155)
> at org.jboss.seam.contexts.Contexts.startup(Contexts.java:304)
> at org.jboss.seam.contexts.Contexts.startup(Contexts.java:278)
> at org.jboss.seam.contexts.ServletLifecycle.endInitialization(ServletLifecycle.java:143)
> at org.jboss.seam.init.Initialization.init(Initialization.java:744)
> at org.jboss.seam.mock.AbstractSeamTest.startSeam(AbstractSeamTest.java:929)
> at org.jboss.seam.mock.SeamTest.startSeam(SeamTest.java:69)
> {noformat}
--
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, 3 months