[JBoss JIRA] Created: (SEAM-87) Field marked @IdentityProperty must be public even if it has a public getter
by Zakaria Yussuf (JIRA)
Field marked @IdentityProperty must be public even if it has a public getter
----------------------------------------------------------------------------
Key: SEAM-87
URL: https://issues.jboss.org/browse/SEAM-87
Project: Seam 3 Distribution
Issue Type: Bug
Affects Versions: 3.0.0.Final
Reporter: Zakaria Yussuf
Background:
IdentityObjectCredential is one of the entity classes setup to be used by JPAIdentityStore. It has a field 'value' that is private. The annotation @IdentityProperty(PropertyType.VALUE) is placed on the field itself (not on the getter).
During the authentication process a call is made to org.jboss.seam.solder.reflection.Reflections.getFieldValue() which attempts to access IdentityObjectCredential.value directly, resulting in the following exception:
java.lang.RuntimeException: java.lang.RuntimeException: Exception reading [value] field from object [com.asalsolutions.security.model.IdentityObjectCredential@74c13549].
at org.jboss.seam.security.IdentityImpl.authenticate(IdentityImpl.java:304)
at org.jboss.seam.security.IdentityImpl.login(IdentityImpl.java:223)
at org.jboss.seam.security.org$jboss$weld$bean-WEB-INF$lib$seam-security-impl-ManagedBean-class_org$jboss$seam$security$IdentityImpl_$$_WeldClientProxy.login(org$jboss$weld$bean-WEB-INF$lib$seam-security-impl-ManagedBean-class_org$jboss$seam$security$IdentityImpl_$$_WeldClientProxy.java)
at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:39)
at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25)
at java.lang.reflect.Method.invoke(Method.java:597)
at com.sun.el.parser.AstValue.invoke(AstValue.java:234)
at com.sun.el.MethodExpressionImpl.invoke(MethodExpressionImpl.java:297)
at org.jboss.weld.util.el.ForwardingMethodExpression.invoke(ForwardingMethodExpression.java:43)
at org.jboss.weld.el.WeldMethodExpression.invoke(WeldMethodExpression.java:56)
at com.sun.faces.facelets.el.TagMethodExpression.invoke(TagMethodExpression.java:105)
at javax.faces.component.MethodBindingMethodExpressionAdapter.invoke(MethodBindingMethodExpressionAdapter.java:88)
at com.sun.faces.application.ActionListenerImpl.processAction(ActionListenerImpl.java:102)
at javax.faces.component.UICommand.broadcast(UICommand.java:315)
at javax.faces.component.UIViewRoot.broadcastEvents(UIViewRoot.java:794)
at javax.faces.component.UIViewRoot.processApplication(UIViewRoot.java:1259)
at com.sun.faces.lifecycle.InvokeApplicationPhase.execute(InvokeApplicationPhase.java:81)
at com.sun.faces.lifecycle.Phase.doPhase(Phase.java:101)
at com.sun.faces.lifecycle.LifecycleImpl.execute(LifecycleImpl.java:118)
at javax.faces.webapp.FacesServlet.service(FacesServlet.java:409)
at org.apache.catalina.core.StandardWrapper.service(StandardWrapper.java:1534)
at org.apache.catalina.core.StandardWrapperValve.invoke(StandardWrapperValve.java:281)
at org.apache.catalina.core.StandardContextValve.invoke(StandardContextValve.java:175)
at org.apache.catalina.core.StandardPipeline.doInvoke(StandardPipeline.java:655)
at org.apache.catalina.core.StandardPipeline.invoke(StandardPipeline.java:595)
at com.sun.enterprise.web.WebPipeline.invoke(WebPipeline.java:98)
at com.sun.enterprise.web.PESessionLockingStandardPipeline.invoke(PESessionLockingStandardPipeline.java:91)
at org.apache.catalina.core.StandardHostValve.invoke(StandardHostValve.java:162)
at org.apache.catalina.connector.CoyoteAdapter.doService(CoyoteAdapter.java:326)
at org.apache.catalina.connector.CoyoteAdapter.service(CoyoteAdapter.java:227)
at com.sun.enterprise.v3.services.impl.ContainerMapper.service(ContainerMapper.java:170)
at com.sun.grizzly.http.ProcessorTask.invokeAdapter(ProcessorTask.java:822)
at com.sun.grizzly.http.ProcessorTask.doProcess(ProcessorTask.java:719)
at com.sun.grizzly.http.ProcessorTask.process(ProcessorTask.java:1013)
at com.sun.grizzly.http.DefaultProtocolFilter.execute(DefaultProtocolFilter.java:225)
at com.sun.grizzly.DefaultProtocolChain.executeProtocolFilter(DefaultProtocolChain.java:137)
at com.sun.grizzly.DefaultProtocolChain.execute(DefaultProtocolChain.java:104)
at com.sun.grizzly.DefaultProtocolChain.execute(DefaultProtocolChain.java:90)
at com.sun.grizzly.http.HttpProtocolChain.execute(HttpProtocolChain.java:79)
at com.sun.grizzly.ProtocolChainContextTask.doCall(ProtocolChainContextTask.java:54)
at com.sun.grizzly.SelectionKeyContextTask.call(SelectionKeyContextTask.java:59)
at com.sun.grizzly.ContextTask.run(ContextTask.java:71)
at com.sun.grizzly.util.AbstractThreadPool$Worker.doWork(AbstractThreadPool.java:532)
at com.sun.grizzly.util.AbstractThreadPool$Worker.run(AbstractThreadPool.java:513)
at java.lang.Thread.run(Thread.java:662)
Caused by: java.lang.RuntimeException: Exception reading [value] field from object [com.asalsolutions.security.model.IdentityObjectCredential@74c13549].
at org.jboss.seam.solder.reflection.Reflections.getFieldValue(Reflections.java:584)
at org.jboss.seam.solder.properties.FieldPropertyImpl.getValue(FieldPropertyImpl.java:66)
at org.jboss.seam.security.management.picketlink.JpaIdentityStore.validateCredential(JpaIdentityStore.java:1634)
at org.picketlink.idm.impl.repository.WrapperIdentityStoreRepository.validateCredential(WrapperIdentityStoreRepository.java:303)
at org.picketlink.idm.impl.api.session.managers.AttributesManagerImpl.validateCredentials(AttributesManagerImpl.java:607)
at com.asalsolutions.security.auth.TIJAuthenticator.authenticate(TIJAuthenticator.java:86)
at org.jboss.seam.security.IdentityImpl.authenticate(IdentityImpl.java:284)
... 45 more
Caused by: java.lang.IllegalAccessException: Class org.jboss.seam.solder.reflection.Reflections can not access a member of class com.asalsolutions.security.model.IdentityObjectCredential with modifiers "private"
at sun.reflect.Reflection.ensureMemberAccess(Reflection.java:65)
at java.lang.reflect.Field.doSecurityCheck(Field.java:960)
at java.lang.reflect.Field.getFieldAccessor(Field.java:896)
at java.lang.reflect.Field.get(Field.java:358)
at org.jboss.seam.solder.reflection.Reflections.getFieldValue(Reflections.java:582)
... 51 more
This issue looks a lot like one fixed for Seam 2 (https://issues.jboss.org/browse/JBSEAM-3556)
--
This message is automatically generated by JIRA.
For more information on JIRA, see: http://www.atlassian.com/software/jira
12 years, 8 months
[JBoss JIRA] Created: (SEAMSECURITY-89) Seam-security should have a non-optional runtime dependency on seam-international because it cannot run without it in the classpath
by Geoffrey De Smet (JIRA)
Seam-security should have a non-optional runtime dependency on seam-international because it cannot run without it in the classpath
-----------------------------------------------------------------------------------------------------------------------------------
Key: SEAMSECURITY-89
URL: https://issues.jboss.org/browse/SEAMSECURITY-89
Project: Seam Security
Issue Type: Bug
Reporter: Geoffrey De Smet
Seam-security has a compile time dependency on seam-international-api, but no runtime dependency on seam-international.
As a result, depending on seam-security and not on seam-international, gives a bootstrap exception:
{code}
org.jboss.weld.exceptions.DeploymentException: WELD-001408 Unsatisfied dependencies for type [Locale] with qualifiers [@Default] at injection point [[field] @Inject org.jboss.seam.international.status.ApplicationBundles.appLocale]
at org.jboss.weld.bootstrap.Validator.validateInjectionPoint(Validator.java:270)
at org.jboss.weld.bootstrap.Validator.validateBean(Validator.java:106)
at org.jboss.weld.bootstrap.Validator.validateRIBean(Validator.java:129)
at org.jboss.weld.bootstrap.Validator.validateBeans(Validator.java:351)
at org.jboss.weld.bootstrap.Validator.validateDeployment(Validator.java:336)
at org.jboss.weld.bootstrap.WeldBootstrap.validateBeans(WeldBootstrap.java:404)
at org.jboss.weld.environment.servlet.Listener.contextInitialized(Listener.java:206)
at org.mortbay.jetty.handler.ContextHandler.startContext(ContextHandler.java:549)
at org.mortbay.jetty.servlet.Context.startContext(Context.java:136)
at org.mortbay.jetty.webapp.WebAppContext.startContext(WebAppContext.java:1282)
at org.mortbay.jetty.handler.ContextHandler.doStart(ContextHandler.java:518)
at org.mortbay.jetty.webapp.WebAppContext.doStart(WebAppContext.java:499)
at org.mortbay.component.AbstractLifeCycle.start(AbstractLifeCycle.java:50)
at org.mortbay.jetty.deployer.ContextDeployer.deploy(ContextDeployer.java:268)
at org.mortbay.jetty.deployer.ContextDeployer.access$000(ContextDeployer.java:67)
at org.mortbay.jetty.deployer.ContextDeployer$ScannerListener.fileAdded(ContextDeployer.java:89)
at org.mortbay.util.Scanner.reportAddition(Scanner.java:410)
at org.mortbay.util.Scanner.reportDifferences(Scanner.java:324)
at org.mortbay.util.Scanner.scan(Scanner.java:280)
at org.mortbay.util.Scanner$1.run(Scanner.java:232)
at java.util.TimerThread.mainLoop(Timer.java:512)
at java.util.TimerThread.run(Timer.java:462)
{code}
--
This message is automatically generated by JIRA.
For more information on JIRA, see: http://www.atlassian.com/software/jira
12 years, 8 months
[JBoss JIRA] Created: (SEAMSECURITY-88) Seam-security should have a non-optional dependency on seam-transaction because it cannot run without it in the classpath
by Geoffrey De Smet (JIRA)
Seam-security should have a non-optional dependency on seam-transaction because it cannot run without it in the classpath
-------------------------------------------------------------------------------------------------------------------------
Key: SEAMSECURITY-88
URL: https://issues.jboss.org/browse/SEAMSECURITY-88
Project: Seam Security
Issue Type: Bug
Reporter: Geoffrey De Smet
I've added seam-config 3.1.0.Beta2 to my dependencies and then got an exception at runtime (see below).
Adding an extra dependency on org.jboss.seam.transaction:seam-transaction fixed it.
{code}
2011-08-29 10:05:42.024:WARN::Failed startup of context org.mortbay.jetty.webapp.WebAppContext@198c6f3{/guvnor-webapp,file:/home/gdesmet/projects/jboss/forked-guvnor/guvnor-webapp/target/guvnor-webapp-5.3.0-SNAPSHOT/}
org.jboss.weld.resources.spi.ResourceLoadingException: Error loading class org.jboss.seam.transaction.TransactionInterceptor; location: <class>org.jboss.seam.transaction.TransactionInterceptor</class> in jar:file:/home/gdesmet/projects/jboss/forked-guvnor/guvnor-webapp/target/guvnor-webapp-5.3.0-SNAPSHOT/WEB-INF/lib/seam-security-3.1.0.Beta2.jar!/META-INF/beans.xml@8
at org.jboss.weld.manager.Enabled$ClassLoader.apply(Enabled.java:75)
at org.jboss.weld.manager.Enabled$ClassLoader.apply(Enabled.java:56)
at com.google.common.collect.Lists$TransformingRandomAccessList.get(Lists.java:435)
at java.util.AbstractList$Itr.next(AbstractList.java:345)
at org.jboss.weld.manager.Enabled.createMetadataMap(Enabled.java:143)
at org.jboss.weld.manager.Enabled.<init>(Enabled.java:113)
at org.jboss.weld.manager.Enabled.of(Enabled.java:95)
at org.jboss.weld.bootstrap.BeanDeployment.<init>(BeanDeployment.java:104)
at org.jboss.weld.bootstrap.WeldBootstrap$DeploymentVisitor.visit(WeldBootstrap.java:185)
at org.jboss.weld.bootstrap.WeldBootstrap$DeploymentVisitor.visit(WeldBootstrap.java:156)
at org.jboss.weld.bootstrap.WeldBootstrap.startContainer(WeldBootstrap.java:293)
at org.jboss.weld.environment.servlet.Listener.contextInitialized(Listener.java:171)
at org.mortbay.jetty.handler.ContextHandler.startContext(ContextHandler.java:549)
at org.mortbay.jetty.servlet.Context.startContext(Context.java:136)
at org.mortbay.jetty.webapp.WebAppContext.startContext(WebAppContext.java:1282)
at org.mortbay.jetty.handler.ContextHandler.doStart(ContextHandler.java:518)
at org.mortbay.jetty.webapp.WebAppContext.doStart(WebAppContext.java:499)
at org.mortbay.component.AbstractLifeCycle.start(AbstractLifeCycle.java:50)
at org.mortbay.jetty.deployer.ContextDeployer.deploy(ContextDeployer.java:268)
at org.mortbay.jetty.deployer.ContextDeployer.access$000(ContextDeployer.java:67)
at org.mortbay.jetty.deployer.ContextDeployer$ScannerListener.fileAdded(ContextDeployer.java:89)
at org.mortbay.util.Scanner.reportAddition(Scanner.java:410)
at org.mortbay.util.Scanner.reportDifferences(Scanner.java:324)
at org.mortbay.util.Scanner.scan(Scanner.java:280)
at org.mortbay.util.Scanner$1.run(Scanner.java:232)
at java.util.TimerThread.mainLoop(Timer.java:512)
at java.util.TimerThread.run(Timer.java:462)
{code}
--
This message is automatically generated by JIRA.
For more information on JIRA, see: http://www.atlassian.com/software/jira
12 years, 8 months
[JBoss JIRA] Created: (SOLDER-98) Documentation issues
by Martin Gencur (JIRA)
Documentation issues
--------------------
Key: SOLDER-98
URL: https://issues.jboss.org/browse/SOLDER-98
Project: Seam Solder
Issue Type: Bug
Components: Documentation
Affects Versions: 3.0.0.Final
Reporter: Martin Gencur
Priority: Minor
Fix For: Future
1) Introduction - question marks links ("???") pointing nowhere [only in Seam 3 distribution bundle]
2) Chapter 6. Getting Started -> Tip -> "Maven user-defined property" link pointing nowhere
3) 7.1.2. @Requires -> "Note" contains "The ProcessAnnotatedType container lifecycle event will be called for vetoed types." where
the word "vetoed" should be "required", in fact
4) TYPO -> 7.5. @FullyQualified bean names -> "This behavior aligns is with the needs of"... (the "is" word shouldn't be there IMHO)
5) TYPO -> 11.1. JBoss Logging: The foundation -> "JBoss Logging has is parallel support" (the "is" should be "its" IMHO)
6) TYPO -> 11.3. Typed loggers -> "If injecting a typed logger seems to "enterprisy" to you" ("to" should be "too")
7) TYPO -> 1.6.2. Including the implementation classes in Arquillian tests -> "Otherwise, you may can an exception like:"
8) section "Chapter 17. Default Beans" has probably wrong formatting of the last code snippet of this subchapter
(the one containing @DefaultBean(Cache.class))
--
This message is automatically generated by JIRA.
For more information on JIRA, see: http://www.atlassian.com/software/jira
12 years, 8 months
[JBoss JIRA] Created: (SEAMSERVLET-28) Integrate Catch with *EventBridge* classes
by Jason Porter (JIRA)
Integrate Catch with *EventBridge* classes
------------------------------------------
Key: SEAMSERVLET-28
URL: https://issues.jboss.org/browse/SEAMSERVLET-28
Project: Seam Servlet
Issue Type: Enhancement
Components: Catch Integration
Affects Versions: 3.0.0.Beta1
Reporter: Jason Porter
None of the EventBridge classes catch exceptions to pass to Seam Catch, thus the following code does not invoke any exception handlers:
{code}
public void initial(@Observes @Path("NullPointer") @Initialized final HttpServletRequestContext ctx)
{
throw new NullPointerException();
}
{code}
I would expect the NPE to be passed to Catch for exception handling.
--
This message is automatically generated by JIRA.
For more information on JIRA, see: http://www.atlassian.com/software/jira
12 years, 8 months
[JBoss JIRA] Created: (SOLDER-119) CNFE org.jboss.logmanager.Logger$AttachmentKey on AS7
by Marek Schmidt (JIRA)
CNFE org.jboss.logmanager.Logger$AttachmentKey on AS7
-----------------------------------------------------
Key: SOLDER-119
URL: https://issues.jboss.org/browse/SOLDER-119
Project: Seam Solder
Issue Type: Bug
Components: Logging
Affects Versions: 3.1.0.Beta1
Environment: jboss-as-7.1.0.Alpha1-SNAPSHOT
Reporter: Marek Schmidt
Assignee: Shane Bryzak
Priority: Blocker
Deployment of a WAR with Seam Solder 3.1.0.Beta1 (such as, Seam Config princess rescue example) fails on AS7.
The application contains the following seam jars and no other libraries:
{noformat}
seam-config-xml-3.1.0.Beta1.jar
seam-solder-3.1.0.Beta1.jar
seam-solder-api-3.1.0.Beta1.jar
seam-solder-logging-3.1.0.Beta1.jar
{noformat}
{noformat}
14:52:59,707 ERROR [org.jboss.msc.service.fail] (MSC service thread 1-1) MSC00001: Failed to start service jboss.deployment.unit."config-princess-rescue.war".POST_MODULE: org.jboss.msc.service.StartException in service jboss.deployment.unit."config-princess-rescue.war".POST_MODULE: Failed to process phase POST_MODULE of deployment "config-princess-rescue.war"
at org.jboss.as.server.deployment.DeploymentUnitPhaseService.start(DeploymentUnitPhaseService.java:121)
at org.jboss.msc.service.ServiceControllerImpl$StartTask.run(ServiceControllerImpl.java:1765)
at org.jboss.msc.service.ServiceControllerImpl$ClearTCCLTask.run(ServiceControllerImpl.java:2291)
at java.util.concurrent.ThreadPoolExecutor$Worker.runTask(ThreadPoolExecutor.java:886) [:1.6.0_24]
at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:908) [:1.6.0_24]
at java.lang.Thread.run(Thread.java:662) [:1.6.0_24]
Caused by: java.lang.NoClassDefFoundError: org/jboss/logmanager/Logger$AttachmentKey
at org.jboss.seam.solder.logging.internal.JBossLogManagerProvider.<clinit>(JBossLogManagerProvider.java:36)
at org.jboss.seam.solder.logging.internal.LoggerProviders.findProvider(LoggerProviders.java:33)
at org.jboss.seam.solder.logging.internal.LoggerProviders.<clinit>(LoggerProviders.java:28)
at org.jboss.seam.solder.logging.internal.Logger.getLogger(Logger.java:2164)
at org.jboss.seam.solder.logging.Logger.<init>(Logger.java:44)
at org.jboss.seam.solder.logging.Logger.getLogger(Logger.java:1965)
at org.jboss.seam.solder.logging.Logger.getLogger(Logger.java:1991)
at org.jboss.seam.solder.bean.defaultbean.DefaultBeanExtension.<clinit>(DefaultBeanExtension.java:81)
at sun.reflect.NativeConstructorAccessorImpl.newInstance0(Native Method) [:1.6.0_24]
at sun.reflect.NativeConstructorAccessorImpl.newInstance(NativeConstructorAccessorImpl.java:39) [:1.6.0_24]
at sun.reflect.DelegatingConstructorAccessorImpl.newInstance(DelegatingConstructorAccessorImpl.java:27) [:1.6.0_24]
at java.lang.reflect.Constructor.newInstance(Constructor.java:513) [:1.6.0_24]
at org.jboss.as.weld.deployment.processors.WeldPortableExtensionProcessor.loadExtension(WeldPortableExtensionProcessor.java:117)
at org.jboss.as.weld.deployment.processors.WeldPortableExtensionProcessor.loadAttachments(WeldPortableExtensionProcessor.java:100)
at org.jboss.as.weld.deployment.processors.WeldPortableExtensionProcessor.deploy(WeldPortableExtensionProcessor.java:86)
at org.jboss.as.server.deployment.DeploymentUnitPhaseService.start(DeploymentUnitPhaseService.java:115)
... 5 more
Caused by: java.lang.ClassNotFoundException: org.jboss.logmanager.Logger$AttachmentKey from [Module "deployment.config-princess-rescue.war:main" from Service Module Loader]
at org.jboss.modules.ModuleClassLoader.findClass(ModuleClassLoader.java:191)
at org.jboss.modules.ConcurrentClassLoader.performLoadClassChecked(ConcurrentClassLoader.java:358)
at org.jboss.modules.ConcurrentClassLoader.performLoadClassChecked(ConcurrentClassLoader.java:330)
at org.jboss.modules.ConcurrentClassLoader.performLoadClass(ConcurrentClassLoader.java:307)
at org.jboss.modules.ConcurrentClassLoader.loadClass(ConcurrentClassLoader.java:101)
... 21 more
14:52:59,710 INFO [org.jboss.as.server.controller] (pool-2-thread-6) Deployment of "config-princess-rescue.war" was rolled back with failure message {"Failed services" => {"jboss.deployment.unit.\"config-princess-rescue.war\".POST_MODULE" => "org.jboss.msc.service.StartException in service jboss.deployment.unit.\"config-princess-rescue.war\".POST_MODULE: Failed to process phase POST_MODULE of deployment \"config-princess-rescue.war\""}}
14:52:59,711 INFO [org.jboss.as.controller] (pool-2-thread-6) Service status report
Services which failed to start:
service jboss.deployment.unit."config-princess-rescue.war".POST_MODULE: org.jboss.msc.service.StartException in service jboss.deployment.unit."config-princess-rescue.war".POST_MODULE: Failed to process phase POST_MODULE of deployment "config-princess-rescue.war"
14:52:59,728 INFO [org.jboss.as.server.deployment] (MSC service thread 1-2) Stopped deployment config-princess-rescue.war in 14ms
{noformat}
--
This message is automatically generated by JIRA.
For more information on JIRA, see: http://www.atlassian.com/software/jira
12 years, 8 months