January 2011 - seam-issues - Jboss List Archives

[JBoss JIRA] Created: (SEAMFORGE-23) Forge needs a de-centralized plugin distribution and repository system

by Lincoln Baxter III (JIRA)

Forge needs a de-centralized plugin distribution and repository system ---------------------------------------------------------------------- Key: SEAMFORGE-23 URL: https://issues.jboss.org/browse/SEAMFORGE-23 Project: Seam Forge Issue Type: Feature Request Components: Brainstorming, Plugin API Affects Versions: 1.0.0.Alpha1 Environment: All Reporter: Lincoln Baxter III Priority: Critical There is no disputing the value of this type of feature, as has been shown with App-stores of all kinds. This would be relatively simple to implement as a Maven-based system, delegating all of the artifact resolution and dependency management to Maven. Features Forge would need to provide: 1) Built-in plugins and native APIs to search/install/remove/update plug-ins (easy using forge Resource APIs + Aether to add/remove JARs.) This internal plugin/commands could be called "forge" for simplicity ------------------------------------------------------------------------------------------ $ forge plugin-find prettyfaces Forge found the following plugins in specified repositories: <--- notice the 'forgeplugin' classifier used to identify forge plugins from other artifacts. * http://ocpsoft.com/repository ...... [prettyfaces] com.ocpsoft.pretty.faces:prettyfaces-forgeplugin:[... 3.1.0, 3.2.0, 3.2.1] * http://repo1.maven.org/ .............. [prettyfaces] com.ocpsoft.pretty.faces:prettyfaces-forgeplugin:3.1.0 $ forge plugin-install prettyfaces --version 3.1.0 ***SUCCESS*** [prettyfaces] plugin was successfully installed. You will need to restart forge to see these changes. $ forge plugin-list Listing installed plugins: * prettyfaces [3.1.0] * forge-scaffold [1.0.0.Alpha1] * forge-javaee6 [1.0.0.Alpha1] * home-control [1.0.0.Alpha1] $ forge plugin-remove prettyfaces Are you sure you you want to remove the plugin(s) [prettyfaces] [Y,n]? Y ***SUCCESS*** [prettyfaces] plugin was successfully removed. You will need to restart forge to see these changes. ------------------------------------------------------------------------------------------ 2) Plugin repository management (add/remove/edit/list current plugin repository targets.) ------------------------------------------------------------------------------------------ $ forge repo-list Currently using the following plugin repositories: * 1. https://repository.jboss.org/nexus/content/groups/public/ * 2. http://ocpsoft.com/repository * 3. http://example.com/forge/plugin-repository $ forge repo-add http://jboss.org/forge/repository/ <-- These two will be KEY, we NEED THESE to happen $ forge repo-add http://javaee.org/forge/repository/ $ forge repo-list Currently using the following plugin repositories: * 1. https://repository.jboss.org/nexus/content/groups/public/ * 2. http://ocpsoft.com/repository * 3. http://example.com/forge/plugin-repository * 4. http://jboss.org/forge/repository/ * 5. http://javaee.org/forge/repository/ $ forge repo-del 5 ***SUCCESS*** removed repository [http://javaee.org/forge/repository/]. Plugins installed from this repository will no longer be auto-updated, and can be removed using [forge plugin-remove {plugin-id}] ------------------------------------------------------------------------------------------ 3) Auto-update functionality Periodically search for updates to existing plugins (or search on request) - ask users if they would like to see a list of updates or perform an automated update / update individual plugins. 4) A meta-data system of identifying compatible versions of plugins w/running version of forge. Possibly need to create a maven packaging type and build plugin in order to facilitate this type of additional metadata and artifact resolution. (Or could require a <classifier>forgeplugin</classifier>. We already have the maven GAV (GroupId : ArtifactId : Version) information. Supplemented with this classifier, we could easily identify forge plugins from other artifacts in maven. -- This message is automatically generated by JIRA. - For more information on JIRA, see: http://www.atlassian.com/software/jira

13 years, 5 months

4
4
0 / 0

[JBoss JIRA] Created: (JBSEAM-4643) Add built-in primefaces option to seam-gen

by sertac anadollu (JIRA)

Add built-in primefaces option to seam-gen ------------------------------------------ Key: JBSEAM-4643 URL: https://jira.jboss.org/jira/browse/JBSEAM-4643 Project: Seam Issue Type: Feature Request Components: JSF Integration Affects Versions: 2.2.1.CR2 Reporter: sertac anadollu Fix For: 2.2.1.CR2 Primefaces is the one of most popular open source jsf component libraries and day by day it is widely used in seam based projects. Some advantages of this library are its simplicity, natural compatibility with other libraries, high performance, having interesting components, simple setup, good documentation, development team behind it and licensed under Apache License V2. I used it many seam based projects and I am very happy for being with it. It is very nice to see primefaces option in the seam-gen setup. -- 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

13 years, 5 months

3
2
0 / 0

[JBoss JIRA] Created: (JBSEAM-4763) Got javax.naming.NoInitialContextException if no jndi.properties while deploying seam to jetty

by Yang Yong (JIRA)

Got javax.naming.NoInitialContextException if no jndi.properties while deploying seam to jetty ---------------------------------------------------------------------------------------------- Key: JBSEAM-4763 URL: https://issues.jboss.org/browse/JBSEAM-4763 Project: Seam Issue Type: Bug Affects Versions: 2.2.1.CR3 Reporter: Yang Yong Note: the actual affect version is 2.2.2.EAP5 distributed with EAP5.1, but the Affects Version doesn't have this version in select list. When I was trying to deploy EAP5.1 admin-console.war to jetty, I got below exception if with jndi disabled(no jndi.properties), if I manually add jndi.properties to WAR/WEB-INF/classes and eanble jndi in jetty, the exception was gone . I think the problem is the method Transaction.getUserTransaction doesn't handle the javax.naming.NoInitialContextException. And the confusion is although transaction manager was disabled by: <component name="org.jboss.seam.core.init"> <property name="debug">false</property>  <property name="transactionManagementEnabled">false</property> </component> Seam still try to create a transaction manager by lookup jndi, this will cause Seam can not be deployed in a pure web server which doesn't provide a jndi server or jndi.properties.. FYI: 7417 [qtp19764978-35] ERROR org.jboss.seam.contexts.Contexts - could not discover transaction status 7420 [qtp19764978-35] WARN org.jboss.seam.contexts.Contexts - Exception destroying context java.lang.RuntimeException: exception invoking: getTransaction at org.jboss.seam.util.Reflections.invokeAndWrap(Reflections.java:154) at org.jboss.seam.Component.callComponentMethod(Component.java:2275) at org.jboss.seam.Component.unwrap(Component.java:2301) at org.jboss.seam.Component.getInstance(Component.java:2044) at org.jboss.seam.Component.getInstance(Component.java:2003) at org.jboss.seam.Component.getInstance(Component.java:1997) at org.jboss.seam.Component.getInstance(Component.java:1970) at org.jboss.seam.Component.getInstance(Component.java:1965) at org.jboss.seam.transaction.Transaction.instance(Transaction.java:39) at org.jboss.seam.util.Work.workInTransaction(Work.java:38) at org.jboss.seam.contexts.Contexts.flushAndDestroyContexts(Contexts.java:350) at org.jboss.seam.contexts.FacesLifecycle.endRequest(FacesLifecycle.java:129) at org.jboss.seam.jsf.SeamPhaseListener.afterRenderResponse(SeamPhaseListener.java:514) at org.jboss.seam.jsf.SeamPhaseListener.afterServletPhase(SeamPhaseListener.java:249) at org.jboss.seam.jsf.SeamPhaseListener.afterPhase(SeamPhaseListener.java:196) at com.sun.faces.lifecycle.Phase.handleAfterPhase(Phase.java:175) at com.sun.faces.lifecycle.Phase.doPhase(Phase.java:114) at com.sun.faces.lifecycle.LifecycleImpl.render(LifecycleImpl.java:139) at javax.faces.webapp.FacesServlet.service(FacesServlet.java:266) at org.eclipse.jetty.servlet.ServletHolder.handle(ServletHolder.java:534) at org.eclipse.jetty.servlet.ServletHandler$CachedChain.doFilter(ServletHandler.java:1351) at org.jboss.seam.servlet.SeamFilter$FilterChainImpl.doFilter(SeamFilter.java:83) at org.jboss.seam.web.IdentityFilter.doFilter(IdentityFilter.java:40) at org.jboss.seam.servlet.SeamFilter$FilterChainImpl.doFilter(SeamFilter.java:69) at org.jboss.seam.web.MultipartFilter.doFilter(MultipartFilter.java:90) at org.jboss.seam.servlet.SeamFilter$FilterChainImpl.doFilter(SeamFilter.java:69) at org.jboss.seam.web.ExceptionFilter.doFilter(ExceptionFilter.java:64) at org.jboss.seam.servlet.SeamFilter$FilterChainImpl.doFilter(SeamFilter.java:69) at org.jboss.seam.web.RedirectFilter.doFilter(RedirectFilter.java:45) at org.jboss.seam.servlet.SeamFilter$FilterChainImpl.doFilter(SeamFilter.java:69) at org.ajax4jsf.webapp.BaseXMLFilter.doXmlFilter(BaseXMLFilter.java:178) at org.ajax4jsf.webapp.BaseFilter.handleRequest(BaseFilter.java:295) at org.ajax4jsf.webapp.BaseFilter.processUploadsAndHandleRequest(BaseFilter.java:373) at org.ajax4jsf.webapp.BaseFilter.doFilter(BaseFilter.java:500) at org.jboss.seam.web.Ajax4jsfFilter.doFilter(Ajax4jsfFilter.java:56) at org.jboss.seam.servlet.SeamFilter$FilterChainImpl.doFilter(SeamFilter.java:69) at org.jboss.seam.web.LoggingFilter.doFilter(LoggingFilter.java:60) at org.jboss.seam.servlet.SeamFilter$FilterChainImpl.doFilter(SeamFilter.java:69) at org.jboss.seam.servlet.SeamFilter.doFilter(SeamFilter.java:158) at org.jboss.on.embedded.LazyStartupFilter.doFilter(LazyStartupFilter.java:87) at org.eclipse.jetty.servlet.ServletHandler$CachedChain.doFilter(ServletHandler.java:1322) at org.eclipse.jetty.servlet.ServletHandler.doHandle(ServletHandler.java:473) at org.eclipse.jetty.server.handler.ScopedHandler.handle(ScopedHandler.java:119) at org.eclipse.jetty.security.SecurityHandler.handle(SecurityHandler.java:479) at org.eclipse.jetty.server.session.SessionHandler.doHandle(SessionHandler.java:226) at org.eclipse.jetty.server.handler.ContextHandler.doHandle(ContextHandler.java:929) at org.eclipse.jetty.servlet.ServletHandler.doScope(ServletHandler.java:403) at org.eclipse.jetty.server.session.SessionHandler.doScope(SessionHandler.java:184) at org.eclipse.jetty.server.handler.ContextHandler.doScope(ContextHandler.java:864) at org.eclipse.jetty.server.handler.ScopedHandler.handle(ScopedHandler.java:117) at org.eclipse.jetty.server.handler.ContextHandlerCollection.handle(ContextHandlerCollection.java:247) at org.eclipse.jetty.server.handler.HandlerCollection.handle(HandlerCollection.java:151) at org.eclipse.jetty.server.handler.HandlerWrapper.handle(HandlerWrapper.java:114) at org.eclipse.jetty.server.Server.handle(Server.java:352) at org.eclipse.jetty.server.HttpConnection.handleRequest(HttpConnection.java:596) at org.eclipse.jetty.server.HttpConnection$RequestHandler.headerComplete(HttpConnection.java:1051) at org.eclipse.jetty.http.HttpParser.parseNext(HttpParser.java:590) at org.eclipse.jetty.http.HttpParser.parseAvailable(HttpParser.java:212) at org.eclipse.jetty.server.HttpConnection.handle(HttpConnection.java:426) at org.eclipse.jetty.io.nio.SelectChannelEndPoint.handle(SelectChannelEndPoint.java:508) at org.eclipse.jetty.io.nio.SelectChannelEndPoint.access$000(SelectChannelEndPoint.java:34) at org.eclipse.jetty.io.nio.SelectChannelEndPoint$1.run(SelectChannelEndPoint.java:40) at org.eclipse.jetty.util.thread.QueuedThreadPool$2.run(QueuedThreadPool.java:451) at java.lang.Thread.run(Thread.java:619) Caused by: javax.naming.NoInitialContextException: Need to specify class name in environment or system property, or as an applet parameter, or in an application resource file: java.naming.factory.initial at javax.naming.spi.NamingManager.getInitialContext(NamingManager.java:645) at javax.naming.InitialContext.getDefaultInitCtx(InitialContext.java:288) at javax.naming.InitialContext.getURLOrDefaultInitCtx(InitialContext.java:325) at javax.naming.InitialContext.lookup(InitialContext.java:392) at org.jboss.seam.transaction.Transaction.getUserTransaction(Transaction.java:82) at org.jboss.seam.transaction.Transaction.createUTTransaction(Transaction.java:74) at org.jboss.seam.transaction.Transaction.getTransaction(Transaction.java:47) 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 org.jboss.seam.util.Reflections.invoke(Reflections.java:22) at org.jboss.seam.util.Reflections.invokeAndWrap(Reflections.java:144) ... 63 more Source code URL: http://viewvc.jboss.org/cgi-bin/viewvc.cgi/seam/tags/JBPAPP_5_1_0/src/mai... -- This message is automatically generated by JIRA. - For more information on JIRA, see: http://www.atlassian.com/software/jira

13 years, 5 months

2
1
0 / 0

[JBoss JIRA] Assigned: (SEAMMAIL-11) root pom.xml is not correct regarding distribution profile

by Martin Gencur (JIRA)

[ https://issues.jboss.org/browse/SEAMMAIL-11?page=com.atlassian.jira.plugi... ] Martin Gencur reassigned SEAMMAIL-11: ------------------------------------- Assignee: Cody Lerum > root pom.xml is not correct regarding distribution profile > ---------------------------------------------------------- > > Key: SEAMMAIL-11 > URL: https://issues.jboss.org/browse/SEAMMAIL-11 > Project: Seam Mail > Issue Type: Bug > Reporter: Martin Gencur > Assignee: Cody Lerum > Fix For: 3.0.0.Beta1 > > > The root pom.xml should contain corrent submodule definition in "distribution" profile. There is a <module>examples/sendmail</module> but should be <module>examples/seam-mail-examples-sendmail</module> instead. Thus, the distribution build is failing. -- This message is automatically generated by JIRA. - For more information on JIRA, see: http://www.atlassian.com/software/jira

13 years, 5 months

1
0
0 / 0

[JBoss JIRA] Created: (SEAMMAIL-10) Support Multiple From Addresses

by Cody Lerum (JIRA)

Support Multiple From Addresses ------------------------------- Key: SEAMMAIL-10 URL: https://issues.jboss.org/browse/SEAMMAIL-10 Project: Seam Mail Issue Type: Enhancement Reporter: Cody Lerum Assignee: Cody Lerum Priority: Minor API should support setting multiple FROM addresses -- This message is automatically generated by JIRA. - For more information on JIRA, see: http://www.atlassian.com/software/jira

13 years, 5 months

1
3
0 / 0

[JBoss JIRA] Created: (SEAMMAIL-1) Handle errors from sending mail

by Pete Muir (JIRA)

Handle errors from sending mail ------------------------------- Key: SEAMMAIL-1 URL: https://jira.jboss.org/browse/SEAMMAIL-1 Project: Seam Mail Issue Type: Feature Request Reporter: Pete Muir > Another thing the current implementation does is render and send at the same > time. This is a bad idea as well. You'd generally want to save the rendered? > email, and retry on send errors. Email has two types of errors, those that the MTA will automatically retry for, and those that cause bounces. If you are referring to bounces, how do you process the bounces? -- 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

13 years, 5 months

3
10
0 / 0

[JBoss JIRA] Created: (SEAMMAIL-5) Save rendered Mail message to JPA

by Pete Muir (JIRA)

Save rendered Mail message to JPA --------------------------------- Key: SEAMMAIL-5 URL: https://jira.jboss.org/browse/SEAMMAIL-5 Project: Seam Mail Issue Type: Feature Request Reporter: Pete Muir -- 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

13 years, 5 months

2
6
0 / 0

[JBoss JIRA] Created: (SEAMMAIL-7) Consider how users can edit mail templates

by Pete Muir (JIRA)

Consider how users can edit mail templates ------------------------------------------ Key: SEAMMAIL-7 URL: https://jira.jboss.org/browse/SEAMMAIL-7 Project: Seam Mail Issue Type: Feature Request Reporter: Pete Muir Apparently XML templates are too complex. -- 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

13 years, 5 months

2
2
0 / 0

[JBoss JIRA] Created: (SEAMMAIL-8) Seam Mail should be able to monitor and receive/process inbound mail messages

by Lincoln Baxter III (JIRA)

Seam Mail should be able to monitor and receive/process inbound mail messages ----------------------------------------------------------------------------- Key: SEAMMAIL-8 URL: https://issues.jboss.org/browse/SEAMMAIL-8 Project: Seam Mail Issue Type: Feature Request Reporter: Lincoln Baxter III To facilitate use-cases where email is used to control application behavior. This could be as simple as polling an email account and firing CDI or subsequent JMS events. The message body, header, and attachments should be made available in the event. -- This message is automatically generated by JIRA. - For more information on JIRA, see: http://www.atlassian.com/software/jira

13 years, 5 months

2
3
0 / 0

[JBoss JIRA] Created: (SEAM-17) Switch to JBoss code style to modules

by Dan Allen (JIRA)

Switch to JBoss code style to modules ------------------------------------- Key: SEAM-17 URL: https://issues.jboss.org/browse/SEAM-17 Project: Seam 3 Issue Type: Task Components: Release tasks Reporter: Dan Allen For reasons people can no longer even remember, Seam uses a very non-conventional code style. This complicates patches, impacts documentation and generally swims upstream against Java conventions. By adopting the JBoss code style (specifically the code style used in AS 7 [1], one of the newest projects at JBoss), it simplifies things on the one hand while providing the appearance of JBoss projects working together on the other. This change would be made in the process of preparing a candidate release of the Seam stack. We'll also need to update the reference guides. The JBoss convention closely parallels the Java convention with a few exceptions. We believe that these exceptions are corrections to poor choices in the Java convention, so we could call it the Java convention 2.0. Those differences are as follows: AS 7 vs Java convention 1. Spaces vs mixed tabs and spaces (a strange default) 2. Single block indent for continued lines vs double block indent for continued lines 3. 128 line width vs 80 4. indent switch statements vs don't indent switch statements 5. indent size 4 vs indent size 8 6. minor javadoc differences [1] https://github.com/jbossas/jboss-as/raw/master/ide-configs/eclipse/as7for... -- This message is automatically generated by JIRA. - For more information on JIRA, see: http://www.atlassian.com/software/jira

13 years, 5 months

1
0
0 / 0

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

2009

2008

2007

2006

seam-issues January 2011