[JBoss JIRA] Created: (WELD-481) Debug-level summary
by Nicklas Karlsson (JIRA)
Debug-level summary
--------------------
Key: WELD-481
URL: https://jira.jboss.org/jira/browse/WELD-481
Project: Weld
Issue Type: Feature Request
Components: Bootstrap and Metamodel API
Affects Versions: 1.0.1.Final
Reporter: Nicklas Karlsson
Assignee: Nicklas Karlsson
Priority: Minor
Fix For: 1.0.2.CR1
> It would be handy if Seam could be configured for full boot-time output that would include
> * All modules present
> * All enabled interceptors in correct ordering
> * All enabled decorators in correct ordering
> * All alternative beans and what they shade
> * All effective beans and their effective execution path, i.e. the order of enabled interceptors and decorators that fire on the way to a method
> (this would require a largeish resolve operation at the end of boot but can probably be a lifesaver when things go wrong)
--
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators: https://jira.jboss.org/jira/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira
14 years, 6 months
[JBoss JIRA] Created: (CDITCK-165) Bug in org.jboss.jsr299.tck.tests.context.NormalContextTest # testSameNormalScopeBeanInjectedEverywhere
by Gurkan Erdogdu (JIRA)
Bug in org.jboss.jsr299.tck.tests.context.NormalContextTest # testSameNormalScopeBeanInjectedEverywhere
-------------------------------------------------------------------------------------------------------
Key: CDITCK-165
URL: https://jira.jboss.org/browse/CDITCK-165
Project: CDI TCK
Issue Type: Bug
Security Level: Public (Everyone can see)
Affects Versions: 1.0.2.CR1
Reporter: Gurkan Erdogdu
In this method, this tests tries to compare the session context instance equality. I think this is not correct.
Normal scoped beans returns "Proxy" for actual instances. In SimpleBeanA and SimpleBeanB bean instances, @Inject SimpleBeanZ z, may return a different proxy instances that represents the same SimpleBeanZ contextual instance.
In OWB, we return different proxy instances for normal scoped beans, therefore instanceOfA.getZ() == instanceOfB.getZ( ) --> False, because we return different proxy instances for instanceOfA.getZ() and instanceOfB.getZ() that both of them represents the same z instance.
Test may be updated to compare some instance variables of z instance.
--
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators: https://jira.jboss.org/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira
14 years, 6 months
[JBoss JIRA] Created: (WELD-473) required meta-annotations for a qualifier specified differently in spec and API
by Wolfgang Frech (JIRA)
required meta-annotations for a qualifier specified differently in spec and API
-------------------------------------------------------------------------------
Key: WELD-473
URL: https://jira.jboss.org/jira/browse/WELD-473
Project: Weld
Issue Type: Bug
Affects Versions: 1.0.1.Final
Environment: n/a
Reporter: Wolfgang Frech
The specification and the API documentation differ on the required and optional meta-annotations of a qualfiier.
JSR-299, 2.3.2 Defining new qualfier type specifies
@Target(METHOD, FIELD, PARAMETER, TYPE} ("is")
@Retention(RUNTIME) ("is")
@Qualifier, but only optional ("may")
API-Doc of Qualifier specifies
@Qualifier
@Retention(RUNTIME)
@Documented (optional, typical)
@Target optional, but various element types as targets possible
Both agree on Retention only.
As a third source I might have a look at the code and the implemented validity check. I have not so far.
I am a bit fussy about this because a missing @Target of my first custom scope messed up the proxying.
--
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators: https://jira.jboss.org/jira/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira
14 years, 6 months
[JBoss JIRA] Created: (WELDX-70) Automate testing of archetypes
by Steven Boscarine (JIRA)
Automate testing of archetypes
------------------------------
Key: WELDX-70
URL: https://jira.jboss.org/jira/browse/WELDX-70
Project: Weld Extensions
Issue Type: Task
Components: Archetypes
Affects Versions: Archetypes 1.0.0-BETA1
Reporter: Steven Boscarine
Assignee: Steven Boscarine
This may be a difficult and funky task. I haven't been able to find examples of people automating maven calls. This may be a very pioneering task if done in Java. I do it presently with a shell script.
Here's what needs to happen:
An archetype needs to be built from source. (mvn clean install)
A project needs to be created from the archetype. (mvn archetype:generate -DartifactId=myproject)
The project's tests need to be run. (mvn clean test -f myproject/pom.xml)
--
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators: https://jira.jboss.org/jira/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira
14 years, 6 months