December 2010 - seam-issues - Jboss List Archives

[JBoss JIRA] Created: (SEAMPERSIST-14) Allow @Transactional and @TransactionAttribute to be used on stereotypes

by Stuart Douglas (JIRA)

Allow @Transactional and @TransactionAttribute to be used on stereotypes ------------------------------------------------------------------------ Key: SEAMPERSIST-14 URL: https://jira.jboss.org/browse/SEAMPERSIST-14 Project: Seam Persistence and Transactions Issue Type: Feature Request Reporter: Stuart Douglas As these are not interceptor bindings this will have to be implemented in the portable extension -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: https://jira.jboss.org/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira

15 years, 1 month

1
1
0 / 0

[JBoss JIRA] Created: (SEAMPERSIST-5) Proxy @PersistenceContext injected EntityManager so that they can use EL in queries

by Stuart Douglas (JIRA)

Proxy @PersistenceContext injected EntityManager so that they can use EL in queries ----------------------------------------------------------------------------------- Key: SEAMPERSIST-5 URL: https://jira.jboss.org/browse/SEAMPERSIST-5 Project: Seam Persistence and Transactions Issue Type: Feature Request Reporter: Stuart Douglas -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: https://jira.jboss.org/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira

15 years, 1 month

1
1
0 / 0

[JBoss JIRA] Created: (SEAMPERSIST-3) Support managed hibernate session

by Stuart Douglas (JIRA)

Support managed hibernate session --------------------------------- Key: SEAMPERSIST-3 URL: https://jira.jboss.org/browse/SEAMPERSIST-3 Project: Seam Persistence and Transactions Issue Type: Feature Request Reporter: Stuart Douglas -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: https://jira.jboss.org/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira

15 years, 1 month

1
1
0 / 0

[JBoss JIRA] Created: (SEAMPERSIST-10) SePersistenceContext extension @PersistenceContext has different semantics to EE @PersistenceContext injection

by Stuart Douglas (JIRA)

SePersistenceContext extension @PersistenceContext has different semantics to EE @PersistenceContext injection -------------------------------------------------------------------------------------------------------------- Key: SEAMPERSIST-10 URL: https://jira.jboss.org/browse/SEAMPERSIST-10 Project: Seam Persistence and Transactions Issue Type: Bug Affects Versions: 3.0.0.Alpha1 Reporter: Stuart Douglas Assignee: Stuart Douglas The SePersistenceContext results in a Dependent (or otherwise) scoped application managed EM. EE PersistenceContext injection results in a transaction scoped container managed EM. We need to either disallow this all together or proxy the entity manager to exactly match the semantics of a container managed EM. -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: https://jira.jboss.org/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira

15 years, 1 month

1
1
0 / 0

[jbossseam-issues] [JBoss JIRA] Created: (JBSEAM-4452) Enable LdapIdentityStore to access LDAP via SSL

by Marco Brizi (JIRA)

Enable LdapIdentityStore to access LDAP via SSL ----------------------------------------------- Key: JBSEAM-4452 URL: https://jira.jboss.org/jira/browse/JBSEAM-4452 Project: Seam Issue Type: Feature Request Affects Versions: 2.2.0.GA Environment: Ubuntu 9.04, JBoss AS 5.1.0 GA Reporter: Marco Brizi The current LdapIdentityStore offers a good support for integrate an LDAP repository. Unfortunately, at the moment, there is no configuration to access it via SSL. The minimum support could be done by adding a new boolean attribute (for ex. ssl-enabled) in the ldap-identity-store element to offer the possibility to choose or not a secure communication. I've tried to implement this extension changing security-2.2.xsd and the LdapIdentityStore class. In the second file my work has been on new attribute getter/setter and on initialiseContext(String principal, String credentials) method just adding the following lines : String ldapProtocol = "ldap"; if (isSslEnabled()) { ldapProtocol = "ldaps"; env.setProperty(Context.SECURITY_PROTOCOL, "ssl"); } String providerUrl = String.format("%s://%s:%d", ldapProtocol, getServerAddress(), getServerPort()); In addition get the server certificate and set the -D/usr/lib/jvm/java-6-sun=/path/to/keystore as JAVA_OPTS is needed. At the moment I'm able to initiate the communication with secure LDAP server but the Identity.authenticate causes a "javax.security.auth.login.LoginException: Login Failure: all modules ignored" The complete stacktrace is attached to the issue. -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: https://jira.jboss.org/jira/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira

15 years, 2 months

3
4
0 / 0

[jbossseam-issues] [JBoss JIRA] Created: (JBSEAM-2652) s:decorate does not respect prependId="false" on h:form

by Erik Magnusson (JIRA)

s:decorate does not respect prependId="false" on h:form ------------------------------------------------------- Key: JBSEAM-2652 URL: http://jira.jboss.com/jira/browse/JBSEAM-2652 Project: JBoss Seam Issue Type: Bug Components: JSF Controls Affects Versions: 2.0.1.GA Environment: JBoss Seam 2.0.1GA Reporter: Erik Magnusson Given the following code: <h:form id="login" prependId="false"> <s:validateAll> <f:facet name="afterInvalidField"> <s:label styleClass="error"> <s:message/> </s:label> </f:facet> <div class="labelinputcombo ilcblock"> <h:outputLabel for="username">User name:</h:outputLabel> <s:decorate> <h:inputText id="username" value="#{registrationService.newUser.userName}" required="true"/> </s:decorate> </div> </s:validateAll> <div> <h:commandButton value="Register" action="#{registrationService.registerUser}"/> </div> </h:form> One would expect that none of the generated <input> elements would have prepended IDs, since the h:form has prependId="false". However, since s:decorate insists on inserting a superfluous <div> with a generated ID around the <input> elements it surrounds, those <input> elements end up having prepended IDs from that <div>. The relevant generated HTML: <div class="labelinputcombo ilcblock"> <label for="j_id31:username">User name:</label><div id="j_id31"><input id="j_id31:username" type="text" name="j_id31:username" /></div> </div> I did not ask for either the <div> or it's ID (<div id="j_id31">), or its insertion into my <input> element's ID (id="j_id31:username"). Proposed solutions: 1. Remove the generated <div>. Is it really necessary for the functionality of s:decorate? If I want a div I can always add it myself. 2. If the <div> really is necessary, at least make s:decorate respect the prependId="false" attribute of the surrounding h:form. 3. If that is not possible, as a last resort, introduce a prependId attribute on the <s:decorate> tag so we can at least force this behaviour if we want it. On a more general note, I'm a really big fan of the JSF-Seam-EJB3 combo, but some of the design decisions in the frameworks are baffling. Why so many superfluous generated html tags? And who thought of the bright idea of prepending element id attributes using : (colon) as the delimeter?? This effectively cripples the ability to use CSS to style JSF-generated HTML elements with a simple CSS id selector (since : is a reserved symbol in CSS). -- 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

15 years, 2 months

4
8
0 / 0

[JBoss JIRA] Created: (JBSEAM-4508) Ensure that Drools is a soft dependency for Seam security 3

by Pete Muir (JIRA)

Ensure that Drools is a soft dependency for Seam security 3 ----------------------------------------------------------- Key: JBSEAM-4508 URL: https://jira.jboss.org/jira/browse/JBSEAM-4508 Project: Seam Issue Type: Feature Request Components: Security Reporter: Pete Muir Priority: Critical Fix For: 3.0.0.BETA1 -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: https://jira.jboss.org/jira/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira

15 years, 2 months

2
3
0 / 0

[JBoss JIRA] Created: (SEAMSECURITY-20) Security won't run on stock Glassfish 3.0.1

by Aaron Siri (JIRA)

Security won't run on stock Glassfish 3.0.1 ------------------------------------------- Key: SEAMSECURITY-20 URL: https://issues.jboss.org/browse/SEAMSECURITY-20 Project: Seam Security Issue Type: Bug Affects Versions: 3.0.0.Alpha1 Environment: Mac OS X, Java 1.6.0_22-b04, Glassfish 3.0.1, EclipseLink JPA Reporter: Aaron Siri Trying to get Seam Security Alpha 1 running in a Glassfish 3.0.1 environment I get the following error during runtime: SEVERE: org/hibernate/EmptyInterceptor java.lang.NoClassDefFoundError: org/hibernate/EmptyInterceptor at java.lang.ClassLoader.defineClass1(Native Method) at java.lang.ClassLoader.defineClassCond(ClassLoader.java:632) at java.lang.ClassLoader.defineClass(ClassLoader.java:616) at java.security.SecureClassLoader.defineClass(SecureClassLoader.java:141) at org.glassfish.web.loader.WebappClassLoader.findClass(WebappClassLoader.java:920) at org.glassfish.web.loader.WebappClassLoader.loadClass(WebappClassLoader.java:1430) at org.glassfish.weld.BeanDeploymentArchiveImpl.collectJarInfo(BeanDeploymentArchiveImpl.java:240) at org.glassfish.weld.BeanDeploymentArchiveImpl.populate(BeanDeploymentArchiveImpl.java:217) at org.glassfish.weld.BeanDeploymentArchiveImpl.<init>(BeanDeploymentArchiveImpl.java:102) at org.glassfish.weld.DeploymentImpl.<init>(DeploymentImpl.java:118) at org.glassfish.weld.WeldDeployer.load(WeldDeployer.java:315) at org.glassfish.weld.WeldDeployer.load(WeldDeployer.java:99) at org.glassfish.internal.data.ModuleInfo.load(ModuleInfo.java:175) at org.glassfish.internal.data.ApplicationInfo.load(ApplicationInfo.java:216) at com.sun.enterprise.v3.server.ApplicationLifecycle.deploy(ApplicationLifecycle.java:338) at com.sun.enterprise.v3.server.ApplicationLifecycle.deploy(ApplicationLifecycle.java:183) at org.glassfish.deployment.admin.DeployCommand.execute(DeployCommand.java:272) at com.sun.enterprise.v3.admin.CommandRunnerImpl$1.execute(CommandRunnerImpl.java:305) at com.sun.enterprise.v3.admin.CommandRunnerImpl.doCommand(CommandRunnerImpl.java:320) at com.sun.enterprise.v3.admin.CommandRunnerImpl.doCommand(CommandRunnerImpl.java:1176) at com.sun.enterprise.v3.admin.CommandRunnerImpl.access$900(CommandRunnerImpl.java:83) at com.sun.enterprise.v3.admin.CommandRunnerImpl$ExecutionContext.execute(CommandRunnerImpl.java:1235) at com.sun.enterprise.v3.admin.CommandRunnerImpl$ExecutionContext.execute(CommandRunnerImpl.java:1224) at com.sun.enterprise.v3.admin.AdminAdapter.doCommand(AdminAdapter.java:365) at com.sun.enterprise.v3.admin.AdminAdapter.service(AdminAdapter.java:204) at com.sun.grizzly.tcp.http11.GrizzlyAdapter.service(GrizzlyAdapter.java:166) at com.sun.enterprise.v3.server.HK2Dispatcher.dispath(HK2Dispatcher.java:100) at com.sun.enterprise.v3.services.impl.ContainerMapper.service(ContainerMapper.java:245) at com.sun.grizzly.http.ProcessorTask.invokeAdapter(ProcessorTask.java:791) at com.sun.grizzly.http.ProcessorTask.doProcess(ProcessorTask.java:693) at com.sun.grizzly.http.ProcessorTask.process(ProcessorTask.java:954) at com.sun.grizzly.http.DefaultProtocolFilter.execute(DefaultProtocolFilter.java:170) at com.sun.grizzly.DefaultProtocolChain.executeProtocolFilter(DefaultProtocolChain.java:135) at com.sun.grizzly.DefaultProtocolChain.execute(DefaultProtocolChain.java:102) at com.sun.grizzly.DefaultProtocolChain.execute(DefaultProtocolChain.java:88) at com.sun.grizzly.http.HttpProtocolChain.execute(HttpProtocolChain.java:76) at com.sun.grizzly.ProtocolChainContextTask.doCall(ProtocolChainContextTask.java:53) at com.sun.grizzly.SelectionKeyContextTask.call(SelectionKeyContextTask.java:57) at com.sun.grizzly.ContextTask.run(ContextTask.java:69) at com.sun.grizzly.util.AbstractThreadPool$Worker.doWork(AbstractThreadPool.java:330) at com.sun.grizzly.util.AbstractThreadPool$Worker.run(AbstractThreadPool.java:309) at java.lang.Thread.run(Thread.java:680) Caused by: java.lang.ClassNotFoundException: org.hibernate.EmptyInterceptor at java.net.URLClassLoader$1.run(URLClassLoader.java:202) at java.security.AccessController.doPrivileged(Native Method) at java.net.URLClassLoader.findClass(URLClassLoader.java:190) at org.glassfish.web.loader.WebappClassLoader.findClass(WebappClassLoader.java:959) at org.glassfish.web.loader.WebappClassLoader.loadClass(WebappClassLoader.java:1430) ... 42 more After installing the Hibernate package the above error goes away and I get the following error instead: org.glassfish.deployment.common.DeploymentException: Exception #0 :java.lang.NoClassDefFoundError: org/jboss/logging/Logger at org.glassfish.weld.WeldDeployer.event(WeldDeployer.java:167) at org.glassfish.kernel.event.EventsImpl.send(EventsImpl.java:125) at org.glassfish.internal.data.ApplicationInfo.load(ApplicationInfo.java:224) at com.sun.enterprise.v3.server.ApplicationLifecycle.deploy(ApplicationLifecycle.java:338) at com.sun.enterprise.v3.server.ApplicationLifecycle.deploy(ApplicationLifecycle.java:183) at org.glassfish.deployment.admin.DeployCommand.execute(DeployCommand.java:272) at com.sun.enterprise.v3.admin.CommandRunnerImpl$1.execute(CommandRunnerImpl.java:305) at com.sun.enterprise.v3.admin.CommandRunnerImpl.doCommand(CommandRunnerImpl.java:320) at com.sun.enterprise.v3.admin.CommandRunnerImpl.doCommand(CommandRunnerImpl.java:1176) at com.sun.enterprise.v3.admin.CommandRunnerImpl.access$900(CommandRunnerImpl.java:83) at com.sun.enterprise.v3.admin.CommandRunnerImpl$ExecutionContext.execute(CommandRunnerImpl.java:1235) at com.sun.enterprise.v3.admin.CommandRunnerImpl$ExecutionContext.execute(CommandRunnerImpl.java:1224) at com.sun.enterprise.v3.admin.AdminAdapter.doCommand(AdminAdapter.java:365) at com.sun.enterprise.v3.admin.AdminAdapter.service(AdminAdapter.java:204) at com.sun.grizzly.tcp.http11.GrizzlyAdapter.service(GrizzlyAdapter.java:166) at com.sun.enterprise.v3.server.HK2Dispatcher.dispath(HK2Dispatcher.java:100) at com.sun.enterprise.v3.services.impl.ContainerMapper.service(ContainerMapper.java:245) at com.sun.grizzly.http.ProcessorTask.invokeAdapter(ProcessorTask.java:791) at com.sun.grizzly.http.ProcessorTask.doProcess(ProcessorTask.java:693) at com.sun.grizzly.http.ProcessorTask.process(ProcessorTask.java:954) at com.sun.grizzly.http.DefaultProtocolFilter.execute(DefaultProtocolFilter.java:170) at com.sun.grizzly.DefaultProtocolChain.executeProtocolFilter(DefaultProtocolChain.java:135) at com.sun.grizzly.DefaultProtocolChain.execute(DefaultProtocolChain.java:102) at com.sun.grizzly.DefaultProtocolChain.execute(DefaultProtocolChain.java:88) at com.sun.grizzly.http.HttpProtocolChain.execute(HttpProtocolChain.java:76) at com.sun.grizzly.ProtocolChainContextTask.doCall(ProtocolChainContextTask.java:53) at com.sun.grizzly.SelectionKeyContextTask.call(SelectionKeyContextTask.java:57) at com.sun.grizzly.ContextTask.run(ContextTask.java:69) at com.sun.grizzly.util.AbstractThreadPool$Worker.doWork(AbstractThreadPool.java:330) at com.sun.grizzly.util.AbstractThreadPool$Worker.run(AbstractThreadPool.java:309) at java.lang.Thread.run(Thread.java:680) Caused by: org.jboss.weld.exceptions.DefinitionException: Exception #0 :java.lang.NoClassDefFoundError: org/jboss/logging/Logger at org.jboss.weld.bootstrap.events.AbstractDefinitionContainerEvent.fire(AbstractDefinitionContainerEvent.java:55) at org.jboss.weld.bootstrap.events.BeforeBeanDiscoveryImpl.fire(BeforeBeanDiscoveryImpl.java:66) at org.jboss.weld.bootstrap.WeldBootstrap.startInitialization(WeldBootstrap.java:361) at org.glassfish.weld.WeldDeployer.event(WeldDeployer.java:163) ... 30 more I was under the impression that Security only required JPA and not Hibernate, -- This message is automatically generated by JIRA. - For more information on JIRA, see: http://www.atlassian.com/software/jira

15 years, 2 months

2
6
0 / 0

[JBoss JIRA] Created: (SEAMSECURITY-11) Use Infinispan to cache user role and group memberships

by Shane Bryzak (JIRA)

Use Infinispan to cache user role and group memberships ------------------------------------------------------- Key: SEAMSECURITY-11 URL: https://jira.jboss.org/browse/SEAMSECURITY-11 Project: Seam Security Issue Type: Feature Request Reporter: Shane Bryzak Assignee: Shane Bryzak Fix For: 3.0.0.Beta1 -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: https://jira.jboss.org/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira

15 years, 2 months

1
2
0 / 0

[jbossseam-issues] [JBoss JIRA] Created: (JBSEAM-4045) Add first class support for groups

by Shane Bryzak (JIRA)

Add first class support for groups ---------------------------------- Key: JBSEAM-4045 URL: https://jira.jboss.org/jira/browse/JBSEAM-4045 Project: Seam Issue Type: Feature Request Affects Versions: 2.1.1.GA Reporter: Shane Bryzak Assignee: Shane Bryzak We should add first class support for user groups - these are a separate from roles, and allow applications to group users by department, location, etc. -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: https://jira.jboss.org/jira/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira

15 years, 2 months

1
3
0 / 0

2026

2025

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

2009

2008

2007

2006

seam-issues December 2010