[weld-issues] [JBoss JIRA] Created: (WELD-919) Conversation propagation token that negates the cid parameter
Conversation propagation token that negates the cid parameter --- Key: WELD-919 URL: https://issues.jboss.org/browse/WELD-919 Project: Weld Issue Type: Feature Request Components: Conversations Affects Versions: 1.1.1.Final Reporter: Nicklas Karlsson A method that negates the propagation of the cid parameter by the ConversationAwareViewHandler so that a non-transient is not resumed even if there is a cid parameter in the request. Stripping it out on a per-component-basis is tricky. Suggested implementation: change the last line in WeldPhaseListener.getConversationId to return facesContext.getExternalContext().getRequestParameterMap().containsKey(nocid) ? null : cid; -- This message is automatically generated by JIRA. For more information on JIRA, see: http://www.atlassian.com/software/jira ___ weld-issues mailing list weld-issues@lists.jboss.org https://lists.jboss.org/mailman/listinfo/weld-issues
[weld-issues] [JBoss JIRA] Assigned: (WELD-919) Conversation propagation token that negates the cid parameter
[ https://issues.jboss.org/browse/WELD-919?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Ales Justin reassigned WELD-919: Assignee: Ales Justin Conversation propagation token that negates the cid parameter --- Key: WELD-919 URL: https://issues.jboss.org/browse/WELD-919 Project: Weld Issue Type: Feature Request Components: Conversations Affects Versions: 1.1.1.Final Reporter: Nicklas Karlsson Assignee: Ales Justin A method that negates the propagation of the cid parameter by the ConversationAwareViewHandler so that a non-transient is not resumed even if there is a cid parameter in the request. Stripping it out on a per-component-basis is tricky. Suggested implementation: change the last line in WeldPhaseListener.getConversationId to return facesContext.getExternalContext().getRequestParameterMap().containsKey(nocid) ? null : cid; -- This message is automatically generated by JIRA. For more information on JIRA, see: http://www.atlassian.com/software/jira ___ weld-issues mailing list weld-issues@lists.jboss.org https://lists.jboss.org/mailman/listinfo/weld-issues
[weld-issues] [JBoss JIRA] Commented: (WELD-919) Conversation propagation token that negates the cid parameter
[ https://issues.jboss.org/browse/WELD-919?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=12607403#comment-12607403 ] Nicklas Karlsson commented on WELD-919: --- Of course, this could be expanded in Seam2-style to name the parameter conversationPropagation and have values of none and end to differ between just abandoning the conversation and ending it. Conversation propagation token that negates the cid parameter --- Key: WELD-919 URL: https://issues.jboss.org/browse/WELD-919 Project: Weld Issue Type: Feature Request Components: Conversations Affects Versions: 1.1.1.Final Reporter: Nicklas Karlsson Assignee: Ales Justin Fix For: 1.1.2.Final A method that negates the propagation of the cid parameter by the ConversationAwareViewHandler so that a non-transient is not resumed even if there is a cid parameter in the request. Stripping it out on a per-component-basis is tricky. Suggested implementation: change the last line in WeldPhaseListener.getConversationId to return facesContext.getExternalContext().getRequestParameterMap().containsKey(nocid) ? null : cid; -- This message is automatically generated by JIRA. For more information on JIRA, see: http://www.atlassian.com/software/jira ___ weld-issues mailing list weld-issues@lists.jboss.org https://lists.jboss.org/mailman/listinfo/weld-issues
[weld-issues] [JBoss JIRA] Commented: (WELD-919) Conversation propagation token that negates the cid parameter
[ https://issues.jboss.org/browse/WELD-919?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=12607408#comment-12607408 ] Ales Justin commented on WELD-919: -- What would be the diff between none and end in this case? Conversation propagation token that negates the cid parameter --- Key: WELD-919 URL: https://issues.jboss.org/browse/WELD-919 Project: Weld Issue Type: Feature Request Components: Conversations Affects Versions: 1.1.1.Final Reporter: Nicklas Karlsson Assignee: Ales Justin Fix For: 1.1.2.Final A method that negates the propagation of the cid parameter by the ConversationAwareViewHandler so that a non-transient is not resumed even if there is a cid parameter in the request. Stripping it out on a per-component-basis is tricky. Suggested implementation: change the last line in WeldPhaseListener.getConversationId to return facesContext.getExternalContext().getRequestParameterMap().containsKey(nocid) ? null : cid; -- This message is automatically generated by JIRA. For more information on JIRA, see: http://www.atlassian.com/software/jira ___ weld-issues mailing list weld-issues@lists.jboss.org https://lists.jboss.org/mailman/listinfo/weld-issues
[weld-issues] [JBoss JIRA] Commented: (WELD-919) Conversation propagation token that negates the cid parameter
[ https://issues.jboss.org/browse/WELD-919?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=12607420#comment-12607420 ] Ales Justin commented on WELD-919: -- Do we really want to push this kind of logic into WeldPhaseListener? Conversation propagation token that negates the cid parameter --- Key: WELD-919 URL: https://issues.jboss.org/browse/WELD-919 Project: Weld Issue Type: Feature Request Components: Conversations Affects Versions: 1.1.1.Final Reporter: Nicklas Karlsson Assignee: Ales Justin Fix For: 1.1.2.Final A method that negates the propagation of the cid parameter by the ConversationAwareViewHandler so that a non-transient is not resumed even if there is a cid parameter in the request. Stripping it out on a per-component-basis is tricky. Suggested implementation: change the last line in WeldPhaseListener.getConversationId to return facesContext.getExternalContext().getRequestParameterMap().containsKey(nocid) ? null : cid; -- This message is automatically generated by JIRA. For more information on JIRA, see: http://www.atlassian.com/software/jira ___ weld-issues mailing list weld-issues@lists.jboss.org https://lists.jboss.org/mailman/listinfo/weld-issues
[weld-issues] [JBoss JIRA] Commented: (CDITCK-216) ContainerEventTest and missing ejb-jar.xml file
[
https://issues.jboss.org/browse/CDITCK-216?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=12607426#comment-12607426
]
Pete Muir commented on CDITCK-216:
--
Hmm, I see it on my unzip.
I'll exclude this test from 1.0.4 but it looks like this is fixed already.
Could you check trunk for me when you have time?
ContainerEventTest and missing ejb-jar.xml file
---
Key: CDITCK-216
URL: https://issues.jboss.org/browse/CDITCK-216
Project: CDI TCK
Issue Type: Bug
Security Level: Public(Everyone can see)
Reporter: David Blevins
Fix For: 1.0.4.Final
Actually pertains to [1.0.4.SP2]
The ContainerEventTest has an ejb-jar.xml file that defines a stateful
session bean which is otherwise not annotated and discoverable. The harness
is not including this ejb-jar.xml in the 'deploy(InputStream archive, String
name)' call on the Containers implement. The contents are as follows:
{code}
2 Wed Jun 08 20:54:02 PDT 2011 META-INF/MANIFEST.MF
0 Wed Jun 08 20:54:02 PDT 2011 META-INF/beans.xml
237 Wed Jun 08 20:54:02 PDT 2011 META-INF/jboss-test-harness.properties
243 Wed Jun 08 20:54:02 PDT 2011
META-INF/services/javax.enterprise.inject.spi.Extension
9369 Wed Jun 08 20:54:02 PDT 2011
org/jboss/jsr299/tck/AbstractJSR299Test.class
860 Wed Jun 08 20:54:02 PDT 2011
org/jboss/jsr299/tck/api/JSR299Configuration.class
824 Wed Jun 08 20:54:02 PDT 2011
org/jboss/jsr299/tck/DeploymentFailure.class
2712 Wed Jun 08 20:54:02 PDT 2011 org/jboss/jsr299/tck/ForwardingBean.class
3199 Wed Jun 08 20:54:02 PDT 2011
org/jboss/jsr299/tck/impl/JSR299ConfigurationImpl.class
2690 Wed Jun 08 20:54:02 PDT 2011
org/jboss/jsr299/tck/impl/JSR299PropertiesBasedConfigurationBuilder.class
1995 Wed Jun 08 20:54:02 PDT 2011
org/jboss/jsr299/tck/impl/MockCreationalContext.class
3914 Wed Jun 08 20:54:02 PDT 2011
org/jboss/jsr299/tck/impl/OldSPIBridge.class
2331 Wed Jun 08 20:54:02 PDT 2011
org/jboss/jsr299/tck/impl/WebProfileMethodSelector.class
497 Wed Jun 08 20:54:02 PDT 2011
org/jboss/jsr299/tck/literals/AnyLiteral.class
521 Wed Jun 08 20:54:02 PDT 2011
org/jboss/jsr299/tck/literals/DefaultLiteral.class
482 Wed Jun 08 20:54:02 PDT 2011
org/jboss/jsr299/tck/literals/InjectLiteral.class
572 Wed Jun 08 20:54:02 PDT 2011
org/jboss/jsr299/tck/literals/NamedLiteral.class
497 Wed Jun 08 20:54:02 PDT 2011
org/jboss/jsr299/tck/literals/NewLiteral.class
524 Wed Jun 08 20:54:02 PDT 2011
org/jboss/jsr299/tck/literals/RetentionLiteral.class
506 Wed Jun 08 20:54:02 PDT 2011
org/jboss/jsr299/tck/literals/TargetLiteral.class
557 Wed Jun 08 20:54:02 PDT 2011 org/jboss/jsr299/tck/spi/Beans.class
684 Wed Jun 08 20:54:02 PDT 2011 org/jboss/jsr299/tck/spi/Contexts.class
800 Wed Jun 08 20:54:02 PDT 2011 org/jboss/jsr299/tck/spi/EL.class
398 Wed Jun 08 20:54:02 PDT 2011 org/jboss/jsr299/tck/spi/Managers.class
421 Wed Jun 08 20:54:02 PDT 2011
org/jboss/jsr299/tck/tests/extensions/container/event/Cheese.class
8613 Wed Jun 08 20:54:02 PDT 2011
org/jboss/jsr299/tck/tests/extensions/container/event/ContainerEventTest.class
412 Wed Jun 08 20:54:02 PDT 2011
org/jboss/jsr299/tck/tests/extensions/container/event/Cow.class
151 Wed Jun 08 20:54:02 PDT 2011
org/jboss/jsr299/tck/tests/extensions/container/event/CowLocal.class
834 Wed Jun 08 20:54:02 PDT 2011
org/jboss/jsr299/tck/tests/extensions/container/event/Farm.class
405 Wed Jun 08 20:54:02 PDT 2011
org/jboss/jsr299/tck/tests/extensions/container/event/Food.class
415 Wed Jun 08 20:54:02 PDT 2011
org/jboss/jsr299/tck/tests/extensions/container/event/Milk.class
3580 Wed Jun 08 20:54:02 PDT 2011
org/jboss/jsr299/tck/tests/extensions/container/event/ProcessAnnotatedTypeObserver.class
5054 Wed Jun 08 20:54:02 PDT 2011
org/jboss/jsr299/tck/tests/extensions/container/event/ProcessBeanObserver.class
6331 Wed Jun 08 20:54:02 PDT 2011
org/jboss/jsr299/tck/tests/extensions/container/event/ProcessInjectionTargetObserver.class
697 Wed Jun 08 20:54:02 PDT 2011
org/jboss/jsr299/tck/tests/extensions/container/event/Sheep.class
786 Wed Jun 08 20:54:02 PDT 2011
org/jboss/jsr299/tck/tests/extensions/container/event/SheepInterceptor.class
235 Wed Jun 08 20:54:02 PDT 2011
org/jboss/jsr299/tck/tests/extensions/container/event/SheepLocal.class
528 Wed Jun 08 20:54:02 PDT 2011
org/jboss/jsr299/tck/tests/extensions/container/event/Tame.class
{code}
Here's the toString() value of the harness Configuration in case that helps.
Possibly there's some flag I need.
{code}
JSR 299 TCK Configuration
-
Beans: org.apache.openejb.tck.cdi.embedded.BeansImpl@61e090ee
Containers:
[weld-issues] [JBoss JIRA] Commented: (CDITCK-215) ProcessSessionBeanTest testProcessSessionBeanEvent count
[
https://issues.jboss.org/browse/CDITCK-215?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=12607427#comment-12607427
]
Pete Muir commented on CDITCK-215:
--
The signature of ProcessSessionBean is
{code}
public interface ProcessSessionBeanX extends ProcessManagedBeanObject {
{code}
So I don't believe you would see a ProcessBeanElephant observer called, as
10.2.1 tells us:
{quote}
the observed event type parameter is an actual type with identical raw type to
the event type parameter, and, if the type is parameterized, the event type
parameter is assignable to the observed event type parameter according to these
rules
{quote}
and Object is not assignable to Elephant.
ProcessSessionBeanTest testProcessSessionBeanEvent count
Key: CDITCK-215
URL: https://issues.jboss.org/browse/CDITCK-215
Project: CDI TCK
Issue Type: Bug
Security Level: Public(Everyone can see)
Affects Versions: 1.0.4.Final
Reporter: David Blevins
[Side note maybe there should be versions for 1.0.4.SP1 and 1.0.4.SP2]
Test:
org.jboss.jsr299.tck.tests.extensions.processBean.ProcessSessionBeanTest.testProcessSessionBeanEvent
Not sure if this is an issue or not, so filling this as a bug and not a
challenge. The test essentially has two observer methods and is asserting
that only one of them are called.
public void observeElephantSessionBean(@Observes
ProcessSessionBeanElephant event)
{
ProcessBeanObserver.elephantProcessSessionBean = event;
}
public void observeElephantBean(@Observes ProcessBeanElephant event)
{
ProcessBeanObserver.elephantProcessBeanCount++;
}
Specifically the test asserts that observeElephantSessionBean is called and
that observeElephantBean is not called.
Currently we call both because ProcessSessionBean is assignable to
ProcessBean and the generics are the same.
Is there a part of the spec that mandates only the most specific observer
method is called?
The only thing I can find is in 10.4 which says pretty clearly:
There may be arbitrarily many observer methods with the same event
parameter type and qualifiers.
A bean (or extension) may declare multiple observer methods.
Well I guess it's not that clear as it says essentially this may happen
rather than this may happen...and when it does the behavior is...[all are
invoked || only the most specific is invoked]
--
This message is automatically generated by JIRA.
For more information on JIRA, see: http://www.atlassian.com/software/jira
___
weld-issues mailing list
weld-issues@lists.jboss.org
https://lists.jboss.org/mailman/listinfo/weld-issues
[weld-issues] [JBoss JIRA] Commented: (WELD-918) interceptor binding for java interfaces/methods
[ https://issues.jboss.org/browse/WELD-918?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=12607433#comment-12607433 ] Pete Muir commented on WELD-918: No, this is not supported by CDI. interceptor binding for java interfaces/methods --- Key: WELD-918 URL: https://issues.jboss.org/browse/WELD-918 Project: Weld Issue Type: Feature Request Components: Weld SPI Affects Versions: 1.1.0.Final Environment: tomcat6 Reporter: Manuel Hartl Priority: Minor - i created an interceptor and marked an java interface class with its binding (or a method of the interface) - interception does not work on methods of beans, that implement this interface. should this work? (interceptor binding to java interfaces?) if yes: it's a bug :) if no: please update weld documentation actually, i would like to use in interfaces -- This message is automatically generated by JIRA. For more information on JIRA, see: http://www.atlassian.com/software/jira ___ weld-issues mailing list weld-issues@lists.jboss.org https://lists.jboss.org/mailman/listinfo/weld-issues
[weld-issues] [JBoss JIRA] Updated: (WELD-918) interceptor binding for java interfaces/methods
[ https://issues.jboss.org/browse/WELD-918?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Pete Muir updated WELD-918: --- Issue Type: Task (was: Feature Request) Please file a CDI issue for using bindings on interfaces. interceptor binding for java interfaces/methods --- Key: WELD-918 URL: https://issues.jboss.org/browse/WELD-918 Project: Weld Issue Type: Task Components: Weld SPI Affects Versions: 1.1.0.Final Environment: tomcat6 Reporter: Manuel Hartl Priority: Minor - i created an interceptor and marked an java interface class with its binding (or a method of the interface) - interception does not work on methods of beans, that implement this interface. should this work? (interceptor binding to java interfaces?) if yes: it's a bug :) if no: please update weld documentation actually, i would like to use in interfaces -- This message is automatically generated by JIRA. For more information on JIRA, see: http://www.atlassian.com/software/jira ___ weld-issues mailing list weld-issues@lists.jboss.org https://lists.jboss.org/mailman/listinfo/weld-issues
[weld-issues] [JBoss JIRA] Commented: (WELD-919) Conversation propagation token that negates the cid parameter
[ https://issues.jboss.org/browse/WELD-919?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=12607435#comment-12607435 ] Pete Muir commented on WELD-919: Nik, make sure you add a CDI feature request as well. Conversation propagation token that negates the cid parameter --- Key: WELD-919 URL: https://issues.jboss.org/browse/WELD-919 Project: Weld Issue Type: Feature Request Components: Conversations Affects Versions: 1.1.1.Final Reporter: Nicklas Karlsson Assignee: Ales Justin Fix For: 1.1.2.Final A method that negates the propagation of the cid parameter by the ConversationAwareViewHandler so that a non-transient is not resumed even if there is a cid parameter in the request. Stripping it out on a per-component-basis is tricky. Suggested implementation: change the last line in WeldPhaseListener.getConversationId to return facesContext.getExternalContext().getRequestParameterMap().containsKey(nocid) ? null : cid; -- This message is automatically generated by JIRA. For more information on JIRA, see: http://www.atlassian.com/software/jira ___ weld-issues mailing list weld-issues@lists.jboss.org https://lists.jboss.org/mailman/listinfo/weld-issues
[weld-issues] [JBoss JIRA] Commented: (CDITCK-216) ContainerEventTest and missing ejb-jar.xml file
[
https://issues.jboss.org/browse/CDITCK-216?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=12607624#comment-12607624
]
David Blevins commented on CDITCK-216:
--
The harness is giving a jar file not an ear. The output was created as you
describe; i.e. breakpoint in Containers.deploy(InputStream archive, String
name) followed by immediately writing the supplied stream to disk then doing
'jar tvf that.jar'
I suspect it might be happening to all the tests with ejb-jar.xml files. With
a debugger I can see that the ejb-jar.xml is not even in the
JSR299ArtifactDescriptor instance, either in the 'resources' HashSet or in the
path that 'explodedJar' points to. So whatever it is is happening quite early.
Will keep debugging.
ContainerEventTest and missing ejb-jar.xml file
---
Key: CDITCK-216
URL: https://issues.jboss.org/browse/CDITCK-216
Project: CDI TCK
Issue Type: Bug
Security Level: Public(Everyone can see)
Reporter: David Blevins
Fix For: 1.0.4.Final
Actually pertains to [1.0.4.SP2]
The ContainerEventTest has an ejb-jar.xml file that defines a stateful
session bean which is otherwise not annotated and discoverable. The harness
is not including this ejb-jar.xml in the 'deploy(InputStream archive, String
name)' call on the Containers implement. The contents are as follows:
{code}
2 Wed Jun 08 20:54:02 PDT 2011 META-INF/MANIFEST.MF
0 Wed Jun 08 20:54:02 PDT 2011 META-INF/beans.xml
237 Wed Jun 08 20:54:02 PDT 2011 META-INF/jboss-test-harness.properties
243 Wed Jun 08 20:54:02 PDT 2011
META-INF/services/javax.enterprise.inject.spi.Extension
9369 Wed Jun 08 20:54:02 PDT 2011
org/jboss/jsr299/tck/AbstractJSR299Test.class
860 Wed Jun 08 20:54:02 PDT 2011
org/jboss/jsr299/tck/api/JSR299Configuration.class
824 Wed Jun 08 20:54:02 PDT 2011
org/jboss/jsr299/tck/DeploymentFailure.class
2712 Wed Jun 08 20:54:02 PDT 2011 org/jboss/jsr299/tck/ForwardingBean.class
3199 Wed Jun 08 20:54:02 PDT 2011
org/jboss/jsr299/tck/impl/JSR299ConfigurationImpl.class
2690 Wed Jun 08 20:54:02 PDT 2011
org/jboss/jsr299/tck/impl/JSR299PropertiesBasedConfigurationBuilder.class
1995 Wed Jun 08 20:54:02 PDT 2011
org/jboss/jsr299/tck/impl/MockCreationalContext.class
3914 Wed Jun 08 20:54:02 PDT 2011
org/jboss/jsr299/tck/impl/OldSPIBridge.class
2331 Wed Jun 08 20:54:02 PDT 2011
org/jboss/jsr299/tck/impl/WebProfileMethodSelector.class
497 Wed Jun 08 20:54:02 PDT 2011
org/jboss/jsr299/tck/literals/AnyLiteral.class
521 Wed Jun 08 20:54:02 PDT 2011
org/jboss/jsr299/tck/literals/DefaultLiteral.class
482 Wed Jun 08 20:54:02 PDT 2011
org/jboss/jsr299/tck/literals/InjectLiteral.class
572 Wed Jun 08 20:54:02 PDT 2011
org/jboss/jsr299/tck/literals/NamedLiteral.class
497 Wed Jun 08 20:54:02 PDT 2011
org/jboss/jsr299/tck/literals/NewLiteral.class
524 Wed Jun 08 20:54:02 PDT 2011
org/jboss/jsr299/tck/literals/RetentionLiteral.class
506 Wed Jun 08 20:54:02 PDT 2011
org/jboss/jsr299/tck/literals/TargetLiteral.class
557 Wed Jun 08 20:54:02 PDT 2011 org/jboss/jsr299/tck/spi/Beans.class
684 Wed Jun 08 20:54:02 PDT 2011 org/jboss/jsr299/tck/spi/Contexts.class
800 Wed Jun 08 20:54:02 PDT 2011 org/jboss/jsr299/tck/spi/EL.class
398 Wed Jun 08 20:54:02 PDT 2011 org/jboss/jsr299/tck/spi/Managers.class
421 Wed Jun 08 20:54:02 PDT 2011
org/jboss/jsr299/tck/tests/extensions/container/event/Cheese.class
8613 Wed Jun 08 20:54:02 PDT 2011
org/jboss/jsr299/tck/tests/extensions/container/event/ContainerEventTest.class
412 Wed Jun 08 20:54:02 PDT 2011
org/jboss/jsr299/tck/tests/extensions/container/event/Cow.class
151 Wed Jun 08 20:54:02 PDT 2011
org/jboss/jsr299/tck/tests/extensions/container/event/CowLocal.class
834 Wed Jun 08 20:54:02 PDT 2011
org/jboss/jsr299/tck/tests/extensions/container/event/Farm.class
405 Wed Jun 08 20:54:02 PDT 2011
org/jboss/jsr299/tck/tests/extensions/container/event/Food.class
415 Wed Jun 08 20:54:02 PDT 2011
org/jboss/jsr299/tck/tests/extensions/container/event/Milk.class
3580 Wed Jun 08 20:54:02 PDT 2011
org/jboss/jsr299/tck/tests/extensions/container/event/ProcessAnnotatedTypeObserver.class
5054 Wed Jun 08 20:54:02 PDT 2011
org/jboss/jsr299/tck/tests/extensions/container/event/ProcessBeanObserver.class
6331 Wed Jun 08 20:54:02 PDT 2011
org/jboss/jsr299/tck/tests/extensions/container/event/ProcessInjectionTargetObserver.class
697 Wed Jun 08 20:54:02 PDT 2011
org/jboss/jsr299/tck/tests/extensions/container/event/Sheep.class
786 Wed Jun 08 20:54:02 PDT 2011
org/jboss/jsr299/tck/tests/extensions/container/event/SheepInterceptor.class
235 Wed Jun 08 20:54:02 PDT 2011
[weld-issues] [JBoss JIRA] Commented: (CDITCK-216) ContainerEventTest and missing ejb-jar.xml file
[
https://issues.jboss.org/browse/CDITCK-216?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=12607633#comment-12607633
]
David Blevins commented on CDITCK-216:
--
Ok, I see. I ran into this before and forgot. The problem is the
jboss-test-harness is hardcoded to the notion that standalone EJB containers do
not exist. With standalone=true it will intentionally leave out the
ejb-jar.xml.
Is the jboss-test-harness code on github?
ContainerEventTest and missing ejb-jar.xml file
---
Key: CDITCK-216
URL: https://issues.jboss.org/browse/CDITCK-216
Project: CDI TCK
Issue Type: Bug
Security Level: Public(Everyone can see)
Reporter: David Blevins
Fix For: 1.0.4.Final
Actually pertains to [1.0.4.SP2]
The ContainerEventTest has an ejb-jar.xml file that defines a stateful
session bean which is otherwise not annotated and discoverable. The harness
is not including this ejb-jar.xml in the 'deploy(InputStream archive, String
name)' call on the Containers implement. The contents are as follows:
{code}
2 Wed Jun 08 20:54:02 PDT 2011 META-INF/MANIFEST.MF
0 Wed Jun 08 20:54:02 PDT 2011 META-INF/beans.xml
237 Wed Jun 08 20:54:02 PDT 2011 META-INF/jboss-test-harness.properties
243 Wed Jun 08 20:54:02 PDT 2011
META-INF/services/javax.enterprise.inject.spi.Extension
9369 Wed Jun 08 20:54:02 PDT 2011
org/jboss/jsr299/tck/AbstractJSR299Test.class
860 Wed Jun 08 20:54:02 PDT 2011
org/jboss/jsr299/tck/api/JSR299Configuration.class
824 Wed Jun 08 20:54:02 PDT 2011
org/jboss/jsr299/tck/DeploymentFailure.class
2712 Wed Jun 08 20:54:02 PDT 2011 org/jboss/jsr299/tck/ForwardingBean.class
3199 Wed Jun 08 20:54:02 PDT 2011
org/jboss/jsr299/tck/impl/JSR299ConfigurationImpl.class
2690 Wed Jun 08 20:54:02 PDT 2011
org/jboss/jsr299/tck/impl/JSR299PropertiesBasedConfigurationBuilder.class
1995 Wed Jun 08 20:54:02 PDT 2011
org/jboss/jsr299/tck/impl/MockCreationalContext.class
3914 Wed Jun 08 20:54:02 PDT 2011
org/jboss/jsr299/tck/impl/OldSPIBridge.class
2331 Wed Jun 08 20:54:02 PDT 2011
org/jboss/jsr299/tck/impl/WebProfileMethodSelector.class
497 Wed Jun 08 20:54:02 PDT 2011
org/jboss/jsr299/tck/literals/AnyLiteral.class
521 Wed Jun 08 20:54:02 PDT 2011
org/jboss/jsr299/tck/literals/DefaultLiteral.class
482 Wed Jun 08 20:54:02 PDT 2011
org/jboss/jsr299/tck/literals/InjectLiteral.class
572 Wed Jun 08 20:54:02 PDT 2011
org/jboss/jsr299/tck/literals/NamedLiteral.class
497 Wed Jun 08 20:54:02 PDT 2011
org/jboss/jsr299/tck/literals/NewLiteral.class
524 Wed Jun 08 20:54:02 PDT 2011
org/jboss/jsr299/tck/literals/RetentionLiteral.class
506 Wed Jun 08 20:54:02 PDT 2011
org/jboss/jsr299/tck/literals/TargetLiteral.class
557 Wed Jun 08 20:54:02 PDT 2011 org/jboss/jsr299/tck/spi/Beans.class
684 Wed Jun 08 20:54:02 PDT 2011 org/jboss/jsr299/tck/spi/Contexts.class
800 Wed Jun 08 20:54:02 PDT 2011 org/jboss/jsr299/tck/spi/EL.class
398 Wed Jun 08 20:54:02 PDT 2011 org/jboss/jsr299/tck/spi/Managers.class
421 Wed Jun 08 20:54:02 PDT 2011
org/jboss/jsr299/tck/tests/extensions/container/event/Cheese.class
8613 Wed Jun 08 20:54:02 PDT 2011
org/jboss/jsr299/tck/tests/extensions/container/event/ContainerEventTest.class
412 Wed Jun 08 20:54:02 PDT 2011
org/jboss/jsr299/tck/tests/extensions/container/event/Cow.class
151 Wed Jun 08 20:54:02 PDT 2011
org/jboss/jsr299/tck/tests/extensions/container/event/CowLocal.class
834 Wed Jun 08 20:54:02 PDT 2011
org/jboss/jsr299/tck/tests/extensions/container/event/Farm.class
405 Wed Jun 08 20:54:02 PDT 2011
org/jboss/jsr299/tck/tests/extensions/container/event/Food.class
415 Wed Jun 08 20:54:02 PDT 2011
org/jboss/jsr299/tck/tests/extensions/container/event/Milk.class
3580 Wed Jun 08 20:54:02 PDT 2011
org/jboss/jsr299/tck/tests/extensions/container/event/ProcessAnnotatedTypeObserver.class
5054 Wed Jun 08 20:54:02 PDT 2011
org/jboss/jsr299/tck/tests/extensions/container/event/ProcessBeanObserver.class
6331 Wed Jun 08 20:54:02 PDT 2011
org/jboss/jsr299/tck/tests/extensions/container/event/ProcessInjectionTargetObserver.class
697 Wed Jun 08 20:54:02 PDT 2011
org/jboss/jsr299/tck/tests/extensions/container/event/Sheep.class
786 Wed Jun 08 20:54:02 PDT 2011
org/jboss/jsr299/tck/tests/extensions/container/event/SheepInterceptor.class
235 Wed Jun 08 20:54:02 PDT 2011
org/jboss/jsr299/tck/tests/extensions/container/event/SheepLocal.class
528 Wed Jun 08 20:54:02 PDT 2011
org/jboss/jsr299/tck/tests/extensions/container/event/Tame.class
{code}
Here's the toString() value of the harness Configuration in case that helps.
Possibly there's some flag I need.
{code}
JSR 299 TCK Configuration
[weld-issues] [JBoss JIRA] Commented: (CDITCK-213) Interceptor classes in TCK do not follow the Interceptor spec
[ https://issues.jboss.org/browse/CDITCK-213?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=12607689#comment-12607689 ] Bob Nettleton commented on CDITCK-213: -- Thanks for excluding these tests. I just tried updating to the latest exclude list at: http://source.jboss.org/browse/Weld/cdi-tck/branches/1.0/impl/src/main/resources/tck-tests-released.xml?r=7244 and ran into two small problems. 1. There appears to be some kind of typo on line 126, with a . after the test case name. This appears to cause a ClassNotFound error when I try to launch the suite with this list. 2. If I fix the typo manually, the suite runs fine, but it looks like one of the tests listed above is not actually excluded yet. I think this also may be a typo, since the methods tag on line 128 does not include a method name. So, this method is not excluded yet when the suite is run. Interceptor classes in TCK do not follow the Interceptor spec - Key: CDITCK-213 URL: https://issues.jboss.org/browse/CDITCK-213 Project: CDI TCK Issue Type: Bug Security Level: Public(Everyone can see) Components: Tests Affects Versions: 1.0.4.Final Reporter: Bob Nettleton Fix For: 1.0.5.CR1 There are some interceptor-related suites in the CDI TCK that are not portable in some situations. The interceptor classes listed here: org.jboss.jsr299.tck.tests.interceptors.definition.enterprise.interceptorOrder.MissileInterceptor org.jboss.jsr299.tck.tests.interceptors.definition.enterprise.nonContextualReference.MissileInterceptor org.jboss.jsr299.tck.tests.interceptors.definition.enterprise.simpleInterception.MissileInterceptor These interceptor classes do not have a public, no-args constructor, which is required by the Interceptor 1.1 specification. This means that the tests may not be portable to all environments, since application servers may choose to treat this as an error condition. The following tests are affected by this issue: org.jboss.jsr299.tck.tests.interceptors.definition.enterprise.interceptorOrder.SessionBeanInterceptorOrderTest.testInterceptorsDeclaredUsingInterceptorsCalledBeforeInterceptorBinding org.jboss.jsr299.tck.tests.interceptors.definition.enterprise.nonContextualReference.SessionBeanInterceptorOnNonContextualEjbReferenceTest.testNonContextualSessionBeanReferenceIsIntercepted org.jboss.jsr299.tck.tests.interceptors.definition.enterprise.simpleInterception.SessionBeanInterceptorDefinitionTest.testSessionBeanIsIntercepted I request that these tests be excluded from the 1.0.4 suite, and that the interceptors be fixed for subsequent versions of the test suite. -- This message is automatically generated by JIRA. For more information on JIRA, see: http://www.atlassian.com/software/jira ___ weld-issues mailing list weld-issues@lists.jboss.org https://lists.jboss.org/mailman/listinfo/weld-issues
