March 2011 - seam-issues - Jboss List Archives

[JBoss JIRA] Created: (SOLDER-59) Create utility for printing the version number of an extension

by Dan Allen (JIRA)

Create utility for printing the version number of an extension -------------------------------------------------------------- Key: SOLDER-59 URL: https://issues.jboss.org/browse/SOLDER-59 Project: Seam Solder Issue Type: Feature Request Components: Core Affects Versions: 3.0.0.Beta1 Reporter: Dan Allen Fix For: 3.0.0.CR1 Quite often, extension writers will want to log the version number of their extension for debugging, compliance or other purposes. We should provide a convenient utility for doing so, possibly even one that handles the logging itself. See CoreExtension for one example and Weld's Bootstrap class for another example. -- This message is automatically generated by JIRA. - For more information on JIRA, see: http://www.atlassian.com/software/jira

15 years

2
4
0 / 0

[JBoss JIRA] Created: (SEAMPERSIST-40) Replace SeamManaged annotation in documentation

by Ondrej Skutka (JIRA)

Replace SeamManaged annotation in documentation ----------------------------------------------- Key: SEAMPERSIST-40 URL: https://issues.jboss.org/browse/SEAMPERSIST-40 Project: Seam Persistence Issue Type: Bug Reporter: Ondrej Skutka Priority: Minor Fix For: 3.0.0.Final As @SeamManaged has been moved and renamed to @ExtensionManaged, please also update documentation to reflect the change: persistence/docs/src/main/docbook/en-US/persistence-general.xml And also javadoc in persistence/impl/src/main/java/org/jboss/seam/persistence/ManagedPersistenceContextBeanLifecycle.java persistence/impl/src/main/java/org/jboss/seam/persistence/ManagedPersistenceContextExtension.java (Affects Seam persistence 3.0.0.CR4) -- This message is automatically generated by JIRA. For more information on JIRA, see: http://www.atlassian.com/software/jira

15 years

3
4
0 / 0

[JBoss JIRA] Created: (SOLDER-91) @Requires does not work in Glassfish

by Shane Bryzak (JIRA)

@Requires does not work in Glassfish ------------------------------------ Key: SOLDER-91 URL: https://issues.jboss.org/browse/SOLDER-91 Project: Seam Solder Issue Type: Bug Components: Core Affects Versions: 3.0.0.CR4 Reporter: Shane Bryzak For example, deploying an application that contains seam-international.jar will fail if the Joda time library isn't bundled also, even though the package-info.java is annotated with: @Requires({ "org.joda.time.DateTimeZone" }) Annotating the individual classes within the package with the same annotation seems to make no difference either. [#|2011-03-23T19:20:41.986+1000|SEVERE|glassfish3.1|javax.enterprise.system.tools.admin.org.glassfish.deployment.admin|_ThreadID=100;_ThreadName=Thread-1;|org/joda/time/DateTimeZone java.lang.ClassNotFoundException: org.joda.time.DateTimeZone at org.glassfish.web.loader.WebappClassLoader.loadClass(WebappClassLoader.java:1518) at org.glassfish.web.loader.WebappClassLoader.loadClass(WebappClassLoader.java:1368) 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:925) at org.glassfish.web.loader.WebappClassLoader.loadClass(WebappClassLoader.java:1485) at org.glassfish.web.loader.WebappClassLoader.loadClass(WebappClassLoader.java:1368) at org.glassfish.weld.BeanDeploymentArchiveImpl.handleEntry(BeanDeploymentArchiveImpl.java:451) at org.glassfish.weld.BeanDeploymentArchiveImpl.collectJarInfo(BeanDeploymentArchiveImpl.java:442) at org.glassfish.weld.BeanDeploymentArchiveImpl.populate(BeanDeploymentArchiveImpl.java:394) at org.glassfish.weld.BeanDeploymentArchiveImpl.<init>(BeanDeploymentArchiveImpl.java:147) at org.glassfish.weld.BeanDeploymentArchiveImpl.populate(BeanDeploymentArchiveImpl.java:371) at org.glassfish.weld.BeanDeploymentArchiveImpl.<init>(BeanDeploymentArchiveImpl.java:147) at org.glassfish.weld.BeanDeploymentArchiveImpl.<init>(BeanDeploymentArchiveImpl.java:123) at org.glassfish.weld.DeploymentImpl.<init>(DeploymentImpl.java:119) at org.glassfish.weld.WeldDeployer.load(WeldDeployer.java:333) at org.glassfish.weld.WeldDeployer.load(WeldDeployer.java:99) at org.glassfish.internal.data.ModuleInfo.load(ModuleInfo.java:186) at org.glassfish.internal.data.ApplicationInfo.load(ApplicationInfo.java:249) at com.sun.enterprise.v3.server.ApplicationLifecycle.deploy(ApplicationLifecycle.java:460) at com.sun.enterprise.v3.server.ApplicationLifecycle.deploy(ApplicationLifecycle.java:240) at org.glassfish.deployment.admin.DeployCommand.execute(DeployCommand.java:370) at com.sun.enterprise.v3.admin.CommandRunnerImpl$1.execute(CommandRunnerImpl.java:354) at com.sun.enterprise.v3.admin.CommandRunnerImpl.doCommand(CommandRunnerImpl.java:369) at com.sun.enterprise.v3.admin.CommandRunnerImpl.doCommand(CommandRunnerImpl.java:1080) at com.sun.enterprise.v3.admin.CommandRunnerImpl.access$1200(CommandRunnerImpl.java:95) at com.sun.enterprise.v3.admin.CommandRunnerImpl$ExecutionContext.execute(CommandRunnerImpl.java:1260) at com.sun.enterprise.v3.admin.CommandRunnerImpl$ExecutionContext.execute(CommandRunnerImpl.java:1248) at org.glassfish.admingui.common.util.LocalDeploymentFacility$LocalDFCommandRunner.run(LocalDeploymentFacility.java:143) at org.glassfish.deployment.client.AbstractDeploymentFacility.deploy(AbstractDeploymentFacility.java:406) at org.glassfish.admingui.common.util.DeployUtil.invokeDeploymentFacility(DeployUtil.java:100) at org.glassfish.admingui.common.util.DeployUtil.deploy(DeployUtil.java:76) at org.glassfish.admingui.common.handlers.DeploymentHandler.deploy(DeploymentHandler.java:191) 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.jsftemplating.layout.descriptors.handler.Handler.invoke(Handler.java:442) at com.sun.jsftemplating.layout.descriptors.LayoutElementBase.dispatchHandlers(LayoutElementBase.java:420) at com.sun.jsftemplating.layout.descriptors.LayoutElementBase.dispatchHandlers(LayoutElementBase.java:394) at com.sun.jsftemplating.layout.event.CommandActionListener.invokeCommandHandlers(CommandActionListener.java:150) at com.sun.jsftemplating.layout.event.CommandActionListener.processAction(CommandActionListener.java:98) at javax.faces.event.ActionEvent.processListener(ActionEvent.java:88) at javax.faces.component.UIComponentBase.broadcast(UIComponentBase.java:769) at javax.faces.component.UICommand.broadcast(UICommand.java:300) at com.sun.webui.jsf.component.WebuiCommand.broadcast(WebuiCommand.java:166) 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:395) at org.apache.catalina.core.StandardWrapper.service(StandardWrapper.java:1534) at org.apache.catalina.core.ApplicationFilterChain.internalDoFilter(ApplicationFilterChain.java:343) at org.apache.catalina.core.ApplicationFilterChain.doFilter(ApplicationFilterChain.java:215) at com.sun.webui.jsf.util.UploadFilter.doFilter(UploadFilter.java:223) at org.apache.catalina.core.ApplicationFilterChain.internalDoFilter(ApplicationFilterChain.java:256) at org.apache.catalina.core.ApplicationFilterChain.doFilter(ApplicationFilterChain.java:215) at org.apache.catalina.core.StandardWrapperValve.invoke(StandardWrapperValve.java:279) 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.doChainInvoke(StandardPipeline.java:600) at com.sun.enterprise.web.WebPipeline.invoke(WebPipeline.java:96) 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:228) at com.sun.grizzly.http.ProcessorTask.invokeAdapter(ProcessorTask.java:818) at com.sun.grizzly.http.ProcessorTask.doProcess(ProcessorTask.java:719) at com.sun.grizzly.http.ProcessorTask.process(ProcessorTask.java:1008) 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:619) |#] -- This message is automatically generated by JIRA. For more information on JIRA, see: http://www.atlassian.com/software/jira

15 years

2
2
0 / 0

[JBoss JIRA] Created: (SEAMFACES-116) Dynamic Resource creation

by Emanuel Zimmermann (JIRA)

Dynamic Resource creation ------------------------- Key: SEAMFACES-116 URL: https://issues.jboss.org/browse/SEAMFACES-116 Project: Seam Faces Issue Type: Feature Request Reporter: Emanuel Zimmermann Priority: Trivial May be this is nonsense, but I was thinking it would be nice to have a feature to create resources programatically that would be mapped to files under the Resource folder. So if, for instance, a user uploads a picture of himself you can create a resource with it, then may be output it by doing: <h:graphicImage name="Matt" library="users/uploads" /> Instead of using a custom servlet or components that simulate this behavior. This would change the use of resources so far and perhaps it can't be implemented. -- This message is automatically generated by JIRA. For more information on JIRA, see: http://www.atlassian.com/software/jira

15 years

1
1
0 / 0

[JBoss JIRA] Created: (SEAM-53) Create infrastructure for Seam Reporting module

by Dan Allen (JIRA)

Create infrastructure for Seam Reporting module ----------------------------------------------- Key: SEAM-53 URL: https://issues.jboss.org/browse/SEAM-53 Project: Seam 3 Distribution Issue Type: Task Components: Build Infrastructure Reporter: Dan Allen Setup the module infrastructure for the Seam reporting module. Create a submodule for spreadsheets by importing code from here: http://anonsvn.jboss.org/repos/seam/sandbox/modules/spreadsheet/ module name: Seam Reporting group id: org.jboss.seam.reporting artifact ids: seam-reporting-core-api, seam-reporting-core-impl submodule name: Seam Reporting Spreadsheets group id: org.jboss.seam.reporting artifact ids: seam-reporting-spreadsheets-api, seam-reporting-spreadsheets-impl Likely the PDF generation will live in this module as well. -- This message is automatically generated by JIRA. For more information on JIRA, see: http://www.atlassian.com/software/jira

15 years

1
0
0 / 0

[JBoss JIRA] Created: (SEAM-52) seam-solder-tooling missing in the distribution

by Jozef Hartinger (JIRA)

seam-solder-tooling missing in the distribution ----------------------------------------------- Key: SEAM-52 URL: https://issues.jboss.org/browse/SEAM-52 Project: Seam 3 Distribution Issue Type: Bug Components: Common Dependencies Affects Versions: 3.0.0.CR3 Reporter: Jozef Hartinger Priority: Critical Fix For: 3.0.0.Final The solder tooling module is mentioned in the docs[1], however, it is missing from the Seam distribution. [1] http://docs.jboss.org/seam//3/3.0.0.CR3/reference/en-US/html/solder-loggi... -- This message is automatically generated by JIRA. For more information on JIRA, see: http://www.atlassian.com/software/jira

15 years

2
2
0 / 0

[JBoss JIRA] Created: (SOLDER-47) Cannot use Solder in Glassfish 3.1

by Jason Porter (JIRA)

Cannot use Solder in Glassfish 3.1 ---------------------------------- Key: SOLDER-47 URL: https://jira.jboss.org/browse/SOLDER-47 Project: Seam Solder Issue Type: Bug Reporter: Jason Porter Please see http://java.net/jira/browse/GLASSFISH-14808 for additional information I communicated to Siva. Siva has closed this bug saying it's not a bug because weld-extensions.jar doesn't have a beans.xml file, which isn't valid, it doesn't need one. You can see the exceptions I've been fighting trying to get my catch jaxrs example running in glassfish 3.1 -- This message is automatically generated by JIRA. - For more information on JIRA, see: http://www.atlassian.com/software/jira

15 years

6
16
0 / 0

[JBoss JIRA] Created: (SEAMFACES-106) Move @RenderScoped to org.jboss.seam.faces.context

by Dan Allen (JIRA)

Move @RenderScoped to org.jboss.seam.faces.context -------------------------------------------------- Key: SEAMFACES-106 URL: https://issues.jboss.org/browse/SEAMFACES-106 Project: Seam Faces Issue Type: Enhancement Components: CDI Integration Affects Versions: 3.0.0.CR1 Reporter: Dan Allen Priority: Minor @RenderScoped was original packaged in javax.faces.bean when it was based on the flash scope in JSF 2. However, now that it's done a different way, there is no more relation and it should be moved back to org.jboss.seam.faces.context. -- This message is automatically generated by JIRA. For more information on JIRA, see: http://www.atlassian.com/software/jira

15 years

2
2
0 / 0

[JBoss JIRA] Created: (SEAM-51) Migrate transaction code in Seam Persistence to new Seam Transaction module

by Dan Allen (JIRA)

Migrate transaction code in Seam Persistence to new Seam Transaction module --------------------------------------------------------------------------- Key: SEAM-51 URL: https://issues.jboss.org/browse/SEAM-51 Project: Seam 3 Distribution Issue Type: Feature Request Components: Build Infrastructure Affects Versions: 3.0.0.Final Reporter: Dan Allen Create a new module Seam Transaction. Move the transaction support code from Seam Persistence into Seam Transaction. name: Seam Transaction groupId: org.jboss.seam.transaction artifactIds: seam-transaction-api seam-transaction-impl repo: http://github.com/seam/transaction -- This message is automatically generated by JIRA. For more information on JIRA, see: http://www.atlassian.com/software/jira

15 years

1
0
0 / 0

[JBoss JIRA] Created: (SEAMJMS-2) Message Destinations may be declared by specifying a @Resource annotation as part of a producer field

by Jordan Ganoff (JIRA)

Message Destinations may be declared by specifying a @Resource annotation as part of a producer field ----------------------------------------------------------------------------------------------------- Key: SEAMJMS-2 URL: https://jira.jboss.org/browse/SEAMJMS-2 Project: Seam JMS Issue Type: Feature Request Components: Injection Reporter: Jordan Ganoff Priority: Blocker >From JSR-299-20090521.pdf: 3.7.2. Declaring a message destination A message destination may be declared by specifying a type Topic or Queue. @Resource annotation as part of a producer field declaration of The @Resource annotation specifies the metadata needed to obtain the topic or queue from the component environment. @Resource(name="java:global/env/jms/PaymentQueue") @Produces @PaymentProcessor Queue paymentQueue; @Resource(name="java:global/env/jms/Prices") @Produces @Prices Topic pricesTopic; The bindings and deployment type of the resource are determined by the producer field declaration. -- 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
6
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 March 2011