[JBoss JIRA] (SEAMSECURITY-148) Authorization, Idmconsole examples are not working corectly on JDK7 due to RuntimeDroolsException
by Tomas Remes (JIRA)
Tomas Remes created SEAMSECURITY-148:
----------------------------------------
Summary: Authorization, Idmconsole examples are not working corectly on JDK7 due to RuntimeDroolsException
Key: SEAMSECURITY-148
URL: https://issues.jboss.org/browse/SEAMSECURITY-148
Project: Seam Security
Issue Type: Bug
Affects Versions: 3.1.0.Final
Environment: Seam 3, SUN JDK7, JBoss AS 7.1.1.Final
Reporter: Tomas Remes
{noformat}
org.drools.RuntimeDroolsException: value '1.7' is not a valid language level
org.drools.rule.builder.dialect.java.JavaDialectConfiguration.getDefaultLanguageLevel(JavaDialectConfiguration.java:162)
org.drools.rule.builder.dialect.java.JavaDialectConfiguration.init(JavaDialectConfiguration.java:57)
org.drools.compiler.PackageBuilderConfiguration.addDialect(PackageBuilderConfiguration.java:279)
org.drools.compiler.PackageBuilderConfiguration.buildDialectConfigurationMap(PackageBuilderConfiguration.java:268)
org.drools.compiler.PackageBuilderConfiguration.init(PackageBuilderConfiguration.java:181)
org.drools.compiler.PackageBuilderConfiguration.<init>(PackageBuilderConfiguration.java:159)
org.drools.builder.impl.KnowledgeBuilderFactoryServiceImpl.newKnowledgeBuilderConfiguration(KnowledgeBuilderFactoryServiceImpl.java:22)
org.drools.builder.KnowledgeBuilderFactory.newKnowledgeBuilderConfiguration(KnowledgeBuilderFactory.java:75)
org.jboss.seam.security.permission.SecurityRuleLoader.init(SecurityRuleLoader.java:42)
sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:57)
sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43)
java.lang.reflect.Method.invoke(Method.java:601)
org.jboss.weld.util.reflection.SecureReflections$13.work(SecureReflections.java:267)
org.jboss.weld.util.reflection.SecureReflectionAccess.run(SecureReflectionAccess.java:52)
org.jboss.weld.util.reflection.SecureReflectionAccess.runAsInvocation(SecureReflectionAccess.java:137)
org.jboss.weld.util.reflection.SecureReflections.invoke(SecureReflections.java:263)
org.jboss.weld.introspector.jlr.WeldMethodImpl.invoke(WeldMethodImpl.java:174)
org.jboss.weld.injection.MethodInjectionPoint.invoke(MethodInjectionPoint.java:111)
org.jboss.weld.util.Beans.callInitializers(Beans.java:707)
org.jboss.weld.util.Beans.injectFieldsAndInitializers(Beans.java:696)
org.jboss.weld.bean.ManagedBean$ManagedBeanInjectionTarget$1$1.proceed(ManagedBean.java:161)
org.jboss.weld.injection.InjectionContextImpl.run(InjectionContextImpl.java:48)
org.jboss.weld.bean.ManagedBean$ManagedBeanInjectionTarget$1.work(ManagedBean.java:157)
org.jboss.weld.bean.ManagedBean$FixInjectionPoint.run(ManagedBean.java:131)
org.jboss.weld.bean.ManagedBean$ManagedBeanInjectionTarget.inject(ManagedBean.java:153)
org.jboss.weld.bean.ManagedBean.create(ManagedBean.java:293)
org.jboss.weld.context.AbstractContext.get(AbstractContext.java:105)
org.jboss.weld.bean.proxy.ContextBeanInstance.getInstance(ContextBeanInstance.java:90)
org.jboss.weld.bean.proxy.ProxyMethodHandler.invoke(ProxyMethodHandler.java:79)
org.jboss.seam.security.permission.SecurityRuleLoader$Proxy$_$$_WeldClientProxy.getKnowledgeBase(SecurityRuleLoader$Proxy$_$$_WeldClientProxy.java)
org.jboss.seam.security.permission.RuleBasedPermissionResolver.getSecurityRules(RuleBasedPermissionResolver.java:237)
org.jboss.seam.security.permission.RuleBasedPermissionResolver.init(RuleBasedPermissionResolver.java:49)
sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:57)
sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43)
java.lang.reflect.Method.invoke(Method.java:601)
org.jboss.weld.util.reflection.SecureReflections$13.work(SecureReflections.java:267)
org.jboss.weld.util.reflection.SecureReflectionAccess.run(SecureReflectionAccess.java:52)
org.jboss.weld.util.reflection.SecureReflectionAccess.runAsInvocation(SecureReflectionAccess.java:137)
org.jboss.weld.util.reflection.SecureReflections.invoke(SecureReflections.java:263)
org.jboss.weld.introspector.jlr.WeldMethodImpl.invoke(WeldMethodImpl.java:174)
org.jboss.weld.injection.MethodInjectionPoint.invoke(MethodInjectionPoint.java:111)
org.jboss.weld.util.Beans.callInitializers(Beans.java:707)
org.jboss.weld.util.Beans.injectFieldsAndInitializers(Beans.java:696)
org.jboss.weld.bean.ManagedBean$ManagedBeanInjectionTarget$1$1.proceed(ManagedBean.java:161)
org.jboss.weld.injection.InjectionContextImpl.run(InjectionContextImpl.java:48)
org.jboss.weld.bean.ManagedBean$ManagedBeanInjectionTarget$1.work(ManagedBean.java:157)
org.jboss.weld.bean.ManagedBean$FixInjectionPoint.run(ManagedBean.java:131)
org.jboss.weld.bean.ManagedBean$ManagedBeanInjectionTarget.inject(ManagedBean.java:153)
org.jboss.weld.bean.ManagedBean.create(ManagedBean.java:293)
org.jboss.weld.context.AbstractContext.get(AbstractContext.java:105)
org.jboss.weld.bean.proxy.ContextBeanInstance.getInstance(ContextBeanInstance.java:90)
org.jboss.weld.bean.proxy.ProxyMethodHandler.invoke(ProxyMethodHandler.java:79)
org.jboss.seam.security.permission.RuleBasedPermissionResolver$Proxy$_$$_WeldClientProxy.hasPermission(RuleBasedPermissionResolver$Proxy$_$$_WeldClientProxy.java)
org.jboss.seam.security.permission.PermissionMapper.resolvePermission(PermissionMapper.java:31)
org.jboss.seam.security.permission.PermissionMapper$Proxy$_$$_WeldClientProxy.resolvePermission(PermissionMapper$Proxy$_$$_WeldClientProxy.java)
org.jboss.seam.security.IdentityImpl.hasPermission(IdentityImpl.java:587)
org.jboss.seam.security.IdentityImpl$Proxy$_$$_WeldClientProxy.hasPermission(IdentityImpl$Proxy$_$$_WeldClientProxy.java)
org.jboss.seam.security.examples.authorization.security.Restrictions.isDemoUser(Restrictions.java:42)
sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:57)
sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43)
java.lang.reflect.Method.invoke(Method.java:601)
org.jboss.solder.reflection.Reflections.invokeMethod(Reflections.java:474)
org.jboss.solder.reflection.Reflections.invokeMethod(Reflections.java:403)
org.jboss.solder.reflection.annotated.InjectableMethod.invoke(InjectableMethod.java:175)
org.jboss.seam.security.SecurityExtension$Authorizer.authorize(SecurityExtension.java:74)
org.jboss.seam.security.SecurityInterceptor.aroundInvoke(SecurityInterceptor.java:31)
sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:57)
sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43)
java.lang.reflect.Method.invoke(Method.java:601)
org.jboss.weld.interceptor.proxy.SimpleMethodInvocation.invoke(SimpleMethodInvocation.java:30)
org.jboss.weld.interceptor.proxy.SimpleInterceptionChain.invokeNextInterceptor(SimpleInterceptionChain.java:68)
org.jboss.weld.interceptor.proxy.InterceptorMethodHandler.executeInterception(InterceptorMethodHandler.java:112)
org.jboss.weld.interceptor.proxy.InterceptorMethodHandler.invoke(InterceptorMethodHandler.java:88)
org.jboss.weld.bean.proxy.CombinedInterceptorAndDecoratorStackMethodHandler.invoke(CombinedInterceptorAndDecoratorStackMethodHandler.java:53)
org.jboss.seam.security.examples.authorization.PrivilegedActions$Proxy$_$$_WeldSubclass.doDemoUserRuleAction(PrivilegedActions$Proxy$_$$_WeldSubclass.java)
org.jboss.seam.security.examples.authorization.PrivilegedActions$Proxy$_$$_WeldClientProxy.doDemoUserRuleAction(PrivilegedActions$Proxy$_$$_WeldClientProxy.java)
sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:57)
sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43)
java.lang.reflect.Method.invoke(Method.java:601)
org.apache.el.parser.AstValue.invoke(AstValue.java:262)
org.apache.el.MethodExpressionImpl.invoke(MethodExpressionImpl.java:278)
org.jboss.weld.util.el.ForwardingMethodExpression.invoke(ForwardingMethodExpression.java:39)
org.jboss.weld.el.WeldMethodExpression.invoke(WeldMethodExpression.java:50)
com.sun.faces.facelets.el.TagMethodExpression.invoke(TagMethodExpression.java:105)
javax.faces.component.MethodBindingMethodExpressionAdapter.invoke(MethodBindingMethodExpressionAdapter.java:88)
com.sun.faces.application.ActionListenerImpl.processAction(ActionListenerImpl.java:102)
javax.faces.component.UICommand.broadcast(UICommand.java:315)
javax.faces.component.UIViewRoot.broadcastEvents(UIViewRoot.java:794)
javax.faces.component.UIViewRoot.processApplication(UIViewRoot.java:1259)
com.sun.faces.lifecycle.InvokeApplicationPhase.execute(InvokeApplicationPhase.java:81)
com.sun.faces.lifecycle.Phase.doPhase(Phase.java:101)
com.sun.faces.lifecycle.LifecycleImpl.execute(LifecycleImpl.java:118)
javax.faces.webapp.FacesServlet.service(FacesServlet.java:593)
org.jboss.weld.servlet.ConversationPropagationFilter.doFilter(ConversationPropagationFilter.java:62)
org.jboss.solder.servlet.exception.CatchExceptionFilter.doFilter(CatchExceptionFilter.java:65)
org.jboss.solder.servlet.event.ServletEventBridgeFilter.doFilter(ServletEventBridgeFilter.java:74)
{noformat}
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.jboss.org/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira
12 years, 1 month
[JBoss JIRA] (SEAM-137) Booking compilation error on IBM JDK 7
by Tomas Remes (JIRA)
Tomas Remes created SEAM-137:
--------------------------------
Summary: Booking compilation error on IBM JDK 7
Key: SEAM-137
URL: https://issues.jboss.org/browse/SEAM-137
Project: Seam 3 Distribution
Issue Type: Bug
Components: Shared Examples
Affects Versions: 3.1.0.Final
Environment: IBM J9 VM build 2.6, JRE 1.7.0 Linux x86-32 20110810_88604
Reporter: Tomas Remes
Cannot compile booking example on IBM JDK 7 because of weird following exception:
{noformat}
[ERROR] Failure executing javac, but could not parse the error:
chyba:Cannot read org.jboss.seam.examples.booking.log package files, cause : java.io.FileNotFoundException: org.jboss.seam.examples.booking.log/BookingLog
at com.sun.tools.javac.processing.JavacFiler.getResource(JavacFiler.java:476)
at org.jboss.logging.generator.apt.TranslationClassGenerator.findTranslationFiles(TranslationClassGenerator.java:132)
at org.jboss.logging.generator.apt.TranslationClassGenerator.processTypeElement(TranslationClassGenerator.java:95)
at org.jboss.logging.generator.apt.LoggingToolsProcessor.process(LoggingToolsProcessor.java:153)
at com.sun.tools.javac.processing.JavacProcessingEnvironment.callProcessor(JavacProcessingEnvironment.java:805)
at com.sun.tools.javac.processing.JavacProcessingEnvironment.discoverAndRunProcs(JavacProcessingEnvironment.java:734)
at com.sun.tools.javac.processing.JavacProcessingEnvironment.access$1700(JavacProcessingEnvironment.java:109)
at com.sun.tools.javac.processing.JavacProcessingEnvironment$Round.run(JavacProcessingEnvironment.java:1041)
at com.sun.tools.javac.processing.JavacProcessingEnvironment.doProcessing(JavacProcessingEnvironment.java:1175)
at com.sun.tools.javac.main.JavaCompiler.processAnnotations(JavaCompiler.java:1118)
at com.sun.tools.javac.main.JavaCompiler.compile(JavaCompiler.java:836)
at com.sun.tools.javac.main.Main.compile(Main.java:429)
at com.sun.tools.javac.main.Main.compile(Main.java:343)
at com.sun.tools.javac.main.Main.compile(Main.java:334)
at com.sun.tools.javac.Main.compile(Main.java:106)
at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:88)
at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:55)
at java.lang.reflect.Method.invoke(Method.java:613)
at org.codehaus.plexus.compiler.javac.JavacCompiler.compileInProcess(JavacCompiler.java:554)
at org.codehaus.plexus.compiler.javac.JavacCompiler.compile(JavacCompiler.java:161)
at org.apache.maven.plugin.AbstractCompilerMojo.execute(AbstractCompilerMojo.java:605)
at org.apache.maven.plugin.CompilerMojo.execute(CompilerMojo.java:128)
at org.apache.maven.plugin.DefaultBuildPluginManager.executeMojo(DefaultBuildPluginManager.java:101)
at org.apache.maven.lifecycle.internal.MojoExecutor.execute(MojoExecutor.java:209)
at org.apache.maven.lifecycle.internal.MojoExecutor.execute(MojoExecutor.java:153)
at org.apache.maven.lifecycle.internal.MojoExecutor.execute(MojoExecutor.java:145)
at org.apache.maven.lifecycle.internal.LifecycleModuleBuilder.buildProject(LifecycleModuleBuilder.java:84)
at org.apache.maven.lifecycle.internal.LifecycleModuleBuilder.buildProject(LifecycleModuleBuilder.java:59)
at org.apache.maven.lifecycle.internal.LifecycleStarter.singleThreadedBuild(LifecycleStarter.java:183)
at org.apache.maven.lifecycle.internal.LifecycleStarter.execute(LifecycleStarter.java:161)
at org.apache.maven.DefaultMaven.doExecute(DefaultMaven.java:319)
at org.apache.maven.DefaultMaven.execute(DefaultMaven.java:156)
at org.apache.maven.cli.MavenCli.execute(MavenCli.java:537)
at org.apache.maven.cli.MavenCli.doMain(MavenCli.java:196)
at org.apache.maven.cli.MavenCli.main(MavenCli.java:141)
at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:88)
at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:55)
at java.lang.reflect.Method.invoke(Method.java:613)
at org.codehaus.plexus.classworlds.launcher.Launcher.launchEnhanced(Launcher.java:290)
at org.codehaus.plexus.classworlds.launcher.Launcher.launch(Launcher.java:230)
at org.codehaus.plexus.classworlds.launcher.Launcher.mainWithExitCode(Launcher.java:409)
at org.codehaus.plexus.classworlds.launcher.Launcher.main(Launcher.java:352)
{noformat}
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.jboss.org/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira
12 years, 1 month
[jbossseam-issues] [JBoss JIRA] Created: (JBSEAM-2697) Add attribute to s:link tag to make creation of magic dataModelSelection URL parameter optional
by Wolfgang Schwendt (JIRA)
Add attribute to s:link tag to make creation of magic dataModelSelection URL parameter optional
-----------------------------------------------------------------------------------------------
Key: JBSEAM-2697
URL: http://jira.jboss.com/jira/browse/JBSEAM-2697
Project: JBoss Seam
Issue Type: Feature Request
Components: JSF Controls
Affects Versions: 2.0.1.GA
Reporter: Wolfgang Schwendt
Priority: Minor
When an s:link component (org.jboss.seam.ui.component.UILink) is placed into a h:dataTable backed by a javax.faces.model.DataModel, the s:link automatically generates the magic token for the magic "dataModelSelection" parameter regardless of whether the latter is really needed or not.
This can generate ugly URLs. The following example is particulary ugly:
http://127.0.0.1:8080/seminaris/seminarDetails.seam?seminarId=2&dataModel...
Without the "dataModelSelection" parameter, the URL would look much cleaner:
http://127.0.0.1:8080/seminaris/seminarDetails.seam?semId=2
So my question: Couldn't we make the "dataModelSelection" parameter optional? (For example, by adding an attribute to the s:link tag).
Btw: I'm aware that org.jboss.seam.ui.component.UISeamCommandBase.getUrl() is the culprit that triggers inclusion of the the dataModelSelection parameter, so I know how to remove the dataModelSelection parameter generation, but it would be nice if also the officially released Seam version allowed the deactivation of the magic token generation.
Further, no magic token is generated if a UIDataTable is supplied by a normal List rather than a DataModel (cf. UISeamCommandBase.getSelection() ), but unfortunately there can be cases where it makes sense to supply the table data as DataModel rather than normal List.
--
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
12 years, 1 month
[JBoss JIRA] (JBSEAM-4949) Seam annotated JSF validator breaks JPDL navigation
by Andrea Martino (JIRA)
Andrea Martino created JBSEAM-4949:
--------------------------------------
Summary: Seam annotated JSF validator breaks JPDL navigation
Key: JBSEAM-4949
URL: https://issues.jboss.org/browse/JBSEAM-4949
Project: Seam 2
Issue Type: Bug
Components: JSF Integration
Affects Versions: 2.3.0.BETA1
Environment: JBoss AS 7.1.1.Final + RichFaces.4.2.0.Final + Seam 2.3.0.Beta1
Reporter: Andrea Martino
An seam annotated JSF validator does not behave as it should when used within a JPDL navigation.
For example, the following JSF form should go to the second page in the pageflow after "conversationTest.success()" method is executed. If the "myValidator" is annotated using @FacesValidator, everything is fine. Otherwise, if it is validated using seam tags, the framework starts a new conversation after the button is clicked.
{code:xml:title=form.xhtml}
<h:form>
<div>
<h:inputText id="textInput" value="#{conversationTest.text}">
<f:validator validatorId="myValidator"/>
</h:inputText>
</div>
<h:commandButton action="#{conversationTest.success}" value="Success" />
</h:form>
{code}
If the validator is annotated as following, everything is fine:
{code:title=MyValidator.java}
package com.example.validator;
import javax.faces.component.UIComponent;
import javax.faces.context.FacesContext;
import javax.faces.validator.ValidatorException;
@javax.faces.validator.FacesValidator("myValidator")
public class FacesValidator implements javax.faces.validator.Validator{
public void validate(FacesContext facesContext, UIComponent uIComponent, Object bDate) throws ValidatorException {
// empty method. Don't do anything
}
}
{code}
Othewise, it the validator is annotated as following the JPDL annotation is broken:
{code:title=MyValidator.java}
package com.example.validator;
import javax.faces.component.UIComponent;
import javax.faces.context.FacesContext;
import javax.faces.validator.ValidatorException;
import org.jboss.seam.ScopeType;
import org.jboss.seam.annotations.Name;
import org.jboss.seam.annotations.Scope;
import org.jboss.seam.annotations.faces.Validator;
import org.jboss.seam.annotations.intercept.BypassInterceptors;
@Name("myValidator")
@BypassInterceptors
@Scope(ScopeType.STATELESS)
@Validator
public class SeamValidator implements javax.faces.validator.Validator{
public void validate(FacesContext facesContext, UIComponent uIComponent, Object bDate) throws ValidatorException {
// empty method. Don't do anything
}
}
{code}
This issue is probably related to JBSEAM-4944
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.jboss.org/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira
12 years, 1 month
[JBoss JIRA] (SEAMMAIL-33) charset / character encoding / german umlaute
by christoph langer (Created) (JIRA)
charset / character encoding / german umlaute
---------------------------------------------
Key: SEAMMAIL-33
URL: https://issues.jboss.org/browse/SEAMMAIL-33
Project: Seam Mail
Issue Type: Bug
Components: templating
Affects Versions: 3.1.0.Beta4
Environment: Jboss AS 7.0.2
Reporter: christoph langer
Special chars like german umlaute ö ä ü do not work in the mail. Of course i can encode them in the html but in the text alternative thats not possible.
The file is in utf-8, everytime i render a mail with a velocitytemplate the special chars are crippled. Even if i try to log to the console the text that was rendered (tostring) the characters are crippled already.
i have tried to put a velocity.properties in the resource dir(and in web-inf) with
input.encoding=UTF-8
output.encoding=UTF-8
but that did not change a thing.
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.jboss.org/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira
12 years, 1 month