[jira] [Reopened] (DELTASPIKE-595) broken assembly config
[ https://issues.apache.org/jira/browse/DELTASPIKE-595?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Gerhard Petracek reopened DELTASPIKE-595: - now the version of the apache-rat-plugin is 0.8-SNAPSHOT instead of 0.8 broken assembly config -- Key: DELTASPIKE-595 URL: https://issues.apache.org/jira/browse/DELTASPIKE-595 Project: DeltaSpike Issue Type: Bug Components: Build Affects Versions: 0.7 Reporter: Gerhard Petracek Assignee: John D. Ament Fix For: 0.8 #1 the artifacts don't get uploaded to the staging repository - they aren't part of the vote #2 the config looks questionable (e.g. the test-control module is excluded) -- This message was sent by Atlassian JIRA (v6.2#6252)
[jira] [Updated] (DELTASPIKE-404) BeanManagerProvider leaks in case of undeploy/redeploy
[ https://issues.apache.org/jira/browse/DELTASPIKE-404?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Gerhard Petracek updated DELTASPIKE-404: Assignee: Mark Struberg (was: Gerhard Petracek) BeanManagerProvider leaks in case of undeploy/redeploy -- Key: DELTASPIKE-404 URL: https://issues.apache.org/jira/browse/DELTASPIKE-404 Project: DeltaSpike Issue Type: Bug Reporter: Romain Manni-Bucau Assignee: Mark Struberg Attachments: patch.diff -- This message was sent by Atlassian JIRA (v6.2#6252)
[jira] [Updated] (DELTASPIKE-549) Add programmatic job scheduling
[ https://issues.apache.org/jira/browse/DELTASPIKE-549?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Gerhard Petracek updated DELTASPIKE-549: Attachment: DELTASPIKE-549_2.patch Add programmatic job scheduling --- Key: DELTASPIKE-549 URL: https://issues.apache.org/jira/browse/DELTASPIKE-549 Project: DeltaSpike Issue Type: Improvement Components: Scheduler Affects Versions: 0.7 Reporter: Piotr Dudkiewicz Assignee: Gerhard Petracek Priority: Minor Attachments: DELTASPIKE-549.patch, DELTASPIKE-549_2.patch Currently the only way to pass job configuration is by using Scheduled annotation. It would be nice to have another registerNewJob method taking job configuration as parameter, for example void registerNewJob(Class? extends T jobClass, JobConfiguration configuration); -- This message was sent by Atlassian JIRA (v6.2#6252)
[jira] [Commented] (DELTASPIKE-613) Avoid windowhandler.html in GET requests from links
[ https://issues.apache.org/jira/browse/DELTASPIKE-613?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=14009493#comment-14009493 ] Thomas Andraschko commented on DELTASPIKE-613: -- AFAICS it's a mix between LAZY and CLIENTWINDOW. I have an similiar idea and already created a ticket: https://issues.apache.org/jira/browse/DELTASPIKE-570 The idea is to NOT render the dswid on the link but overwrite the onclick to lazy add the windowId and add a cookie. So on a GET request, the server will check if a windowId and the cookie exists - otherwise stream windowhandler.html. Therefore if you do a open in new tab - no windowId in the url, windowhandler will be streamed. The streaming of the windowhandler is reduced to a minimum. Avoid windowhandler.html in GET requests from links --- Key: DELTASPIKE-613 URL: https://issues.apache.org/jira/browse/DELTASPIKE-613 Project: DeltaSpike Issue Type: Improvement Components: JSF-Module Affects Versions: 0.7 Reporter: Janario Assignee: Mark Struberg Attachments: dsrid_in_url.patch Some generated url could already detect the windowId and send with the first get avoiding windowhandler.html. In the actual model basically this are the steps from a click in a link: - Click in link (GET) to new page Response windowhandler.html - windowhandler.html detect windowId by window.name and get page again adding dsrid and windowId in cookie So I suggest the detection of windowhandler.html be done before the first get avoing one more request. To this every urls should have a dsrid(could be equals as windowId) and the storeWindowTree function should also add the cookie, same as in windowhandler.html Clicking in a link the cookie will be generated and in server side read identifying the windowId To explain better I attatched a patch with some changes. Could anyone try this? -- This message was sent by Atlassian JIRA (v6.2#6252)
[jira] [Updated] (DELTASPIKE-614) @Named support for ExecutableCallbackDescriptor
[ https://issues.apache.org/jira/browse/DELTASPIKE-614?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Gerhard Petracek updated DELTASPIKE-614: Attachment: DELTASPIKE-614.patch @Named support for ExecutableCallbackDescriptor --- Key: DELTASPIKE-614 URL: https://issues.apache.org/jira/browse/DELTASPIKE-614 Project: DeltaSpike Issue Type: Improvement Components: Core Affects Versions: 0.7 Reporter: Gerhard Petracek Assignee: Gerhard Petracek Fix For: 0.8 Attachments: DELTASPIKE-614.patch -- This message was sent by Atlassian JIRA (v6.2#6252)
[jira] [Created] (DELTASPIKE-614) @Named support for ExecutableCallbackDescriptor
Gerhard Petracek created DELTASPIKE-614: --- Summary: @Named support for ExecutableCallbackDescriptor Key: DELTASPIKE-614 URL: https://issues.apache.org/jira/browse/DELTASPIKE-614 Project: DeltaSpike Issue Type: Improvement Components: Core Affects Versions: 0.7 Reporter: Gerhard Petracek Assignee: Gerhard Petracek Fix For: 0.8 Attachments: DELTASPIKE-614.patch -- This message was sent by Atlassian JIRA (v6.2#6252)
[jira] [Resolved] (DELTASPIKE-614) @Named support for ExecutableCallbackDescriptor
[ https://issues.apache.org/jira/browse/DELTASPIKE-614?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Gerhard Petracek resolved DELTASPIKE-614. - Resolution: Fixed @Named support for ExecutableCallbackDescriptor --- Key: DELTASPIKE-614 URL: https://issues.apache.org/jira/browse/DELTASPIKE-614 Project: DeltaSpike Issue Type: Improvement Components: Core Affects Versions: 0.7 Reporter: Gerhard Petracek Assignee: Gerhard Petracek Fix For: 0.8 -- This message was sent by Atlassian JIRA (v6.2#6252)
Re: Apache DeltaSpike Logo Revised Samples
Sorry for the confusion – I thought I’d included everybody when I shared the Dropbox link but I guess that email didn’t get completely through, either. -- James Parenti Visuale 1800 W. Cornelia Avenue Chicago, IL 60657 Office: 773.234.0178 Cell: 773.469.8843 Skype: jamesparenti Google: google.com/+JamesParentiVisuale http://www.visuale.net ja...@visuale.net On May 27, 2014, at 6:46 AM, Pete Muir pm...@redhat.com wrote: Jim’s email bounced. Here are the logos: https://www.dropbox.com/sh/6doraoq6ap3qyr3/AABXLSF-LyxEEL29jyHkyWCUa?n=289270217
[jira] [Created] (DELTASPIKE-615) create list of undocumented api classes
Gerhard Petracek created DELTASPIKE-615: --- Summary: create list of undocumented api classes Key: DELTASPIKE-615 URL: https://issues.apache.org/jira/browse/DELTASPIKE-615 Project: DeltaSpike Issue Type: Task Affects Versions: 0.7 Reporter: Gerhard Petracek Assignee: Rafael Benevides Fix For: 0.8 -- This message was sent by Atlassian JIRA (v6.2#6252)
[jira] [Assigned] (DELTASPIKE-370) ContainerCtrlTckTest - fix testShutdownWithInactiveContexts()
[ https://issues.apache.org/jira/browse/DELTASPIKE-370?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Rafael Benevides reassigned DELTASPIKE-370: --- Assignee: Rafael Benevides (was: Mark Struberg) ContainerCtrlTckTest - fix testShutdownWithInactiveContexts() - Key: DELTASPIKE-370 URL: https://issues.apache.org/jira/browse/DELTASPIKE-370 Project: DeltaSpike Issue Type: Bug Components: CdiControl Affects Versions: 0.3-incubating Reporter: Martin Kouba Assignee: Rafael Benevides Attachments: deltaspike-370.patch Line 175: cdiContainer.getContextControl().startContexts(); should be: cdiContainer.getContextControl().stopContexts(); Fixing this causes the testShutdownWithInactiveContexts() failure, due to https://issues.jboss.org/browse/WELD-1072 In fact testRestartContexts() should also fail but it doesn't by coincidence, the reasons: - WeldContainerControl.shutdown() does not stop contexts - Weld core does not invalidate other contexts than @ApplicationScoped during shutdown - Weld core uses some request scoped caching optimization WELD-1072 is going to be fixed in 1.1.13.Final and 2.0.1.Final. The test should be fixed. I'm going to address the other problem (WeldContainerControl.shutdown()) in a different issue. -- This message was sent by Atlassian JIRA (v6.2#6252)
[jira] [Assigned] (DELTASPIKE-371) Weld ContextController.stopApplicationScope() does not destroy application scoped beans properly
[ https://issues.apache.org/jira/browse/DELTASPIKE-371?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Rafael Benevides reassigned DELTASPIKE-371: --- Assignee: Rafael Benevides (was: Mark Struberg) Weld ContextController.stopApplicationScope() does not destroy application scoped beans properly Key: DELTASPIKE-371 URL: https://issues.apache.org/jira/browse/DELTASPIKE-371 Project: DeltaSpike Issue Type: Bug Components: CdiControl Affects Versions: 0.3-incubating Reporter: Martin Kouba Assignee: Rafael Benevides The current impl simply clears the application context's bean store which is not enough, e.g. @PreDestroy callback is not invoked. The impl should call org.jboss.weld.context.ApplicationContext.invalidate() as it originally did. It was probably changed in the context of WELD-1072... -- This message was sent by Atlassian JIRA (v6.2#6252)
[jira] [Resolved] (DELTASPIKE-371) Weld ContextController.stopApplicationScope() does not destroy application scoped beans properly
[ https://issues.apache.org/jira/browse/DELTASPIKE-371?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Rafael Benevides resolved DELTASPIKE-371. - Resolution: Fixed Weld ContextController.stopApplicationScope() does not destroy application scoped beans properly Key: DELTASPIKE-371 URL: https://issues.apache.org/jira/browse/DELTASPIKE-371 Project: DeltaSpike Issue Type: Bug Components: CdiControl Affects Versions: 0.3-incubating Reporter: Martin Kouba Assignee: Rafael Benevides The current impl simply clears the application context's bean store which is not enough, e.g. @PreDestroy callback is not invoked. The impl should call org.jboss.weld.context.ApplicationContext.invalidate() as it originally did. It was probably changed in the context of WELD-1072... -- This message was sent by Atlassian JIRA (v6.2#6252)
[jira] [Resolved] (DELTASPIKE-370) ContainerCtrlTckTest - fix testShutdownWithInactiveContexts()
[ https://issues.apache.org/jira/browse/DELTASPIKE-370?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Rafael Benevides resolved DELTASPIKE-370. - Resolution: Fixed ContainerCtrlTckTest - fix testShutdownWithInactiveContexts() - Key: DELTASPIKE-370 URL: https://issues.apache.org/jira/browse/DELTASPIKE-370 Project: DeltaSpike Issue Type: Bug Components: CdiControl Affects Versions: 0.3-incubating Reporter: Martin Kouba Assignee: Rafael Benevides Attachments: deltaspike-370.patch Line 175: cdiContainer.getContextControl().startContexts(); should be: cdiContainer.getContextControl().stopContexts(); Fixing this causes the testShutdownWithInactiveContexts() failure, due to https://issues.jboss.org/browse/WELD-1072 In fact testRestartContexts() should also fail but it doesn't by coincidence, the reasons: - WeldContainerControl.shutdown() does not stop contexts - Weld core does not invalidate other contexts than @ApplicationScoped during shutdown - Weld core uses some request scoped caching optimization WELD-1072 is going to be fixed in 1.1.13.Final and 2.0.1.Final. The test should be fixed. I'm going to address the other problem (WeldContainerControl.shutdown()) in a different issue. -- This message was sent by Atlassian JIRA (v6.2#6252)
[jira] [Resolved] (DELTASPIKE-372) WeldContainerControl should stop contexts during shutdown
[ https://issues.apache.org/jira/browse/DELTASPIKE-372?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Rafael Benevides resolved DELTASPIKE-372. - Resolution: Fixed WeldContainerControl should stop contexts during shutdown - Key: DELTASPIKE-372 URL: https://issues.apache.org/jira/browse/DELTASPIKE-372 Project: DeltaSpike Issue Type: Bug Components: CdiControl Affects Versions: 0.3-incubating Reporter: Martin Kouba Assignee: Rafael Benevides Fix For: 0.8 As described in DELTASPIKE-370 the Weld core does only invalidate application context during shutdown. Given that the other started contexts are not invalidated properly. -- This message was sent by Atlassian JIRA (v6.2#6252)
[jira] [Resolved] (DELTASPIKE-549) Add programmatic job scheduling
[ https://issues.apache.org/jira/browse/DELTASPIKE-549?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Gerhard Petracek resolved DELTASPIKE-549. - Resolution: Won't Fix for now Scheduler#unwrap is enough. we have to avoid that our api gets too large for 1-2 use-cases. jobs added manually can benefit from the same functionality - it shouldn't be a big issue to use #unwrap. Add programmatic job scheduling --- Key: DELTASPIKE-549 URL: https://issues.apache.org/jira/browse/DELTASPIKE-549 Project: DeltaSpike Issue Type: Improvement Components: Scheduler Affects Versions: 0.7 Reporter: Piotr Dudkiewicz Assignee: Gerhard Petracek Priority: Minor Attachments: DELTASPIKE-549.patch, DELTASPIKE-549_2.patch Currently the only way to pass job configuration is by using Scheduled annotation. It would be nice to have another registerNewJob method taking job configuration as parameter, for example void registerNewJob(Class? extends T jobClass, JobConfiguration configuration); -- This message was sent by Atlassian JIRA (v6.2#6252)
[jira] [Closed] (DELTASPIKE-549) Add programmatic job scheduling
[ https://issues.apache.org/jira/browse/DELTASPIKE-549?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Gerhard Petracek closed DELTASPIKE-549. --- Add programmatic job scheduling --- Key: DELTASPIKE-549 URL: https://issues.apache.org/jira/browse/DELTASPIKE-549 Project: DeltaSpike Issue Type: Improvement Components: Scheduler Affects Versions: 0.7 Reporter: Piotr Dudkiewicz Assignee: Gerhard Petracek Priority: Minor Attachments: DELTASPIKE-549.patch, DELTASPIKE-549_2.patch Currently the only way to pass job configuration is by using Scheduled annotation. It would be nice to have another registerNewJob method taking job configuration as parameter, for example void registerNewJob(Class? extends T jobClass, JobConfiguration configuration); -- This message was sent by Atlassian JIRA (v6.2#6252)
[jira] [Resolved] (DELTASPIKE-617) Utility Method for TypedQuery in AbstractEntityRepository
[ https://issues.apache.org/jira/browse/DELTASPIKE-617?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Thomas Hug resolved DELTASPIKE-617. --- Resolution: Fixed Utility Method for TypedQuery in AbstractEntityRepository - Key: DELTASPIKE-617 URL: https://issues.apache.org/jira/browse/DELTASPIKE-617 Project: DeltaSpike Issue Type: Improvement Components: Data-Module Reporter: Thomas Hug Assignee: Thomas Hug Fix For: 0.8 As there is also a criteriaQuery(). Should encourage users to rather use a TypedQuery than a JPA 1 Query, conflicting with the repository @Query. -- This message was sent by Atlassian JIRA (v6.2#6252)
[jira] [Resolved] (DELTASPIKE-597) Use correct names of brands and products in documentation
[ https://issues.apache.org/jira/browse/DELTASPIKE-597?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Rafael Benevides resolved DELTASPIKE-597. - Resolution: Fixed SVN r1597899 Use correct names of brands and products in documentation - Key: DELTASPIKE-597 URL: https://issues.apache.org/jira/browse/DELTASPIKE-597 Project: DeltaSpike Issue Type: Bug Components: Documentation Reporter: Ron Smeral Assignee: Rafael Benevides Priority: Trivial The front page at http://deltaspike.apache.org/ currently contains some wrong brand names (again in Docs/Introduction): * JBoss-AS7 should be JBoss AS7 (no dash) * JBoss WildFly8 should be just WildFly 8 (no longer branded JBoss, also add space) * Websphere is camel-cased - WebSphere * Weblogic is camel-cased - WebLogic If there are mentions of these anywhere else in the docs, they need to be made correct and consistent. -- This message was sent by Atlassian JIRA (v6.2#6252)
