[jira] [Commented] (DELTASPIKE-1086) DeltaSpike @Scheduled does not firing on Wildfly 10

[Rafael Benevides (JIRA)]

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

Rafael Benevides commented on DELTASPIKE-1086:
--

Do you have a zip file to provide with the code example ?

> DeltaSpike @Scheduled does not firing on Wildfly 10
> ---
>
> Key: DELTASPIKE-1086
> URL: https://issues.apache.org/jira/browse/DELTASPIKE-1086
> Project: DeltaSpike
>  Issue Type: Bug
>  Components: Scheduler
>Affects Versions: 1.5.2, 1.5.3
> Environment: Wildfly 10 + quarts 2.2.2
>Reporter: Ícaro Goulart Faria Motta França
>Assignee: Rafael Benevides
>  Labels: easyfix
>   Original Estimate: 8h
>  Remaining Estimate: 8h
>
> http://stackoverflow.com/questions/35637609/deltaspike-scheduled-does-not-firing
> My job annotated with @Scheduled does not fire the task. I am using Wildfly 10
> deltaspike-scheduler-module 1.5.3
> quartz 2.2.2
> Quartz alone works fine.
> My actual code problem:
> @Scheduled(cronExpression = "0 * * * * ?")
> public class CronTask implements Job{
> static public final Logger log = Logger.getLogger(CronTask.class.getName());
> @Override
> public void execute(JobExecutionContext arg0) throws JobExecutionException {
> log.info("Run");
> System.out.println("a");
>   }
> }
> Any help is welcome.
> PS: This code on Jboss EAP works



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

[jira] [Closed] (DELTASPIKE-1086) DeltaSpike @Scheduled does not firing on Wildfly 10

[Rafael Benevides (JIRA)]

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

Rafael Benevides closed DELTASPIKE-1086.

Resolution: Cannot Reproduce

It worked in my WF10. Test project: https://github.com/rafabene/demo_deltaspike

> DeltaSpike @Scheduled does not firing on Wildfly 10
> ---
>
> Key: DELTASPIKE-1086
> URL: https://issues.apache.org/jira/browse/DELTASPIKE-1086
> Project: DeltaSpike
>  Issue Type: Bug
>  Components: Scheduler
>Affects Versions: 1.5.2, 1.5.3
> Environment: Wildfly 10 + quarts 2.2.2
>Reporter: Ícaro Goulart Faria Motta França
>Assignee: Rafael Benevides
>  Labels: easyfix
>   Original Estimate: 8h
>  Remaining Estimate: 8h
>
> http://stackoverflow.com/questions/35637609/deltaspike-scheduled-does-not-firing
> My job annotated with @Scheduled does not fire the task. I am using Wildfly 10
> deltaspike-scheduler-module 1.5.3
> quartz 2.2.2
> Quartz alone works fine.
> My actual code problem:
> @Scheduled(cronExpression = "0 * * * * ?")
> public class CronTask implements Job{
> static public final Logger log = Logger.getLogger(CronTask.class.getName());
> @Override
> public void execute(JobExecutionContext arg0) throws JobExecutionException {
> log.info("Run");
> System.out.println("a");
>   }
> }
> Any help is welcome.
> PS: This code on Jboss EAP works



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

[jira] [Resolved] (DELTASPIKE-1031) Update profiles for Wildfly

[Rafael Benevides (JIRA)]

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

Rafael Benevides resolved DELTASPIKE-1031.
--
Resolution: Fixed

Merged as: 
https://github.com/apache/deltaspike/commit/9ab5c5cac3a97c63e31858992f1046fa4fcd31cb

Thanks for the PR.

> Update profiles for Wildfly
> ---
>
> Key: DELTASPIKE-1031
> URL: https://issues.apache.org/jira/browse/DELTASPIKE-1031
> Project: DeltaSpike
>  Issue Type: Improvement
>  Components: Configuration, Tests
>Affects Versions: 1.5.1
>Reporter: Matej Novotny
>Assignee: Rafael Benevides
> Fix For: 1.5.2
>
>
> Taking a closer look at how test structure looks like, I saw that running 
> tests against Wildfly:
> {{mvn clean verify -Pwildfly-managed}}
> will launch Arquillian profile named {{jbossas-managed-7}}.
> Similar situation is with remote profile (and maybe other tiny bits).
> This naming seems inappropriate and highly confusing when (for instance) you 
> need to temper with Arq. settings in order to debug code.
> I would suggest adding separate profiles to {{arquillian-jboss.xml}}.
> Apart from this, what do you think about updating the default WFLY from 8 to 
> 9 (or even 10, there is CR4 already)?
> Will send a PR with these tiny changes soon.



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

[jira] [Comment Edited] (DELTASPIKE-985) It's not possible to run tests against latest WildFly

[Rafael Benevides (JIRA)]

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

Rafael Benevides edited comment on DELTASPIKE-985 at 9/3/15 4:00 PM:
-

Hi [~tremes]

I just run __mvn clean install -Pwildfly-build-managed__ with your PR without 
specifying any WF version.


was (Author: rafabene):
Hi [~tremes]

I just run `mvn clean install -Pwildfly-build-managed` with your PR without 
specifying any WF version.

> It's not possible to run tests against latest WildFly
> -
>
> Key: DELTASPIKE-985
> URL: https://issues.apache.org/jira/browse/DELTASPIKE-985
> Project: DeltaSpike
>  Issue Type: Bug
>  Components: Tests
>Affects Versions: 1.5.0
>Reporter: Tomas Remes
>Assignee: Rafael Benevides
>




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

[jira] [Comment Edited] (DELTASPIKE-985) It's not possible to run tests against latest WildFly

[Rafael Benevides (JIRA)]

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

Rafael Benevides edited comment on DELTASPIKE-985 at 9/3/15 3:59 PM:
-

Hi [~tremes]

I just run `mvn clean install -Pwildfly-build-managed` with your PR without 
specifying any WF version.


was (Author: rafabene):
Hi [~tremes]

I just run mvn clean install -Pwildfly-build-managed with your PR without 
specifying any WF version.

> It's not possible to run tests against latest WildFly
> -
>
> Key: DELTASPIKE-985
> URL: https://issues.apache.org/jira/browse/DELTASPIKE-985
> Project: DeltaSpike
>  Issue Type: Bug
>  Components: Tests
>Affects Versions: 1.5.0
>Reporter: Tomas Remes
>Assignee: Rafael Benevides
>




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

[jira] [Resolved] (DELTASPIKE-985) It's not possible to run tests against latest WildFly

[Rafael Benevides (JIRA)]

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

Rafael Benevides resolved DELTASPIKE-985.
-
   Resolution: Fixed
Fix Version/s: 1.5.1

> It's not possible to run tests against latest WildFly
> -
>
> Key: DELTASPIKE-985
> URL: https://issues.apache.org/jira/browse/DELTASPIKE-985
> Project: DeltaSpike
>  Issue Type: Bug
>  Components: Tests
>Affects Versions: 1.5.0
>Reporter: Tomas Remes
>Assignee: Rafael Benevides
> Fix For: 1.5.1
>
>




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

[jira] [Commented] (DELTASPIKE-985) It's not possible to run tests against latest WildFly

[Rafael Benevides (JIRA)]

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

Rafael Benevides commented on DELTASPIKE-985:
-

I fixed in this commit: 
https://github.com/apache/deltaspike/commit/72cac006d89009a69411601adb0d3097c8b165cc

> It's not possible to run tests against latest WildFly
> -
>
> Key: DELTASPIKE-985
> URL: https://issues.apache.org/jira/browse/DELTASPIKE-985
> Project: DeltaSpike
>  Issue Type: Bug
>  Components: Tests
>Affects Versions: 1.5.0
>Reporter: Tomas Remes
>Assignee: Rafael Benevides
> Fix For: 1.5.1
>
>




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

[jira] [Commented] (DELTASPIKE-985) It's not possible to run tests against latest WildFly

[Rafael Benevides (JIRA)]

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

Rafael Benevides commented on DELTASPIKE-985:
-

Hi [~tremes]

I just run mvn clean install -Pwildfly-build-managed with your PR without 
specifying any WF version.

> It's not possible to run tests against latest WildFly
> -
>
> Key: DELTASPIKE-985
> URL: https://issues.apache.org/jira/browse/DELTASPIKE-985
> Project: DeltaSpike
>  Issue Type: Bug
>  Components: Tests
>Affects Versions: 1.5.0
>Reporter: Tomas Remes
>Assignee: Rafael Benevides
>




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

[jira] [Created] (DELTASPIKE-983) Investigate issue with DeltaSpike Validation Module

[Rafael Benevides (JIRA)]

Rafael Benevides created DELTASPIKE-983:
---

 Summary: Investigate issue with DeltaSpike Validation Module
 Key: DELTASPIKE-983
 URL: https://issues.apache.org/jira/browse/DELTASPIKE-983
 Project: DeltaSpike
  Issue Type: Bug
  Components: BeanValidation-Module
Affects Versions: 1.5.0
Reporter: Rafael Benevides
Assignee: Rafael Benevides
 Fix For: 1.5.1


Using BV with Java EE 7 libs causes the following exception:

{code}
Exception in thread Thread-0 java.lang.AbstractMethodError: 
org.apache.deltaspike.beanvalidation.impl.CDIAwareConstraintValidatorFactory.releaseInstance(Ljavax/validation/ConstraintValidator;)V
 at 
org.hibernate.validator.internal.engine.constraintvalidation.ConstraintValidatorManager.clear(ConstraintValidatorManager.java:201)
 at 
org.hibernate.validator.internal.engine.ValidatorFactoryImpl.close(ValidatorFactoryImpl.java:315)
 at 
org.hibernate.validator.internal.cdi.ValidatorFactoryBean.destroy(ValidatorFactoryBean.java:125)
 at 
org.hibernate.validator.internal.cdi.ValidatorFactoryBean.destroy(ValidatorFactoryBean.java:45)
 at 
org.jboss.weld.util.bean.IsolatedForwardingBean.destroy(IsolatedForwardingBean.java:50)
 at 
org.jboss.weld.context.AbstractContext.destroyContextualInstance(AbstractContext.java:147)
 at org.jboss.weld.context.AbstractContext.destroy(AbstractContext.java:161) at 
org.jboss.weld.context.AbstractSharedContext.destroy(AbstractSharedContext.java:61)
 at 
org.jboss.weld.context.AbstractSharedContext.invalidate(AbstractSharedContext.java:56)
 at org.jboss.weld.bootstrap.WeldRuntime.shutdown(WeldRuntime.java:54) at 
org.jboss.weld.bootstrap.WeldBootstrap.shutdown(WeldBootstrap.java:113) at 
org.jboss.weld.environment.se.ShutdownManager.shutdown(ShutdownManager.java:50) 
at org.jboss.weld.environment.se.Weld.shutdown(Weld.java:259) at 
org.jboss.weld.environment.se.StartMain$ShutdownHook.run(StartMain.java:84)
{code}

Example project: https://github.com/jpangamarca/bean-validation-shutdown-issue



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

[jira] [Commented] (DELTASPIKE-983) Investigate issue with DeltaSpike Validation Module

[Rafael Benevides (JIRA)]

[ 
https://issues.apache.org/jira/browse/DELTASPIKE-983?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=14706892#comment-14706892
 ] 

Rafael Benevides commented on DELTASPIKE-983:
-

After some investigation I found that ConstraintValidatorFactory included a new 
method in Java EE 7 (#releaseInstance) 

- ConstraintValidatorFactory (Java EE 6): 
http://docs.oracle.com/javaee/6/api/javax/validation/ConstraintValidatorFactory.html
- ConstraintValidatorFactory (Java EE 7): 
https://docs.oracle.com/javaee/7/api/javax/validation/ConstraintValidatorFactory.html

As informed by [~johndament]: The bean validation module should not be used in 
EE 7 app servers, it was meant to plug a hole in EE 6 containers to continue to 
leverage injection into EE 6 constraint validators (a need I had at the time, 
which is now replaced by using an EE 7 container).

 Investigate issue with DeltaSpike Validation Module
 ---

 Key: DELTASPIKE-983
 URL: https://issues.apache.org/jira/browse/DELTASPIKE-983
 Project: DeltaSpike
  Issue Type: Bug
  Components: BeanValidation-Module
Affects Versions: 1.5.0
Reporter: Rafael Benevides
Assignee: Rafael Benevides
 Fix For: 1.5.1


 Using BV with Java EE 7 libs causes the following exception:
 {code}
 Exception in thread Thread-0 java.lang.AbstractMethodError: 
 org.apache.deltaspike.beanvalidation.impl.CDIAwareConstraintValidatorFactory.releaseInstance(Ljavax/validation/ConstraintValidator;)V
  at 
 org.hibernate.validator.internal.engine.constraintvalidation.ConstraintValidatorManager.clear(ConstraintValidatorManager.java:201)
  at 
 org.hibernate.validator.internal.engine.ValidatorFactoryImpl.close(ValidatorFactoryImpl.java:315)
  at 
 org.hibernate.validator.internal.cdi.ValidatorFactoryBean.destroy(ValidatorFactoryBean.java:125)
  at 
 org.hibernate.validator.internal.cdi.ValidatorFactoryBean.destroy(ValidatorFactoryBean.java:45)
  at 
 org.jboss.weld.util.bean.IsolatedForwardingBean.destroy(IsolatedForwardingBean.java:50)
  at 
 org.jboss.weld.context.AbstractContext.destroyContextualInstance(AbstractContext.java:147)
  at org.jboss.weld.context.AbstractContext.destroy(AbstractContext.java:161) 
 at 
 org.jboss.weld.context.AbstractSharedContext.destroy(AbstractSharedContext.java:61)
  at 
 org.jboss.weld.context.AbstractSharedContext.invalidate(AbstractSharedContext.java:56)
  at org.jboss.weld.bootstrap.WeldRuntime.shutdown(WeldRuntime.java:54) at 
 org.jboss.weld.bootstrap.WeldBootstrap.shutdown(WeldBootstrap.java:113) at 
 org.jboss.weld.environment.se.ShutdownManager.shutdown(ShutdownManager.java:50)
  at org.jboss.weld.environment.se.Weld.shutdown(Weld.java:259) at 
 org.jboss.weld.environment.se.StartMain$ShutdownHook.run(StartMain.java:84)
 {code}
 Example project: https://github.com/jpangamarca/bean-validation-shutdown-issue



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

[jira] [Resolved] (DELTASPIKE-964) Publish Javadoc 1.4.2 and 1.4.3-SNAPSHOT

[Rafael Benevides (JIRA)]

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

Rafael Benevides resolved DELTASPIKE-964.
-
Resolution: Fixed

Javadocs published

 Publish Javadoc 1.4.2 and 1.4.3-SNAPSHOT
 

 Key: DELTASPIKE-964
 URL: https://issues.apache.org/jira/browse/DELTASPIKE-964
 Project: DeltaSpike
  Issue Type: Task
  Components: Documentation
Affects Versions: 1.4.2
Reporter: Rafael Benevides
Assignee: Rafael Benevides
 Fix For: 1.4.3






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

[jira] [Created] (DELTASPIKE-964) Publish Javadoc 1.4.2 and 1.4.3-SNAPSHOT

[Rafael Benevides (JIRA)]

Rafael Benevides created DELTASPIKE-964:
---

 Summary: Publish Javadoc 1.4.2 and 1.4.3-SNAPSHOT
 Key: DELTASPIKE-964
 URL: https://issues.apache.org/jira/browse/DELTASPIKE-964
 Project: DeltaSpike
  Issue Type: Task
  Components: Documentation
Affects Versions: 1.4.2
Reporter: Rafael Benevides
Assignee: Rafael Benevides
 Fix For: 1.4.3






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

[jira] [Created] (DELTASPIKE-945) Verify WildFly 9 profile

[Rafael Benevides (JIRA)]

Rafael Benevides created DELTASPIKE-945:
---

 Summary: Verify WildFly 9 profile
 Key: DELTASPIKE-945
 URL: https://issues.apache.org/jira/browse/DELTASPIKE-945
 Project: DeltaSpike
  Issue Type: Improvement
  Components: Build
Affects Versions: 1.4.1
Reporter: Rafael Benevides
Assignee: Rafael Benevides
 Fix For: 1.4.2






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

[jira] [Commented] (DELTASPIKE-937) Relese Javadoc for 1.4.1 and 1.4.2-SNAPSHOST

[Rafael Benevides (JIRA)]

[ 
https://issues.apache.org/jira/browse/DELTASPIKE-937?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=14593502#comment-14593502
 ] 

Rafael Benevides commented on DELTASPIKE-937:
-

javadocs released at http://deltaspike.apache.org/javadoc/

 Relese Javadoc for 1.4.1 and 1.4.2-SNAPSHOST
 

 Key: DELTASPIKE-937
 URL: https://issues.apache.org/jira/browse/DELTASPIKE-937
 Project: DeltaSpike
  Issue Type: Task
  Components: Documentation
Affects Versions: 1.4.1
Reporter: Rafael Benevides
Assignee: Rafael Benevides
 Fix For: 1.4.1


 It is giving 404 at http://deltaspike.apache.org/javadoc.html



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

[jira] [Updated] (DELTASPIKE-937) Relese Javadoc for 1.4.1 and 1.4.2-SNAPSHOST

[Rafael Benevides (JIRA)]

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

Rafael Benevides updated DELTASPIKE-937:

Description: It is giving 404 at http://deltaspike.apache.org/javadoc.html  
(was: It is fi the 404 at http://deltaspike.apache.org/javadoc.html)

 Relese Javadoc for 1.4.1 and 1.4.2-SNAPSHOST
 

 Key: DELTASPIKE-937
 URL: https://issues.apache.org/jira/browse/DELTASPIKE-937
 Project: DeltaSpike
  Issue Type: Task
  Components: Documentation
Affects Versions: 1.4.1
Reporter: Rafael Benevides
Assignee: Rafael Benevides
 Fix For: 1.4.1


 It is giving 404 at http://deltaspike.apache.org/javadoc.html



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

[jira] [Resolved] (DELTASPIKE-937) Relese Javadoc for 1.4.1 and 1.4.2-SNAPSHOST

[Rafael Benevides (JIRA)]

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

Rafael Benevides resolved DELTASPIKE-937.
-
Resolution: Fixed

 Relese Javadoc for 1.4.1 and 1.4.2-SNAPSHOST
 

 Key: DELTASPIKE-937
 URL: https://issues.apache.org/jira/browse/DELTASPIKE-937
 Project: DeltaSpike
  Issue Type: Task
  Components: Documentation
Affects Versions: 1.4.1
Reporter: Rafael Benevides
Assignee: Rafael Benevides
 Fix For: 1.4.1


 It is fi the 404 at http://deltaspike.apache.org/javadoc.html



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

[jira] [Created] (DELTASPIKE-937) Relese Javadoc for 1.4.1 and 1.4.2-SNAPSHOST

[Rafael Benevides (JIRA)]

Rafael Benevides created DELTASPIKE-937:
---

 Summary: Relese Javadoc for 1.4.1 and 1.4.2-SNAPSHOST
 Key: DELTASPIKE-937
 URL: https://issues.apache.org/jira/browse/DELTASPIKE-937
 Project: DeltaSpike
  Issue Type: Task
  Components: Documentation
Affects Versions: 1.4.1
Reporter: Rafael Benevides
Assignee: Rafael Benevides
 Fix For: 1.4.1


It is fi the 404 at http://deltaspike.apache.org/javadoc.html



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

[jira] [Commented] (DELTASPIKE-701) Add method in EntityRepository to merge a detached entity and remove it

[Rafael Benevides (JIRA)]

[ 
https://issues.apache.org/jira/browse/DELTASPIKE-701?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=14577347#comment-14577347
 ] 

Rafael Benevides commented on DELTASPIKE-701:
-

Thanks [~danielsoro]

 Add method in EntityRepository to merge a detached entity and remove it
 ---

 Key: DELTASPIKE-701
 URL: https://issues.apache.org/jira/browse/DELTASPIKE-701
 Project: DeltaSpike
  Issue Type: Improvement
  Components: Data-Module
Reporter: Juliano Marques
Assignee: Thomas Hug
 Attachments: DELTASPIKE-701.patch


 It will be nice if EntityRepository has a method like:
 public void attachAndRemove(Entity entity) {
 if (entityManager.contains(entity)) {
 entityManager.remove(entity);
 } else {
 entityManager.remove(entityManager.merge(entity));
 }
 }
 This method will be useful to handle java.lang.IllegalArgumentException: 
 Removing a detached instance exceptions.
 Workaround: Create a query delegate with this method.
 http://mail-archives.apache.org/mod_mbox/deltaspike-users/201408.mbox/%3CCAAuOd%3DXhb%3D-ssdzU%3DTdxWg8d18XXC15U7EjNiGya9eEgaA%2BUpA%40mail.gmail.com%3E



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

[jira] [Commented] (DELTASPIKE-905) Missing OSGi headers in Proxy modules

[Rafael Benevides (JIRA)]

[ 
https://issues.apache.org/jira/browse/DELTASPIKE-905?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=14573181#comment-14573181
 ] 

Rafael Benevides commented on DELTASPIKE-905:
-

Thanks




 Missing OSGi headers in Proxy modules
 -

 Key: DELTASPIKE-905
 URL: https://issues.apache.org/jira/browse/DELTASPIKE-905
 Project: DeltaSpike
  Issue Type: Bug
  Components: PartialBean
Affects Versions: 1.4.0
Reporter: Harald Wellmann
Assignee: Rafael Benevides
 Fix For: 1.4.1


 {{deltaspike-partial-bean-module-impl}} imports package 
 {{org.apache.deltaspike.proxy.api}}, but the new proxy modules are missing 
 OSGi manifest headers.
 This breaks Partial Beans and Data modules for OSGi users.



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

[jira] [Commented] (DELTASPIKE-905) Missing OSGi headers in Proxy modules

[Rafael Benevides (JIRA)]

[ 
https://issues.apache.org/jira/browse/DELTASPIKE-905?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=14573398#comment-14573398
 ] 

Rafael Benevides commented on DELTASPIKE-905:
-

That's true. Thanks.

I merged the right one.

 Missing OSGi headers in Proxy modules
 -

 Key: DELTASPIKE-905
 URL: https://issues.apache.org/jira/browse/DELTASPIKE-905
 Project: DeltaSpike
  Issue Type: Bug
  Components: PartialBean
Affects Versions: 1.4.0
Reporter: Harald Wellmann
Assignee: Rafael Benevides
 Fix For: 1.4.1


 {{deltaspike-partial-bean-module-impl}} imports package 
 {{org.apache.deltaspike.proxy.api}}, but the new proxy modules are missing 
 OSGi manifest headers.
 This breaks Partial Beans and Data modules for OSGi users.



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

[jira] [Commented] (DELTASPIKE-905) Missing OSGi headers in Proxy modules

[Rafael Benevides (JIRA)]

[ 
https://issues.apache.org/jira/browse/DELTASPIKE-905?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=14569598#comment-14569598
 ] 

Rafael Benevides commented on DELTASPIKE-905:
-

[~hwellmann]

Can you test the following changes, please 
https://github.com/apache/deltaspike/pull/36 ?

Thanks

 Missing OSGi headers in Proxy modules
 -

 Key: DELTASPIKE-905
 URL: https://issues.apache.org/jira/browse/DELTASPIKE-905
 Project: DeltaSpike
  Issue Type: Bug
  Components: PartialBean
Affects Versions: 1.4.0
Reporter: Harald Wellmann
Assignee: Rafael Benevides
 Fix For: 1.4.1


 {{deltaspike-partial-bean-module-impl}} imports package 
 {{org.apache.deltaspike.proxy.api}}, but the new proxy modules are missing 
 OSGi manifest headers.
 This breaks Partial Beans and Data modules for OSGi users.



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

[jira] [Reopened] (DELTASPIKE-905) Missing OSGi headers in Proxy modules

[Rafael Benevides (JIRA)]

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

Rafael Benevides reopened DELTASPIKE-905:
-

move the code from ProxyClassGeneratorLookup to DeltaSpikeProxyFactory (1:1) 
and change the class in AsmProxyClassGenerator.xml + ask harald to test the 
change

 Missing OSGi headers in Proxy modules
 -

 Key: DELTASPIKE-905
 URL: https://issues.apache.org/jira/browse/DELTASPIKE-905
 Project: DeltaSpike
  Issue Type: Bug
  Components: PartialBean
Affects Versions: 1.4.0
Reporter: Harald Wellmann
Assignee: Rafael Benevides
 Fix For: 1.4.1


 {{deltaspike-partial-bean-module-impl}} imports package 
 {{org.apache.deltaspike.proxy.api}}, but the new proxy modules are missing 
 OSGi manifest headers.
 This breaks Partial Beans and Data modules for OSGi users.



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

[jira] [Commented] (DELTASPIKE-905) Missing OSGi headers in Proxy modules

[Rafael Benevides (JIRA)]

[ 
https://issues.apache.org/jira/browse/DELTASPIKE-905?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=14568165#comment-14568165
 ] 

Rafael Benevides commented on DELTASPIKE-905:
-

PR merged

 Missing OSGi headers in Proxy modules
 -

 Key: DELTASPIKE-905
 URL: https://issues.apache.org/jira/browse/DELTASPIKE-905
 Project: DeltaSpike
  Issue Type: Bug
  Components: PartialBean
Affects Versions: 1.4.0
Reporter: Harald Wellmann
 Fix For: 1.4.1


 {{deltaspike-partial-bean-module-impl}} imports package 
 {{org.apache.deltaspike.proxy.api}}, but the new proxy modules are missing 
 OSGi manifest headers.
 This breaks Partial Beans and Data modules for OSGi users.



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

[jira] [Resolved] (DELTASPIKE-603) removeBy* - similiar to findBy*

[Rafael Benevides (JIRA)]

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

Rafael Benevides resolved DELTASPIKE-603.
-
Resolution: Fixed

 removeBy* - similiar to findBy*
 ---

 Key: DELTASPIKE-603
 URL: https://issues.apache.org/jira/browse/DELTASPIKE-603
 Project: DeltaSpike
  Issue Type: Improvement
  Components: Data-Module
Reporter: Thomas Andraschko
Assignee: Thomas Hug

 It would be great to allow a removeBy* - simliar to findBy*
 e.g.
 void removeByBrandId(String brandId);



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

[jira] [Assigned] (DELTASPIKE-901) org.apache.deltaspike.data.impl.builder.postprocessor.CountQueryPostProcessor doesn't respect order by

[Rafael Benevides (JIRA)]

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

Rafael Benevides reassigned DELTASPIKE-901:
---

Assignee: Rafael Benevides

 org.apache.deltaspike.data.impl.builder.postprocessor.CountQueryPostProcessor 
 doesn't respect order by
 --

 Key: DELTASPIKE-901
 URL: https://issues.apache.org/jira/browse/DELTASPIKE-901
 Project: DeltaSpike
  Issue Type: Bug
Affects Versions: 1.3.0
Reporter: Romain Manni-Bucau
Assignee: Rafael Benevides
 Attachments: DELTASPIKE-901.patch


 using select p from MyEntity p order by p.someString
 and
 {code}
 @Query(named = MyEntity.findAll)
 QueryResultMyEntity all(@FirstResult int start, @MaxResults int 
 pageSize);
 {code}
 I get 
 {code}
 org.apache.openjpa.lib.jdbc.ReportingSQLException: expression not in 
 aggregate or GROUP BY columns: T0.PROPERTY_KEY {SELECT 
 COUNT(t0.property_key), t0.property_key FROM properties t0} [code=-5574, 
 state=42574]
 {code}
 the count post processor doesn't handle the order by correctly.
 Wonder if we should add order by parameters in the select clause or just 
 ignore it.



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

[jira] [Commented] (DELTASPIKE-901) org.apache.deltaspike.data.impl.builder.postprocessor.CountQueryPostProcessor doesn't respect order by

[Rafael Benevides (JIRA)]

[ 
https://issues.apache.org/jira/browse/DELTASPIKE-901?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=14556595#comment-14556595
 ] 

Rafael Benevides commented on DELTASPIKE-901:
-

Patch tested and applied. Is there any more item that prevents to close this 
issue ?

 org.apache.deltaspike.data.impl.builder.postprocessor.CountQueryPostProcessor 
 doesn't respect order by
 --

 Key: DELTASPIKE-901
 URL: https://issues.apache.org/jira/browse/DELTASPIKE-901
 Project: DeltaSpike
  Issue Type: Bug
Affects Versions: 1.3.0
Reporter: Romain Manni-Bucau
 Attachments: DELTASPIKE-901.patch


 using select p from MyEntity p order by p.someString
 and
 {code}
 @Query(named = MyEntity.findAll)
 QueryResultMyEntity all(@FirstResult int start, @MaxResults int 
 pageSize);
 {code}
 I get 
 {code}
 org.apache.openjpa.lib.jdbc.ReportingSQLException: expression not in 
 aggregate or GROUP BY columns: T0.PROPERTY_KEY {SELECT 
 COUNT(t0.property_key), t0.property_key FROM properties t0} [code=-5574, 
 state=42574]
 {code}
 the count post processor doesn't handle the order by correctly.
 Wonder if we should add order by parameters in the select clause or just 
 ignore it.



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

[jira] [Resolved] (DELTASPIKE-902) Test for EntityRepository#removeAndFlush(entity)

[Rafael Benevides (JIRA)]

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

Rafael Benevides resolved DELTASPIKE-902.
-
Resolution: Fixed

 Test for EntityRepository#removeAndFlush(entity)
 

 Key: DELTASPIKE-902
 URL: https://issues.apache.org/jira/browse/DELTASPIKE-902
 Project: DeltaSpike
  Issue Type: Test
  Components: Data-Module
Affects Versions: 1.3.0
Reporter: Daniel Cunha (soro)
Assignee: Rafael Benevides
Priority: Minor
 Attachments: DELTASPIKE-902.patch






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

[jira] [Commented] (DELTASPIKE-902) Test for EntityRepository#removeAndFlush(entity)

[Rafael Benevides (JIRA)]

[ 
https://issues.apache.org/jira/browse/DELTASPIKE-902?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=14556623#comment-14556623
 ] 

Rafael Benevides commented on DELTASPIKE-902:
-

Patch tested and applied

 Test for EntityRepository#removeAndFlush(entity)
 

 Key: DELTASPIKE-902
 URL: https://issues.apache.org/jira/browse/DELTASPIKE-902
 Project: DeltaSpike
  Issue Type: Test
  Components: Data-Module
Affects Versions: 1.3.0
Reporter: Daniel Cunha (soro)
Assignee: Rafael Benevides
Priority: Minor
 Attachments: DELTASPIKE-902.patch






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

[jira] [Commented] (DELTASPIKE-908) org.apache.deltaspike.test.scheduler.custom.CustomSchedulerWarFileTest fails with Weld

[Rafael Benevides (JIRA)]

[ 
https://issues.apache.org/jira/browse/DELTASPIKE-908?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=14556557#comment-14556557
 ] 

Rafael Benevides commented on DELTASPIKE-908:
-

PR reviewed and merged!

 org.apache.deltaspike.test.scheduler.custom.CustomSchedulerWarFileTest fails 
 with Weld
 --

 Key: DELTASPIKE-908
 URL: https://issues.apache.org/jira/browse/DELTASPIKE-908
 Project: DeltaSpike
  Issue Type: Bug
  Components: Scheduler
Affects Versions: 1.3.0
Reporter: Tomas Remes
Assignee: Gerhard Petracek
Priority: Minor
 Fix For: 1.4.1


 {noformat}
 junit.framework.AssertionFailedError: expected:lt;1gt; but was:lt;0gt;
   at junit.framework.Assert.fail(Assert.java:50)
   at junit.framework.Assert.failNotEquals(Assert.java:287)
   at junit.framework.Assert.assertEquals(Assert.java:67)
   at junit.framework.Assert.assertEquals(Assert.java:199)
   at junit.framework.Assert.assertEquals(Assert.java:205)
   at 
 org.apache.deltaspike.test.scheduler.custom.CustomSchedulerTest.checkAutoRegisteredSchedulerJob(CustomSchedulerTest.java:54)
   at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
   at 
 sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:62)
   at 
 sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43)
   at java.lang.reflect.Method.invoke(Method.java:483)
   at 
 org.junit.runners.model.FrameworkMethod$1.runReflectiveCall(FrameworkMethod.java:45)
   at 
 org.junit.internal.runners.model.ReflectiveCallable.run(ReflectiveCallable.java:15)
   at 
 org.junit.runners.model.FrameworkMethod.invokeExplosively(FrameworkMethod.java:42)
   at org.jboss.arquillian.junit.Arquillian$6$1.invoke(Arquillian.java:273)
   at 
 org.jboss.arquillian.container.test.impl.execution.LocalTestExecuter.execute(LocalTestExecuter.java:60)
 {noformat}
 I am not sure what's the cause yet. I need to do further investigation. Weld 
 version doesn't matter here. 



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

[jira] [Comment Edited] (DELTASPIKE-701) Add method in EntityRepository to merge a detached entity and remove it

[Rafael Benevides (JIRA)]

[ 
https://issues.apache.org/jira/browse/DELTASPIKE-701?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=14542322#comment-14542322
 ] 

Rafael Benevides edited comment on DELTASPIKE-701 at 5/22/15 7:13 PM:
--

Patch reviewed. But since this modifies the API I would like a second 
validation on this Patch. Thanks


was (Author: rafabene):
Patch reviewed. It's good to go

 Add method in EntityRepository to merge a detached entity and remove it
 ---

 Key: DELTASPIKE-701
 URL: https://issues.apache.org/jira/browse/DELTASPIKE-701
 Project: DeltaSpike
  Issue Type: Improvement
  Components: Data-Module
Reporter: Juliano Marques
Assignee: Thomas Hug
 Attachments: DELTASPIKE-701.patch


 It will be nice if EntityRepository has a method like:
 public void attachAndRemove(Entity entity) {
 if (entityManager.contains(entity)) {
 entityManager.remove(entity);
 } else {
 entityManager.remove(entityManager.merge(entity));
 }
 }
 This method will be useful to handle java.lang.IllegalArgumentException: 
 Removing a detached instance exceptions.
 Workaround: Create a query delegate with this method.
 http://mail-archives.apache.org/mod_mbox/deltaspike-users/201408.mbox/%3CCAAuOd%3DXhb%3D-ssdzU%3DTdxWg8d18XXC15U7EjNiGya9eEgaA%2BUpA%40mail.gmail.com%3E



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

[jira] [Commented] (DELTASPIKE-603) removeBy* - similiar to findBy*

[Rafael Benevides (JIRA)]

[ 
https://issues.apache.org/jira/browse/DELTASPIKE-603?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=14556669#comment-14556669
 ] 

Rafael Benevides commented on DELTASPIKE-603:
-

The patch is outdated now. Needs to be updated.

 removeBy* - similiar to findBy*
 ---

 Key: DELTASPIKE-603
 URL: https://issues.apache.org/jira/browse/DELTASPIKE-603
 Project: DeltaSpike
  Issue Type: Improvement
  Components: Data-Module
Reporter: Thomas Andraschko
Assignee: Thomas Hug
 Attachments: DELTASPIKE-603.patch


 It would be great to allow a removeBy* - simliar to findBy*
 e.g.
 void removeByBrandId(String brandId);



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

[jira] [Created] (DELTASPIKE-909) Site/Docs/Javadoc Release procedures for DS 1.4

[Rafael Benevides (JIRA)]

Rafael Benevides created DELTASPIKE-909:
---

 Summary: Site/Docs/Javadoc Release procedures for DS 1.4
 Key: DELTASPIKE-909
 URL: https://issues.apache.org/jira/browse/DELTASPIKE-909
 Project: DeltaSpike
  Issue Type: Task
  Components: Documentation
Affects Versions: 1.4.0
Reporter: Rafael Benevides
Assignee: Rafael Benevides
 Fix For: 1.4.0






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

[jira] [Resolved] (DELTASPIKE-909) Site/Docs/Javadoc Release procedures for DS 1.4

[Rafael Benevides (JIRA)]

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

Rafael Benevides resolved DELTASPIKE-909.
-
Resolution: Fixed

 Site/Docs/Javadoc Release procedures for DS 1.4
 ---

 Key: DELTASPIKE-909
 URL: https://issues.apache.org/jira/browse/DELTASPIKE-909
 Project: DeltaSpike
  Issue Type: Task
  Components: Documentation
Affects Versions: 1.4.0
Reporter: Rafael Benevides
Assignee: Rafael Benevides
 Fix For: 1.4.0






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

[jira] [Commented] (DELTASPIKE-909) Site/Docs/Javadoc Release procedures for DS 1.4

[Rafael Benevides (JIRA)]

[ 
https://issues.apache.org/jira/browse/DELTASPIKE-909?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=1428#comment-1428
 ] 

Rafael Benevides commented on DELTASPIKE-909:
-

Commit: 
https://github.com/apache/deltaspike/commit/391dbb4d81944e00b2a8dbee39bfd33eb4f6a93d

 Site/Docs/Javadoc Release procedures for DS 1.4
 ---

 Key: DELTASPIKE-909
 URL: https://issues.apache.org/jira/browse/DELTASPIKE-909
 Project: DeltaSpike
  Issue Type: Task
  Components: Documentation
Affects Versions: 1.4.0
Reporter: Rafael Benevides
Assignee: Rafael Benevides
 Fix For: 1.4.0






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

[jira] [Assigned] (DELTASPIKE-906) Extract debug information in pom.xml and put in documentation.

[Rafael Benevides (JIRA)]

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

Rafael Benevides reassigned DELTASPIKE-906:
---

Assignee: Rafael Benevides

 Extract debug information in pom.xml and put in documentation.
 --

 Key: DELTASPIKE-906
 URL: https://issues.apache.org/jira/browse/DELTASPIKE-906
 Project: DeltaSpike
  Issue Type: Task
Reporter: Daniel Cunha (soro)
Assignee: Rafael Benevides
Priority: Trivial

 In parent/code/pom.xml we have this: 
 * DEBUGGING:
 * mvn test -Ptomee-build-managed -Dtest=UnitTestName 
 -Dopenejb.server.debug=true
 * then use remote debuggig at port 5005
 Maybe this information should be in DeltaSpike documentation.



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

[jira] [Resolved] (DELTASPIKE-906) Extract debug information in pom.xml and put in documentation.

[Rafael Benevides (JIRA)]

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

Rafael Benevides resolved DELTASPIKE-906.
-
Resolution: Fixed

PR merged!

 Extract debug information in pom.xml and put in documentation.
 --

 Key: DELTASPIKE-906
 URL: https://issues.apache.org/jira/browse/DELTASPIKE-906
 Project: DeltaSpike
  Issue Type: Task
Reporter: Daniel Cunha (soro)
Assignee: Rafael Benevides
Priority: Trivial

 In parent/code/pom.xml we have this: 
 * DEBUGGING:
 * mvn test -Ptomee-build-managed -Dtest=UnitTestName 
 -Dopenejb.server.debug=true
 * then use remote debuggig at port 5005
 Maybe this information should be in DeltaSpike documentation.



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

[jira] [Commented] (DELTASPIKE-701) Add method in EntityRepository to merge a detached entity and remove it

[Rafael Benevides (JIRA)]

[ 
https://issues.apache.org/jira/browse/DELTASPIKE-701?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=14542322#comment-14542322
 ] 

Rafael Benevides commented on DELTASPIKE-701:
-

Patch reviewed. It's good to go

 Add method in EntityRepository to merge a detached entity and remove it
 ---

 Key: DELTASPIKE-701
 URL: https://issues.apache.org/jira/browse/DELTASPIKE-701
 Project: DeltaSpike
  Issue Type: Improvement
  Components: Data-Module
Reporter: Juliano Marques
Assignee: Thomas Hug
 Attachments: DELTASPIKE-701.patch


 It will be nice if EntityRepository has a method like:
 public void attachAndRemove(Entity entity) {
 if (entityManager.contains(entity)) {
 entityManager.remove(entity);
 } else {
 entityManager.remove(entityManager.merge(entity));
 }
 }
 This method will be useful to handle java.lang.IllegalArgumentException: 
 Removing a detached instance exceptions.
 Workaround: Create a query delegate with this method.
 http://mail-archives.apache.org/mod_mbox/deltaspike-users/201408.mbox/%3CCAAuOd%3DXhb%3D-ssdzU%3DTdxWg8d18XXC15U7EjNiGya9eEgaA%2BUpA%40mail.gmail.com%3E



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

[jira] [Commented] (DELTASPIKE-894) Trim for CriteriaSupport API

[Rafael Benevides (JIRA)]

[ 
https://issues.apache.org/jira/browse/DELTASPIKE-894?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=14542334#comment-14542334
 ] 

Rafael Benevides commented on DELTASPIKE-894:
-

It looks ok but I'd like a second opinion here on the API.

 Trim for CriteriaSupport API
 

 Key: DELTASPIKE-894
 URL: https://issues.apache.org/jira/browse/DELTASPIKE-894
 Project: DeltaSpike
  Issue Type: New Feature
  Components: Data-Module
Reporter: Daniel Cunha (soro)
Assignee: Thomas Hug
Priority: Minor
 Attachments: DELTASPIKE-894.patch






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

[jira] [Resolved] (DELTASPIKE-899) Build fail for OWB15

[Rafael Benevides (JIRA)]

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

Rafael Benevides resolved DELTASPIKE-899.
-
Resolution: Pending Closed

Fixed: 
https://github.com/apache/deltaspike/commit/1c828f3fd35cdbd353bc9ed6a763f4624b49022a

 Build fail for OWB15
 

 Key: DELTASPIKE-899
 URL: https://issues.apache.org/jira/browse/DELTASPIKE-899
 Project: DeltaSpike
  Issue Type: Bug
Reporter: Rafael Benevides
Assignee: Rafael Benevides

 There seems to be an issue with the owb15 profile. it basically works, just 3 
 tests fails because there is somewhere a dependency which pulls in the cdi 
 1.0 api instead cdi 1.1.
 How to test:
 {code}
 mvn clean install -POWB15 -Dowb.version=1.5.0
 {code}
 Failing build: 
 https://builds.apache.org/view/A-D/view/DeltaSpike/job/DeltaSpike%20OWB%201.5.0/
 Extra info: The openejb tests just fail because we need to wait for a new 
 release which contains the cdi 1.1 api but the jsf module should pass already



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

[jira] [Created] (DELTASPIKE-899) Build fail for OWB15

[Rafael Benevides (JIRA)]

Rafael Benevides created DELTASPIKE-899:
---

 Summary: Build fail for OWB15
 Key: DELTASPIKE-899
 URL: https://issues.apache.org/jira/browse/DELTASPIKE-899
 Project: DeltaSpike
  Issue Type: Bug
Reporter: Rafael Benevides
Assignee: Rafael Benevides


There seems to be an issue with the owb15 profile. it basically works, just 3 
tests fails because there is somewhere a dependency which pulls in the cdi 1.0 
api instead cdi 1.1.

How to test:
{code}
mvn clean install -POWB15 -Dowb.version=1.5.0
{code}

Failing build: 
https://builds.apache.org/view/A-D/view/DeltaSpike/job/DeltaSpike%20OWB%201.5.0/

Extra info: The openejb tests just fail because we need to wait for a new 
release which contains the cdi 1.1 api but the jsf module should pass already



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

[jira] [Resolved] (DELTASPIKE-882) Create a new module for proxy

[Rafael Benevides (JIRA)]

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

Rafael Benevides resolved DELTASPIKE-882.
-
Resolution: Fixed

PR merged

 Create a new module for proxy
 -

 Key: DELTASPIKE-882
 URL: https://issues.apache.org/jira/browse/DELTASPIKE-882
 Project: DeltaSpike
  Issue Type: Improvement
  Components: Core
Reporter: Rafael Benevides
Assignee: Rafael Benevides
Priority: Blocker
 Fix For: 1.4.0


 We are now using asm to create our own proxies - with 1.3.0 that was added to 
 the partial bean module - now We replace the optional proxies created in the 
 JSF module for converters/validators with the same approach - the proxy code 
 was moved to ds-core. that works but isn't nice and not that flexible - the 
 goal is an own module side by side with core and all modules which need 
 proxy stuff have core and that new proxy module as dep. (currently the 
 partial-bean and JSF module).It allows to support different versions of asm 
 once it's needed... (e.g. for diff. versions of java if the latest version 
 drops e.g. backward compat. to and old version...) It's already discussed and 
 agreed on the dev list so you can just create a ticket and just move the code 
 + update the release poms so that the new module is part of the release as 
 well...
 The new module should be called proxy-utils. GAV: 
 org.apache.deltaspike.modules:deltaspike-proxy-module-api
 *don't* move org.apache.deltaspike.core.util.ProxyUtils - because it doesn't 
 depend on asm and is valid for any proxy (weld-proxy, owb-proxy, 
 javassist-proxy,...) We support at all + it's needed a lot in ds-core. If you 
 would move it ds-core would depend on the proxy-module (which shouldn't be 
 the case).
 The goal is really that the proxy-module is just needed once you need the 
 partial-bean module and/or the optional proxies in the JSF module so the 
 proxy-module needs to be an optional dep. of the JSF module... but in case of 
 the partial-bean module the proxy-api module is a compile dep. since it's 
 required anyway
 That's currently the release blocker, because now ds-core has a dependency to 
 a fixed version of asm and so far Core didn't introduce a 3rd party dep. So 
 We need to move to the new module before the next release...



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

[jira] [Resolved] (DELTASPIKE-893) Remove erroneous WarpTest annotation and Warp dependency from JSF impl tests

[Rafael Benevides (JIRA)]

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

Rafael Benevides resolved DELTASPIKE-893.
-
Resolution: Fixed

Fixed: 
https://github.com/apache/deltaspike/commit/320ae6e1ffb856276c4864d540d003d65d530976

 Remove erroneous WarpTest annotation and Warp dependency from JSF impl tests
 

 Key: DELTASPIKE-893
 URL: https://issues.apache.org/jira/browse/DELTASPIKE-893
 Project: DeltaSpike
  Issue Type: Bug
  Components: Tests
Affects Versions: 1.3.0
Reporter: Ron Smeral
Assignee: Rafael Benevides
 Fix For: 1.4.0


 Many tests in the JSF impl module are annotated {{@WarpTest}} and the 
 {{modules/jsf/impl/pom.xml}} contains {{arquillian-warp-api}} dependency.
 Tests annotated WarpTest:
 https://github.com/apache/deltaspike/search?utf8=%E2%9C%93q=WarpTesttype=Code
 However, the Warp API doesn't seem to be used at all. 
 Therefore, the dependency and annotation on tests (and import) should most 
 likely be removed.
 For reference, see https://github.com/arquillian/arquillian-extension-warp on 
 how Warp API is used and for what purpose. It is used for making server-side 
 assertions in client-side tests.



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

[jira] [Commented] (DELTASPIKE-882) Create a new module for proxy

[Rafael Benevides (JIRA)]

[ 
https://issues.apache.org/jira/browse/DELTASPIKE-882?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=14518100#comment-14518100
 ] 

Rafael Benevides commented on DELTASPIKE-882:
-

The following PR was opened for discussion: 
https://github.com/apache/deltaspike/pull/30

 Create a new module for proxy
 -

 Key: DELTASPIKE-882
 URL: https://issues.apache.org/jira/browse/DELTASPIKE-882
 Project: DeltaSpike
  Issue Type: Improvement
  Components: Core
Affects Versions: 1.3.0, 1.3.1
Reporter: Rafael Benevides
Assignee: Rafael Benevides
Priority: Blocker
 Fix For: 1.4.0


 We are now using asm to create our own proxies - with 1.3.0 that was added to 
 the partial bean module - now We replace the optional proxies created in the 
 JSF module for converters/validators with the same approach - the proxy code 
 was moved to ds-core. that works but isn't nice and not that flexible - the 
 goal is an own module side by side with core and all modules which need 
 proxy stuff have core and that new proxy module as dep. (currently the 
 partial-bean and JSF module).It allows to support different versions of asm 
 once it's needed... (e.g. for diff. versions of java if the latest version 
 drops e.g. backward compat. to and old version...) It's already discussed and 
 agreed on the dev list so you can just create a ticket and just move the code 
 + update the release poms so that the new module is part of the release as 
 well...
 The new module should be called proxy-utils. GAV: 
 org.apache.deltaspike.modules:deltaspike-proxy-module-api
 *don't* move org.apache.deltaspike.core.util.ProxyUtils - because it doesn't 
 depend on asm and is valid for any proxy (weld-proxy, owb-proxy, 
 javassist-proxy,...) We support at all + it's needed a lot in ds-core. If you 
 would move it ds-core would depend on the proxy-module (which shouldn't be 
 the case).
 The goal is really that the proxy-module is just needed once you need the 
 partial-bean module and/or the optional proxies in the JSF module so the 
 proxy-module needs to be an optional dep. of the JSF module... but in case of 
 the partial-bean module the proxy-api module is a compile dep. since it's 
 required anyway
 That's currently the release blocker, because now ds-core has a dependency to 
 a fixed version of asm and so far Core didn't introduce a 3rd party dep. So 
 We need to move to the new module before the next release...



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

[jira] [Created] (DELTASPIKE-883) Create a new module for proxy

[Rafael Benevides (JIRA)]

Rafael Benevides created DELTASPIKE-883:
---

 Summary: Create a new module for proxy
 Key: DELTASPIKE-883
 URL: https://issues.apache.org/jira/browse/DELTASPIKE-883
 Project: DeltaSpike
  Issue Type: Improvement
  Components: Core
Affects Versions: 1.3.0, 1.3.1
Reporter: Rafael Benevides
Assignee: Rafael Benevides
Priority: Blocker
 Fix For: 1.4.0


We are now using asm to create our own proxies - with 1.3.0 that was added to 
the partial bean module - now We replace the optional proxies created in the 
JSF module for converters/validators with the same approach - the proxy code 
was moved to ds-core. that works but isn't nice and not that flexible - the 
goal is an own module side by side with core and all modules which need proxy 
stuff have core and that new proxy module as dep. (currently the partial-bean 
and JSF module).It allows to support different versions of asm once it's 
needed... (e.g. for diff. versions of java if the latest version drops e.g. 
backward compat. to and old version...) It's already discussed and agreed on 
the dev list so you can just create a ticket and just move the code + update 
the release poms so that the new module is part of the release as well...

The new module should be called proxy-utils. GAV: 
org.apache.deltaspike.modules:deltaspike-proxy-module-api

*don't* move org.apache.deltaspike.core.util.ProxyUtils - because it doesn't 
depend on asm and is valid for any proxy (weld-proxy, owb-proxy, 
javassist-proxy,...) We support at all + it's needed a lot in ds-core. If you 
would move it ds-core would depend on the proxy-module (which shouldn't be the 
case).

The goal is really that the proxy-module is just needed once you need the 
partial-bean module and/or the optional proxies in the JSF module so the 
proxy-module needs to be an optional dep. of the JSF module... but in case of 
the partial-bean module the proxy-api module is a compile dep. since it's 
required anyway

That's currently the release blocker, because now ds-core has a dependency to a 
fixed version of asm and so far Core didn't introduce a 3rd party dep. So We 
need to move to the new module before the next release...






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

[jira] [Created] (DELTASPIKE-882) Create a new module for proxy

[Rafael Benevides (JIRA)]

Rafael Benevides created DELTASPIKE-882:
---

 Summary: Create a new module for proxy
 Key: DELTASPIKE-882
 URL: https://issues.apache.org/jira/browse/DELTASPIKE-882
 Project: DeltaSpike
  Issue Type: Improvement
  Components: Core
Affects Versions: 1.3.0, 1.3.1
Reporter: Rafael Benevides
Assignee: Rafael Benevides
Priority: Blocker
 Fix For: 1.4.0


We are now using asm to create our own proxies - with 1.3.0 that was added to 
the partial bean module - now We replace the optional proxies created in the 
JSF module for converters/validators with the same approach - the proxy code 
was moved to ds-core. that works but isn't nice and not that flexible - the 
goal is an own module side by side with core and all modules which need proxy 
stuff have core and that new proxy module as dep. (currently the partial-bean 
and JSF module).It allows to support different versions of asm once it's 
needed... (e.g. for diff. versions of java if the latest version drops e.g. 
backward compat. to and old version...) It's already discussed and agreed on 
the dev list so you can just create a ticket and just move the code + update 
the release poms so that the new module is part of the release as well...

The new module should be called proxy-utils. GAV: 
org.apache.deltaspike.modules:deltaspike-proxy-module-api

*don't* move org.apache.deltaspike.core.util.ProxyUtils - because it doesn't 
depend on asm and is valid for any proxy (weld-proxy, owb-proxy, 
javassist-proxy,...) We support at all + it's needed a lot in ds-core. If you 
would move it ds-core would depend on the proxy-module (which shouldn't be the 
case).

The goal is really that the proxy-module is just needed once you need the 
partial-bean module and/or the optional proxies in the JSF module so the 
proxy-module needs to be an optional dep. of the JSF module... but in case of 
the partial-bean module the proxy-api module is a compile dep. since it's 
required anyway

That's currently the release blocker, because now ds-core has a dependency to a 
fixed version of asm and so far Core didn't introduce a 3rd party dep. So We 
need to move to the new module before the next release...






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

[jira] [Closed] (DELTASPIKE-883) Create a new module for proxy

[Rafael Benevides (JIRA)]

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

Rafael Benevides closed DELTASPIKE-883.
---
Resolution: Duplicate

duplicated with DELTASPIKE-882

 Create a new module for proxy
 -

 Key: DELTASPIKE-883
 URL: https://issues.apache.org/jira/browse/DELTASPIKE-883
 Project: DeltaSpike
  Issue Type: Improvement
  Components: Core
Affects Versions: 1.3.0, 1.3.1
Reporter: Rafael Benevides
Assignee: Rafael Benevides
Priority: Blocker
 Fix For: 1.4.0


 We are now using asm to create our own proxies - with 1.3.0 that was added to 
 the partial bean module - now We replace the optional proxies created in the 
 JSF module for converters/validators with the same approach - the proxy code 
 was moved to ds-core. that works but isn't nice and not that flexible - the 
 goal is an own module side by side with core and all modules which need 
 proxy stuff have core and that new proxy module as dep. (currently the 
 partial-bean and JSF module).It allows to support different versions of asm 
 once it's needed... (e.g. for diff. versions of java if the latest version 
 drops e.g. backward compat. to and old version...) It's already discussed and 
 agreed on the dev list so you can just create a ticket and just move the code 
 + update the release poms so that the new module is part of the release as 
 well...
 The new module should be called proxy-utils. GAV: 
 org.apache.deltaspike.modules:deltaspike-proxy-module-api
 *don't* move org.apache.deltaspike.core.util.ProxyUtils - because it doesn't 
 depend on asm and is valid for any proxy (weld-proxy, owb-proxy, 
 javassist-proxy,...) We support at all + it's needed a lot in ds-core. If you 
 would move it ds-core would depend on the proxy-module (which shouldn't be 
 the case).
 The goal is really that the proxy-module is just needed once you need the 
 partial-bean module and/or the optional proxies in the JSF module so the 
 proxy-module needs to be an optional dep. of the JSF module... but in case of 
 the partial-bean module the proxy-api module is a compile dep. since it's 
 required anyway
 That's currently the release blocker, because now ds-core has a dependency to 
 a fixed version of asm and so far Core didn't introduce a 3rd party dep. So 
 We need to move to the new module before the next release...



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

[jira] [Commented] (DELTASPIKE-875) HTTPS support for site and documentation

[Rafael Benevides (JIRA)]

[ 
https://issues.apache.org/jira/browse/DELTASPIKE-875?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=14500260#comment-14500260
 ] 

Rafael Benevides commented on DELTASPIKE-875:
-

I mean, the same changes applied by this PR is also on the DELTASPIKE-876 PR.

 HTTPS support for site and documentation
 

 Key: DELTASPIKE-875
 URL: https://issues.apache.org/jira/browse/DELTASPIKE-875
 Project: DeltaSpike
  Issue Type: Improvement
  Components: Documentation
Reporter: Ron Smeral
Assignee: Ron Smeral
Priority: Minor

 Currently, HTTPS access to DS website is slightly broken due to some HTTP 
 elements which should be HTTPS (google site search, font awesome link, ..).
 That yields browser warnings and broken icons in documentation.



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

[jira] [Updated] (DELTASPIKE-876) Website navigation bar active tab highlighting broken

[Rafael Benevides (JIRA)]

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

Rafael Benevides updated DELTASPIKE-876:

Assignee: Ron Smeral

 Website navigation bar active tab highlighting broken
 -

 Key: DELTASPIKE-876
 URL: https://issues.apache.org/jira/browse/DELTASPIKE-876
 Project: DeltaSpike
  Issue Type: Bug
  Components: Documentation
Reporter: Ron Smeral
Assignee: Ron Smeral
Priority: Minor

 The website currently always shows Home as the active tab.



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

[jira] [Updated] (DELTASPIKE-875) HTTPS support for site and documentation

[Rafael Benevides (JIRA)]

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

Rafael Benevides updated DELTASPIKE-875:

Assignee: Ron Smeral

 HTTPS support for site and documentation
 

 Key: DELTASPIKE-875
 URL: https://issues.apache.org/jira/browse/DELTASPIKE-875
 Project: DeltaSpike
  Issue Type: Improvement
  Components: Documentation
Reporter: Ron Smeral
Assignee: Ron Smeral
Priority: Minor

 Currently, HTTPS access to DS website is slightly broken due to some HTTP 
 elements which should be HTTPS (google site search, font awesome link, ..).
 That yields browser warnings and broken icons in documentation.



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

[jira] [Comment Edited] (DELTASPIKE-875) HTTPS support for site and documentation

[Rafael Benevides (JIRA)]

[ 
https://issues.apache.org/jira/browse/DELTASPIKE-875?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=14500202#comment-14500202
 ] 

Rafael Benevides edited comment on DELTASPIKE-875 at 4/17/15 5:07 PM:
--

It seems that you handle it in DELTASPIKE-876, right ?


was (Author: rafabene):
It seems that you handle it in DELTASPIKE--876, right ?

 HTTPS support for site and documentation
 

 Key: DELTASPIKE-875
 URL: https://issues.apache.org/jira/browse/DELTASPIKE-875
 Project: DeltaSpike
  Issue Type: Improvement
  Components: Documentation
Reporter: Ron Smeral
Assignee: Ron Smeral
Priority: Minor

 Currently, HTTPS access to DS website is slightly broken due to some HTTP 
 elements which should be HTTPS (google site search, font awesome link, ..).
 That yields browser warnings and broken icons in documentation.



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

[jira] [Commented] (DELTASPIKE-875) HTTPS support for site and documentation

[Rafael Benevides (JIRA)]

[ 
https://issues.apache.org/jira/browse/DELTASPIKE-875?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=14500202#comment-14500202
 ] 

Rafael Benevides commented on DELTASPIKE-875:
-

It seems that you handle it in DELTASPIKE--876, right ?

 HTTPS support for site and documentation
 

 Key: DELTASPIKE-875
 URL: https://issues.apache.org/jira/browse/DELTASPIKE-875
 Project: DeltaSpike
  Issue Type: Improvement
  Components: Documentation
Reporter: Ron Smeral
Assignee: Ron Smeral
Priority: Minor

 Currently, HTTPS access to DS website is slightly broken due to some HTTP 
 elements which should be HTTPS (google site search, font awesome link, ..).
 That yields browser warnings and broken icons in documentation.



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

[jira] [Comment Edited] (DELTASPIKE-874) observe @javax.faces.bean.RequestScoped via @javax.enterprise.context.Initialized and @javax.enterprise.context.Destroyed

[Rafael Benevides (JIRA)]

[ 
https://issues.apache.org/jira/browse/DELTASPIKE-874?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=14496319#comment-14496319
 ] 

Rafael Benevides edited comment on DELTASPIKE-874 at 4/15/15 3:11 PM:
--

This is how I documented it (Staging site):  
http://deltaspike.apache.org/staging/documentation/jsf.html#_observing_jsf_requests

If there are no objections I'll publish it on production.


was (Author: rafabene):
This is how I documented it: 
http://deltaspike.apache.org/staging/documentation/jsf.html#_observing_jsf_requests

If there are no objections I'll publish it on production.

 observe @javax.faces.bean.RequestScoped via 
 @javax.enterprise.context.Initialized and @javax.enterprise.context.Destroyed
 -

 Key: DELTASPIKE-874
 URL: https://issues.apache.org/jira/browse/DELTASPIKE-874
 Project: DeltaSpike
  Issue Type: New Feature
  Components: JSF-Module
Affects Versions: 1.3.0
Reporter: Mark Struberg
Assignee: Gerhard Petracek
 Fix For: 1.3.1


 currently it's supported to observe faces-requests via 
 org.apache.deltaspike.core.api.lifecycle.Initialized and 
 org.apache.deltaspike.core.api.lifecycle.Destroyed
 since cdi 1.1 there are annotations with the same name.
 to avoid confusion, we can support those annotations optionally (if cdi 1.1+ 
 is available). both cdi 1.1+ annotations require the corresponding 
 scope-annotation as value. since javax.enterprise.context.RequestScoped is 
 supported out-of-the-box and this event is about the faces-request, we have 
 to use javax.faces.bean.RequestScoped.
 the benefit is that it's possible to observe faces-requests via std. 
 annotations and it's possible to access the faces-context (which isn't the 
 case with an observer for javax.enterprise.context.RequestScoped).
 cdi 1.1+ out-of-the-box support:
 {code}
 protected void onRequestStart(@Observes 
 @javax.enterprise.context.Initialized(javax.enterprise.context.RequestScoped.class)
  Object payload) {
 //...
 }
 protected void onRequestEnd(@Observes 
 @javax.enterprise.context.Destroyed(javax.enterprise.context.RequestScoped.class)
  Object payload) {
 //...
 }
 {code}
 ds observer for cdi 1.0+
 {code}
 protected void onFacesRequestStart(@Observes 
 @org.apache.deltaspike.core.api.lifecycle.Initialized FacesContext 
 facesContext) {
 //...
 }
 protected void onFacesRequestEnd(@Observes 
 @org.apache.deltaspike.core.api.lifecycle.Destroyed FacesContext 
 facesContext) {
 //...
 }
 {code}
 additional option for cdi 1.1+ introduced by this ticket:
 {code}
 protected void onFacesRequestStart(@Observes 
 @javax.enterprise.context.Initialized(javax.faces.bean.RequestScoped.class) 
 FacesContext facesContext) {
 //...
 }
 protected void onFacesRequestEnd(@Observes 
 @javax.enterprise.context.Destroyed(javax.faces.bean.RequestScoped.class) 
 FacesContext facesContext) {
 //...
 }
 {code}



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

[jira] [Commented] (DELTASPIKE-874) observe @javax.faces.bean.RequestScoped via @javax.enterprise.context.Initialized and @javax.enterprise.context.Destroyed

[Rafael Benevides (JIRA)]

[ 
https://issues.apache.org/jira/browse/DELTASPIKE-874?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=14496319#comment-14496319
 ] 

Rafael Benevides commented on DELTASPIKE-874:
-

This is how I documented it: 
http://deltaspike.apache.org/staging/documentation/jsf.html#_observing_jsf_requests

If there are no objections I'll publish it on production.

 observe @javax.faces.bean.RequestScoped via 
 @javax.enterprise.context.Initialized and @javax.enterprise.context.Destroyed
 -

 Key: DELTASPIKE-874
 URL: https://issues.apache.org/jira/browse/DELTASPIKE-874
 Project: DeltaSpike
  Issue Type: New Feature
  Components: JSF-Module
Affects Versions: 1.3.0
Reporter: Mark Struberg
Assignee: Gerhard Petracek
 Fix For: 1.3.1


 currently it's supported to observe faces-requests via 
 org.apache.deltaspike.core.api.lifecycle.Initialized and 
 org.apache.deltaspike.core.api.lifecycle.Destroyed
 since cdi 1.1 there are annotations with the same name.
 to avoid confusion, we can support those annotations optionally (if cdi 1.1+ 
 is available). both cdi 1.1+ annotations require the corresponding 
 scope-annotation as value. since javax.enterprise.context.RequestScoped is 
 supported out-of-the-box and this event is about the faces-request, we have 
 to use javax.faces.bean.RequestScoped.
 the benefit is that it's possible to observe faces-requests via std. 
 annotations and it's possible to access the faces-context (which isn't the 
 case with an observer for javax.enterprise.context.RequestScoped).
 cdi 1.1+ out-of-the-box support:
 {code}
 protected void onRequestStart(@Observes 
 @javax.enterprise.context.Initialized(javax.enterprise.context.RequestScoped.class)
  Object payload) {
 //...
 }
 protected void onRequestEnd(@Observes 
 @javax.enterprise.context.Destroyed(javax.enterprise.context.RequestScoped.class)
  Object payload) {
 //...
 }
 {code}
 ds observer for cdi 1.0+
 {code}
 protected void onFacesRequestStart(@Observes 
 @org.apache.deltaspike.core.api.lifecycle.Initialized FacesContext 
 facesContext) {
 //...
 }
 protected void onFacesRequestEnd(@Observes 
 @org.apache.deltaspike.core.api.lifecycle.Destroyed FacesContext 
 facesContext) {
 //...
 }
 {code}
 additional option for cdi 1.1+ introduced by this ticket:
 {code}
 protected void onFacesRequestStart(@Observes 
 @javax.enterprise.context.Initialized(javax.faces.bean.RequestScoped.class) 
 FacesContext facesContext) {
 //...
 }
 protected void onFacesRequestEnd(@Observes 
 @javax.enterprise.context.Destroyed(javax.faces.bean.RequestScoped.class) 
 FacesContext facesContext) {
 //...
 }
 {code}



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

[jira] [Commented] (DELTASPIKE-874) observe @javax.faces.bean.RequestScoped via @javax.enterprise.context.Initialized and @javax.enterprise.context.Destroyed

[Rafael Benevides (JIRA)]

[ 
https://issues.apache.org/jira/browse/DELTASPIKE-874?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=14497123#comment-14497123
 ] 

Rafael Benevides commented on DELTASPIKE-874:
-

Another proposal: 
http://deltaspike.apache.org/staging/documentation/jsf#_observe_faces_requests

 observe @javax.faces.bean.RequestScoped via 
 @javax.enterprise.context.Initialized and @javax.enterprise.context.Destroyed
 -

 Key: DELTASPIKE-874
 URL: https://issues.apache.org/jira/browse/DELTASPIKE-874
 Project: DeltaSpike
  Issue Type: New Feature
  Components: JSF-Module
Affects Versions: 1.3.0
Reporter: Mark Struberg
Assignee: Gerhard Petracek
 Fix For: 1.3.1


 currently it's supported to observe faces-requests via 
 org.apache.deltaspike.core.api.lifecycle.Initialized and 
 org.apache.deltaspike.core.api.lifecycle.Destroyed
 since cdi 1.1 there are annotations with the same name.
 to avoid confusion, we can support those annotations optionally (if cdi 1.1+ 
 is available). both cdi 1.1+ annotations require the corresponding 
 scope-annotation as value. since javax.enterprise.context.RequestScoped is 
 supported out-of-the-box and this event is about the faces-request, we have 
 to use javax.faces.bean.RequestScoped.
 the benefit is that it's possible to observe faces-requests via std. 
 annotations and it's possible to access the faces-context (which isn't the 
 case with an observer for javax.enterprise.context.RequestScoped).
 cdi 1.1+ out-of-the-box support:
 {code}
 protected void onRequestStart(@Observes 
 @javax.enterprise.context.Initialized(javax.enterprise.context.RequestScoped.class)
  Object payload) {
 //...
 }
 protected void onRequestEnd(@Observes 
 @javax.enterprise.context.Destroyed(javax.enterprise.context.RequestScoped.class)
  Object payload) {
 //...
 }
 {code}
 ds observer for cdi 1.0+
 {code}
 protected void onFacesRequestStart(@Observes 
 @org.apache.deltaspike.core.api.lifecycle.Initialized FacesContext 
 facesContext) {
 //...
 }
 protected void onFacesRequestEnd(@Observes 
 @org.apache.deltaspike.core.api.lifecycle.Destroyed FacesContext 
 facesContext) {
 //...
 }
 {code}
 additional option for cdi 1.1+ introduced by this ticket:
 {code}
 protected void onFacesRequestStart(@Observes 
 @javax.enterprise.context.Initialized(javax.faces.bean.RequestScoped.class) 
 FacesContext facesContext) {
 //...
 }
 protected void onFacesRequestEnd(@Observes 
 @javax.enterprise.context.Destroyed(javax.faces.bean.RequestScoped.class) 
 FacesContext facesContext) {
 //...
 }
 {code}



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

[jira] [Commented] (DELTASPIKE-874) observe @javax.faces.bean.RequestScoped via @javax.enterprise.context.Initialized and @javax.enterprise.context.Destroyed

[Rafael Benevides (JIRA)]

[ 
https://issues.apache.org/jira/browse/DELTASPIKE-874?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=14497025#comment-14497025
 ] 

Rafael Benevides commented on DELTASPIKE-874:
-

I realised that this is already documented here: 
http://deltaspike.apache.org/documentation/jsf#_event_broadcasting Or Am I 
missing something about DELTASPIKE-874 ?

 observe @javax.faces.bean.RequestScoped via 
 @javax.enterprise.context.Initialized and @javax.enterprise.context.Destroyed
 -

 Key: DELTASPIKE-874
 URL: https://issues.apache.org/jira/browse/DELTASPIKE-874
 Project: DeltaSpike
  Issue Type: New Feature
  Components: JSF-Module
Affects Versions: 1.3.0
Reporter: Mark Struberg
Assignee: Gerhard Petracek
 Fix For: 1.3.1


 currently it's supported to observe faces-requests via 
 org.apache.deltaspike.core.api.lifecycle.Initialized and 
 org.apache.deltaspike.core.api.lifecycle.Destroyed
 since cdi 1.1 there are annotations with the same name.
 to avoid confusion, we can support those annotations optionally (if cdi 1.1+ 
 is available). both cdi 1.1+ annotations require the corresponding 
 scope-annotation as value. since javax.enterprise.context.RequestScoped is 
 supported out-of-the-box and this event is about the faces-request, we have 
 to use javax.faces.bean.RequestScoped.
 the benefit is that it's possible to observe faces-requests via std. 
 annotations and it's possible to access the faces-context (which isn't the 
 case with an observer for javax.enterprise.context.RequestScoped).
 cdi 1.1+ out-of-the-box support:
 {code}
 protected void onRequestStart(@Observes 
 @javax.enterprise.context.Initialized(javax.enterprise.context.RequestScoped.class)
  Object payload) {
 //...
 }
 protected void onRequestEnd(@Observes 
 @javax.enterprise.context.Destroyed(javax.enterprise.context.RequestScoped.class)
  Object payload) {
 //...
 }
 {code}
 ds observer for cdi 1.0+
 {code}
 protected void onFacesRequestStart(@Observes 
 @org.apache.deltaspike.core.api.lifecycle.Initialized FacesContext 
 facesContext) {
 //...
 }
 protected void onFacesRequestEnd(@Observes 
 @org.apache.deltaspike.core.api.lifecycle.Destroyed FacesContext 
 facesContext) {
 //...
 }
 {code}
 additional option for cdi 1.1+ introduced by this ticket:
 {code}
 protected void onFacesRequestStart(@Observes 
 @javax.enterprise.context.Initialized(javax.faces.bean.RequestScoped.class) 
 FacesContext facesContext) {
 //...
 }
 protected void onFacesRequestEnd(@Observes 
 @javax.enterprise.context.Destroyed(javax.faces.bean.RequestScoped.class) 
 FacesContext facesContext) {
 //...
 }
 {code}



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

[jira] [Issue Comment Deleted] (DELTASPIKE-874) observe @javax.faces.bean.RequestScoped via @javax.enterprise.context.Initialized and @javax.enterprise.context.Destroyed

[Rafael Benevides (JIRA)]

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

Rafael Benevides updated DELTASPIKE-874:

Comment: was deleted

(was: I realised that this is already documented here: 
http://deltaspike.apache.org/documentation/jsf#_event_broadcasting Or Am I 
missing something about DELTASPIKE-874 ?)

 observe @javax.faces.bean.RequestScoped via 
 @javax.enterprise.context.Initialized and @javax.enterprise.context.Destroyed
 -

 Key: DELTASPIKE-874
 URL: https://issues.apache.org/jira/browse/DELTASPIKE-874
 Project: DeltaSpike
  Issue Type: New Feature
  Components: JSF-Module
Affects Versions: 1.3.0
Reporter: Mark Struberg
Assignee: Gerhard Petracek
 Fix For: 1.3.1


 currently it's supported to observe faces-requests via 
 org.apache.deltaspike.core.api.lifecycle.Initialized and 
 org.apache.deltaspike.core.api.lifecycle.Destroyed
 since cdi 1.1 there are annotations with the same name.
 to avoid confusion, we can support those annotations optionally (if cdi 1.1+ 
 is available). both cdi 1.1+ annotations require the corresponding 
 scope-annotation as value. since javax.enterprise.context.RequestScoped is 
 supported out-of-the-box and this event is about the faces-request, we have 
 to use javax.faces.bean.RequestScoped.
 the benefit is that it's possible to observe faces-requests via std. 
 annotations and it's possible to access the faces-context (which isn't the 
 case with an observer for javax.enterprise.context.RequestScoped).
 cdi 1.1+ out-of-the-box support:
 {code}
 protected void onRequestStart(@Observes 
 @javax.enterprise.context.Initialized(javax.enterprise.context.RequestScoped.class)
  Object payload) {
 //...
 }
 protected void onRequestEnd(@Observes 
 @javax.enterprise.context.Destroyed(javax.enterprise.context.RequestScoped.class)
  Object payload) {
 //...
 }
 {code}
 ds observer for cdi 1.0+
 {code}
 protected void onFacesRequestStart(@Observes 
 @org.apache.deltaspike.core.api.lifecycle.Initialized FacesContext 
 facesContext) {
 //...
 }
 protected void onFacesRequestEnd(@Observes 
 @org.apache.deltaspike.core.api.lifecycle.Destroyed FacesContext 
 facesContext) {
 //...
 }
 {code}
 additional option for cdi 1.1+ introduced by this ticket:
 {code}
 protected void onFacesRequestStart(@Observes 
 @javax.enterprise.context.Initialized(javax.faces.bean.RequestScoped.class) 
 FacesContext facesContext) {
 //...
 }
 protected void onFacesRequestEnd(@Observes 
 @javax.enterprise.context.Destroyed(javax.faces.bean.RequestScoped.class) 
 FacesContext facesContext) {
 //...
 }
 {code}



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

[jira] [Assigned] (DELTASPIKE-846) Docs: Clarify that scheduler module has manual dependencies

[Rafael Benevides (JIRA)]

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

Rafael Benevides reassigned DELTASPIKE-846:
---

Assignee: Rafael Benevides

 Docs: Clarify that scheduler module has manual dependencies
 ---

 Key: DELTASPIKE-846
 URL: https://issues.apache.org/jira/browse/DELTASPIKE-846
 Project: DeltaSpike
  Issue Type: Improvement
  Components: Documentation
Affects Versions: 1.2.1
Reporter: Ron Smeral
Assignee: Rafael Benevides
Priority: Minor

 See DELTASPIKE-824.



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

[jira] [Commented] (DELTASPIKE-846) Docs: Clarify that scheduler module has manual dependencies

[Rafael Benevides (JIRA)]

[ 
https://issues.apache.org/jira/browse/DELTASPIKE-846?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=14483219#comment-14483219
 ] 

Rafael Benevides commented on DELTASPIKE-846:
-

PR merged: 
https://github.com/apache/deltaspike/commit/cb62677ff9e89cf09fe47daeda01febb57210d2e

Docs published: 
http://deltaspike.apache.org/documentation/scheduler.html#_3_declare_container_control_dependency

 Docs: Clarify that scheduler module has manual dependencies
 ---

 Key: DELTASPIKE-846
 URL: https://issues.apache.org/jira/browse/DELTASPIKE-846
 Project: DeltaSpike
  Issue Type: Improvement
  Components: Documentation
Affects Versions: 1.2.1
Reporter: Ron Smeral
Assignee: Rafael Benevides
Priority: Minor

 See DELTASPIKE-824.



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

[jira] [Resolved] (DELTASPIKE-846) Docs: Clarify that scheduler module has manual dependencies

[Rafael Benevides (JIRA)]

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

Rafael Benevides resolved DELTASPIKE-846.
-
Resolution: Fixed
  Assignee: (was: Rafael Benevides)

 Docs: Clarify that scheduler module has manual dependencies
 ---

 Key: DELTASPIKE-846
 URL: https://issues.apache.org/jira/browse/DELTASPIKE-846
 Project: DeltaSpike
  Issue Type: Improvement
  Components: Documentation
Affects Versions: 1.2.1
Reporter: Ron Smeral
Priority: Minor

 See DELTASPIKE-824.



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

[jira] [Resolved] (DELTASPIKE-867) Clarify that Test-Control module has manual dependencies on CDI implementations

[Rafael Benevides (JIRA)]

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

Rafael Benevides resolved DELTASPIKE-867.
-
Resolution: Fixed

 Clarify that Test-Control module has manual dependencies on CDI 
 implementations
 ---

 Key: DELTASPIKE-867
 URL: https://issues.apache.org/jira/browse/DELTASPIKE-867
 Project: DeltaSpike
  Issue Type: Bug
  Components: Documentation
Reporter: Ron Smeral
Assignee: Rafael Benevides
Priority: Minor

 It is kind of obvious, but it may be easier for beginners to start with 
 DeltaSpike Test-Control module if this is mentioned - that openwebbeans-impl 
 or weld-se-core needs to be added as a dependency manually.



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

[jira] [Commented] (DELTASPIKE-867) Clarify that Test-Control module has manual dependencies on CDI implementations

[Rafael Benevides (JIRA)]

[ 
https://issues.apache.org/jira/browse/DELTASPIKE-867?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=14481260#comment-14481260
 ] 

Rafael Benevides commented on DELTASPIKE-867:
-

It looks that it was already merged and published:

Commit: 
https://github.com/apache/deltaspike/commit/7077eec04fd2c7bec87c289e6df8007e79294eb7
Doc: 
http://deltaspike.apache.org/documentation/test-control#_2_declare_cdi_implementation_specific_dependencies

 Clarify that Test-Control module has manual dependencies on CDI 
 implementations
 ---

 Key: DELTASPIKE-867
 URL: https://issues.apache.org/jira/browse/DELTASPIKE-867
 Project: DeltaSpike
  Issue Type: Bug
  Components: Documentation
Reporter: Ron Smeral
Assignee: Rafael Benevides
Priority: Minor

 It is kind of obvious, but it may be easier for beginners to start with 
 DeltaSpike Test-Control module if this is mentioned - that openwebbeans-impl 
 or weld-se-core needs to be added as a dependency manually.



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

[jira] [Resolved] (DELTASPIKE-862) document JsfMessage

[Rafael Benevides (JIRA)]

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

Rafael Benevides resolved DELTASPIKE-862.
-
Resolution: Fixed

Published: http://deltaspike.apache.org/documentation/jsf.html#_jsf_messages

 document JsfMessage
 ---

 Key: DELTASPIKE-862
 URL: https://issues.apache.org/jira/browse/DELTASPIKE-862
 Project: DeltaSpike
  Issue Type: Task
  Components: JSF-Module
Affects Versions: 1.3.0
Reporter: Gerhard Petracek
Assignee: Rafael Benevides
 Fix For: 1.3.1






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

[jira] [Resolved] (DELTASPIKE-850) Add Weld 3 profile

[Rafael Benevides (JIRA)]

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

Rafael Benevides resolved DELTASPIKE-850.
-
Resolution: Fixed

PR tested with all Weld 3.x versions and merged

 Add Weld 3 profile
 --

 Key: DELTASPIKE-850
 URL: https://issues.apache.org/jira/browse/DELTASPIKE-850
 Project: DeltaSpike
  Issue Type: Task
  Components: Build
Reporter: Ron Smeral
Assignee: Rafael Benevides
Priority: Trivial

 Weld 3 is now split into several modules and the weld-core module is renamed 
 to weld-core-impl, so the Weld profile no longer works for Weld 3. 



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

[jira] [Commented] (DELTASPIKE-856) Eclipse deployment to container add remove view shows deltaspike-jsf-module-impl-ee6-1.2.1 as if it was an app module - in weblogic we get a double jar file

[Rafael Benevides (JIRA)]

[ 
https://issues.apache.org/jira/browse/DELTASPIKE-856?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=14389753#comment-14389753
 ] 

Rafael Benevides commented on DELTASPIKE-856:
-

Thanks. I'm following there.

 Eclipse deployment to container add remove view shows 
 deltaspike-jsf-module-impl-ee6-1.2.1 as if it was an app module - in weblogic 
 we get a double jar file
 

 Key: DELTASPIKE-856
 URL: https://issues.apache.org/jira/browse/DELTASPIKE-856
 Project: DeltaSpike
  Issue Type: Bug
  Components: JSF-Module
Affects Versions: 1.2.1
 Environment: Windows 7 , Eclipse Version: Luna (4.4) Build id: 
 I20140606-1215, WTP plugin  Version: 
 1.2.100.v201405081709-797LBiCcNBHQFTGaGVbu3KEF
 Build id: 20131017041352, Oracle enterprise Pack for Ecliplse plugin: Build 
 id: 20131017041352
Reporter: Nuno G. de M
Assignee: Rafael Benevides
 Attachments: Screenshot 2015-03-13 18.05.21.png, Screenshot 
 2015-03-16 12.42.13.png


 There is something special about the deltaspike-jsf-module-impl-ee6-1.2.1.jar 
 .
 This project dependency alone, unlike every other project dependency, it is 
 displayed itself by eclipse Add  Remove view to an application server as if 
 it were a module itself of the war application to be deployed.
 When a user, for example, configures weblogic 12.1.2 server to take in 
 deployments as exploded war files, what ends up happening after the 
 deployment goes through is that we see within
 Weblogic Domain  AdminServer  temp  mydeployment  war Web-inf/lib 
 we see the jar dependency twice.
 First we see the correct and expected dependency:
 deltaspike-jsf-module-impl-ee6-1.2.1.jar
 But then we have a second file in the lib folder called:
 deltaspike-jsf-module-impl-ee6-1.2.1.jar.jar
 This appears to be releated to the Add  Remove view of eclipse, since 
 normally under the project war file itself we only see other open project 
 modules.
 I am pasting in this post an url to a google driver sample application that 
 you can use to simulate the scenario.
 The zip file will contain both a sample application that I have once before 
 submitted to you already (regarding the view access scoped beans) and 
 document file illustrating the issue in my IDE.
 To simulate the issue simply:
 (a) create a domain
 (b) do mvn eclipse:eclipse and import the project
 (c) Configure your weblogic domain to accept exploded war deployment
 (d) click on add and remove on the domain you want to deploy to and see that 
 the JEE6 impl appears as a module.
 (e) deploy, and look at what happens within the weblogic deployment folder
 URL:
 https://drive.google.com/file/d/0B_dEiNBGUsxqOGZRUjBJQU85WXc/view?usp=sharing
 It is not yet clear if this phenomena may be creating problems for us when we 
 use eclipse to run the deployment.
 In the sample application we have no issues.
 Thank you for your support,
 My kindest regards.



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

[jira] [Resolved] (DELTASPIKE-856) Eclipse deployment to container add remove view shows deltaspike-jsf-module-impl-ee6-1.2.1 as if it was an app module - in weblogic we get a double jar file

[Rafael Benevides (JIRA)]

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

Rafael Benevides resolved DELTASPIKE-856.
-
Resolution: Invalid

Hi Nuno.

Now I was able to reproduce it but I was not able to found a cause in 
DeltaSpike. 

I was able to see the deltaspike-jsf-module-impl-ee6-1.2.1.jar as a module of 
jsf-viewscoped project on [WTP + OEPE] and [WTP + JBoss Tools] enviroments. 
This leads me to think that it's related to maven eclipse:eclipse plugin.

Anyway, on both environments I was not able to have the ds jsf module-jar.jar 
file

Having said that, I don't believe that there's an issue on DS JSF module. 
Sorry, but I recommend you to fire a bug report on OEPE side.

 Eclipse deployment to container add remove view shows 
 deltaspike-jsf-module-impl-ee6-1.2.1 as if it was an app module - in weblogic 
 we get a double jar file
 

 Key: DELTASPIKE-856
 URL: https://issues.apache.org/jira/browse/DELTASPIKE-856
 Project: DeltaSpike
  Issue Type: Bug
  Components: JSF-Module
Affects Versions: 1.2.1
 Environment: Windows 7 , Eclipse Version: Luna (4.4) Build id: 
 I20140606-1215, WTP plugin  Version: 
 1.2.100.v201405081709-797LBiCcNBHQFTGaGVbu3KEF
 Build id: 20131017041352, Oracle enterprise Pack for Ecliplse plugin: Build 
 id: 20131017041352
Reporter: Nuno G. de M
Assignee: Rafael Benevides
 Attachments: Screenshot 2015-03-13 18.05.21.png, Screenshot 
 2015-03-16 12.42.13.png


 There is something special about the deltaspike-jsf-module-impl-ee6-1.2.1.jar 
 .
 This project dependency alone, unlike every other project dependency, it is 
 displayed itself by eclipse Add  Remove view to an application server as if 
 it were a module itself of the war application to be deployed.
 When a user, for example, configures weblogic 12.1.2 server to take in 
 deployments as exploded war files, what ends up happening after the 
 deployment goes through is that we see within
 Weblogic Domain  AdminServer  temp  mydeployment  war Web-inf/lib 
 we see the jar dependency twice.
 First we see the correct and expected dependency:
 deltaspike-jsf-module-impl-ee6-1.2.1.jar
 But then we have a second file in the lib folder called:
 deltaspike-jsf-module-impl-ee6-1.2.1.jar.jar
 This appears to be releated to the Add  Remove view of eclipse, since 
 normally under the project war file itself we only see other open project 
 modules.
 I am pasting in this post an url to a google driver sample application that 
 you can use to simulate the scenario.
 The zip file will contain both a sample application that I have once before 
 submitted to you already (regarding the view access scoped beans) and 
 document file illustrating the issue in my IDE.
 To simulate the issue simply:
 (a) create a domain
 (b) do mvn eclipse:eclipse and import the project
 (c) Configure your weblogic domain to accept exploded war deployment
 (d) click on add and remove on the domain you want to deploy to and see that 
 the JEE6 impl appears as a module.
 (e) deploy, and look at what happens within the weblogic deployment folder
 URL:
 https://drive.google.com/file/d/0B_dEiNBGUsxqOGZRUjBJQU85WXc/view?usp=sharing
 It is not yet clear if this phenomena may be creating problems for us when we 
 use eclipse to run the deployment.
 In the sample application we have no issues.
 Thank you for your support,
 My kindest regards.



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

[jira] [Resolved] (DELTASPIKE-855) Review deltaspike-release-plugin and distribution profile to not consider deltaspike-root

[Rafael Benevides (JIRA)]

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

Rafael Benevides resolved DELTASPIKE-855.
-
Resolution: Fixed

Commit: 
https://github.com/apache/deltaspike/commit/6fb873142020d3e259182f689a226c0df7ab2cf3

 Review deltaspike-release-plugin and distribution profile to not consider 
 deltaspike-root
 -

 Key: DELTASPIKE-855
 URL: https://issues.apache.org/jira/browse/DELTASPIKE-855
 Project: DeltaSpike
  Issue Type: Improvement
  Components: Build
Affects Versions: 1.3.0
Reporter: Rafael Benevides
Assignee: Rafael Benevides
 Fix For: 1.3.1, 1.4.0


 Because DELTASPIKE-814 the maven-release-plugin it introduced a now expected 
 behaviour in the distribution.
 Effects:
 - Sources distribution name change: deltaspike-root-1.3.0-source-release.zip
 - Sources distribution content have site and documentation included.
 - git tag name change: 
 https://github.com/apache/deltaspike/releases/tag/deltaspike-root-1.3.0
 The distribution profile and maven-release-plugin should be reviewed to 
 include only deltaspike-project.



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

[jira] [Commented] (DELTASPIKE-850) Add Weld 3 profile

[Rafael Benevides (JIRA)]

[ 
https://issues.apache.org/jira/browse/DELTASPIKE-850?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=14384617#comment-14384617
 ] 

Rafael Benevides commented on DELTASPIKE-850:
-

Hi [~rsmeral] Do you have a reference Jira for Weld ? I'd like to know what 
version of Weld will have this fix?

Btw, regarding the PR. Will you closed it?

Thanks


 Add Weld 3 profile
 --

 Key: DELTASPIKE-850
 URL: https://issues.apache.org/jira/browse/DELTASPIKE-850
 Project: DeltaSpike
  Issue Type: Task
  Components: Build
Reporter: Ron Smeral
Assignee: Rafael Benevides
Priority: Trivial

 Weld 3 is now split into several modules and the weld-core module is renamed 
 to weld-core-impl, so the Weld profile no longer works for Weld 3. 



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

[jira] [Reopened] (DELTASPIKE-856) Eclipse deployment to container add remove view shows deltaspike-jsf-module-impl-ee6-1.2.1 as if it was an app module - in weblogic we get a double jar file

[Rafael Benevides (JIRA)]

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

Rafael Benevides reopened DELTASPIKE-856:
-

 Eclipse deployment to container add remove view shows 
 deltaspike-jsf-module-impl-ee6-1.2.1 as if it was an app module - in weblogic 
 we get a double jar file
 

 Key: DELTASPIKE-856
 URL: https://issues.apache.org/jira/browse/DELTASPIKE-856
 Project: DeltaSpike
  Issue Type: Bug
  Components: JSF-Module
Affects Versions: 1.2.1
 Environment: Windows 7 , Eclipse Version: Luna (4.4) Build id: 
 I20140606-1215, WTP plugin  Version: 
 1.2.100.v201405081709-797LBiCcNBHQFTGaGVbu3KEF
 Build id: 20131017041352, Oracle enterprise Pack for Ecliplse plugin: Build 
 id: 20131017041352
Reporter: Nuno G. de M
Assignee: Rafael Benevides
 Attachments: Screenshot 2015-03-13 18.05.21.png, Screenshot 
 2015-03-16 12.42.13.png


 There is something special about the deltaspike-jsf-module-impl-ee6-1.2.1.jar 
 .
 This project dependency alone, unlike every other project dependency, it is 
 displayed itself by eclipse Add  Remove view to an application server as if 
 it were a module itself of the war application to be deployed.
 When a user, for example, configures weblogic 12.1.2 server to take in 
 deployments as exploded war files, what ends up happening after the 
 deployment goes through is that we see within
 Weblogic Domain  AdminServer  temp  mydeployment  war Web-inf/lib 
 we see the jar dependency twice.
 First we see the correct and expected dependency:
 deltaspike-jsf-module-impl-ee6-1.2.1.jar
 But then we have a second file in the lib folder called:
 deltaspike-jsf-module-impl-ee6-1.2.1.jar.jar
 This appears to be releated to the Add  Remove view of eclipse, since 
 normally under the project war file itself we only see other open project 
 modules.
 I am pasting in this post an url to a google driver sample application that 
 you can use to simulate the scenario.
 The zip file will contain both a sample application that I have once before 
 submitted to you already (regarding the view access scoped beans) and 
 document file illustrating the issue in my IDE.
 To simulate the issue simply:
 (a) create a domain
 (b) do mvn eclipse:eclipse and import the project
 (c) Configure your weblogic domain to accept exploded war deployment
 (d) click on add and remove on the domain you want to deploy to and see that 
 the JEE6 impl appears as a module.
 (e) deploy, and look at what happens within the weblogic deployment folder
 URL:
 https://drive.google.com/file/d/0B_dEiNBGUsxqOGZRUjBJQU85WXc/view?usp=sharing
 It is not yet clear if this phenomena may be creating problems for us when we 
 use eclipse to run the deployment.
 In the sample application we have no issues.
 Thank you for your support,
 My kindest regards.



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

[jira] [Resolved] (DELTASPIKE-860) documentation says @LoggedIn User user, but that's impossible

[Rafael Benevides (JIRA)]

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

Rafael Benevides resolved DELTASPIKE-860.
-
Resolution: Fixed

PR merged

 documentation says @LoggedIn User user, but that's impossible
 ---

 Key: DELTASPIKE-860
 URL: https://issues.apache.org/jira/browse/DELTASPIKE-860
 Project: DeltaSpike
  Issue Type: Bug
  Components: Documentation
Reporter: The Alchemist
Assignee: Rafael Benevides
Priority: Minor

 h3. Documentation Snippet
 http://deltaspike.apache.org/documentation/security.html
 {noformat}
 Create the Authorizer
 @ApplicationScoped
 public class CustomAuthorizer
 {
 @Secures
 @CustomSecurityBinding
 public boolean doSecuredCheck(InvocationContext invocationContext, 
 BeanManager manager, @LoggedIn User user) throws Exception
 {
 return user.isLoggedIn(); // perform security check
 }
 }
 {noformat}
 h3. Compilation Error
 {noformat}
 The annotation @LoggedIn is disallowed for this location
 {noformat}
 h3. Explanation?
 I think it's because {{LoggedIn}} is missing a {{@Target}} of {{PARAMETER}}.
 {code:java,title=LoggedIn.java}
 @Retention(value = RetentionPolicy.RUNTIME)
 @Target({ ElementType.TYPE, ElementType.METHOD })
 @Documented
 @SecurityBindingType
 public @interface LoggedIn {
 {code}
 h3. Conclusion
 Not sure if this is supposed to work, given that {{LoggedIn}} is part of 
 PicketLink, not DeltaSpike.
 Is there a workaround for this type of situation?



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

[jira] [Commented] (DELTASPIKE-860) documentation says @LoggedIn User user, but that's impossible

[Rafael Benevides (JIRA)]

[ 
https://issues.apache.org/jira/browse/DELTASPIKE-860?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=14375965#comment-14375965
 ] 

Rafael Benevides commented on DELTASPIKE-860:
-

Thanks [~rsmeral] and [~the_alchemist].

PR merged and documentation updated.

 documentation says @LoggedIn User user, but that's impossible
 ---

 Key: DELTASPIKE-860
 URL: https://issues.apache.org/jira/browse/DELTASPIKE-860
 Project: DeltaSpike
  Issue Type: Bug
  Components: Documentation
Reporter: The Alchemist
Assignee: Rafael Benevides
Priority: Minor

 h3. Documentation Snippet
 http://deltaspike.apache.org/documentation/security.html
 {noformat}
 Create the Authorizer
 @ApplicationScoped
 public class CustomAuthorizer
 {
 @Secures
 @CustomSecurityBinding
 public boolean doSecuredCheck(InvocationContext invocationContext, 
 BeanManager manager, @LoggedIn User user) throws Exception
 {
 return user.isLoggedIn(); // perform security check
 }
 }
 {noformat}
 h3. Compilation Error
 {noformat}
 The annotation @LoggedIn is disallowed for this location
 {noformat}
 h3. Explanation?
 I think it's because {{LoggedIn}} is missing a {{@Target}} of {{PARAMETER}}.
 {code:java,title=LoggedIn.java}
 @Retention(value = RetentionPolicy.RUNTIME)
 @Target({ ElementType.TYPE, ElementType.METHOD })
 @Documented
 @SecurityBindingType
 public @interface LoggedIn {
 {code}
 h3. Conclusion
 Not sure if this is supposed to work, given that {{LoggedIn}} is part of 
 PicketLink, not DeltaSpike.
 Is there a workaround for this type of situation?



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

[jira] [Resolved] (DELTASPIKE-854) Jacoco profile doesn't work anymore

[Rafael Benevides (JIRA)]

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

Rafael Benevides resolved DELTASPIKE-854.
-
Resolution: Fixed

PR merged

 Jacoco profile doesn't work anymore
 ---

 Key: DELTASPIKE-854
 URL: https://issues.apache.org/jira/browse/DELTASPIKE-854
 Project: DeltaSpike
  Issue Type: Bug
Reporter: Tomas Remes
Assignee: Rafael Benevides

 Executing code coverage report profile will fail in partial-bean module with:
 {noformat}
 org.jboss.shrinkwrap.api.exporter.ArchiveExportException: Failed to write 
 asset to output: /WEB-INF/lib/asm-tree-5.0.3.jar
   at 
 org.jboss.shrinkwrap.impl.base.exporter.StreamExporterDelegateBase$3.handle(StreamExporterDelegateBase.java:272)
   at 
 org.jboss.shrinkwrap.impl.base.io.IOUtil.closeOnComplete(IOUtil.java:219)
   at 
 org.jboss.shrinkwrap.impl.base.exporter.StreamExporterDelegateBase.processNode(StreamExporterDelegateBase.java:233)
   at 
 org.jboss.shrinkwrap.impl.base.exporter.AbstractExporterDelegate.processNode(AbstractExporterDelegate.java:105)
   at 
 org.jboss.shrinkwrap.impl.base.exporter.AbstractExporterDelegate.processNode(AbstractExporterDelegate.java:109)
   at 
 org.jboss.shrinkwrap.impl.base.exporter.AbstractExporterDelegate.processNode(AbstractExporterDelegate.java:109)
   at 
 org.jboss.shrinkwrap.impl.base.exporter.AbstractExporterDelegate.doExport(AbstractExporterDelegate.java:95)
   at 
 org.jboss.shrinkwrap.impl.base.exporter.StreamExporterDelegateBase.access$001(StreamExporterDelegateBase.java:50)
   at 
 org.jboss.shrinkwrap.impl.base.exporter.StreamExporterDelegateBase$1.call(StreamExporterDelegateBase.java:121)
   at 
 org.jboss.shrinkwrap.impl.base.exporter.StreamExporterDelegateBase$1.call(StreamExporterDelegateBase.java:116)
   at 
 org.jboss.shrinkwrap.impl.base.exporter.zip.JdkZipExporterDelegate$1.call(JdkZipExporterDelegate.java:124)
   at 
 org.jboss.shrinkwrap.impl.base.exporter.zip.JdkZipExporterDelegate$1.call(JdkZipExporterDelegate.java:118)
   at java.util.concurrent.FutureTask.run(FutureTask.java:262)
   at 
 java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1145)
   at 
 java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:615)
   at java.lang.Thread.run(Thread.java:745)
 Caused by: org.jboss.shrinkwrap.api.exporter.ArchiveExportException: 
 java.lang.IncompatibleClassChangeError: Implementing class
   at 
 org.jboss.shrinkwrap.impl.base.exporter.FutureCompletionInputStream.awaitOnFutureOnDone(FutureCompletionInputStream.java:125)
   at 
 org.jboss.shrinkwrap.impl.base.exporter.FutureCompletionInputStream.read(FutureCompletionInputStream.java:81)
   at java.io.PipedInputStream.read(PipedInputStream.java:378)
   at 
 org.jboss.shrinkwrap.impl.base.exporter.FutureCompletionInputStream.read(FutureCompletionInputStream.java:92)
   at java.io.InputStream.read(InputStream.java:101)
   at org.jboss.shrinkwrap.impl.base.io.IOUtil.copy(IOUtil.java:138)
   at 
 org.jboss.shrinkwrap.impl.base.exporter.StreamExporterDelegateBase$2.execute(StreamExporterDelegateBase.java:261)
   at 
 org.jboss.shrinkwrap.impl.base.exporter.StreamExporterDelegateBase$2.execute(StreamExporterDelegateBase.java:233)
   at 
 org.jboss.shrinkwrap.impl.base.io.IOUtil.closeOnComplete(IOUtil.java:217)
   ... 14 more
 Caused by: java.lang.IncompatibleClassChangeError: Implementing class
   at java.lang.ClassLoader.defineClass1(Native Method)
   at java.lang.ClassLoader.defineClass(ClassLoader.java:800)
   at 
 java.security.SecureClassLoader.defineClass(SecureClassLoader.java:142)
   at java.net.URLClassLoader.defineClass(URLClassLoader.java:449)
   at java.net.URLClassLoader.access$100(URLClassLoader.java:71)
   at java.net.URLClassLoader$1.run(URLClassLoader.java:361)
   at java.net.URLClassLoader$1.run(URLClassLoader.java:355)
   at java.security.AccessController.doPrivileged(Native Method)
   at java.net.URLClassLoader.findClass(URLClassLoader.java:354)
   at java.lang.ClassLoader.loadClass(ClassLoader.java:425)
   at sun.misc.Launcher$AppClassLoader.loadClass(Launcher.java:308)
   at java.lang.ClassLoader.loadClass(ClassLoader.java:358)
   at 
 org.jboss.arquillian.extension.jacoco.client.InstrumenterAsset.openStream(InstrumenterAsset.java:52)
   at 
 org.jboss.shrinkwrap.impl.base.exporter.StreamExporterDelegateBase.processNode(StreamExporterDelegateBase.java:227)
   at 
 org.jboss.shrinkwrap.impl.base.exporter.AbstractExporterDelegate.processNode(AbstractExporterDelegate.java:105)
   at 
 org.jboss.shrinkwrap.impl.base.exporter.AbstractExporterDelegate.processNode(AbstractExporterDelegate.java:109)
   at 
 

[jira] [Commented] (DELTASPIKE-856) Eclipse deployment to container add remove view shows deltaspike-jsf-module-impl-ee6-1.2.1 as if it was an app module - in weblogic we get a double jar file

[Rafael Benevides (JIRA)]

[ 
https://issues.apache.org/jira/browse/DELTASPIKE-856?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=14365085#comment-14365085
 ] 

Rafael Benevides commented on DELTASPIKE-856:
-

You're welcome! :)

 Eclipse deployment to container add remove view shows 
 deltaspike-jsf-module-impl-ee6-1.2.1 as if it was an app module - in weblogic 
 we get a double jar file
 

 Key: DELTASPIKE-856
 URL: https://issues.apache.org/jira/browse/DELTASPIKE-856
 Project: DeltaSpike
  Issue Type: Bug
  Components: JSF-Module
Affects Versions: 1.2.1
 Environment: Windows 7 , Eclipse Version: Luna (4.4) Build id: 
 I20140606-1215, WTP plugin  Version: 
 1.2.100.v201405081709-797LBiCcNBHQFTGaGVbu3KEF
 Build id: 20131017041352, Oracle enterprise Pack for Ecliplse plugin: Build 
 id: 20131017041352
Reporter: Nuno G. de M
Assignee: Rafael Benevides
 Attachments: Screenshot 2015-03-13 18.05.21.png, Screenshot 
 2015-03-16 12.42.13.png


 There is something special about the deltaspike-jsf-module-impl-ee6-1.2.1.jar 
 .
 This project dependency alone, unlike every other project dependency, it is 
 displayed itself by eclipse Add  Remove view to an application server as if 
 it were a module itself of the war application to be deployed.
 When a user, for example, configures weblogic 12.1.2 server to take in 
 deployments as exploded war files, what ends up happening after the 
 deployment goes through is that we see within
 Weblogic Domain  AdminServer  temp  mydeployment  war Web-inf/lib 
 we see the jar dependency twice.
 First we see the correct and expected dependency:
 deltaspike-jsf-module-impl-ee6-1.2.1.jar
 But then we have a second file in the lib folder called:
 deltaspike-jsf-module-impl-ee6-1.2.1.jar.jar
 This appears to be releated to the Add  Remove view of eclipse, since 
 normally under the project war file itself we only see other open project 
 modules.
 I am pasting in this post an url to a google driver sample application that 
 you can use to simulate the scenario.
 The zip file will contain both a sample application that I have once before 
 submitted to you already (regarding the view access scoped beans) and 
 document file illustrating the issue in my IDE.
 To simulate the issue simply:
 (a) create a domain
 (b) do mvn eclipse:eclipse and import the project
 (c) Configure your weblogic domain to accept exploded war deployment
 (d) click on add and remove on the domain you want to deploy to and see that 
 the JEE6 impl appears as a module.
 (e) deploy, and look at what happens within the weblogic deployment folder
 URL:
 https://drive.google.com/file/d/0B_dEiNBGUsxqOGZRUjBJQU85WXc/view?usp=sharing
 It is not yet clear if this phenomena may be creating problems for us when we 
 use eclipse to run the deployment.
 In the sample application we have no issues.
 Thank you for your support,
 My kindest regards.



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

[jira] [Commented] (DELTASPIKE-856) Eclipse deployment to container add remove view shows deltaspike-jsf-module-impl-ee6-1.2.1 as if it was an app module - in weblogic we get a double jar file

[Rafael Benevides (JIRA)]

[ 
https://issues.apache.org/jira/browse/DELTASPIKE-856?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=14363367#comment-14363367
 ] 

Rafael Benevides commented on DELTASPIKE-856:
-

I'll try again with a fresh install

 Eclipse deployment to container add remove view shows 
 deltaspike-jsf-module-impl-ee6-1.2.1 as if it was an app module - in weblogic 
 we get a double jar file
 

 Key: DELTASPIKE-856
 URL: https://issues.apache.org/jira/browse/DELTASPIKE-856
 Project: DeltaSpike
  Issue Type: Bug
  Components: JSF-Module
Affects Versions: 1.2.1
 Environment: Windows 7 , Eclipse Version: Luna (4.4) Build id: 
 I20140606-1215, WTP plugin  Version: 
 1.2.100.v201405081709-797LBiCcNBHQFTGaGVbu3KEF
 Build id: 20131017041352, Oracle enterprise Pack for Ecliplse plugin: Build 
 id: 20131017041352
Reporter: Nuno G. de M
Assignee: Rafael Benevides
 Attachments: Screenshot 2015-03-13 18.05.21.png


 There is something special about the deltaspike-jsf-module-impl-ee6-1.2.1.jar 
 .
 This project dependency alone, unlike every other project dependency, it is 
 displayed itself by eclipse Add  Remove view to an application server as if 
 it were a module itself of the war application to be deployed.
 When a user, for example, configures weblogic 12.1.2 server to take in 
 deployments as exploded war files, what ends up happening after the 
 deployment goes through is that we see within
 Weblogic Domain  AdminServer  temp  mydeployment  war Web-inf/lib 
 we see the jar dependency twice.
 First we see the correct and expected dependency:
 deltaspike-jsf-module-impl-ee6-1.2.1.jar
 But then we have a second file in the lib folder called:
 deltaspike-jsf-module-impl-ee6-1.2.1.jar.jar
 This appears to be releated to the Add  Remove view of eclipse, since 
 normally under the project war file itself we only see other open project 
 modules.
 I am pasting in this post an url to a google driver sample application that 
 you can use to simulate the scenario.
 The zip file will contain both a sample application that I have once before 
 submitted to you already (regarding the view access scoped beans) and 
 document file illustrating the issue in my IDE.
 To simulate the issue simply:
 (a) create a domain
 (b) do mvn eclipse:eclipse and import the project
 (c) Configure your weblogic domain to accept exploded war deployment
 (d) click on add and remove on the domain you want to deploy to and see that 
 the JEE6 impl appears as a module.
 (e) deploy, and look at what happens within the weblogic deployment folder
 URL:
 https://drive.google.com/file/d/0B_dEiNBGUsxqOGZRUjBJQU85WXc/view?usp=sharing
 It is not yet clear if this phenomena may be creating problems for us when we 
 use eclipse to run the deployment.
 In the sample application we have no issues.
 Thank you for your support,
 My kindest regards.



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

[jira] [Issue Comment Deleted] (DELTASPIKE-854) Jacoco profile doesn't work anymore

[Rafael Benevides (JIRA)]

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

Rafael Benevides updated DELTASPIKE-854:

Comment: was deleted

(was: Thanks for the PR. Now It's failing for mvn clean install 
-Ptomee-build-managed. )

 Jacoco profile doesn't work anymore
 ---

 Key: DELTASPIKE-854
 URL: https://issues.apache.org/jira/browse/DELTASPIKE-854
 Project: DeltaSpike
  Issue Type: Bug
Reporter: Tomas Remes
Assignee: Rafael Benevides

 Executing code coverage report profile will fail in partial-bean module with:
 {noformat}
 org.jboss.shrinkwrap.api.exporter.ArchiveExportException: Failed to write 
 asset to output: /WEB-INF/lib/asm-tree-5.0.3.jar
   at 
 org.jboss.shrinkwrap.impl.base.exporter.StreamExporterDelegateBase$3.handle(StreamExporterDelegateBase.java:272)
   at 
 org.jboss.shrinkwrap.impl.base.io.IOUtil.closeOnComplete(IOUtil.java:219)
   at 
 org.jboss.shrinkwrap.impl.base.exporter.StreamExporterDelegateBase.processNode(StreamExporterDelegateBase.java:233)
   at 
 org.jboss.shrinkwrap.impl.base.exporter.AbstractExporterDelegate.processNode(AbstractExporterDelegate.java:105)
   at 
 org.jboss.shrinkwrap.impl.base.exporter.AbstractExporterDelegate.processNode(AbstractExporterDelegate.java:109)
   at 
 org.jboss.shrinkwrap.impl.base.exporter.AbstractExporterDelegate.processNode(AbstractExporterDelegate.java:109)
   at 
 org.jboss.shrinkwrap.impl.base.exporter.AbstractExporterDelegate.doExport(AbstractExporterDelegate.java:95)
   at 
 org.jboss.shrinkwrap.impl.base.exporter.StreamExporterDelegateBase.access$001(StreamExporterDelegateBase.java:50)
   at 
 org.jboss.shrinkwrap.impl.base.exporter.StreamExporterDelegateBase$1.call(StreamExporterDelegateBase.java:121)
   at 
 org.jboss.shrinkwrap.impl.base.exporter.StreamExporterDelegateBase$1.call(StreamExporterDelegateBase.java:116)
   at 
 org.jboss.shrinkwrap.impl.base.exporter.zip.JdkZipExporterDelegate$1.call(JdkZipExporterDelegate.java:124)
   at 
 org.jboss.shrinkwrap.impl.base.exporter.zip.JdkZipExporterDelegate$1.call(JdkZipExporterDelegate.java:118)
   at java.util.concurrent.FutureTask.run(FutureTask.java:262)
   at 
 java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1145)
   at 
 java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:615)
   at java.lang.Thread.run(Thread.java:745)
 Caused by: org.jboss.shrinkwrap.api.exporter.ArchiveExportException: 
 java.lang.IncompatibleClassChangeError: Implementing class
   at 
 org.jboss.shrinkwrap.impl.base.exporter.FutureCompletionInputStream.awaitOnFutureOnDone(FutureCompletionInputStream.java:125)
   at 
 org.jboss.shrinkwrap.impl.base.exporter.FutureCompletionInputStream.read(FutureCompletionInputStream.java:81)
   at java.io.PipedInputStream.read(PipedInputStream.java:378)
   at 
 org.jboss.shrinkwrap.impl.base.exporter.FutureCompletionInputStream.read(FutureCompletionInputStream.java:92)
   at java.io.InputStream.read(InputStream.java:101)
   at org.jboss.shrinkwrap.impl.base.io.IOUtil.copy(IOUtil.java:138)
   at 
 org.jboss.shrinkwrap.impl.base.exporter.StreamExporterDelegateBase$2.execute(StreamExporterDelegateBase.java:261)
   at 
 org.jboss.shrinkwrap.impl.base.exporter.StreamExporterDelegateBase$2.execute(StreamExporterDelegateBase.java:233)
   at 
 org.jboss.shrinkwrap.impl.base.io.IOUtil.closeOnComplete(IOUtil.java:217)
   ... 14 more
 Caused by: java.lang.IncompatibleClassChangeError: Implementing class
   at java.lang.ClassLoader.defineClass1(Native Method)
   at java.lang.ClassLoader.defineClass(ClassLoader.java:800)
   at 
 java.security.SecureClassLoader.defineClass(SecureClassLoader.java:142)
   at java.net.URLClassLoader.defineClass(URLClassLoader.java:449)
   at java.net.URLClassLoader.access$100(URLClassLoader.java:71)
   at java.net.URLClassLoader$1.run(URLClassLoader.java:361)
   at java.net.URLClassLoader$1.run(URLClassLoader.java:355)
   at java.security.AccessController.doPrivileged(Native Method)
   at java.net.URLClassLoader.findClass(URLClassLoader.java:354)
   at java.lang.ClassLoader.loadClass(ClassLoader.java:425)
   at sun.misc.Launcher$AppClassLoader.loadClass(Launcher.java:308)
   at java.lang.ClassLoader.loadClass(ClassLoader.java:358)
   at 
 org.jboss.arquillian.extension.jacoco.client.InstrumenterAsset.openStream(InstrumenterAsset.java:52)
   at 
 org.jboss.shrinkwrap.impl.base.exporter.StreamExporterDelegateBase.processNode(StreamExporterDelegateBase.java:227)
   at 
 org.jboss.shrinkwrap.impl.base.exporter.AbstractExporterDelegate.processNode(AbstractExporterDelegate.java:105)
   at 
 

[jira] [Commented] (DELTASPIKE-854) Jacoco profile doesn't work anymore

[Rafael Benevides (JIRA)]

[ 
https://issues.apache.org/jira/browse/DELTASPIKE-854?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=14363362#comment-14363362
 ] 

Rafael Benevides commented on DELTASPIKE-854:
-

PR merged

 Jacoco profile doesn't work anymore
 ---

 Key: DELTASPIKE-854
 URL: https://issues.apache.org/jira/browse/DELTASPIKE-854
 Project: DeltaSpike
  Issue Type: Bug
Reporter: Tomas Remes
Assignee: Rafael Benevides

 Executing code coverage report profile will fail in partial-bean module with:
 {noformat}
 org.jboss.shrinkwrap.api.exporter.ArchiveExportException: Failed to write 
 asset to output: /WEB-INF/lib/asm-tree-5.0.3.jar
   at 
 org.jboss.shrinkwrap.impl.base.exporter.StreamExporterDelegateBase$3.handle(StreamExporterDelegateBase.java:272)
   at 
 org.jboss.shrinkwrap.impl.base.io.IOUtil.closeOnComplete(IOUtil.java:219)
   at 
 org.jboss.shrinkwrap.impl.base.exporter.StreamExporterDelegateBase.processNode(StreamExporterDelegateBase.java:233)
   at 
 org.jboss.shrinkwrap.impl.base.exporter.AbstractExporterDelegate.processNode(AbstractExporterDelegate.java:105)
   at 
 org.jboss.shrinkwrap.impl.base.exporter.AbstractExporterDelegate.processNode(AbstractExporterDelegate.java:109)
   at 
 org.jboss.shrinkwrap.impl.base.exporter.AbstractExporterDelegate.processNode(AbstractExporterDelegate.java:109)
   at 
 org.jboss.shrinkwrap.impl.base.exporter.AbstractExporterDelegate.doExport(AbstractExporterDelegate.java:95)
   at 
 org.jboss.shrinkwrap.impl.base.exporter.StreamExporterDelegateBase.access$001(StreamExporterDelegateBase.java:50)
   at 
 org.jboss.shrinkwrap.impl.base.exporter.StreamExporterDelegateBase$1.call(StreamExporterDelegateBase.java:121)
   at 
 org.jboss.shrinkwrap.impl.base.exporter.StreamExporterDelegateBase$1.call(StreamExporterDelegateBase.java:116)
   at 
 org.jboss.shrinkwrap.impl.base.exporter.zip.JdkZipExporterDelegate$1.call(JdkZipExporterDelegate.java:124)
   at 
 org.jboss.shrinkwrap.impl.base.exporter.zip.JdkZipExporterDelegate$1.call(JdkZipExporterDelegate.java:118)
   at java.util.concurrent.FutureTask.run(FutureTask.java:262)
   at 
 java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1145)
   at 
 java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:615)
   at java.lang.Thread.run(Thread.java:745)
 Caused by: org.jboss.shrinkwrap.api.exporter.ArchiveExportException: 
 java.lang.IncompatibleClassChangeError: Implementing class
   at 
 org.jboss.shrinkwrap.impl.base.exporter.FutureCompletionInputStream.awaitOnFutureOnDone(FutureCompletionInputStream.java:125)
   at 
 org.jboss.shrinkwrap.impl.base.exporter.FutureCompletionInputStream.read(FutureCompletionInputStream.java:81)
   at java.io.PipedInputStream.read(PipedInputStream.java:378)
   at 
 org.jboss.shrinkwrap.impl.base.exporter.FutureCompletionInputStream.read(FutureCompletionInputStream.java:92)
   at java.io.InputStream.read(InputStream.java:101)
   at org.jboss.shrinkwrap.impl.base.io.IOUtil.copy(IOUtil.java:138)
   at 
 org.jboss.shrinkwrap.impl.base.exporter.StreamExporterDelegateBase$2.execute(StreamExporterDelegateBase.java:261)
   at 
 org.jboss.shrinkwrap.impl.base.exporter.StreamExporterDelegateBase$2.execute(StreamExporterDelegateBase.java:233)
   at 
 org.jboss.shrinkwrap.impl.base.io.IOUtil.closeOnComplete(IOUtil.java:217)
   ... 14 more
 Caused by: java.lang.IncompatibleClassChangeError: Implementing class
   at java.lang.ClassLoader.defineClass1(Native Method)
   at java.lang.ClassLoader.defineClass(ClassLoader.java:800)
   at 
 java.security.SecureClassLoader.defineClass(SecureClassLoader.java:142)
   at java.net.URLClassLoader.defineClass(URLClassLoader.java:449)
   at java.net.URLClassLoader.access$100(URLClassLoader.java:71)
   at java.net.URLClassLoader$1.run(URLClassLoader.java:361)
   at java.net.URLClassLoader$1.run(URLClassLoader.java:355)
   at java.security.AccessController.doPrivileged(Native Method)
   at java.net.URLClassLoader.findClass(URLClassLoader.java:354)
   at java.lang.ClassLoader.loadClass(ClassLoader.java:425)
   at sun.misc.Launcher$AppClassLoader.loadClass(Launcher.java:308)
   at java.lang.ClassLoader.loadClass(ClassLoader.java:358)
   at 
 org.jboss.arquillian.extension.jacoco.client.InstrumenterAsset.openStream(InstrumenterAsset.java:52)
   at 
 org.jboss.shrinkwrap.impl.base.exporter.StreamExporterDelegateBase.processNode(StreamExporterDelegateBase.java:227)
   at 
 org.jboss.shrinkwrap.impl.base.exporter.AbstractExporterDelegate.processNode(AbstractExporterDelegate.java:105)
   at 
 

[jira] [Comment Edited] (DELTASPIKE-856) Eclipse deployment to container add remove view shows deltaspike-jsf-module-impl-ee6-1.2.1 as if it was an app module - in weblogic we get a double jar file

[Rafael Benevides (JIRA)]

[ 
https://issues.apache.org/jira/browse/DELTASPIKE-856?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=14363367#comment-14363367
 ] 

Rafael Benevides edited comment on DELTASPIKE-856 at 3/16/15 3:47 PM:
--

I'll try again with a fresh install of eclipse and OOPE


was (Author: rafabene):
I'll try again with a fresh install

 Eclipse deployment to container add remove view shows 
 deltaspike-jsf-module-impl-ee6-1.2.1 as if it was an app module - in weblogic 
 we get a double jar file
 

 Key: DELTASPIKE-856
 URL: https://issues.apache.org/jira/browse/DELTASPIKE-856
 Project: DeltaSpike
  Issue Type: Bug
  Components: JSF-Module
Affects Versions: 1.2.1
 Environment: Windows 7 , Eclipse Version: Luna (4.4) Build id: 
 I20140606-1215, WTP plugin  Version: 
 1.2.100.v201405081709-797LBiCcNBHQFTGaGVbu3KEF
 Build id: 20131017041352, Oracle enterprise Pack for Ecliplse plugin: Build 
 id: 20131017041352
Reporter: Nuno G. de M
Assignee: Rafael Benevides
 Attachments: Screenshot 2015-03-13 18.05.21.png


 There is something special about the deltaspike-jsf-module-impl-ee6-1.2.1.jar 
 .
 This project dependency alone, unlike every other project dependency, it is 
 displayed itself by eclipse Add  Remove view to an application server as if 
 it were a module itself of the war application to be deployed.
 When a user, for example, configures weblogic 12.1.2 server to take in 
 deployments as exploded war files, what ends up happening after the 
 deployment goes through is that we see within
 Weblogic Domain  AdminServer  temp  mydeployment  war Web-inf/lib 
 we see the jar dependency twice.
 First we see the correct and expected dependency:
 deltaspike-jsf-module-impl-ee6-1.2.1.jar
 But then we have a second file in the lib folder called:
 deltaspike-jsf-module-impl-ee6-1.2.1.jar.jar
 This appears to be releated to the Add  Remove view of eclipse, since 
 normally under the project war file itself we only see other open project 
 modules.
 I am pasting in this post an url to a google driver sample application that 
 you can use to simulate the scenario.
 The zip file will contain both a sample application that I have once before 
 submitted to you already (regarding the view access scoped beans) and 
 document file illustrating the issue in my IDE.
 To simulate the issue simply:
 (a) create a domain
 (b) do mvn eclipse:eclipse and import the project
 (c) Configure your weblogic domain to accept exploded war deployment
 (d) click on add and remove on the domain you want to deploy to and see that 
 the JEE6 impl appears as a module.
 (e) deploy, and look at what happens within the weblogic deployment folder
 URL:
 https://drive.google.com/file/d/0B_dEiNBGUsxqOGZRUjBJQU85WXc/view?usp=sharing
 It is not yet clear if this phenomena may be creating problems for us when we 
 use eclipse to run the deployment.
 In the sample application we have no issues.
 Thank you for your support,
 My kindest regards.



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

[jira] [Reopened] (DELTASPIKE-856) Eclipse deployment to container add remove view shows deltaspike-jsf-module-impl-ee6-1.2.1 as if it was an app module - in weblogic we get a double jar file

[Rafael Benevides (JIRA)]

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

Rafael Benevides reopened DELTASPIKE-856:
-

 Eclipse deployment to container add remove view shows 
 deltaspike-jsf-module-impl-ee6-1.2.1 as if it was an app module - in weblogic 
 we get a double jar file
 

 Key: DELTASPIKE-856
 URL: https://issues.apache.org/jira/browse/DELTASPIKE-856
 Project: DeltaSpike
  Issue Type: Bug
  Components: JSF-Module
Affects Versions: 1.2.1
 Environment: Windows 7 , Eclipse Version: Luna (4.4) Build id: 
 I20140606-1215, WTP plugin  Version: 
 1.2.100.v201405081709-797LBiCcNBHQFTGaGVbu3KEF
 Build id: 20131017041352, Oracle enterprise Pack for Ecliplse plugin: Build 
 id: 20131017041352
Reporter: Nuno G. de M
Assignee: Rafael Benevides
 Attachments: Screenshot 2015-03-13 18.05.21.png


 There is something special about the deltaspike-jsf-module-impl-ee6-1.2.1.jar 
 .
 This project dependency alone, unlike every other project dependency, it is 
 displayed itself by eclipse Add  Remove view to an application server as if 
 it were a module itself of the war application to be deployed.
 When a user, for example, configures weblogic 12.1.2 server to take in 
 deployments as exploded war files, what ends up happening after the 
 deployment goes through is that we see within
 Weblogic Domain  AdminServer  temp  mydeployment  war Web-inf/lib 
 we see the jar dependency twice.
 First we see the correct and expected dependency:
 deltaspike-jsf-module-impl-ee6-1.2.1.jar
 But then we have a second file in the lib folder called:
 deltaspike-jsf-module-impl-ee6-1.2.1.jar.jar
 This appears to be releated to the Add  Remove view of eclipse, since 
 normally under the project war file itself we only see other open project 
 modules.
 I am pasting in this post an url to a google driver sample application that 
 you can use to simulate the scenario.
 The zip file will contain both a sample application that I have once before 
 submitted to you already (regarding the view access scoped beans) and 
 document file illustrating the issue in my IDE.
 To simulate the issue simply:
 (a) create a domain
 (b) do mvn eclipse:eclipse and import the project
 (c) Configure your weblogic domain to accept exploded war deployment
 (d) click on add and remove on the domain you want to deploy to and see that 
 the JEE6 impl appears as a module.
 (e) deploy, and look at what happens within the weblogic deployment folder
 URL:
 https://drive.google.com/file/d/0B_dEiNBGUsxqOGZRUjBJQU85WXc/view?usp=sharing
 It is not yet clear if this phenomena may be creating problems for us when we 
 use eclipse to run the deployment.
 In the sample application we have no issues.
 Thank you for your support,
 My kindest regards.



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

[jira] [Commented] (DELTASPIKE-854) Jacoco profile doesn't work anymore

[Rafael Benevides (JIRA)]

[ 
https://issues.apache.org/jira/browse/DELTASPIKE-854?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=14363357#comment-14363357
 ] 

Rafael Benevides commented on DELTASPIKE-854:
-

Thanks for the PR. Now It's failing for mvn clean install 
-Ptomee-build-managed. 

 Jacoco profile doesn't work anymore
 ---

 Key: DELTASPIKE-854
 URL: https://issues.apache.org/jira/browse/DELTASPIKE-854
 Project: DeltaSpike
  Issue Type: Bug
Reporter: Tomas Remes
Assignee: Rafael Benevides

 Executing code coverage report profile will fail in partial-bean module with:
 {noformat}
 org.jboss.shrinkwrap.api.exporter.ArchiveExportException: Failed to write 
 asset to output: /WEB-INF/lib/asm-tree-5.0.3.jar
   at 
 org.jboss.shrinkwrap.impl.base.exporter.StreamExporterDelegateBase$3.handle(StreamExporterDelegateBase.java:272)
   at 
 org.jboss.shrinkwrap.impl.base.io.IOUtil.closeOnComplete(IOUtil.java:219)
   at 
 org.jboss.shrinkwrap.impl.base.exporter.StreamExporterDelegateBase.processNode(StreamExporterDelegateBase.java:233)
   at 
 org.jboss.shrinkwrap.impl.base.exporter.AbstractExporterDelegate.processNode(AbstractExporterDelegate.java:105)
   at 
 org.jboss.shrinkwrap.impl.base.exporter.AbstractExporterDelegate.processNode(AbstractExporterDelegate.java:109)
   at 
 org.jboss.shrinkwrap.impl.base.exporter.AbstractExporterDelegate.processNode(AbstractExporterDelegate.java:109)
   at 
 org.jboss.shrinkwrap.impl.base.exporter.AbstractExporterDelegate.doExport(AbstractExporterDelegate.java:95)
   at 
 org.jboss.shrinkwrap.impl.base.exporter.StreamExporterDelegateBase.access$001(StreamExporterDelegateBase.java:50)
   at 
 org.jboss.shrinkwrap.impl.base.exporter.StreamExporterDelegateBase$1.call(StreamExporterDelegateBase.java:121)
   at 
 org.jboss.shrinkwrap.impl.base.exporter.StreamExporterDelegateBase$1.call(StreamExporterDelegateBase.java:116)
   at 
 org.jboss.shrinkwrap.impl.base.exporter.zip.JdkZipExporterDelegate$1.call(JdkZipExporterDelegate.java:124)
   at 
 org.jboss.shrinkwrap.impl.base.exporter.zip.JdkZipExporterDelegate$1.call(JdkZipExporterDelegate.java:118)
   at java.util.concurrent.FutureTask.run(FutureTask.java:262)
   at 
 java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1145)
   at 
 java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:615)
   at java.lang.Thread.run(Thread.java:745)
 Caused by: org.jboss.shrinkwrap.api.exporter.ArchiveExportException: 
 java.lang.IncompatibleClassChangeError: Implementing class
   at 
 org.jboss.shrinkwrap.impl.base.exporter.FutureCompletionInputStream.awaitOnFutureOnDone(FutureCompletionInputStream.java:125)
   at 
 org.jboss.shrinkwrap.impl.base.exporter.FutureCompletionInputStream.read(FutureCompletionInputStream.java:81)
   at java.io.PipedInputStream.read(PipedInputStream.java:378)
   at 
 org.jboss.shrinkwrap.impl.base.exporter.FutureCompletionInputStream.read(FutureCompletionInputStream.java:92)
   at java.io.InputStream.read(InputStream.java:101)
   at org.jboss.shrinkwrap.impl.base.io.IOUtil.copy(IOUtil.java:138)
   at 
 org.jboss.shrinkwrap.impl.base.exporter.StreamExporterDelegateBase$2.execute(StreamExporterDelegateBase.java:261)
   at 
 org.jboss.shrinkwrap.impl.base.exporter.StreamExporterDelegateBase$2.execute(StreamExporterDelegateBase.java:233)
   at 
 org.jboss.shrinkwrap.impl.base.io.IOUtil.closeOnComplete(IOUtil.java:217)
   ... 14 more
 Caused by: java.lang.IncompatibleClassChangeError: Implementing class
   at java.lang.ClassLoader.defineClass1(Native Method)
   at java.lang.ClassLoader.defineClass(ClassLoader.java:800)
   at 
 java.security.SecureClassLoader.defineClass(SecureClassLoader.java:142)
   at java.net.URLClassLoader.defineClass(URLClassLoader.java:449)
   at java.net.URLClassLoader.access$100(URLClassLoader.java:71)
   at java.net.URLClassLoader$1.run(URLClassLoader.java:361)
   at java.net.URLClassLoader$1.run(URLClassLoader.java:355)
   at java.security.AccessController.doPrivileged(Native Method)
   at java.net.URLClassLoader.findClass(URLClassLoader.java:354)
   at java.lang.ClassLoader.loadClass(ClassLoader.java:425)
   at sun.misc.Launcher$AppClassLoader.loadClass(Launcher.java:308)
   at java.lang.ClassLoader.loadClass(ClassLoader.java:358)
   at 
 org.jboss.arquillian.extension.jacoco.client.InstrumenterAsset.openStream(InstrumenterAsset.java:52)
   at 
 org.jboss.shrinkwrap.impl.base.exporter.StreamExporterDelegateBase.processNode(StreamExporterDelegateBase.java:227)
   at 
 org.jboss.shrinkwrap.impl.base.exporter.AbstractExporterDelegate.processNode(AbstractExporterDelegate.java:105)
   at 
 

[jira] [Updated] (DELTASPIKE-856) Eclipse deployment to container add remove view shows deltaspike-jsf-module-impl-ee6-1.2.1 as if it was an app module - in weblogic we get a double jar file

[Rafael Benevides (JIRA)]

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

Rafael Benevides updated DELTASPIKE-856:

Assignee: (was: Rafael Benevides)

 Eclipse deployment to container add remove view shows 
 deltaspike-jsf-module-impl-ee6-1.2.1 as if it was an app module - in weblogic 
 we get a double jar file
 

 Key: DELTASPIKE-856
 URL: https://issues.apache.org/jira/browse/DELTASPIKE-856
 Project: DeltaSpike
  Issue Type: Bug
  Components: JSF-Module
Affects Versions: 1.2.1
 Environment: Windows 7 , Eclipse Version: Luna (4.4) Build id: 
 I20140606-1215, WTP plugin  Version: 
 1.2.100.v201405081709-797LBiCcNBHQFTGaGVbu3KEF
 Build id: 20131017041352, Oracle enterprise Pack for Ecliplse plugin: Build 
 id: 20131017041352
Reporter: Nuno G. de M

 There is something special about the deltaspike-jsf-module-impl-ee6-1.2.1.jar 
 .
 This project dependency alone, unlike every other project dependency, it is 
 displayed itself by eclipse Add  Remove view to an application server as if 
 it were a module itself of the war application to be deployed.
 When a user, for example, configures weblogic 12.1.2 server to take in 
 deployments as exploded war files, what ends up happening after the 
 deployment goes through is that we see within
 Weblogic Domain  AdminServer  temp  mydeployment  war Web-inf/lib 
 we see the jar dependency twice.
 First we see the correct and expected dependency:
 deltaspike-jsf-module-impl-ee6-1.2.1.jar
 But then we have a second file in the lib folder called:
 deltaspike-jsf-module-impl-ee6-1.2.1.jar.jar
 This appears to be releated to the Add  Remove view of eclipse, since 
 normally under the project war file itself we only see other open project 
 modules.
 I am pasting in this post an url to a google driver sample application that 
 you can use to simulate the scenario.
 The zip file will contain both a sample application that I have once before 
 submitted to you already (regarding the view access scoped beans) and 
 document file illustrating the issue in my IDE.
 To simulate the issue simply:
 (a) create a domain
 (b) do mvn eclipse:eclipse and import the project
 (c) Configure your weblogic domain to accept exploded war deployment
 (d) click on add and remove on the domain you want to deploy to and see that 
 the JEE6 impl appears as a module.
 (e) deploy, and look at what happens within the weblogic deployment folder
 URL:
 https://drive.google.com/file/d/0B_dEiNBGUsxqOGZRUjBJQU85WXc/view?usp=sharing
 It is not yet clear if this phenomena may be creating problems for us when we 
 use eclipse to run the deployment.
 In the sample application we have no issues.
 Thank you for your support,
 My kindest regards.



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

[jira] [Updated] (DELTASPIKE-856) Eclipse deployment to container add remove view shows deltaspike-jsf-module-impl-ee6-1.2.1 as if it was an app module - in weblogic we get a double jar file

[Rafael Benevides (JIRA)]

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

Rafael Benevides updated DELTASPIKE-856:

Attachment: Screenshot 2015-03-13 18.05.21.png

The add/remove pop up is attached now.


 Eclipse deployment to container add remove view shows 
 deltaspike-jsf-module-impl-ee6-1.2.1 as if it was an app module - in weblogic 
 we get a double jar file
 

 Key: DELTASPIKE-856
 URL: https://issues.apache.org/jira/browse/DELTASPIKE-856
 Project: DeltaSpike
  Issue Type: Bug
  Components: JSF-Module
Affects Versions: 1.2.1
 Environment: Windows 7 , Eclipse Version: Luna (4.4) Build id: 
 I20140606-1215, WTP plugin  Version: 
 1.2.100.v201405081709-797LBiCcNBHQFTGaGVbu3KEF
 Build id: 20131017041352, Oracle enterprise Pack for Ecliplse plugin: Build 
 id: 20131017041352
Reporter: Nuno G. de M
 Attachments: Screenshot 2015-03-13 18.05.21.png


 There is something special about the deltaspike-jsf-module-impl-ee6-1.2.1.jar 
 .
 This project dependency alone, unlike every other project dependency, it is 
 displayed itself by eclipse Add  Remove view to an application server as if 
 it were a module itself of the war application to be deployed.
 When a user, for example, configures weblogic 12.1.2 server to take in 
 deployments as exploded war files, what ends up happening after the 
 deployment goes through is that we see within
 Weblogic Domain  AdminServer  temp  mydeployment  war Web-inf/lib 
 we see the jar dependency twice.
 First we see the correct and expected dependency:
 deltaspike-jsf-module-impl-ee6-1.2.1.jar
 But then we have a second file in the lib folder called:
 deltaspike-jsf-module-impl-ee6-1.2.1.jar.jar
 This appears to be releated to the Add  Remove view of eclipse, since 
 normally under the project war file itself we only see other open project 
 modules.
 I am pasting in this post an url to a google driver sample application that 
 you can use to simulate the scenario.
 The zip file will contain both a sample application that I have once before 
 submitted to you already (regarding the view access scoped beans) and 
 document file illustrating the issue in my IDE.
 To simulate the issue simply:
 (a) create a domain
 (b) do mvn eclipse:eclipse and import the project
 (c) Configure your weblogic domain to accept exploded war deployment
 (d) click on add and remove on the domain you want to deploy to and see that 
 the JEE6 impl appears as a module.
 (e) deploy, and look at what happens within the weblogic deployment folder
 URL:
 https://drive.google.com/file/d/0B_dEiNBGUsxqOGZRUjBJQU85WXc/view?usp=sharing
 It is not yet clear if this phenomena may be creating problems for us when we 
 use eclipse to run the deployment.
 In the sample application we have no issues.
 Thank you for your support,
 My kindest regards.



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

[jira] [Reopened] (DELTASPIKE-856) Eclipse deployment to container add remove view shows deltaspike-jsf-module-impl-ee6-1.2.1 as if it was an app module - in weblogic we get a double jar file

[Rafael Benevides (JIRA)]

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

Rafael Benevides reopened DELTASPIKE-856:
-

 Eclipse deployment to container add remove view shows 
 deltaspike-jsf-module-impl-ee6-1.2.1 as if it was an app module - in weblogic 
 we get a double jar file
 

 Key: DELTASPIKE-856
 URL: https://issues.apache.org/jira/browse/DELTASPIKE-856
 Project: DeltaSpike
  Issue Type: Bug
  Components: JSF-Module
Affects Versions: 1.2.1
 Environment: Windows 7 , Eclipse Version: Luna (4.4) Build id: 
 I20140606-1215, WTP plugin  Version: 
 1.2.100.v201405081709-797LBiCcNBHQFTGaGVbu3KEF
 Build id: 20131017041352, Oracle enterprise Pack for Ecliplse plugin: Build 
 id: 20131017041352
Reporter: Nuno G. de M

 There is something special about the deltaspike-jsf-module-impl-ee6-1.2.1.jar 
 .
 This project dependency alone, unlike every other project dependency, it is 
 displayed itself by eclipse Add  Remove view to an application server as if 
 it were a module itself of the war application to be deployed.
 When a user, for example, configures weblogic 12.1.2 server to take in 
 deployments as exploded war files, what ends up happening after the 
 deployment goes through is that we see within
 Weblogic Domain  AdminServer  temp  mydeployment  war Web-inf/lib 
 we see the jar dependency twice.
 First we see the correct and expected dependency:
 deltaspike-jsf-module-impl-ee6-1.2.1.jar
 But then we have a second file in the lib folder called:
 deltaspike-jsf-module-impl-ee6-1.2.1.jar.jar
 This appears to be releated to the Add  Remove view of eclipse, since 
 normally under the project war file itself we only see other open project 
 modules.
 I am pasting in this post an url to a google driver sample application that 
 you can use to simulate the scenario.
 The zip file will contain both a sample application that I have once before 
 submitted to you already (regarding the view access scoped beans) and 
 document file illustrating the issue in my IDE.
 To simulate the issue simply:
 (a) create a domain
 (b) do mvn eclipse:eclipse and import the project
 (c) Configure your weblogic domain to accept exploded war deployment
 (d) click on add and remove on the domain you want to deploy to and see that 
 the JEE6 impl appears as a module.
 (e) deploy, and look at what happens within the weblogic deployment folder
 URL:
 https://drive.google.com/file/d/0B_dEiNBGUsxqOGZRUjBJQU85WXc/view?usp=sharing
 It is not yet clear if this phenomena may be creating problems for us when we 
 use eclipse to run the deployment.
 In the sample application we have no issues.
 Thank you for your support,
 My kindest regards.



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

[jira] [Comment Edited] (DELTASPIKE-856) Eclipse deployment to container add remove view shows deltaspike-jsf-module-impl-ee6-1.2.1 as if it was an app module - in weblogic we get a double jar file

[Rafael Benevides (JIRA)]

[ 
https://issues.apache.org/jira/browse/DELTASPIKE-856?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=14361179#comment-14361179
 ] 

Rafael Benevides edited comment on DELTASPIKE-856 at 3/13/15 10:13 PM:
---

Hi Nuno.

The add/remove pop up is attached now. I used Latest Eclipse Luna SR2 with 
latest WTP and OEEPE installed through Eclipse Marketplace.



was (Author: rafabene):
The add/remove pop up is attached now.


 Eclipse deployment to container add remove view shows 
 deltaspike-jsf-module-impl-ee6-1.2.1 as if it was an app module - in weblogic 
 we get a double jar file
 

 Key: DELTASPIKE-856
 URL: https://issues.apache.org/jira/browse/DELTASPIKE-856
 Project: DeltaSpike
  Issue Type: Bug
  Components: JSF-Module
Affects Versions: 1.2.1
 Environment: Windows 7 , Eclipse Version: Luna (4.4) Build id: 
 I20140606-1215, WTP plugin  Version: 
 1.2.100.v201405081709-797LBiCcNBHQFTGaGVbu3KEF
 Build id: 20131017041352, Oracle enterprise Pack for Ecliplse plugin: Build 
 id: 20131017041352
Reporter: Nuno G. de M
 Attachments: Screenshot 2015-03-13 18.05.21.png


 There is something special about the deltaspike-jsf-module-impl-ee6-1.2.1.jar 
 .
 This project dependency alone, unlike every other project dependency, it is 
 displayed itself by eclipse Add  Remove view to an application server as if 
 it were a module itself of the war application to be deployed.
 When a user, for example, configures weblogic 12.1.2 server to take in 
 deployments as exploded war files, what ends up happening after the 
 deployment goes through is that we see within
 Weblogic Domain  AdminServer  temp  mydeployment  war Web-inf/lib 
 we see the jar dependency twice.
 First we see the correct and expected dependency:
 deltaspike-jsf-module-impl-ee6-1.2.1.jar
 But then we have a second file in the lib folder called:
 deltaspike-jsf-module-impl-ee6-1.2.1.jar.jar
 This appears to be releated to the Add  Remove view of eclipse, since 
 normally under the project war file itself we only see other open project 
 modules.
 I am pasting in this post an url to a google driver sample application that 
 you can use to simulate the scenario.
 The zip file will contain both a sample application that I have once before 
 submitted to you already (regarding the view access scoped beans) and 
 document file illustrating the issue in my IDE.
 To simulate the issue simply:
 (a) create a domain
 (b) do mvn eclipse:eclipse and import the project
 (c) Configure your weblogic domain to accept exploded war deployment
 (d) click on add and remove on the domain you want to deploy to and see that 
 the JEE6 impl appears as a module.
 (e) deploy, and look at what happens within the weblogic deployment folder
 URL:
 https://drive.google.com/file/d/0B_dEiNBGUsxqOGZRUjBJQU85WXc/view?usp=sharing
 It is not yet clear if this phenomena may be creating problems for us when we 
 use eclipse to run the deployment.
 In the sample application we have no issues.
 Thank you for your support,
 My kindest regards.



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

[jira] [Reopened] (DELTASPIKE-854) Jacoco profile doesn't work anymore

[Rafael Benevides (JIRA)]

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

Rafael Benevides reopened DELTASPIKE-854:
-

I had to revert the PR because it fails with Weld.

please, run mvn clean install -PWeld to check.

 Jacoco profile doesn't work anymore
 ---

 Key: DELTASPIKE-854
 URL: https://issues.apache.org/jira/browse/DELTASPIKE-854
 Project: DeltaSpike
  Issue Type: Bug
Reporter: Tomas Remes
Assignee: Rafael Benevides

 Executing code coverage report profile will fail in partial-bean module with:
 {noformat}
 org.jboss.shrinkwrap.api.exporter.ArchiveExportException: Failed to write 
 asset to output: /WEB-INF/lib/asm-tree-5.0.3.jar
   at 
 org.jboss.shrinkwrap.impl.base.exporter.StreamExporterDelegateBase$3.handle(StreamExporterDelegateBase.java:272)
   at 
 org.jboss.shrinkwrap.impl.base.io.IOUtil.closeOnComplete(IOUtil.java:219)
   at 
 org.jboss.shrinkwrap.impl.base.exporter.StreamExporterDelegateBase.processNode(StreamExporterDelegateBase.java:233)
   at 
 org.jboss.shrinkwrap.impl.base.exporter.AbstractExporterDelegate.processNode(AbstractExporterDelegate.java:105)
   at 
 org.jboss.shrinkwrap.impl.base.exporter.AbstractExporterDelegate.processNode(AbstractExporterDelegate.java:109)
   at 
 org.jboss.shrinkwrap.impl.base.exporter.AbstractExporterDelegate.processNode(AbstractExporterDelegate.java:109)
   at 
 org.jboss.shrinkwrap.impl.base.exporter.AbstractExporterDelegate.doExport(AbstractExporterDelegate.java:95)
   at 
 org.jboss.shrinkwrap.impl.base.exporter.StreamExporterDelegateBase.access$001(StreamExporterDelegateBase.java:50)
   at 
 org.jboss.shrinkwrap.impl.base.exporter.StreamExporterDelegateBase$1.call(StreamExporterDelegateBase.java:121)
   at 
 org.jboss.shrinkwrap.impl.base.exporter.StreamExporterDelegateBase$1.call(StreamExporterDelegateBase.java:116)
   at 
 org.jboss.shrinkwrap.impl.base.exporter.zip.JdkZipExporterDelegate$1.call(JdkZipExporterDelegate.java:124)
   at 
 org.jboss.shrinkwrap.impl.base.exporter.zip.JdkZipExporterDelegate$1.call(JdkZipExporterDelegate.java:118)
   at java.util.concurrent.FutureTask.run(FutureTask.java:262)
   at 
 java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1145)
   at 
 java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:615)
   at java.lang.Thread.run(Thread.java:745)
 Caused by: org.jboss.shrinkwrap.api.exporter.ArchiveExportException: 
 java.lang.IncompatibleClassChangeError: Implementing class
   at 
 org.jboss.shrinkwrap.impl.base.exporter.FutureCompletionInputStream.awaitOnFutureOnDone(FutureCompletionInputStream.java:125)
   at 
 org.jboss.shrinkwrap.impl.base.exporter.FutureCompletionInputStream.read(FutureCompletionInputStream.java:81)
   at java.io.PipedInputStream.read(PipedInputStream.java:378)
   at 
 org.jboss.shrinkwrap.impl.base.exporter.FutureCompletionInputStream.read(FutureCompletionInputStream.java:92)
   at java.io.InputStream.read(InputStream.java:101)
   at org.jboss.shrinkwrap.impl.base.io.IOUtil.copy(IOUtil.java:138)
   at 
 org.jboss.shrinkwrap.impl.base.exporter.StreamExporterDelegateBase$2.execute(StreamExporterDelegateBase.java:261)
   at 
 org.jboss.shrinkwrap.impl.base.exporter.StreamExporterDelegateBase$2.execute(StreamExporterDelegateBase.java:233)
   at 
 org.jboss.shrinkwrap.impl.base.io.IOUtil.closeOnComplete(IOUtil.java:217)
   ... 14 more
 Caused by: java.lang.IncompatibleClassChangeError: Implementing class
   at java.lang.ClassLoader.defineClass1(Native Method)
   at java.lang.ClassLoader.defineClass(ClassLoader.java:800)
   at 
 java.security.SecureClassLoader.defineClass(SecureClassLoader.java:142)
   at java.net.URLClassLoader.defineClass(URLClassLoader.java:449)
   at java.net.URLClassLoader.access$100(URLClassLoader.java:71)
   at java.net.URLClassLoader$1.run(URLClassLoader.java:361)
   at java.net.URLClassLoader$1.run(URLClassLoader.java:355)
   at java.security.AccessController.doPrivileged(Native Method)
   at java.net.URLClassLoader.findClass(URLClassLoader.java:354)
   at java.lang.ClassLoader.loadClass(ClassLoader.java:425)
   at sun.misc.Launcher$AppClassLoader.loadClass(Launcher.java:308)
   at java.lang.ClassLoader.loadClass(ClassLoader.java:358)
   at 
 org.jboss.arquillian.extension.jacoco.client.InstrumenterAsset.openStream(InstrumenterAsset.java:52)
   at 
 org.jboss.shrinkwrap.impl.base.exporter.StreamExporterDelegateBase.processNode(StreamExporterDelegateBase.java:227)
   at 
 org.jboss.shrinkwrap.impl.base.exporter.AbstractExporterDelegate.processNode(AbstractExporterDelegate.java:105)
   at 
 

[jira] [Resolved] (DELTASPIKE-854) Jacoco profile doesn't work anymore

[Rafael Benevides (JIRA)]

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

Rafael Benevides resolved DELTASPIKE-854.
-
Resolution: Fixed

PR merged

 Jacoco profile doesn't work anymore
 ---

 Key: DELTASPIKE-854
 URL: https://issues.apache.org/jira/browse/DELTASPIKE-854
 Project: DeltaSpike
  Issue Type: Bug
Reporter: Tomas Remes
Assignee: Rafael Benevides

 Executing code coverage report profile will fail in partial-bean module with:
 {noformat}
 org.jboss.shrinkwrap.api.exporter.ArchiveExportException: Failed to write 
 asset to output: /WEB-INF/lib/asm-tree-5.0.3.jar
   at 
 org.jboss.shrinkwrap.impl.base.exporter.StreamExporterDelegateBase$3.handle(StreamExporterDelegateBase.java:272)
   at 
 org.jboss.shrinkwrap.impl.base.io.IOUtil.closeOnComplete(IOUtil.java:219)
   at 
 org.jboss.shrinkwrap.impl.base.exporter.StreamExporterDelegateBase.processNode(StreamExporterDelegateBase.java:233)
   at 
 org.jboss.shrinkwrap.impl.base.exporter.AbstractExporterDelegate.processNode(AbstractExporterDelegate.java:105)
   at 
 org.jboss.shrinkwrap.impl.base.exporter.AbstractExporterDelegate.processNode(AbstractExporterDelegate.java:109)
   at 
 org.jboss.shrinkwrap.impl.base.exporter.AbstractExporterDelegate.processNode(AbstractExporterDelegate.java:109)
   at 
 org.jboss.shrinkwrap.impl.base.exporter.AbstractExporterDelegate.doExport(AbstractExporterDelegate.java:95)
   at 
 org.jboss.shrinkwrap.impl.base.exporter.StreamExporterDelegateBase.access$001(StreamExporterDelegateBase.java:50)
   at 
 org.jboss.shrinkwrap.impl.base.exporter.StreamExporterDelegateBase$1.call(StreamExporterDelegateBase.java:121)
   at 
 org.jboss.shrinkwrap.impl.base.exporter.StreamExporterDelegateBase$1.call(StreamExporterDelegateBase.java:116)
   at 
 org.jboss.shrinkwrap.impl.base.exporter.zip.JdkZipExporterDelegate$1.call(JdkZipExporterDelegate.java:124)
   at 
 org.jboss.shrinkwrap.impl.base.exporter.zip.JdkZipExporterDelegate$1.call(JdkZipExporterDelegate.java:118)
   at java.util.concurrent.FutureTask.run(FutureTask.java:262)
   at 
 java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1145)
   at 
 java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:615)
   at java.lang.Thread.run(Thread.java:745)
 Caused by: org.jboss.shrinkwrap.api.exporter.ArchiveExportException: 
 java.lang.IncompatibleClassChangeError: Implementing class
   at 
 org.jboss.shrinkwrap.impl.base.exporter.FutureCompletionInputStream.awaitOnFutureOnDone(FutureCompletionInputStream.java:125)
   at 
 org.jboss.shrinkwrap.impl.base.exporter.FutureCompletionInputStream.read(FutureCompletionInputStream.java:81)
   at java.io.PipedInputStream.read(PipedInputStream.java:378)
   at 
 org.jboss.shrinkwrap.impl.base.exporter.FutureCompletionInputStream.read(FutureCompletionInputStream.java:92)
   at java.io.InputStream.read(InputStream.java:101)
   at org.jboss.shrinkwrap.impl.base.io.IOUtil.copy(IOUtil.java:138)
   at 
 org.jboss.shrinkwrap.impl.base.exporter.StreamExporterDelegateBase$2.execute(StreamExporterDelegateBase.java:261)
   at 
 org.jboss.shrinkwrap.impl.base.exporter.StreamExporterDelegateBase$2.execute(StreamExporterDelegateBase.java:233)
   at 
 org.jboss.shrinkwrap.impl.base.io.IOUtil.closeOnComplete(IOUtil.java:217)
   ... 14 more
 Caused by: java.lang.IncompatibleClassChangeError: Implementing class
   at java.lang.ClassLoader.defineClass1(Native Method)
   at java.lang.ClassLoader.defineClass(ClassLoader.java:800)
   at 
 java.security.SecureClassLoader.defineClass(SecureClassLoader.java:142)
   at java.net.URLClassLoader.defineClass(URLClassLoader.java:449)
   at java.net.URLClassLoader.access$100(URLClassLoader.java:71)
   at java.net.URLClassLoader$1.run(URLClassLoader.java:361)
   at java.net.URLClassLoader$1.run(URLClassLoader.java:355)
   at java.security.AccessController.doPrivileged(Native Method)
   at java.net.URLClassLoader.findClass(URLClassLoader.java:354)
   at java.lang.ClassLoader.loadClass(ClassLoader.java:425)
   at sun.misc.Launcher$AppClassLoader.loadClass(Launcher.java:308)
   at java.lang.ClassLoader.loadClass(ClassLoader.java:358)
   at 
 org.jboss.arquillian.extension.jacoco.client.InstrumenterAsset.openStream(InstrumenterAsset.java:52)
   at 
 org.jboss.shrinkwrap.impl.base.exporter.StreamExporterDelegateBase.processNode(StreamExporterDelegateBase.java:227)
   at 
 org.jboss.shrinkwrap.impl.base.exporter.AbstractExporterDelegate.processNode(AbstractExporterDelegate.java:105)
   at 
 org.jboss.shrinkwrap.impl.base.exporter.AbstractExporterDelegate.processNode(AbstractExporterDelegate.java:109)
   at 
 

[jira] [Created] (DELTASPIKE-855) Review deltaspike-release-plugin and distribution profile to not consider deltaspike-root

[Rafael Benevides (JIRA)]

Rafael Benevides created DELTASPIKE-855:
---

 Summary: Review deltaspike-release-plugin and distribution profile 
to not consider deltaspike-root
 Key: DELTASPIKE-855
 URL: https://issues.apache.org/jira/browse/DELTASPIKE-855
 Project: DeltaSpike
  Issue Type: Improvement
  Components: Build
Affects Versions: 1.3.0
Reporter: Rafael Benevides
Assignee: Rafael Benevides
 Fix For: 1.3.1, 1.4.0


Because DELTASPIKE-814 the maven-release-plugin it introduced a now expected 
behaviour in the distribution.
Effects:
- Sources distribution name change: deltaspike-root-1.3.0-source-release.zip
- Sources distribution content have site and documentation included.
- git tag name change: 
https://github.com/apache/deltaspike/releases/tag/deltaspike-root-1.3.0

The distribution profile and maven-release-plugin should be reviewed to include 
only deltaspike-project.



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

[jira] [Resolved] (DELTASPIKE-835) Improve build config and add tests

[Rafael Benevides (JIRA)]

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

Rafael Benevides resolved DELTASPIKE-835.
-
Resolution: Fixed

Commit: 
https://github.com/apache/deltaspike/commit/12a3a43270c24f76ce96108f98e76e367cb55065

 Improve build config and add tests
 --

 Key: DELTASPIKE-835
 URL: https://issues.apache.org/jira/browse/DELTASPIKE-835
 Project: DeltaSpike
  Issue Type: Improvement
Reporter: Rafael Benevides
Assignee: Rafael Benevides





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

[jira] [Closed] (DELTASPIKE-820) check injection of extension-instances

[Rafael Benevides (JIRA)]

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

Rafael Benevides closed DELTASPIKE-820.
---
Resolution: Not a Problem

 check injection of extension-instances
 --

 Key: DELTASPIKE-820
 URL: https://issues.apache.org/jira/browse/DELTASPIKE-820
 Project: DeltaSpike
  Issue Type: Task
  Components: Documentation
Affects Versions: 1.2.1
 Environment: JBoss EAP 6.3
Reporter: Martin E.
Assignee: Rafael Benevides
Priority: Minor

 if there is an issue caused by jboss eap, it needs to be documented.



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

[jira] [Resolved] (DELTASPIKE-829) add hints for using jersey-test with test-control

[Rafael Benevides (JIRA)]

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

Rafael Benevides resolved DELTASPIKE-829.
-
Resolution: Fixed

Published: 
http://deltaspike.apache.org/documentation/test-control.html#_using_jersey_test_with_test_control

 add hints for using jersey-test with test-control
 -

 Key: DELTASPIKE-829
 URL: https://issues.apache.org/jira/browse/DELTASPIKE-829
 Project: DeltaSpike
  Issue Type: Improvement
  Components: Documentation, TestControl
Reporter: Gerhard Petracek
Assignee: Rafael Benevides

 jersey-test starts jetty which answers requests in a separated thread. since 
 ds test-control just handles the thread of the test itself, it's needed to 
 integrate jetty and jersey with the cdi-container. usually that's done via a 
 ServletRequestListener - the following part describes an alternative approach 
 for jersey-test:
 {code}
 //use: 
 -Djersey.config.test.container.factory=custom.CdiAwareJettyTestContainerFactory
 @RunWith(CdiTestRunner.class)
 public class SimpleCdiAndJaxRsTest extends JerseyTest
 {
   //...
 }
 {code}
 or
 {code}
 public class CdiAwareJerseyTest extends JerseyTest
 {
 static
 {
 System.setProperty(jersey.config.test.container.factory, 
 CdiAwareJettyTestContainerFactory.class.getName());
 }
 }
 @RunWith(CdiTestRunner.class)
 public class SimpleCdiAndJaxRsTest extends CdiAwareJerseyTest
 {
 //...
 }
 {code}
 {code}
 public class CdiAwareJettyTestContainerFactory implements TestContainerFactory
 {
 @Override
 public TestContainer create(final URI baseUri, final DeploymentContext 
 context) throws IllegalArgumentException
 {
 return new CdiAwareJettyTestContainer(baseUri, context);
 }
 }
 {code}
 CdiAwareJettyTestContainer is a copy of 
 JettyTestContainerFactory.JettyTestContainer but with
 {code}
 HandlerWrapper cdiHandlerWrapper = new CdiAwareHandlerWrapper();
 cdiHandlerWrapper.setHandler(this.server.getHandler());
 this.server.setHandler(cdiHandlerWrapper);
 {code}
 after the line with JettyHttpContainerFactory#createServer
 {code}
 //activate the request-context e.g. via:
 public class CdiAwareHandlerWrapper extends HandlerWrapper
 {
 @Override
 public void handle(String target, Request baseRequest, HttpServletRequest 
 request, HttpServletResponse response) throws IOException, ServletException
 {
 CdiContainer cdiContainer = CdiContainerLoader.getCdiContainer();
 try
 {
 
 cdiContainer.getContextControl().startContext(RequestScoped.class);
 super.handle(target, baseRequest, request, response);
 }
 finally
 {
 cdiContainer.getContextControl().stopContext(RequestScoped.class);
 }
 }
 }
 {code}



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

[jira] [Resolved] (DELTASPIKE-811) document custom project-stages

[Rafael Benevides (JIRA)]

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

Rafael Benevides resolved DELTASPIKE-811.
-
Resolution: Fixed

Published:
- http://deltaspike.apache.org/documentation/core.html#_type_safe_projectstage
- http://deltaspike.apache.org/documentation/projectstage.html

 document custom project-stages
 --

 Key: DELTASPIKE-811
 URL: https://issues.apache.org/jira/browse/DELTASPIKE-811
 Project: DeltaSpike
  Issue Type: Task
  Components: Documentation
Affects Versions: 1.2.1
Reporter: Gerhard Petracek
Assignee: Rafael Benevides
 Fix For: 1.2.2


 see e.g.:
 https://github.com/os890/tomee_mf_stack_001/blob/master/src/main/java/org/superbiz/myfaces/CustomProjectStage.java
 https://github.com/os890/tomee_mf_stack_001/blob/master/src/main/resources/META-INF/services/org.apache.myfaces.extensions.cdi.core.api.projectstage.ProjectStageHolder



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

[jira] [Commented] (DELTASPIKE-648) @ConfigProperty in Wildfly 8.1 not working correctly

[Rafael Benevides (JIRA)]

[ 
https://issues.apache.org/jira/browse/DELTASPIKE-648?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=14302571#comment-14302571
 ] 

Rafael Benevides commented on DELTASPIKE-648:
-

I tried the revert and obviously it broke the WildFly implementation. I'm not 
sure how we should deal with it or just leave it (as it only happens for EARs 
and they aren't fully supported anyway). 


 @ConfigProperty in Wildfly 8.1 not working correctly
 

 Key: DELTASPIKE-648
 URL: https://issues.apache.org/jira/browse/DELTASPIKE-648
 Project: DeltaSpike
  Issue Type: Bug
  Components: Configuration
Affects Versions: 1.0.0
 Environment: Mac OS X 10.9, Java 1.7.45, Wildfly 8.1
Reporter: Sven Panko
Assignee: Mark Struberg
Priority: Minor
 Fix For: 1.0.1

 Attachments: DELTASPIKE-648.patch


 I am not quite sure if my problem is related to the (already closed) 
 DELTASPIKE-451, but it is quite similar in behavior:
 * I have an EAR file that packages a few EJB jars (these are NOT contained in 
 the lib directory of the EAR)
 * the application.xml uses the default isolation mechanism, which means that 
 all libs in /lib have access to all classes (although I don't think this is 
 relevant in my case since my EJB jars are not located in /lib)
 * inside one of the EJB jars I put a property file that should be used ONLY 
 by beans inside this jar file
 * I created an implementation of PropertyFileConfig and provided the path to 
 this property file
 * during startup I can see that the property file is correctly detected and 
 stored in the hashmap using the EAR classloader
 * I have a bean (@Singleton, @Startup) inside the aforementioned EJB jar that 
 expects a property to be injected via @Inject @ConfigProperty - which does 
 not work
 I debugged the startup process and detected that the property injection into 
 the bean fails because the lookup into the hashmap will not be done with the 
 EAR classloader, but with the jar's classloader, which is totally 
 understandable. What I do not understand, however, is, why the resolution 
 process which kicks in afterwards does no longer find my PropertyFileConfig 
 implementation, which worked in the EAR classloader case.
 My temporary solution now is to put a 
 META-INF/services/org.apache.deltaspike.core.spi.config.ConfigSourceProvider 
 file into the EJB jar and reference a custom ConfigSourceProvider. This file 
 is always picked up correctly (interestingly in both cases, the EAR 
 classloader and the jar classloader).
 Shouldn't the ConfigResolver pick up my PropertyFileConfig implementation in 
 both cases as well?



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

[jira] [Resolved] (DELTASPIKE-807) update external resources

[Rafael Benevides (JIRA)]

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

Rafael Benevides resolved DELTASPIKE-807.
-
Resolution: Fixed

 update external resources
 -

 Key: DELTASPIKE-807
 URL: https://issues.apache.org/jira/browse/DELTASPIKE-807
 Project: DeltaSpike
  Issue Type: Task
  Components: Documentation
Reporter: Gerhard Petracek
Assignee: Rafael Benevides
 Fix For: 1.2.2


 there are multiple resources we should link - e.g.
 http://www.slideshare.net/os890/apache-deltaspike
 http://www.slideshare.net/os890/flexibilitaet-mit-cdi-und-apache-delta-spike
 http://www.slideshare.net/os890/myfaces-codi-and-jboss-seam3-become-apache-deltaspike
 http://de.slideshare.net/MarioLeanderReimer/migrating-a-jsfbased-web-application-from-spring-3-to-java-ee-7-and-cdi
  [JavaOne - Migrating a JSF-Based Web Application from Spring 3 to Java EE 7 
 and CDI]
 https://parleys.com/play/543faae5e4b06e1184ae423a/about
 https://github.com/rsmeral/deltaspike-examples
 and many others...



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

[jira] [Reopened] (DELTASPIKE-807) update external resources

[Rafael Benevides (JIRA)]

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

Rafael Benevides reopened DELTASPIKE-807:
-

Add [~antoine] slides and presentaion to the External resources

 update external resources
 -

 Key: DELTASPIKE-807
 URL: https://issues.apache.org/jira/browse/DELTASPIKE-807
 Project: DeltaSpike
  Issue Type: Task
  Components: Documentation
Reporter: Gerhard Petracek
Assignee: Rafael Benevides
 Fix For: 1.2.2


 there are multiple resources we should link - e.g.
 http://www.slideshare.net/os890/apache-deltaspike
 http://www.slideshare.net/os890/flexibilitaet-mit-cdi-und-apache-delta-spike
 http://www.slideshare.net/os890/myfaces-codi-and-jboss-seam3-become-apache-deltaspike
 http://de.slideshare.net/MarioLeanderReimer/migrating-a-jsfbased-web-application-from-spring-3-to-java-ee-7-and-cdi
  [JavaOne - Migrating a JSF-Based Web Application from Spring 3 to Java EE 7 
 and CDI]
 https://parleys.com/play/543faae5e4b06e1184ae423a/about
 https://github.com/rsmeral/deltaspike-examples
 and many others...



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

[jira] [Updated] (DELTASPIKE-809) Clean up cdi ctrl and cdi imp pages

[Rafael Benevides (JIRA)]

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

Rafael Benevides updated DELTASPIKE-809:

Assignee: John D. Ament  (was: Rafael Benevides)

 Clean up cdi ctrl and cdi imp pages
 ---

 Key: DELTASPIKE-809
 URL: https://issues.apache.org/jira/browse/DELTASPIKE-809
 Project: DeltaSpike
  Issue Type: Improvement
  Components: Documentation
Affects Versions: 1.2.1
Reporter: John D. Ament
Assignee: John D. Ament

 There's some issues between these two pages:
 http://deltaspike.apache.org/documentation/container-control.html
 http://deltaspike.apache.org/documentation/cdiimp.html
 I would recommend somehow merging them together to avoid redundancy.  For 
 example, container-control doesn't explain how to add dependencies properly.  
 cdiimp explains too much.
 I think cdiimp should just link to container-control to declare the 
 dependencies.  WDYT?



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

[jira] [Resolved] (DELTASPIKE-807) update external resources

[Rafael Benevides (JIRA)]

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

Rafael Benevides resolved DELTASPIKE-807.
-
Resolution: Fixed

Published: http://deltaspike.apache.org/external.html

 update external resources
 -

 Key: DELTASPIKE-807
 URL: https://issues.apache.org/jira/browse/DELTASPIKE-807
 Project: DeltaSpike
  Issue Type: Task
  Components: Documentation
Reporter: Gerhard Petracek
Assignee: Rafael Benevides
 Fix For: 1.2.2


 there are multiple resources we should link - e.g.
 http://www.slideshare.net/os890/apache-deltaspike
 http://www.slideshare.net/os890/flexibilitaet-mit-cdi-und-apache-delta-spike
 http://www.slideshare.net/os890/myfaces-codi-and-jboss-seam3-become-apache-deltaspike
 http://de.slideshare.net/MarioLeanderReimer/migrating-a-jsfbased-web-application-from-spring-3-to-java-ee-7-and-cdi
  [JavaOne - Migrating a JSF-Based Web Application from Spring 3 to Java EE 7 
 and CDI]
 https://parleys.com/play/543faae5e4b06e1184ae423a/about
 https://github.com/rsmeral/deltaspike-examples
 and many others...



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

[jira] [Commented] (DELTASPIKE-810) improve site headers

[Rafael Benevides (JIRA)]

[ 
https://issues.apache.org/jira/browse/DELTASPIKE-810?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=14261186#comment-14261186
 ] 

Rafael Benevides commented on DELTASPIKE-810:
-

I think that we don't want to disable the cache (NO-CACHE) here, right? Because 
that isn't something that infra would recommend, and maybe can slow down the 
page reply time since it would fetch the whole content again.

I saw that CMS replies already uses Last-Modified and ETag headers.

That makes me wonder that the page is kept in browser memory until a forced 
refresh or when the browser is closed and opened again which is optimised for 
this kind of content. 

 improve site headers
 

 Key: DELTASPIKE-810
 URL: https://issues.apache.org/jira/browse/DELTASPIKE-810
 Project: DeltaSpike
  Issue Type: Task
  Components: Documentation
Reporter: Gerhard Petracek
Assignee: Rafael Benevides
 Fix For: 1.2.2


 we need to improve the page-metadata e.g. via cache-control to ensure that 
 users always see the latest content.



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

[jira] [Resolved] (DELTASPIKE-808) Make website to read pom.xml properties

[Rafael Benevides (JIRA)]

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

Rafael Benevides resolved DELTASPIKE-808.
-
Resolution: Fixed

 Make website to read pom.xml properties
 ---

 Key: DELTASPIKE-808
 URL: https://issues.apache.org/jira/browse/DELTASPIKE-808
 Project: DeltaSpike
  Issue Type: Bug
Reporter: Rafael Benevides
Assignee: Rafael Benevides

 website have references to DeltaSpike version on the following web pages:
 - http://deltaspike.apache.org/documentation/configure.html
 - http://deltaspike.apache.org/documentation/snapshots.html
 It should be read from a pom.xml properties so it can be easily updated



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

[jira] [Created] (DELTASPIKE-814) Create a root pom.xml to share common properties

[Rafael Benevides (JIRA)]

Rafael Benevides created DELTASPIKE-814:
---

 Summary: Create a root pom.xml to share common properties
 Key: DELTASPIKE-814
 URL: https://issues.apache.org/jira/browse/DELTASPIKE-814
 Project: DeltaSpike
  Issue Type: Bug
Affects Versions: 1.2.1
Reporter: Rafael Benevides
Assignee: Rafael Benevides
 Fix For: 1.2.2






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

[jira] [Resolved] (DELTASPIKE-815) Publish 1.2.1 Javadoc

[Rafael Benevides (JIRA)]

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

Rafael Benevides resolved DELTASPIKE-815.
-
Resolution: Fixed

 Publish 1.2.1 Javadoc
 -

 Key: DELTASPIKE-815
 URL: https://issues.apache.org/jira/browse/DELTASPIKE-815
 Project: DeltaSpike
  Issue Type: Task
Reporter: Rafael Benevides
Assignee: Rafael Benevides





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

[jira] [Resolved] (DELTASPIKE-814) Create a root pom.xml to share common properties

[Rafael Benevides (JIRA)]

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

Rafael Benevides resolved DELTASPIKE-814.
-
Resolution: Fixed

 Create a root pom.xml to share common properties
 

 Key: DELTASPIKE-814
 URL: https://issues.apache.org/jira/browse/DELTASPIKE-814
 Project: DeltaSpike
  Issue Type: Bug
Affects Versions: 1.2.1
Reporter: Rafael Benevides
Assignee: Rafael Benevides
 Fix For: 1.2.2






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

[jira] [Commented] (DELTASPIKE-806) update site to 1.2.1

[Rafael Benevides (JIRA)]

[ 
https://issues.apache.org/jira/browse/DELTASPIKE-806?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=14261584#comment-14261584
 ] 

Rafael Benevides commented on DELTASPIKE-806:
-

With DELTASPIKE-808 this kind of Jira should be reduced

 update site to 1.2.1
 

 Key: DELTASPIKE-806
 URL: https://issues.apache.org/jira/browse/DELTASPIKE-806
 Project: DeltaSpike
  Issue Type: Task
Reporter: Gerhard Petracek
Assignee: Gerhard Petracek
 Fix For: 1.2.2






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