[JBoss JIRA] Created: (WELD-524) org.jboss.weld.environment.se.discovery.URLScanner does not work with resources inside OSGI bundles
by Morten Christensen (JIRA)
org.jboss.weld.environment.se.discovery.URLScanner does not work with resources inside OSGI bundles
----------------------------------------------------------------------------------------------------
Key: WELD-524
URL: https://jira.jboss.org/jira/browse/WELD-524
Project: Weld
Issue Type: Bug
Environment: JavaSE 6 + Weld SE
Reporter: Morten Christensen
Priority: Blocker
The class org.jboss.weld.environment.se.discovery.URLScanner does no work with resources inside OSGI bundles. So if one try to start WeldSe inside an OSGI bundle and get around the classloader bug in WeldSE by tempoarily setting the ContextClassLoader you will get an NullPointerException.
The problem is OSGI resource url related. For a OSGI bundle you will f.x. get "bundleresource://4.fwk1362875764:1/META-INF/beans.xml" from bundleClassLoader.getResources("META-INF/beans.xml" but this is not a valid filename as URLScanner assumes so one will get this exception:
java.lang.NullPointerException
at org.jboss.weld.environment.se.discovery.URLScanner.handleDirectory(URLScanner.java:177)
at org.jboss.weld.environment.se.discovery.URLScanner.handleDirectory(URLScanner.java:183)
at org.jboss.weld.environment.se.discovery.URLScanner.handleDirectory(URLScanner.java:160)
at org.jboss.weld.environment.se.discovery.URLScanner.handle(URLScanner.java:122)
at org.jboss.weld.environment.se.discovery.URLScanner.scanResources(URLScanner.java:107)
at org.jboss.weld.environment.se.discovery.SEWeldDiscovery.scan(SEWeldDiscovery.java:71)
at org.jboss.weld.environment.se.discovery.SEWeldDiscovery.<init>(SEWeldDiscovery.java:45)
--
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
13 years, 5 months
[JBoss JIRA] Created: (WELD-376) Callouts poorly formatted in HTML docs
by Pete Muir (JIRA)
Callouts poorly formatted in HTML docs
--------------------------------------
Key: WELD-376
URL: https://jira.jboss.org/jira/browse/WELD-376
Project: Weld
Issue Type: Task
Components: Documentation
Affects Versions: 1.0.0.GA
Reporter: Jozef Hartinger
Fix For: 1.0.1.CR1
Global problems
- a significant number of links is missing the value of href attribute (these links point nowhere)
- JBoss AS 5.2.x have become obsolete recently (changed to 6.0.0.M1) - the documentation references this obsolete version. i.e. Chapters 6, section 18.1
- there is a number of unnecessary blank pages in the PDF version
- Section 2.1.2. Scope - there is a missing *want* in the Note in the sentence: "If you don't the bean to live in the session indefinitely..."
- Section 6.2 Deploying to JBoss AS - there is a missing space in the sentence "Create a new file namedlocal.build.properties ..."
- Section 6.2 Deploying to JBoss AS - is not finished - there is a TODO at the very end of the section
- Secion 7.1. The numberguess example in depth - the numbers which mark an important line of a code sample (1), (2), etc... are broken in the second sample of the section (web.xml). They are placed on wrong places (wrong line, beggining of the line instead of end) and they are followed by "ml_plain">" in the HTML version.
Besides, I would emphasize more the benefit of the typesafe resolution i.e. in section 1.2 - (that all the unsatisfied and ambiguous dependencies are discovered at the deployment time - you do not need to click anything to find out that the you set some dependencies wrong - more formal verification) - I don't say it is not there already. I just had a feeling that it is not stated explicitly enough.
--
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
13 years, 5 months
[JBoss JIRA] Created: (WELD-824) injection/initializer/observer inheritance broken on Beans registered through BBD.addAnnotatedType()
by Jozef Hartinger (JIRA)
injection/initializer/observer inheritance broken on Beans registered through BBD.addAnnotatedType()
----------------------------------------------------------------------------------------------------
Key: WELD-824
URL: https://issues.jboss.org/browse/WELD-824
Project: Weld
Issue Type: Bug
Components: Class Beans (Managed and Session)
Affects Versions: 1.1.0.CR4
Reporter: Jozef Hartinger
I am having two classes: Foo and Bar where Bar extends Foo. Both these classes are outside of BDA (a jar with no beans.xml placed in WEB-INF/lib of a web app that has beans.xml) The Bar class is registered through a portable Extension (BeforeBeanDiscovery.addAnnotatedType()).
The problem is that while injection/initializers/event observers defined on the Bar class work as expected, the ones defined on the Foo class are never called. (Note that the Foo class itself is not registered as a Bean - Nevertheless, CDI services should be enabled on Bar's superclasses according to the spec)
--
This message is automatically generated by JIRA.
-
For more information on JIRA, see: http://www.atlassian.com/software/jira
13 years, 5 months
[JBoss JIRA] Created: (WELD-780) Place beans.xml under WEB-INF instead of WEB-INF/classes/META-INF in jsf/permalink example
by Sivakumar Thyagarajan (JIRA)
Place beans.xml under WEB-INF instead of WEB-INF/classes/META-INF in jsf/permalink example
------------------------------------------------------------------------------------------
Key: WELD-780
URL: https://jira.jboss.org/browse/WELD-780
Project: Weld
Issue Type: Bug
Components: Examples
Affects Versions: 1.1.0.Beta2
Reporter: Sivakumar Thyagarajan
Priority: Minor
As per Section 12.1 of CDI 1.0 specification:
> • The WEB-INF/classes directory of a war is a bean archive if there is a file named beans.xml in the WEB-INF directory of the war.
> • A directory in the JVM classpath is a bean archive if it has a file named beans.xml in the META-INF directory.
However the jsf/permalink sample bundles beans.xml under WEB-INF/classes/META-INF. This may not work in other containers (for instance see http://java.net/jira/browse/GLASSFISH-15009 ). So request to move the file (in weld-core): from
examples/jsf/permalink/src/main/resources/META-INF/beans.xml
to
examples/jsf/permalink/src/main/webapp/WEB-INF/beans.xml
--
This message is automatically generated by JIRA.
-
For more information on JIRA, see: http://www.atlassian.com/software/jira
13 years, 5 months