Re: first steps for the next release

2015-07-14 Thread John D. Ament 
I don't see any issues, with a 1.4.2, but I think we might have some WF9
compatibility issues in the current code base.  I'm going to do some
additional testing to see what's the real issue.

If I find anything, we may need to consider a quick 1.4.3 release after
this.

- John

On Fri, Jul 10, 2015 at 4:49 AM Gerhard Petracek 
wrote:

> hi @ all,
>
> if there are no objections, i will start with the first steps for the next
> release (v1.4.2) by the end of next week.
>
> regards,
> gerhard
>

[jira] [Created] (DELTASPIKE-957) Improve how TransactionStrategies are looked up

2015-07-14 Thread John D. Ament (JIRA) 
John D. Ament created DELTASPIKE-957:


 Summary: Improve how TransactionStrategies are looked up
 Key: DELTASPIKE-957
 URL: https://issues.apache.org/jira/browse/DELTASPIKE-957
 Project: DeltaSpike
  Issue Type: New Feature
  Components: Data-Module, Documentation, JPA-Module
Affects Versions: 1.4.1
Reporter: John D. Ament


Currently transaction strategies are implemented as alternatives.  I created a 
WAR for WildFly 9, and ran into a lot of issues getting it to work.  My WAR has 
many JARs in it, all with beans.xml files.  I tried to enable the alternative 
in various spots, but no luck, even went through all 30 beans.xml files in my 
project and enabled it.  Still went with the default transaction strategy.

In order to fix, I had to enable a global alternative with the strategy.  This 
seems to go against our docs, which indicate it should be a regular 
alternative.  

I'd recommend a few things to think about.

- Expect a concrete producer.
- Use a class look up in apache-deltaspike.properties




--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

[jira] [Created] (DELTASPIKE-956) Clearly document transaction integration patterns for repository classes

2015-07-14 Thread John D. Ament (JIRA) 
John D. Ament created DELTASPIKE-956:


 Summary: Clearly document transaction integration patterns for 
repository classes
 Key: DELTASPIKE-956
 URL: https://issues.apache.org/jira/browse/DELTASPIKE-956
 Project: DeltaSpike
  Issue Type: New Feature
  Components: Data-Module, Documentation, JPA-Module
Affects Versions: 1.4.1
Reporter: John D. Ament


I was implementing Data on top of WildFly 9 today.  After about an hour of 
battling I got it to work end to end.  In my case I was using a REST API, but 
used these steps:

- Annotate the outermost layer with @javax.transactional.Transactional
- Set the transaction strategy to container managed (Separate JIRA ticket 
coming for this pain)

Only then did saves work properly for the repository interface.



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

[jira] [Created] (DELTASPIKE-955) Built in class deactivator

2015-07-14 Thread John D. Ament (JIRA) 
John D. Ament created DELTASPIKE-955:


 Summary: Built in class deactivator
 Key: DELTASPIKE-955
 URL: https://issues.apache.org/jira/browse/DELTASPIKE-955
 Project: DeltaSpike
  Issue Type: New Feature
  Components: Core
Affects Versions: 1.4.1
Reporter: John D. Ament


Add a built in ClassDeactivator that maybe reads from 
apache-deltaspike.properties

Today I was reimplementing DS for the data module.  One of the things I noticed 
was that there's no built in support for deactivation (via plain 
configuration).  If look at 
https://deltaspike.apache.org/documentation/spi.html#ClassDeactivator it seems 
like one of the key features missing is to add a property, e.g.

```
deactivate.fqcn=true
```

Which would deactivate that class.  Seems like a cool native deactivator that 
we could bundle in by default, but still activate via config.



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

[DOCUMENTATION] Incorrect Link?

2015-07-14 Thread MarvinToll 
On the following page:

https://deltaspike.apache.org/community.html#_mailing_lists 

The "User List" "Nabble" link appears to point to the DEV list rather than
the USER list.

Not sure if this is deliberate or not?



-
--
|  USA Cell: 248.866.4897
|  Email: mar...@gtcgroup.com
|  Web: http://MarvinToll.com
|  Skype: marvin.toll
--

--
View this message in context: 
http://apache-deltaspike-incubator-discussions.2316169.n4.nabble.com/DOCUMENTATION-Incorrect-Link-tp4661077.html
Sent from the Apache DeltaSpike Incubator Discussions mailing list archive at 
Nabble.com.

[jira] [Resolved] (DELTASPIKE-953) Refactor ClientWindow client side

2015-07-14 Thread Thomas Andraschko (JIRA) 

 [ 
https://issues.apache.org/jira/browse/DELTASPIKE-953?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Thomas Andraschko resolved DELTASPIKE-953.
--
Resolution: Fixed

> Refactor ClientWindow client side
> -
>
> Key: DELTASPIKE-953
> URL: https://issues.apache.org/jira/browse/DELTASPIKE-953
> Project: DeltaSpike
>  Issue Type: Improvement
>  Components: JSF-Module, JSF22-Module
>Affects Versions: 1.4.1
>Reporter: Thomas Andraschko
>Assignee: Thomas Andraschko
> Fix For: 1.4.2
>
>




--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

[jira] [Resolved] (DELTASPIKE-932) Refactor ClientWindow server side

2015-07-14 Thread Thomas Andraschko (JIRA) 

 [ 
https://issues.apache.org/jira/browse/DELTASPIKE-932?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Thomas Andraschko resolved DELTASPIKE-932.
--
Resolution: Fixed

> Refactor ClientWindow server side
> -
>
> Key: DELTASPIKE-932
> URL: https://issues.apache.org/jira/browse/DELTASPIKE-932
> Project: DeltaSpike
>  Issue Type: Improvement
>  Components: JSF-Module, JSF22-Module
>Affects Versions: 1.4.1
>Reporter: Thomas Andraschko
>Assignee: Thomas Andraschko
> Fix For: 1.4.2
>
>
> Split DefaultClientWindow to own implementations with a abstract basis
> currently DefaultClientWindow contains the logic for every mode and feels 
> very unstructured



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

[jira] [Resolved] (DELTASPIKE-954) CLIENTWINDOW windowhandler.html contains unreplaced variable

2015-07-14 Thread Thomas Andraschko (JIRA) 

 [ 
https://issues.apache.org/jira/browse/DELTASPIKE-954?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Thomas Andraschko resolved DELTASPIKE-954.
--
Resolution: Fixed

> CLIENTWINDOW windowhandler.html contains unreplaced variable
> 
>
> Key: DELTASPIKE-954
> URL: https://issues.apache.org/jira/browse/DELTASPIKE-954
> Project: DeltaSpike
>  Issue Type: Bug
>  Components: JSF-Module, JSF22-Module
>Affects Versions: 1.4.1
>Reporter: Thomas Andraschko
>Assignee: Thomas Andraschko
> Fix For: 1.4.2
>
>
> variable: $$bodyAttributes$$
> was not replaced in DS nor in CODI.



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

[jira] [Created] (DELTASPIKE-954) CLIENTWINDOW windowhandler.html contains unreplaced variable

2015-07-14 Thread Thomas Andraschko (JIRA) 
Thomas Andraschko created DELTASPIKE-954:


 Summary: CLIENTWINDOW windowhandler.html contains unreplaced 
variable
 Key: DELTASPIKE-954
 URL: https://issues.apache.org/jira/browse/DELTASPIKE-954
 Project: DeltaSpike
  Issue Type: Bug
  Components: JSF-Module, JSF22-Module
Affects Versions: 1.4.1
Reporter: Thomas Andraschko
Assignee: Thomas Andraschko
 Fix For: 1.4.2


variable: $$bodyAttributes$$

was not replaced in DS nor in CODI.



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

[jira] [Comment Edited] (DELTASPIKE-830) Now active ViewAccessScoped context during restore view phase

2015-07-14 Thread Thomas Andraschko (JIRA) 

[ 
https://issues.apache.org/jira/browse/DELTASPIKE-830?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14627025#comment-14627025
 ] 

Thomas Andraschko edited comment on DELTASPIKE-830 at 7/14/15 8:52 PM:
---

Should be fixed now in trunk. Would you please give it a try? (you need to 
place ds:windowId at the end of the body)


was (Author: tandraschko):
Should be fixed now in trunk. Would you please give it a try?

> Now active ViewAccessScoped context during restore view phase
> -
>
> Key: DELTASPIKE-830
> URL: https://issues.apache.org/jira/browse/DELTASPIKE-830
> Project: DeltaSpike
>  Issue Type: Bug
>  Components: JSF-Module
>Affects Versions: 1.2.1
> Environment: Glassfish 3.1.2.2 and Weblogic 12.1.2.2
>Reporter: Nuno G. de M
>Assignee: Thomas Andraschko
> Fix For: 1.4.2
>
>
> While testing delta-spike in clientview mode, coming from CODI, we have one 
> view that is giving problems trying to access ViewAccessScoped beans  during 
> the restored view phase.
> Caused by: org.jboss.weld.context.ContextNotActiveException: WELD-001303 No 
> active contexts for scope type 
> org.apache.deltaspike.core.api.scope.ViewAccessScoped
> Namely the exception we get in our page is the following:
> Caused By: org.jboss.weld.context.ContextNotActiveException: WELD-001303 No 
> active contexts for scope type 
> org.apache.deltaspike.core.api.scope.ViewAccessScoped
>   at 
> org.jboss.weld.manager.BeanManagerImpl.getContext(BeanManagerImpl.java:590)
>   at 
> org.jboss.weld.bean.proxy.ContextBeanInstance.getInstance(ContextBeanInstance.java:71)
>   at 
> org.jboss.weld.bean.proxy.ProxyMethodHandler.invoke(ProxyMethodHandler.java:79)
>   at 
> com.corp.whatever.component.ui.web.CR100Bean$Proxy$_$$_WeldClientProxy.getPageIds(CR100Bean$Proxy$_$$_WeldClientProxy.java)
>   at sun.reflect.GeneratedMethodAccessor1663.invoke(Unknown Source)
>   at 
> sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43)
>   at java.lang.reflect.Method.invoke(Method.java:606)
>   at javax.el.BeanELResolver.getValue(BeanELResolver.java:305)
>   at 
> com.sun.faces.el.DemuxCompositeELResolver._getValue(DemuxCompositeELResolver.java:176)
>   at 
> com.sun.faces.el.DemuxCompositeELResolver.getValue(DemuxCompositeELResolver.java:203)
>   at com.sun.el.parser.AstValue.getValue(AstValue.java:138)
>   at com.sun.el.parser.AstValue.getValue(AstValue.java:183)
>   at com.sun.el.ValueExpressionImpl.getValue(ValueExpressionImpl.java:224)
>   at 
> org.jboss.weld.el.WeldValueExpression.getValue(WeldValueExpression.java:50)
>   at 
> org.jboss.weld.el.WeldValueExpression.getValue(WeldValueExpression.java:50)
>   at 
> com.sun.faces.facelets.el.TagValueExpression.getValue(TagValueExpression.java:109)
>   at com.sun.el.parser.AstIdentifier.getValue(AstIdentifier.java:99)
>   at com.sun.el.ValueExpressionImpl.getValue(ValueExpressionImpl.java:224)
>   at 
> org.jboss.weld.el.WeldValueExpression.getValue(WeldValueExpression.java:50)
>   at 
> org.jboss.weld.el.WeldValueExpression.getValue(WeldValueExpression.java:50)
>   at 
> com.sun.faces.facelets.el.TagValueExpression.getValue(TagValueExpression.java:109)
>   at 
> com.sun.faces.facelets.tag.jstl.core.SetHandler.apply(SetHandler.java:163)
>   at 
> javax.faces.view.facelets.CompositeFaceletHandler.apply(CompositeFaceletHandler.java:95)
>   at 
> javax.faces.view.facelets.DelegatingMetaTagHandler.applyNextHandler(DelegatingMetaTagHandler.java:137)
>   at 
> com.sun.faces.facelets.tag.jsf.ComponentTagHandlerDelegateImpl.apply(ComponentTagHandlerDelegateImpl.java:187)
>   at 
> javax.faces.view.facelets.DelegatingMetaTagHandler.apply(DelegatingMetaTagHandler.java:120)
>   at 
> javax.faces.view.facelets.CompositeFaceletHandler.apply(CompositeFaceletHandler.java:95)
>   at 
> com.sun.faces.facelets.tag.jsf.core.ViewHandler.apply(ViewHandler.java:188)
>   at 
> javax.faces.view.facelets.CompositeFaceletHandler.apply(CompositeFaceletHandler.java:95)
>   at 
> com.sun.faces.facelets.compiler.NamespaceHandler.apply(NamespaceHandler.java:93)
>   at 
> com.sun.faces.facelets.compiler.EncodingHandler.apply(EncodingHandler.java:87)
>   at 
> com.sun.faces.facelets.impl.DefaultFacelet.include(DefaultFacelet.java:320)
>   at 
> com.sun.faces.facelets.impl.DefaultFacelet.include(DefaultFacelet.java:379)
>   at 
> com.sun.faces.facelets.impl.DefaultFacelet.include(DefaultFacelet.java:358)
>   at 
> com.sun.faces.facelets.impl.DefaultFaceletContext.includeFacelet(DefaultFaceletContext.java:199)
>   at 
> com.sun.faces.facelets.tag.ui.CompositionHandler.apply(CompositionHandle

[jira] [Resolved] (DELTASPIKE-830) Now active ViewAccessScoped context during restore view phase

2015-07-14 Thread Thomas Andraschko (JIRA) 

 [ 
https://issues.apache.org/jira/browse/DELTASPIKE-830?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Thomas Andraschko resolved DELTASPIKE-830.
--
Resolution: Fixed

> Now active ViewAccessScoped context during restore view phase
> -
>
> Key: DELTASPIKE-830
> URL: https://issues.apache.org/jira/browse/DELTASPIKE-830
> Project: DeltaSpike
>  Issue Type: Bug
>  Components: JSF-Module
>Affects Versions: 1.2.1
> Environment: Glassfish 3.1.2.2 and Weblogic 12.1.2.2
>Reporter: Nuno G. de M
>Assignee: Thomas Andraschko
> Fix For: 1.4.2
>
>
> While testing delta-spike in clientview mode, coming from CODI, we have one 
> view that is giving problems trying to access ViewAccessScoped beans  during 
> the restored view phase.
> Caused by: org.jboss.weld.context.ContextNotActiveException: WELD-001303 No 
> active contexts for scope type 
> org.apache.deltaspike.core.api.scope.ViewAccessScoped
> Namely the exception we get in our page is the following:
> Caused By: org.jboss.weld.context.ContextNotActiveException: WELD-001303 No 
> active contexts for scope type 
> org.apache.deltaspike.core.api.scope.ViewAccessScoped
>   at 
> org.jboss.weld.manager.BeanManagerImpl.getContext(BeanManagerImpl.java:590)
>   at 
> org.jboss.weld.bean.proxy.ContextBeanInstance.getInstance(ContextBeanInstance.java:71)
>   at 
> org.jboss.weld.bean.proxy.ProxyMethodHandler.invoke(ProxyMethodHandler.java:79)
>   at 
> com.corp.whatever.component.ui.web.CR100Bean$Proxy$_$$_WeldClientProxy.getPageIds(CR100Bean$Proxy$_$$_WeldClientProxy.java)
>   at sun.reflect.GeneratedMethodAccessor1663.invoke(Unknown Source)
>   at 
> sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43)
>   at java.lang.reflect.Method.invoke(Method.java:606)
>   at javax.el.BeanELResolver.getValue(BeanELResolver.java:305)
>   at 
> com.sun.faces.el.DemuxCompositeELResolver._getValue(DemuxCompositeELResolver.java:176)
>   at 
> com.sun.faces.el.DemuxCompositeELResolver.getValue(DemuxCompositeELResolver.java:203)
>   at com.sun.el.parser.AstValue.getValue(AstValue.java:138)
>   at com.sun.el.parser.AstValue.getValue(AstValue.java:183)
>   at com.sun.el.ValueExpressionImpl.getValue(ValueExpressionImpl.java:224)
>   at 
> org.jboss.weld.el.WeldValueExpression.getValue(WeldValueExpression.java:50)
>   at 
> org.jboss.weld.el.WeldValueExpression.getValue(WeldValueExpression.java:50)
>   at 
> com.sun.faces.facelets.el.TagValueExpression.getValue(TagValueExpression.java:109)
>   at com.sun.el.parser.AstIdentifier.getValue(AstIdentifier.java:99)
>   at com.sun.el.ValueExpressionImpl.getValue(ValueExpressionImpl.java:224)
>   at 
> org.jboss.weld.el.WeldValueExpression.getValue(WeldValueExpression.java:50)
>   at 
> org.jboss.weld.el.WeldValueExpression.getValue(WeldValueExpression.java:50)
>   at 
> com.sun.faces.facelets.el.TagValueExpression.getValue(TagValueExpression.java:109)
>   at 
> com.sun.faces.facelets.tag.jstl.core.SetHandler.apply(SetHandler.java:163)
>   at 
> javax.faces.view.facelets.CompositeFaceletHandler.apply(CompositeFaceletHandler.java:95)
>   at 
> javax.faces.view.facelets.DelegatingMetaTagHandler.applyNextHandler(DelegatingMetaTagHandler.java:137)
>   at 
> com.sun.faces.facelets.tag.jsf.ComponentTagHandlerDelegateImpl.apply(ComponentTagHandlerDelegateImpl.java:187)
>   at 
> javax.faces.view.facelets.DelegatingMetaTagHandler.apply(DelegatingMetaTagHandler.java:120)
>   at 
> javax.faces.view.facelets.CompositeFaceletHandler.apply(CompositeFaceletHandler.java:95)
>   at 
> com.sun.faces.facelets.tag.jsf.core.ViewHandler.apply(ViewHandler.java:188)
>   at 
> javax.faces.view.facelets.CompositeFaceletHandler.apply(CompositeFaceletHandler.java:95)
>   at 
> com.sun.faces.facelets.compiler.NamespaceHandler.apply(NamespaceHandler.java:93)
>   at 
> com.sun.faces.facelets.compiler.EncodingHandler.apply(EncodingHandler.java:87)
>   at 
> com.sun.faces.facelets.impl.DefaultFacelet.include(DefaultFacelet.java:320)
>   at 
> com.sun.faces.facelets.impl.DefaultFacelet.include(DefaultFacelet.java:379)
>   at 
> com.sun.faces.facelets.impl.DefaultFacelet.include(DefaultFacelet.java:358)
>   at 
> com.sun.faces.facelets.impl.DefaultFaceletContext.includeFacelet(DefaultFaceletContext.java:199)
>   at 
> com.sun.faces.facelets.tag.ui.CompositionHandler.apply(CompositionHandler.java:155)
>   at 
> com.sun.faces.facelets.compiler.NamespaceHandler.apply(NamespaceHandler.java:93)
>   at 
> com.sun.faces.facelets.compiler.EncodingHandler.apply(EncodingHandler.java:87)
>   at 
> com.sun.faces.facelets.impl.DefaultFacelet.include(DefaultFacelet.java:320)
>

[jira] [Updated] (DELTASPIKE-830) Now active ViewAccessScoped context during restore view phase

2015-07-14 Thread Thomas Andraschko (JIRA) 

 [ 
https://issues.apache.org/jira/browse/DELTASPIKE-830?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Thomas Andraschko updated DELTASPIKE-830:
-
Fix Version/s: (was: 1.4.0)
   1.4.2

> Now active ViewAccessScoped context during restore view phase
> -
>
> Key: DELTASPIKE-830
> URL: https://issues.apache.org/jira/browse/DELTASPIKE-830
> Project: DeltaSpike
>  Issue Type: Bug
>  Components: JSF-Module
>Affects Versions: 1.2.1
> Environment: Glassfish 3.1.2.2 and Weblogic 12.1.2.2
>Reporter: Nuno G. de M
>Assignee: Thomas Andraschko
> Fix For: 1.4.2
>
>
> While testing delta-spike in clientview mode, coming from CODI, we have one 
> view that is giving problems trying to access ViewAccessScoped beans  during 
> the restored view phase.
> Caused by: org.jboss.weld.context.ContextNotActiveException: WELD-001303 No 
> active contexts for scope type 
> org.apache.deltaspike.core.api.scope.ViewAccessScoped
> Namely the exception we get in our page is the following:
> Caused By: org.jboss.weld.context.ContextNotActiveException: WELD-001303 No 
> active contexts for scope type 
> org.apache.deltaspike.core.api.scope.ViewAccessScoped
>   at 
> org.jboss.weld.manager.BeanManagerImpl.getContext(BeanManagerImpl.java:590)
>   at 
> org.jboss.weld.bean.proxy.ContextBeanInstance.getInstance(ContextBeanInstance.java:71)
>   at 
> org.jboss.weld.bean.proxy.ProxyMethodHandler.invoke(ProxyMethodHandler.java:79)
>   at 
> com.corp.whatever.component.ui.web.CR100Bean$Proxy$_$$_WeldClientProxy.getPageIds(CR100Bean$Proxy$_$$_WeldClientProxy.java)
>   at sun.reflect.GeneratedMethodAccessor1663.invoke(Unknown Source)
>   at 
> sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43)
>   at java.lang.reflect.Method.invoke(Method.java:606)
>   at javax.el.BeanELResolver.getValue(BeanELResolver.java:305)
>   at 
> com.sun.faces.el.DemuxCompositeELResolver._getValue(DemuxCompositeELResolver.java:176)
>   at 
> com.sun.faces.el.DemuxCompositeELResolver.getValue(DemuxCompositeELResolver.java:203)
>   at com.sun.el.parser.AstValue.getValue(AstValue.java:138)
>   at com.sun.el.parser.AstValue.getValue(AstValue.java:183)
>   at com.sun.el.ValueExpressionImpl.getValue(ValueExpressionImpl.java:224)
>   at 
> org.jboss.weld.el.WeldValueExpression.getValue(WeldValueExpression.java:50)
>   at 
> org.jboss.weld.el.WeldValueExpression.getValue(WeldValueExpression.java:50)
>   at 
> com.sun.faces.facelets.el.TagValueExpression.getValue(TagValueExpression.java:109)
>   at com.sun.el.parser.AstIdentifier.getValue(AstIdentifier.java:99)
>   at com.sun.el.ValueExpressionImpl.getValue(ValueExpressionImpl.java:224)
>   at 
> org.jboss.weld.el.WeldValueExpression.getValue(WeldValueExpression.java:50)
>   at 
> org.jboss.weld.el.WeldValueExpression.getValue(WeldValueExpression.java:50)
>   at 
> com.sun.faces.facelets.el.TagValueExpression.getValue(TagValueExpression.java:109)
>   at 
> com.sun.faces.facelets.tag.jstl.core.SetHandler.apply(SetHandler.java:163)
>   at 
> javax.faces.view.facelets.CompositeFaceletHandler.apply(CompositeFaceletHandler.java:95)
>   at 
> javax.faces.view.facelets.DelegatingMetaTagHandler.applyNextHandler(DelegatingMetaTagHandler.java:137)
>   at 
> com.sun.faces.facelets.tag.jsf.ComponentTagHandlerDelegateImpl.apply(ComponentTagHandlerDelegateImpl.java:187)
>   at 
> javax.faces.view.facelets.DelegatingMetaTagHandler.apply(DelegatingMetaTagHandler.java:120)
>   at 
> javax.faces.view.facelets.CompositeFaceletHandler.apply(CompositeFaceletHandler.java:95)
>   at 
> com.sun.faces.facelets.tag.jsf.core.ViewHandler.apply(ViewHandler.java:188)
>   at 
> javax.faces.view.facelets.CompositeFaceletHandler.apply(CompositeFaceletHandler.java:95)
>   at 
> com.sun.faces.facelets.compiler.NamespaceHandler.apply(NamespaceHandler.java:93)
>   at 
> com.sun.faces.facelets.compiler.EncodingHandler.apply(EncodingHandler.java:87)
>   at 
> com.sun.faces.facelets.impl.DefaultFacelet.include(DefaultFacelet.java:320)
>   at 
> com.sun.faces.facelets.impl.DefaultFacelet.include(DefaultFacelet.java:379)
>   at 
> com.sun.faces.facelets.impl.DefaultFacelet.include(DefaultFacelet.java:358)
>   at 
> com.sun.faces.facelets.impl.DefaultFaceletContext.includeFacelet(DefaultFaceletContext.java:199)
>   at 
> com.sun.faces.facelets.tag.ui.CompositionHandler.apply(CompositionHandler.java:155)
>   at 
> com.sun.faces.facelets.compiler.NamespaceHandler.apply(NamespaceHandler.java:93)
>   at 
> com.sun.faces.facelets.compiler.EncodingHandler.apply(EncodingHandler.java:87)
>   at 
> com.sun.faces.facelets.impl.DefaultFacele

[jira] [Reopened] (DELTASPIKE-830) Now active ViewAccessScoped context during restore view phase

2015-07-14 Thread Thomas Andraschko (JIRA) 

 [ 
https://issues.apache.org/jira/browse/DELTASPIKE-830?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Thomas Andraschko reopened DELTASPIKE-830:
--

> Now active ViewAccessScoped context during restore view phase
> -
>
> Key: DELTASPIKE-830
> URL: https://issues.apache.org/jira/browse/DELTASPIKE-830
> Project: DeltaSpike
>  Issue Type: Bug
>  Components: JSF-Module
>Affects Versions: 1.2.1
> Environment: Glassfish 3.1.2.2 and Weblogic 12.1.2.2
>Reporter: Nuno G. de M
>Assignee: Thomas Andraschko
> Fix For: 1.4.2
>
>
> While testing delta-spike in clientview mode, coming from CODI, we have one 
> view that is giving problems trying to access ViewAccessScoped beans  during 
> the restored view phase.
> Caused by: org.jboss.weld.context.ContextNotActiveException: WELD-001303 No 
> active contexts for scope type 
> org.apache.deltaspike.core.api.scope.ViewAccessScoped
> Namely the exception we get in our page is the following:
> Caused By: org.jboss.weld.context.ContextNotActiveException: WELD-001303 No 
> active contexts for scope type 
> org.apache.deltaspike.core.api.scope.ViewAccessScoped
>   at 
> org.jboss.weld.manager.BeanManagerImpl.getContext(BeanManagerImpl.java:590)
>   at 
> org.jboss.weld.bean.proxy.ContextBeanInstance.getInstance(ContextBeanInstance.java:71)
>   at 
> org.jboss.weld.bean.proxy.ProxyMethodHandler.invoke(ProxyMethodHandler.java:79)
>   at 
> com.corp.whatever.component.ui.web.CR100Bean$Proxy$_$$_WeldClientProxy.getPageIds(CR100Bean$Proxy$_$$_WeldClientProxy.java)
>   at sun.reflect.GeneratedMethodAccessor1663.invoke(Unknown Source)
>   at 
> sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43)
>   at java.lang.reflect.Method.invoke(Method.java:606)
>   at javax.el.BeanELResolver.getValue(BeanELResolver.java:305)
>   at 
> com.sun.faces.el.DemuxCompositeELResolver._getValue(DemuxCompositeELResolver.java:176)
>   at 
> com.sun.faces.el.DemuxCompositeELResolver.getValue(DemuxCompositeELResolver.java:203)
>   at com.sun.el.parser.AstValue.getValue(AstValue.java:138)
>   at com.sun.el.parser.AstValue.getValue(AstValue.java:183)
>   at com.sun.el.ValueExpressionImpl.getValue(ValueExpressionImpl.java:224)
>   at 
> org.jboss.weld.el.WeldValueExpression.getValue(WeldValueExpression.java:50)
>   at 
> org.jboss.weld.el.WeldValueExpression.getValue(WeldValueExpression.java:50)
>   at 
> com.sun.faces.facelets.el.TagValueExpression.getValue(TagValueExpression.java:109)
>   at com.sun.el.parser.AstIdentifier.getValue(AstIdentifier.java:99)
>   at com.sun.el.ValueExpressionImpl.getValue(ValueExpressionImpl.java:224)
>   at 
> org.jboss.weld.el.WeldValueExpression.getValue(WeldValueExpression.java:50)
>   at 
> org.jboss.weld.el.WeldValueExpression.getValue(WeldValueExpression.java:50)
>   at 
> com.sun.faces.facelets.el.TagValueExpression.getValue(TagValueExpression.java:109)
>   at 
> com.sun.faces.facelets.tag.jstl.core.SetHandler.apply(SetHandler.java:163)
>   at 
> javax.faces.view.facelets.CompositeFaceletHandler.apply(CompositeFaceletHandler.java:95)
>   at 
> javax.faces.view.facelets.DelegatingMetaTagHandler.applyNextHandler(DelegatingMetaTagHandler.java:137)
>   at 
> com.sun.faces.facelets.tag.jsf.ComponentTagHandlerDelegateImpl.apply(ComponentTagHandlerDelegateImpl.java:187)
>   at 
> javax.faces.view.facelets.DelegatingMetaTagHandler.apply(DelegatingMetaTagHandler.java:120)
>   at 
> javax.faces.view.facelets.CompositeFaceletHandler.apply(CompositeFaceletHandler.java:95)
>   at 
> com.sun.faces.facelets.tag.jsf.core.ViewHandler.apply(ViewHandler.java:188)
>   at 
> javax.faces.view.facelets.CompositeFaceletHandler.apply(CompositeFaceletHandler.java:95)
>   at 
> com.sun.faces.facelets.compiler.NamespaceHandler.apply(NamespaceHandler.java:93)
>   at 
> com.sun.faces.facelets.compiler.EncodingHandler.apply(EncodingHandler.java:87)
>   at 
> com.sun.faces.facelets.impl.DefaultFacelet.include(DefaultFacelet.java:320)
>   at 
> com.sun.faces.facelets.impl.DefaultFacelet.include(DefaultFacelet.java:379)
>   at 
> com.sun.faces.facelets.impl.DefaultFacelet.include(DefaultFacelet.java:358)
>   at 
> com.sun.faces.facelets.impl.DefaultFaceletContext.includeFacelet(DefaultFaceletContext.java:199)
>   at 
> com.sun.faces.facelets.tag.ui.CompositionHandler.apply(CompositionHandler.java:155)
>   at 
> com.sun.faces.facelets.compiler.NamespaceHandler.apply(NamespaceHandler.java:93)
>   at 
> com.sun.faces.facelets.compiler.EncodingHandler.apply(EncodingHandler.java:87)
>   at 
> com.sun.faces.facelets.impl.DefaultFacelet.include(DefaultFacelet.java:320)
>   at 
> com.sun.fa

[jira] [Commented] (DELTASPIKE-830) Now active ViewAccessScoped context during restore view phase

2015-07-14 Thread Thomas Andraschko (JIRA) 

[ 
https://issues.apache.org/jira/browse/DELTASPIKE-830?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14627025#comment-14627025
 ] 

Thomas Andraschko commented on DELTASPIKE-830:
--

Should be fixed now in trunk. Would you please give it a try?

> Now active ViewAccessScoped context during restore view phase
> -
>
> Key: DELTASPIKE-830
> URL: https://issues.apache.org/jira/browse/DELTASPIKE-830
> Project: DeltaSpike
>  Issue Type: Bug
>  Components: JSF-Module
>Affects Versions: 1.2.1
> Environment: Glassfish 3.1.2.2 and Weblogic 12.1.2.2
>Reporter: Nuno G. de M
>Assignee: Thomas Andraschko
> Fix For: 1.4.0
>
>
> While testing delta-spike in clientview mode, coming from CODI, we have one 
> view that is giving problems trying to access ViewAccessScoped beans  during 
> the restored view phase.
> Caused by: org.jboss.weld.context.ContextNotActiveException: WELD-001303 No 
> active contexts for scope type 
> org.apache.deltaspike.core.api.scope.ViewAccessScoped
> Namely the exception we get in our page is the following:
> Caused By: org.jboss.weld.context.ContextNotActiveException: WELD-001303 No 
> active contexts for scope type 
> org.apache.deltaspike.core.api.scope.ViewAccessScoped
>   at 
> org.jboss.weld.manager.BeanManagerImpl.getContext(BeanManagerImpl.java:590)
>   at 
> org.jboss.weld.bean.proxy.ContextBeanInstance.getInstance(ContextBeanInstance.java:71)
>   at 
> org.jboss.weld.bean.proxy.ProxyMethodHandler.invoke(ProxyMethodHandler.java:79)
>   at 
> com.corp.whatever.component.ui.web.CR100Bean$Proxy$_$$_WeldClientProxy.getPageIds(CR100Bean$Proxy$_$$_WeldClientProxy.java)
>   at sun.reflect.GeneratedMethodAccessor1663.invoke(Unknown Source)
>   at 
> sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43)
>   at java.lang.reflect.Method.invoke(Method.java:606)
>   at javax.el.BeanELResolver.getValue(BeanELResolver.java:305)
>   at 
> com.sun.faces.el.DemuxCompositeELResolver._getValue(DemuxCompositeELResolver.java:176)
>   at 
> com.sun.faces.el.DemuxCompositeELResolver.getValue(DemuxCompositeELResolver.java:203)
>   at com.sun.el.parser.AstValue.getValue(AstValue.java:138)
>   at com.sun.el.parser.AstValue.getValue(AstValue.java:183)
>   at com.sun.el.ValueExpressionImpl.getValue(ValueExpressionImpl.java:224)
>   at 
> org.jboss.weld.el.WeldValueExpression.getValue(WeldValueExpression.java:50)
>   at 
> org.jboss.weld.el.WeldValueExpression.getValue(WeldValueExpression.java:50)
>   at 
> com.sun.faces.facelets.el.TagValueExpression.getValue(TagValueExpression.java:109)
>   at com.sun.el.parser.AstIdentifier.getValue(AstIdentifier.java:99)
>   at com.sun.el.ValueExpressionImpl.getValue(ValueExpressionImpl.java:224)
>   at 
> org.jboss.weld.el.WeldValueExpression.getValue(WeldValueExpression.java:50)
>   at 
> org.jboss.weld.el.WeldValueExpression.getValue(WeldValueExpression.java:50)
>   at 
> com.sun.faces.facelets.el.TagValueExpression.getValue(TagValueExpression.java:109)
>   at 
> com.sun.faces.facelets.tag.jstl.core.SetHandler.apply(SetHandler.java:163)
>   at 
> javax.faces.view.facelets.CompositeFaceletHandler.apply(CompositeFaceletHandler.java:95)
>   at 
> javax.faces.view.facelets.DelegatingMetaTagHandler.applyNextHandler(DelegatingMetaTagHandler.java:137)
>   at 
> com.sun.faces.facelets.tag.jsf.ComponentTagHandlerDelegateImpl.apply(ComponentTagHandlerDelegateImpl.java:187)
>   at 
> javax.faces.view.facelets.DelegatingMetaTagHandler.apply(DelegatingMetaTagHandler.java:120)
>   at 
> javax.faces.view.facelets.CompositeFaceletHandler.apply(CompositeFaceletHandler.java:95)
>   at 
> com.sun.faces.facelets.tag.jsf.core.ViewHandler.apply(ViewHandler.java:188)
>   at 
> javax.faces.view.facelets.CompositeFaceletHandler.apply(CompositeFaceletHandler.java:95)
>   at 
> com.sun.faces.facelets.compiler.NamespaceHandler.apply(NamespaceHandler.java:93)
>   at 
> com.sun.faces.facelets.compiler.EncodingHandler.apply(EncodingHandler.java:87)
>   at 
> com.sun.faces.facelets.impl.DefaultFacelet.include(DefaultFacelet.java:320)
>   at 
> com.sun.faces.facelets.impl.DefaultFacelet.include(DefaultFacelet.java:379)
>   at 
> com.sun.faces.facelets.impl.DefaultFacelet.include(DefaultFacelet.java:358)
>   at 
> com.sun.faces.facelets.impl.DefaultFaceletContext.includeFacelet(DefaultFaceletContext.java:199)
>   at 
> com.sun.faces.facelets.tag.ui.CompositionHandler.apply(CompositionHandler.java:155)
>   at 
> com.sun.faces.facelets.compiler.NamespaceHandler.apply(NamespaceHandler.java:93)
>   at 
> com.sun.faces.facelets.compiler.EncodingHandler.apply(EncodingHandler.java:

[jira] [Resolved] (DELTASPIKE-887) ds:windowId should initialize the windowhandler script

2015-07-14 Thread Thomas Andraschko (JIRA) 

 [ 
https://issues.apache.org/jira/browse/DELTASPIKE-887?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Thomas Andraschko resolved DELTASPIKE-887.
--
Resolution: Fixed

> ds:windowId should initialize the windowhandler script
> --
>
> Key: DELTASPIKE-887
> URL: https://issues.apache.org/jira/browse/DELTASPIKE-887
> Project: DeltaSpike
>  Issue Type: Bug
>Affects Versions: 1.3.0
>Reporter: Thomas Andraschko
>Assignee: Thomas Andraschko
>
> Currently the windowhandler will be initialized with window.onload but if the 
> user defined an onload attribute on the body, the js version will be ignored.
> This requires an bigger refactoring on the client side, therefore i will fix 
> in the future when developing the new mixed mode between LAZY/CLIENT_WINDOW.



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

[jira] [Updated] (DELTASPIKE-887) ds:windowId should initialize the windowhandler script

2015-07-14 Thread Thomas Andraschko (JIRA) 

 [ 
https://issues.apache.org/jira/browse/DELTASPIKE-887?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Thomas Andraschko updated DELTASPIKE-887:
-
Fix Version/s: 1.4.2

> ds:windowId should initialize the windowhandler script
> --
>
> Key: DELTASPIKE-887
> URL: https://issues.apache.org/jira/browse/DELTASPIKE-887
> Project: DeltaSpike
>  Issue Type: Bug
>Affects Versions: 1.3.0
>Reporter: Thomas Andraschko
>Assignee: Thomas Andraschko
> Fix For: 1.4.2
>
>
> Currently the windowhandler will be initialized with window.onload but if the 
> user defined an onload attribute on the body, the js version will be ignored.
> This requires an bigger refactoring on the client side, therefore i will fix 
> in the future when developing the new mixed mode between LAZY/CLIENT_WINDOW.



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

[jira] [Created] (DELTASPIKE-953) Refactor ClientWindow client side

2015-07-14 Thread Thomas Andraschko (JIRA) 
Thomas Andraschko created DELTASPIKE-953:


 Summary: Refactor ClientWindow client side
 Key: DELTASPIKE-953
 URL: https://issues.apache.org/jira/browse/DELTASPIKE-953
 Project: DeltaSpike
  Issue Type: Improvement
  Components: JSF-Module, JSF22-Module
Affects Versions: 1.4.1
Reporter: Thomas Andraschko
Assignee: Thomas Andraschko
 Fix For: 1.4.2






--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

Re: Proxy module documentation - Volunteer needed

2015-07-14 Thread Josimar Alves 
I'll start ASAP.

Certainly I'll need some help :-) .

Att.




*Josimar Silva*
Desenvolvedor Padawan
    
 [image:  Ghost Blog]


   

On Tue, Jul 14, 2015 at 10:17 AM, Rafael Benevides 
wrote:

> Thanks so much, Josimar!
>
> Can you start to draft the proxy.adoc in the sources, please?
>
> I opened https://issues.apache.org/jira/browse/DELTASPIKE-952 to track
> this task.
>
> Feel free to send a PR having the commit with the prefix "DELTASPIKE-952 -
> "
>
> I'm not a proxy expert but if you need any further help, please, feel free
> to contact me or ask for it in this mailing list.
>
> You can follow the pattern used on the other modules docs.
>
>
> - Mensagem original -
> De: "Josimar Alves" 
> Para: dev@deltaspike.apache.org
> Enviadas: Terça-feira, 14 de julho de 2015 8:35:54
> Assunto: Re: Proxy module documentation - Volunteer needed
>
> Hey.
>
> I want to help  👋 .
>
>
> *Josimar Silva*
> Desenvolvedor Padawan
>     
>  [image:  Ghost Blog]
>  
>
>
>
> On Mon, Jul 13, 2015 at 4:03 PM, Rafael Benevides 
> wrote:
>
> > Hi all,
> >
> > Today I added Proxy module as a dependency for JSF and Partial-Bean on
> > http://deltaspike.apache.org/documentation/
> >
> > As a result, we need to document Proxy Module:
> > http://deltaspike.apache.org/documentation/proxy.html
> >
> > I'm sending this email to ask for volunteers to do that.
> >
> > Thanks
> >
> > Rafael Benevides | Senior Software Engineer
> > JBoss Developer Materials lead
> > M: +1-919-592-6255
> >
> > Red Hat
> >
> > Better technology. Faster innovation. Powered by community collaboration.
> > See how it works at www.redhat.com
> >
> >
>

Re: Proxy module documentation - Volunteer needed

2015-07-14 Thread Rafael Benevides 
Thanks so much, Josimar!

Can you start to draft the proxy.adoc in the sources, please?

I opened https://issues.apache.org/jira/browse/DELTASPIKE-952 to track this 
task. 

Feel free to send a PR having the commit with the prefix "DELTASPIKE-952 - 
"

I'm not a proxy expert but if you need any further help, please, feel free to 
contact me or ask for it in this mailing list.

You can follow the pattern used on the other modules docs.


- Mensagem original -
De: "Josimar Alves" 
Para: dev@deltaspike.apache.org
Enviadas: Terça-feira, 14 de julho de 2015 8:35:54
Assunto: Re: Proxy module documentation - Volunteer needed

Hey.

I want to help  👋 .


*Josimar Silva*
Desenvolvedor Padawan
    
 [image:  Ghost Blog]
 

   

On Mon, Jul 13, 2015 at 4:03 PM, Rafael Benevides 
wrote:

> Hi all,
>
> Today I added Proxy module as a dependency for JSF and Partial-Bean on
> http://deltaspike.apache.org/documentation/
>
> As a result, we need to document Proxy Module:
> http://deltaspike.apache.org/documentation/proxy.html
>
> I'm sending this email to ask for volunteers to do that.
>
> Thanks
>
> Rafael Benevides | Senior Software Engineer
> JBoss Developer Materials lead
> M: +1-919-592-6255
>
> Red Hat
>
> Better technology. Faster innovation. Powered by community collaboration.
> See how it works at www.redhat.com
>
>

[jira] [Created] (DELTASPIKE-952) Document Proxy Module

2015-07-14 Thread Rafael Benevides (JIRA) 
Rafael Benevides created DELTASPIKE-952:
---

 Summary: Document Proxy Module
 Key: DELTASPIKE-952
 URL: https://issues.apache.org/jira/browse/DELTASPIKE-952
 Project: DeltaSpike
  Issue Type: Task
  Components: Documentation
Affects Versions: 1.4.1
Reporter: Rafael Benevides






--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

Re: Proxy module documentation - Volunteer needed

2015-07-14 Thread Josimar Alves 
Hey.

I want to help  👋 .






*Josimar Silva*
Desenvolvedor Padawan
    
 [image:  Ghost Blog]
 

   

On Mon, Jul 13, 2015 at 4:03 PM, Rafael Benevides 
wrote:

> Hi all,
>
> Today I added Proxy module as a dependency for JSF and Partial-Bean on
> http://deltaspike.apache.org/documentation/
>
> As a result, we need to document Proxy Module:
> http://deltaspike.apache.org/documentation/proxy.html
>
> I'm sending this email to ask for volunteers to do that.
>
> Thanks
>
> Rafael Benevides | Senior Software Engineer
> JBoss Developer Materials lead
> M: +1-919-592-6255
>
> Red Hat
>
> Better technology. Faster innovation. Powered by community collaboration.
> See how it works at www.redhat.com
>
>