2:52 p.m.
Support for dual SE and EE applications that uses weld
------------------------------------------------------
Key: WELD-521
URL: https://jira.jboss.org/jira/browse/WELD-521
Project: Weld
Issue Type: Feature Request
Environment: Java SE and Java EE + weld
Reporter: Morten Christensen
Better support for dual SE and EE applications. I have some weld-using jar's that can
be deployed on a Java EE and work standalone. It is possible to get this to work using
both weld SE and weld EE but it is a pain. F.x. when deployed under glassfish weld will
fail unless I include a few weld SE dummy classes.... Weld should either combine weld SE
and weld EE OR there should at least be some support for having weld ignoring some of my
classes/packages depending on which environment it is running under.
--
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
2:59 p.m.
New subject: [JBoss JIRA] Commented: (WELD-521) Support for dual SE and EE applications that uses weld
[
https://jira.jboss.org/jira/browse/WELD-521?page=com.atlassian.jira.plugi...
]
Pete Muir commented on WELD-521:
--------------------------------
Hi Morten, Can you provide some more details on the app you are trying to deploy and
errors you see. This way we can actually resolve the issue you are having, not the vague
description above ;-)
Support for dual SE and EE applications that uses weld
------------------------------------------------------
Key: WELD-521
URL: https://jira.jboss.org/jira/browse/WELD-521
Project: Weld
Issue Type: Feature Request
Environment: Java SE and Java EE + weld
Reporter: Morten Christensen
Better support for dual SE and EE applications. I have some weld-using jar's that can
be deployed on a Java EE and work standalone. It is possible to get this to work using
both weld SE and weld EE but it is a pain. F.x. when deployed under glassfish weld will
fail unless I include a few weld SE dummy classes.... Weld should either combine weld SE
and weld EE OR there should at least be some support for having weld ignoring some of my
classes/packages depending on which environment it is running under.
--
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
3:14 p.m.
New subject: [JBoss JIRA] Commented: (WELD-521) Support for dual SE and EE applications that uses weld
[
https://jira.jboss.org/jira/browse/WELD-521?page=com.atlassian.jira.plugi...
]
Morten Christensen commented on WELD-521:
-----------------------------------------
Guilty as accused, my description was vague. What I am trying to do is to create a java
application that can be deployed as both a WAR file under a Java 6 EE application server
AND run as plain Java SE application from commandline (+ maybe run in OSGI environment as
well - this is very new). This was inspired by the famous Hudson build server but
implemented without a internal web server and just using jersey on top of grizzly when
running in SE mode.
The main problem with using Weld for dual Java apps is that it will try to make weld beans
out of ALL classes in the jar/war that contains the bean.xml file regardless of if they
make sense or not in the given environment. So if my war file also contains a few weld SE
classes, Weld will faill under glassfish because it does not know about the weld SE
classes. All my java SE stuff (like my main method) is in a separate package, so if I
could just tell weld to please ignore this when running under an JEE app server that would
be great (i.e. an environment specific package-ignore thing in bean.xml OR if Weld could
please completely ignore any classes with a specific annotation when running under a
specific environment such as JEE, JSE, OSGI).
BTW: I will attach the dummy weld-se-ee-passifier.jar file that I have created to keep
Weld and glassfish happy.
Support for dual SE and EE applications that uses weld
------------------------------------------------------
Key: WELD-521
URL: https://jira.jboss.org/jira/browse/WELD-521
Project: Weld
Issue Type: Feature Request
Environment: Java SE and Java EE + weld
Reporter: Morten Christensen
Better support for dual SE and EE applications. I have some weld-using jar's that can
be deployed on a Java EE and work standalone. It is possible to get this to work using
both weld SE and weld EE but it is a pain. F.x. when deployed under glassfish weld will
fail unless I include a few weld SE dummy classes.... Weld should either combine weld SE
and weld EE OR there should at least be some support for having weld ignoring some of my
classes/packages depending on which environment it is running under.
--
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
3:16 p.m.
New subject: [JBoss JIRA] Updated: (WELD-521) Support for dual SE and EE applications that uses weld
[
https://jira.jboss.org/jira/browse/WELD-521?page=com.atlassian.jira.plugi...
]
Morten Christensen updated WELD-521:
------------------------------------
Attachment: weld-se-ee-passifier.jar
The dummy jar file I have created to keep Weld happy with my JavaSE+EE app under Java EE
Support for dual SE and EE applications that uses weld
------------------------------------------------------
Key: WELD-521
URL: https://jira.jboss.org/jira/browse/WELD-521
Project: Weld
Issue Type: Feature Request
Environment: Java SE and Java EE + weld
Reporter: Morten Christensen
Attachments: weld-se-ee-passifier.jar
Better support for dual SE and EE applications. I have some weld-using jar's that can
be deployed on a Java EE and work standalone. It is possible to get this to work using
both weld SE and weld EE but it is a pain. F.x. when deployed under glassfish weld will
fail unless I include a few weld SE dummy classes.... Weld should either combine weld SE
and weld EE OR there should at least be some support for having weld ignoring some of my
classes/packages depending on which environment it is running under.
--
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
4:37 p.m.
New subject: [JBoss JIRA] Updated: (WELD-521) Introduce a way to exclude classes or packages from scanning
[
https://jira.jboss.org/jira/browse/WELD-521?page=com.atlassian.jira.plugi...
]
Pete Muir updated WELD-521:
---------------------------
Summary: Introduce a way to exclude classes or packages from scanning (was:
Support for dual SE and EE applications that uses weld)
Component/s: Bootstrap and Metamodel API
Introduce a way to exclude classes or packages from scanning
------------------------------------------------------------
Key: WELD-521
URL: https://jira.jboss.org/jira/browse/WELD-521
Project: Weld
Issue Type: Feature Request
Components: Bootstrap and Metamodel API
Environment: Java SE and Java EE + weld
Reporter: Morten Christensen
Attachments: weld-se-ee-passifier.jar
Better support for dual SE and EE applications. I have some weld-using jar's that can
be deployed on a Java EE and work standalone. It is possible to get this to work using
both weld SE and weld EE but it is a pain. F.x. when deployed under glassfish weld will
fail unless I include a few weld SE dummy classes.... Weld should either combine weld SE
and weld EE OR there should at least be some support for having weld ignoring some of my
classes/packages depending on which environment it is running under.
--
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
4:37 p.m.
New subject: [JBoss JIRA] Commented: (WELD-521) Support for dual SE and EE applications that uses weld
[
https://jira.jboss.org/jira/browse/WELD-521?page=com.atlassian.jira.plugi...
]
Pete Muir commented on WELD-521:
--------------------------------
Ok, I see the problem. We have always planned to introduce a Weld specific way of
excluding packages or classes from scanning. I will adjust this JIRA issue to reflect
that.
Support for dual SE and EE applications that uses weld
------------------------------------------------------
Key: WELD-521
URL: https://jira.jboss.org/jira/browse/WELD-521
Project: Weld
Issue Type: Feature Request
Components: Bootstrap and Metamodel API
Environment: Java SE and Java EE + weld
Reporter: Morten Christensen
Attachments: weld-se-ee-passifier.jar
Better support for dual SE and EE applications. I have some weld-using jar's that can
be deployed on a Java EE and work standalone. It is possible to get this to work using
both weld SE and weld EE but it is a pain. F.x. when deployed under glassfish weld will
fail unless I include a few weld SE dummy classes.... Weld should either combine weld SE
and weld EE OR there should at least be some support for having weld ignoring some of my
classes/packages depending on which environment it is running under.
--
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
4:47 p.m.
New subject: [JBoss JIRA] Commented: (WELD-521) Introduce a way to exclude classes or packages from scanning
[
https://jira.jboss.org/jira/browse/WELD-521?page=com.atlassian.jira.plugi...
]
Morten Christensen commented on WELD-521:
-----------------------------------------
Ok, just remember that what packages/classes to exclude could depend on the execution
environment (JSE, JEE, OSGI) and some application/custom settings.
As for the CDI 1.1 spec, it could be good with a standard qualifier that is environment
specific + a standard qualifier to tell weld to "keep hands of this class/package and
ignore it".
Introduce a way to exclude classes or packages from scanning
------------------------------------------------------------
Key: WELD-521
URL: https://jira.jboss.org/jira/browse/WELD-521
Project: Weld
Issue Type: Feature Request
Components: Bootstrap and Metamodel API
Environment: Java SE and Java EE + weld
Reporter: Morten Christensen
Attachments: weld-se-ee-passifier.jar
Better support for dual SE and EE applications. I have some weld-using jar's that can
be deployed on a Java EE and work standalone. It is possible to get this to work using
both weld SE and weld EE but it is a pain. F.x. when deployed under glassfish weld will
fail unless I include a few weld SE dummy classes.... Weld should either combine weld SE
and weld EE OR there should at least be some support for having weld ignoring some of my
classes/packages depending on which environment it is running under.
--
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
4:51 p.m.
New subject: [JBoss JIRA] Commented: (WELD-521) Introduce a way to exclude classes or packages from scanning
[
https://jira.jboss.org/jira/browse/WELD-521?page=com.atlassian.jira.plugi...
]
Pete Muir commented on WELD-521:
--------------------------------
It would be some sort of (e.g. xml) config file that would specify the excludes. We could
also make it pluggable via a service, so that you can do your own impl of what to ignore.
Introduce a way to exclude classes or packages from scanning
------------------------------------------------------------
Key: WELD-521
URL: https://jira.jboss.org/jira/browse/WELD-521
Project: Weld
Issue Type: Feature Request
Components: Bootstrap and Metamodel API
Environment: Java SE and Java EE + weld
Reporter: Morten Christensen
Attachments: weld-se-ee-passifier.jar
Better support for dual SE and EE applications. I have some weld-using jar's that can
be deployed on a Java EE and work standalone. It is possible to get this to work using
both weld SE and weld EE but it is a pain. F.x. when deployed under glassfish weld will
fail unless I include a few weld SE dummy classes.... Weld should either combine weld SE
and weld EE OR there should at least be some support for having weld ignoring some of my
classes/packages depending on which environment it is running under.
--
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
4:55 p.m.
New subject: [JBoss JIRA] Commented: (WELD-521) Introduce a way to exclude classes or packages from scanning
[
https://jira.jboss.org/jira/browse/WELD-521?page=com.atlassian.jira.plugi...
]
Morten Christensen commented on WELD-521:
-----------------------------------------
Yes, if you do that then you cover both static configuration at compile time + if one
needed it dynamic at runtime. Sounds good.
Introduce a way to exclude classes or packages from scanning
------------------------------------------------------------
Key: WELD-521
URL: https://jira.jboss.org/jira/browse/WELD-521
Project: Weld
Issue Type: Feature Request
Components: Bootstrap and Metamodel API
Environment: Java SE and Java EE + weld
Reporter: Morten Christensen
Attachments: weld-se-ee-passifier.jar
Better support for dual SE and EE applications. I have some weld-using jar's that can
be deployed on a Java EE and work standalone. It is possible to get this to work using
both weld SE and weld EE but it is a pain. F.x. when deployed under glassfish weld will
fail unless I include a few weld SE dummy classes.... Weld should either combine weld SE
and weld EE OR there should at least be some support for having weld ignoring some of my
classes/packages depending on which environment it is running under.
--
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
12:51 a.m.
New subject: [JBoss JIRA] Commented: (WELD-521) Introduce a way to exclude classes or packages from scanning
[
https://jira.jboss.org/browse/WELD-521?page=com.atlassian.jira.plugin.sys...
]
Morten Christensen commented on WELD-521:
-----------------------------------------
This issue is getting more and more important as i am running into more and more
situations where weld will explode in class(def) not found because Weld wrongly assumes
that all classes in a jar is necessarily valid in all types of deployment.
My application is distributed in ONE jar file with various subpackages like
myapp.container.jse, myapp.container.jee, myapp.container.osgi that contains classes that
are only valid in their respective containers. This kind of hybrid application
is simply not possible as long as Weld blindly tries to load all classes in a jar. Java
has defined lazy class loading for reason!
On Weld-SE it seems we will soon be able to work around this by using a custom
createDeployment override that works on explicit mentioned classes but what about JavaEE?
I strongly need a way to exclude classes depending on environment that will also work with
JavaEE (and consequently in glassfish and JBoss etc.). I also suspect this solution will
need to arrive soon in order to have a chance to get included in upcomming glassfish 3.01
P.S. Besides helping with hybrid applications, this will also potentially improve
performance in some cases as Weld processing won't need to deal with packages without
bean classes.
Introduce a way to exclude classes or packages from scanning
------------------------------------------------------------
Key: WELD-521
URL: https://jira.jboss.org/browse/WELD-521
Project: Weld
Issue Type: Feature Request
Components: Bootstrap and Metamodel API
Environment: Java SE and Java EE + weld
Reporter: Morten Christensen
Attachments: weld-se-ee-passifier.jar
Better support for dual SE and EE applications. I have some weld-using jar's that can
be deployed on a Java EE and work standalone. It is possible to get this to work using
both weld SE and weld EE but it is a pain. F.x. when deployed under glassfish weld will
fail unless I include a few weld SE dummy classes.... Weld should either combine weld SE
and weld EE OR there should at least be some support for having weld ignoring some of my
classes/packages depending on which environment it is running under.
--
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
1:01 p.m.
New subject: [JBoss JIRA] Commented: (WELD-521) Introduce a way to exclude classes or packages from scanning
[
https://jira.jboss.org/browse/WELD-521?page=com.atlassian.jira.plugin.sys...
]
Pete Muir commented on WELD-521:
--------------------------------
On Weld-SE it seems we will soon be able to work around this by using
a custom createDeployment
override that works on explicit mentioned classes but what about JavaEE?
It seems to me this would be a good way to prototype this. We can then migrate the support
into the core as it matures
Actually support this is easy enough. What is harder is defining a nice configuration
format. We should brainstorm that here. Any ideas?
I strongly need a way to exclude classes depending on environment
that will also work with JavaEE (and consequently
in glassfish and JBoss etc.). I also suspect this solution will need to arrive soon in
order to
have a chance to get included in upcomming glassfish 3.01
The cutoff for 3.0.1 has long gone. We can aim for GF 3.1
Introduce a way to exclude classes or packages from scanning
------------------------------------------------------------
Key: WELD-521
URL: https://jira.jboss.org/browse/WELD-521
Project: Weld
Issue Type: Feature Request
Components: Bootstrap and Metamodel API
Environment: Java SE and Java EE + weld
Reporter: Morten Christensen
Attachments: weld-se-ee-passifier.jar
Better support for dual SE and EE applications. I have some weld-using jar's that can
be deployed on a Java EE and work standalone. It is possible to get this to work using
both weld SE and weld EE but it is a pain. F.x. when deployed under glassfish weld will
fail unless I include a few weld SE dummy classes.... Weld should either combine weld SE
and weld EE OR there should at least be some support for having weld ignoring some of my
classes/packages depending on which environment it is running under.
--
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
6:45 p.m.
New subject: [JBoss JIRA] Commented: (WELD-521) Introduce a way to exclude classes or packages from scanning
[
https://jira.jboss.org/browse/WELD-521?page=com.atlassian.jira.plugin.sys...
]
Morten Christensen commented on WELD-521:
-----------------------------------------
Oh, sad news about being to late for Glassfish 3.01. I will need to check for other
workarounds (f.x. if the OSGI classes that I embed can resolve under glassfish so Weld
does not blow up). If I can't do a workaround, I will have to either drop glassfish 3
support or replace Weld with another dependency management framework.
As for the format, what about something with multiple include and exclude regular
expressions where exclude has priority over include and where the include/exclude's
can be enabled/disabled dynamically using a static method that returns true/false. Fx.
<beanclasses>
<include regExpr="com.mypackage.*"/>
<include regExpr="org.somelib.*"
if="com.mypackage.MyUtil.isProfessional">
<exclude regExpr="com.mypackage.container.osgi.*"
unless="com.mypackage.MyUtil.isOsgi"/>
</beanclasses>
Where the default would be:
<beanclasses>
<include regExpr=".*"/>
</beanclasses>
And it would be easy to optimize this so when the default is used, then the performance
impact of filtering would be zero. In other cases, there would be a slight added
performance overhead for filtering but that would likely be offset by improved performance
of weld not having to deal with the excluded classes.
Introduce a way to exclude classes or packages from scanning
------------------------------------------------------------
Key: WELD-521
URL: https://jira.jboss.org/browse/WELD-521
Project: Weld
Issue Type: Feature Request
Components: Bootstrap and Metamodel API
Environment: Java SE and Java EE + weld
Reporter: Morten Christensen
Attachments: weld-se-ee-passifier.jar
Better support for dual SE and EE applications. I have some weld-using jar's that can
be deployed on a Java EE and work standalone. It is possible to get this to work using
both weld SE and weld EE but it is a pain. F.x. when deployed under glassfish weld will
fail unless I include a few weld SE dummy classes.... Weld should either combine weld SE
and weld EE OR there should at least be some support for having weld ignoring some of my
classes/packages depending on which environment it is running under.
--
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
12:52 a.m.
New subject: [JBoss JIRA] Commented: (WELD-521) Introduce a way to exclude classes or packages from scanning
[
https://jira.jboss.org/browse/WELD-521?page=com.atlassian.jira.plugin.sys...
]
Pete Muir commented on WELD-521:
--------------------------------
So you think we should reuse beans.xml for this?
I'll think about your ideas for how to enable/disable. I don't love the syntax
right now, but I like the functionality.
Introduce a way to exclude classes or packages from scanning
------------------------------------------------------------
Key: WELD-521
URL: https://jira.jboss.org/browse/WELD-521
Project: Weld
Issue Type: Feature Request
Components: Bootstrap and Metamodel API
Environment: Java SE and Java EE + weld
Reporter: Morten Christensen
Attachments: weld-se-ee-passifier.jar
Better support for dual SE and EE applications. I have some weld-using jar's that can
be deployed on a Java EE and work standalone. It is possible to get this to work using
both weld SE and weld EE but it is a pain. F.x. when deployed under glassfish weld will
fail unless I include a few weld SE dummy classes.... Weld should either combine weld SE
and weld EE OR there should at least be some support for having weld ignoring some of my
classes/packages depending on which environment it is running under.
--
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
1:14 a.m.
New subject: [JBoss JIRA] Commented: (WELD-521) Introduce a way to exclude classes or packages from scanning
[
https://jira.jboss.org/browse/WELD-521?page=com.atlassian.jira.plugin.sys...
]
Morten Christensen commented on WELD-521:
-----------------------------------------
Actually, I thought reusing beans.xml was what you wanted so that's why I went this
way in the proposal ? I have no strong opinion here, but since beans.xml is used by both
JEE and JSE (and in the future OSGI) it seems like a good place to place this.
Designing API's is always hard (especially in XML) so I am very interested to hear
other ideas. The include/exclude approach is both powerful and familiar and easy to
understand. The "if" and "unless" are the simplest way to do
conditions and the attributes are similar to what ANT uses for conditional targets. And
implementation wise also think this should be simple to support using java's build in
regular expressions.
Introduce a way to exclude classes or packages from scanning
------------------------------------------------------------
Key: WELD-521
URL: https://jira.jboss.org/browse/WELD-521
Project: Weld
Issue Type: Feature Request
Components: Bootstrap and Metamodel API
Environment: Java SE and Java EE + weld
Reporter: Morten Christensen
Attachments: weld-se-ee-passifier.jar
Better support for dual SE and EE applications. I have some weld-using jar's that can
be deployed on a Java EE and work standalone. It is possible to get this to work using
both weld SE and weld EE but it is a pain. F.x. when deployed under glassfish weld will
fail unless I include a few weld SE dummy classes.... Weld should either combine weld SE
and weld EE OR there should at least be some support for having weld ignoring some of my
classes/packages depending on which environment it is running under.
--
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
1:23 a.m.
New subject: [JBoss JIRA] Commented: (WELD-521) Introduce a way to exclude classes or packages from scanning
[
https://jira.jboss.org/browse/WELD-521?page=com.atlassian.jira.plugin.sys...
]
Morten Christensen commented on WELD-521:
-----------------------------------------
BTW: This is a critical feature for me so what is the deadline to get this into glassfish
3.1 and jboss 6 ?
Introduce a way to exclude classes or packages from scanning
------------------------------------------------------------
Key: WELD-521
URL: https://jira.jboss.org/browse/WELD-521
Project: Weld
Issue Type: Feature Request
Components: Bootstrap and Metamodel API
Environment: Java SE and Java EE + weld
Reporter: Morten Christensen
Attachments: weld-se-ee-passifier.jar
Better support for dual SE and EE applications. I have some weld-using jar's that can
be deployed on a Java EE and work standalone. It is possible to get this to work using
both weld SE and weld EE but it is a pain. F.x. when deployed under glassfish weld will
fail unless I include a few weld SE dummy classes.... Weld should either combine weld SE
and weld EE OR there should at least be some support for having weld ignoring some of my
classes/packages depending on which environment it is running under.
--
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
9:22 p.m.
New subject: [JBoss JIRA] Commented: (WELD-521) Introduce a way to exclude classes or packages from scanning
[
https://jira.jboss.org/browse/WELD-521?page=com.atlassian.jira.plugin.sys...
]
Pete Muir commented on WELD-521:
--------------------------------
On reflection, yes, beans.xml sounds good. I will work on this tonight, and it will be
released in time for AS6/GF 3.1.
In terms of syntax, I would change it very slightly:
<scan>
<include pattern="com.mypackage" />
<exclude pattern="org."somelib.*
if="com.mypackage.MyUtil.isProfessional" />
<exclude pattern="com.mypackage.container.osgi.*"
if="!com.mypackage.MyUtil.isOsgi"/>
</scan>
Parsing out that initial bang is easy.
Agree with you on precedence of include/exclude.
Introduce a way to exclude classes or packages from scanning
------------------------------------------------------------
Key: WELD-521
URL: https://jira.jboss.org/browse/WELD-521
Project: Weld
Issue Type: Feature Request
Components: Bootstrap and Metamodel API
Environment: Java SE and Java EE + weld
Reporter: Morten Christensen
Attachments: weld-se-ee-passifier.jar
Better support for dual SE and EE applications. I have some weld-using jar's that can
be deployed on a Java EE and work standalone. It is possible to get this to work using
both weld SE and weld EE but it is a pain. F.x. when deployed under glassfish weld will
fail unless I include a few weld SE dummy classes.... Weld should either combine weld SE
and weld EE OR there should at least be some support for having weld ignoring some of my
classes/packages depending on which environment it is running under.
--
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
9:24 p.m.
New subject: [JBoss JIRA] Commented: (WELD-521) Introduce a way to exclude classes or packages from scanning
[
https://jira.jboss.org/browse/WELD-521?page=com.atlassian.jira.plugin.sys...
]
Pete Muir commented on WELD-521:
--------------------------------
BTW I would suggest we put this in a different namespace, just to be friendly.
Introduce a way to exclude classes or packages from scanning
------------------------------------------------------------
Key: WELD-521
URL: https://jira.jboss.org/browse/WELD-521
Project: Weld
Issue Type: Feature Request
Components: Bootstrap and Metamodel API
Environment: Java SE and Java EE + weld
Reporter: Morten Christensen
Attachments: weld-se-ee-passifier.jar
Better support for dual SE and EE applications. I have some weld-using jar's that can
be deployed on a Java EE and work standalone. It is possible to get this to work using
both weld SE and weld EE but it is a pain. F.x. when deployed under glassfish weld will
fail unless I include a few weld SE dummy classes.... Weld should either combine weld SE
and weld EE OR there should at least be some support for having weld ignoring some of my
classes/packages depending on which environment it is running under.
--
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
9:24 p.m.
New subject: [JBoss JIRA] Commented: (WELD-521) Introduce a way to exclude classes or packages from scanning
[
https://jira.jboss.org/browse/WELD-521?page=com.atlassian.jira.plugin.sys...
]
Pete Muir commented on WELD-521:
--------------------------------
Mark, how do you feel about this syntax, would you adopt the same in OWB making it
consistent?
Introduce a way to exclude classes or packages from scanning
------------------------------------------------------------
Key: WELD-521
URL: https://jira.jboss.org/browse/WELD-521
Project: Weld
Issue Type: Feature Request
Components: Bootstrap and Metamodel API
Environment: Java SE and Java EE + weld
Reporter: Morten Christensen
Attachments: weld-se-ee-passifier.jar
Better support for dual SE and EE applications. I have some weld-using jar's that can
be deployed on a Java EE and work standalone. It is possible to get this to work using
both weld SE and weld EE but it is a pain. F.x. when deployed under glassfish weld will
fail unless I include a few weld SE dummy classes.... Weld should either combine weld SE
and weld EE OR there should at least be some support for having weld ignoring some of my
classes/packages depending on which environment it is running under.
--
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
9:26 p.m.
New subject: [JBoss JIRA] Commented: (WELD-521) Introduce a way to exclude classes or packages from scanning
[
https://jira.jboss.org/browse/WELD-521?page=com.atlassian.jira.plugin.sys...
]
Pete Muir commented on WELD-521:
--------------------------------
namespacewise, how about urn:cdi:extensions
Introduce a way to exclude classes or packages from scanning
------------------------------------------------------------
Key: WELD-521
URL: https://jira.jboss.org/browse/WELD-521
Project: Weld
Issue Type: Feature Request
Components: Bootstrap and Metamodel API
Environment: Java SE and Java EE + weld
Reporter: Morten Christensen
Attachments: weld-se-ee-passifier.jar
Better support for dual SE and EE applications. I have some weld-using jar's that can
be deployed on a Java EE and work standalone. It is possible to get this to work using
both weld SE and weld EE but it is a pain. F.x. when deployed under glassfish weld will
fail unless I include a few weld SE dummy classes.... Weld should either combine weld SE
and weld EE OR there should at least be some support for having weld ignoring some of my
classes/packages depending on which environment it is running under.
--
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
9:45 p.m.
New subject: [JBoss JIRA] Commented: (WELD-521) Introduce a way to exclude classes or packages from scanning
[
https://jira.jboss.org/browse/WELD-521?page=com.atlassian.jira.plugin.sys...
]
Morten Christensen commented on WELD-521:
-----------------------------------------
Great. I am happy you liked my first try at API design for weld. I am quite used to ANT
and ruby so I think if/unless is cleaner but that is not a problem.
I have also thought a bit more about the enable/disable support. I need the static method
support myself so I am quite happy with this, but maybe other people would also like an
alternative when java system properties can be used instead (it would be trivial to make a
static method that resolves to a java system property but some might want to be able to
specify a java system property directly ?). What do you think?
Introduce a way to exclude classes or packages from scanning
------------------------------------------------------------
Key: WELD-521
URL: https://jira.jboss.org/browse/WELD-521
Project: Weld
Issue Type: Feature Request
Components: Bootstrap and Metamodel API
Environment: Java SE and Java EE + weld
Reporter: Morten Christensen
Attachments: weld-se-ee-passifier.jar
Better support for dual SE and EE applications. I have some weld-using jar's that can
be deployed on a Java EE and work standalone. It is possible to get this to work using
both weld SE and weld EE but it is a pain. F.x. when deployed under glassfish weld will
fail unless I include a few weld SE dummy classes.... Weld should either combine weld SE
and weld EE OR there should at least be some support for having weld ignoring some of my
classes/packages depending on which environment it is running under.
--
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
9:48 p.m.
New subject: [JBoss JIRA] Commented: (WELD-521) Introduce a way to exclude classes or packages from scanning
[
https://jira.jboss.org/browse/WELD-521?page=com.atlassian.jira.plugin.sys...
]
Pete Muir commented on WELD-521:
--------------------------------
I think that can be done fairly trivially by using an if method really, so I think
it's covered personally. Too complex an API is a bad thing.
Introduce a way to exclude classes or packages from scanning
------------------------------------------------------------
Key: WELD-521
URL: https://jira.jboss.org/browse/WELD-521
Project: Weld
Issue Type: Feature Request
Components: Bootstrap and Metamodel API
Environment: Java SE and Java EE + weld
Reporter: Morten Christensen
Attachments: weld-se-ee-passifier.jar
Better support for dual SE and EE applications. I have some weld-using jar's that can
be deployed on a Java EE and work standalone. It is possible to get this to work using
both weld SE and weld EE but it is a pain. F.x. when deployed under glassfish weld will
fail unless I include a few weld SE dummy classes.... Weld should either combine weld SE
and weld EE OR there should at least be some support for having weld ignoring some of my
classes/packages depending on which environment it is running under.
--
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
10:15 p.m.
New subject: [JBoss JIRA] Commented: (WELD-521) Introduce a way to exclude classes or packages from scanning
[
https://jira.jboss.org/browse/WELD-521?page=com.atlassian.jira.plugin.sys...
]
Morten Christensen commented on WELD-521:
-----------------------------------------
yea, I would tend to agree. Just wanted to make sure we discussed it..
BTW: I am very happy that you are adding this now. Will solve a LOT of problems + help
performance.
Introduce a way to exclude classes or packages from scanning
------------------------------------------------------------
Key: WELD-521
URL: https://jira.jboss.org/browse/WELD-521
Project: Weld
Issue Type: Feature Request
Components: Bootstrap and Metamodel API
Environment: Java SE and Java EE + weld
Reporter: Morten Christensen
Attachments: weld-se-ee-passifier.jar
Better support for dual SE and EE applications. I have some weld-using jar's that can
be deployed on a Java EE and work standalone. It is possible to get this to work using
both weld SE and weld EE but it is a pain. F.x. when deployed under glassfish weld will
fail unless I include a few weld SE dummy classes.... Weld should either combine weld SE
and weld EE OR there should at least be some support for having weld ignoring some of my
classes/packages depending on which environment it is running under.
--
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
12:01 p.m.
New subject: [JBoss JIRA] Commented: (WELD-521) Introduce a way to exclude classes or packages from scanning
[
https://jira.jboss.org/browse/WELD-521?page=com.atlassian.jira.plugin.sys...
]
Morten Christensen commented on WELD-521:
-----------------------------------------
I have a question about how we integrate this with the on-going Weld SE work so it will
work in both JEE and JSE (and when eventually OSGI)?
Also, for the JSE/OSGI work that I am helping with, I think - at least for use by my own
project - I will end up with implementing a configuration (list of bean classes). Such a
plain list of classnames can be mapped into a bunch of includes but it might be better
performance-wise to support both patterns and fully qualified class names directly in weld
? I.e. both a "pattern" attribute and a "name" attribute ?
Finally, in our examples we need to change the regular expressions as we forgot to escape
the "." in package names. It should still work but let's be careful such an
error won't escape into any documentation/tests at it would be confusing.
Introduce a way to exclude classes or packages from scanning
------------------------------------------------------------
Key: WELD-521
URL: https://jira.jboss.org/browse/WELD-521
Project: Weld
Issue Type: Feature Request
Components: Bootstrap and Metamodel API
Environment: Java SE and Java EE + weld
Reporter: Morten Christensen
Attachments: weld-se-ee-passifier.jar
Better support for dual SE and EE applications. I have some weld-using jar's that can
be deployed on a Java EE and work standalone. It is possible to get this to work using
both weld SE and weld EE but it is a pain. F.x. when deployed under glassfish weld will
fail unless I include a few weld SE dummy classes.... Weld should either combine weld SE
and weld EE OR there should at least be some support for having weld ignoring some of my
classes/packages depending on which environment it is running under.
--
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
9:46 a.m.
New subject: [JBoss JIRA] Commented: (WELD-521) Introduce a way to exclude classes or packages from scanning
[
https://jira.jboss.org/browse/WELD-521?page=com.atlassian.jira.plugin.sys...
]
Pete Muir commented on WELD-521:
--------------------------------
To have this work in all environments, in such a way that we don't actually load class
definitions we don't need, we need to change the Weld SPI so that rather than passing
in Collection<Class<?>> we pass in Collection<String> (containing the
class names of the classes to load). This way, we can apply the include/exclude before we
load the class definition.
Such a plain list of classnames can be mapped into a bunch of
includes but it might
be better performance-wise to support both patterns and fully qualified class names
directly in weld ? I.e. both a "pattern" attribute and a "name"
attribute ?
We're starting to produce a pretty complex API for a simple problem. Let's try to
keep it simple.
Finally, in our examples we need to change the regular expressions as
we forgot to escape the "." in package names.
Ugh! Now I'm wondering if supporting real regular expressions is a good idea at all. I
think supporting Ant style include/exclude names might be much better (and scrap the
regular expressions totally).
Introduce a way to exclude classes or packages from scanning
------------------------------------------------------------
Key: WELD-521
URL: https://jira.jboss.org/browse/WELD-521
Project: Weld
Issue Type: Feature Request
Components: Bootstrap and Metamodel API
Environment: Java SE and Java EE + weld
Reporter: Morten Christensen
Attachments: weld-se-ee-passifier.jar
Better support for dual SE and EE applications. I have some weld-using jar's that can
be deployed on a Java EE and work standalone. It is possible to get this to work using
both weld SE and weld EE but it is a pain. F.x. when deployed under glassfish weld will
fail unless I include a few weld SE dummy classes.... Weld should either combine weld SE
and weld EE OR there should at least be some support for having weld ignoring some of my
classes/packages depending on which environment it is running under.
--
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
1:47 p.m.
New subject: [JBoss JIRA] Commented: (WELD-521) Introduce a way to exclude classes or packages from scanning
[
https://jira.jboss.org/browse/WELD-521?page=com.atlassian.jira.plugin.sys...
]
Pete Muir commented on WELD-521:
--------------------------------
I talked to Gavin about this, and he convinced me we consider specific use cases for the
if/unless, rather than a generic static method.
Morten, what is yours?
Introduce a way to exclude classes or packages from scanning
------------------------------------------------------------
Key: WELD-521
URL: https://jira.jboss.org/browse/WELD-521
Project: Weld
Issue Type: Feature Request
Components: Bootstrap and Metamodel API
Environment: Java SE and Java EE + weld
Reporter: Morten Christensen
Attachments: weld-se-ee-passifier.jar
Better support for dual SE and EE applications. I have some weld-using jar's that can
be deployed on a Java EE and work standalone. It is possible to get this to work using
both weld SE and weld EE but it is a pain. F.x. when deployed under glassfish weld will
fail unless I include a few weld SE dummy classes.... Weld should either combine weld SE
and weld EE OR there should at least be some support for having weld ignoring some of my
classes/packages depending on which environment it is running under.
--
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
3:14 p.m.
New subject: [JBoss JIRA] Commented: (WELD-521) Introduce a way to exclude classes or packages from scanning
[
https://jira.jboss.org/browse/WELD-521?page=com.atlassian.jira.plugin.sys...
]
Morten Christensen commented on WELD-521:
-----------------------------------------
My needs are:
1) Support running environments: JEE, JSE, OSGI (but I don't think this can be
auto-detected - I think only the application will be able to know what the environment is,
which is why a static method is good).
2) Support different versions of the same software - f.x. "standard",
"professionel", "enterprise".
Both these needs affect the classpath and what classes/packages should be scanned (f.x. my
app's OSGI specific classes will simply not resolve if running as JSE and maybe not
under JEE) . Normally, in Java this is not a problem because the Java standard has lazy
loading of classes.... But since the weld scanner loads everything, this will cause
applications to "blow up" unless we have a way to customize where to look.
Introduce a way to exclude classes or packages from scanning
------------------------------------------------------------
Key: WELD-521
URL: https://jira.jboss.org/browse/WELD-521
Project: Weld
Issue Type: Feature Request
Components: Bootstrap and Metamodel API
Environment: Java SE and Java EE + weld
Reporter: Morten Christensen
Attachments: weld-se-ee-passifier.jar
Better support for dual SE and EE applications. I have some weld-using jar's that can
be deployed on a Java EE and work standalone. It is possible to get this to work using
both weld SE and weld EE but it is a pain. F.x. when deployed under glassfish weld will
fail unless I include a few weld SE dummy classes.... Weld should either combine weld SE
and weld EE OR there should at least be some support for having weld ignoring some of my
classes/packages depending on which environment it is running under.
--
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
11:06 p.m.
New subject: [JBoss JIRA] Commented: (WELD-521) Introduce a way to exclude classes or packages from scanning
[
https://jira.jboss.org/browse/WELD-521?page=com.atlassian.jira.plugin.sys...
]
Pete Muir commented on WELD-521:
--------------------------------
Ok, lets dig into what the static method would do in both (1) and (2). Can you give us an
example of how you intend to write this method?
Introduce a way to exclude classes or packages from scanning
------------------------------------------------------------
Key: WELD-521
URL: https://jira.jboss.org/browse/WELD-521
Project: Weld
Issue Type: Feature Request
Components: Bootstrap and Metamodel API
Environment: Java SE and Java EE + weld
Reporter: Morten Christensen
Attachments: weld-se-ee-passifier.jar
Better support for dual SE and EE applications. I have some weld-using jar's that can
be deployed on a Java EE and work standalone. It is possible to get this to work using
both weld SE and weld EE but it is a pain. F.x. when deployed under glassfish weld will
fail unless I include a few weld SE dummy classes.... Weld should either combine weld SE
and weld EE OR there should at least be some support for having weld ignoring some of my
classes/packages depending on which environment it is running under.
--
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
11:18 p.m.
New subject: [JBoss JIRA] Commented: (WELD-521) Introduce a way to exclude classes or packages from scanning
[
https://jira.jboss.org/browse/WELD-521?page=com.atlassian.jira.plugin.sys...
]
Morten Christensen commented on WELD-521:
-----------------------------------------
implementation details:
1) Currently, I use a custom (application-specific) Java system property for this. The
property is setup differently depending on which entry point my app has (Main method, Osgi
activator or ServletContextListener.
2) I am not sure how I will implement this yet. I might use lookup and see what different
implementatons are available on the classpath or what services are registered under OSGI
?
Introduce a way to exclude classes or packages from scanning
------------------------------------------------------------
Key: WELD-521
URL: https://jira.jboss.org/browse/WELD-521
Project: Weld
Issue Type: Feature Request
Components: Bootstrap and Metamodel API
Environment: Java SE and Java EE + weld
Reporter: Morten Christensen
Attachments: weld-se-ee-passifier.jar
Better support for dual SE and EE applications. I have some weld-using jar's that can
be deployed on a Java EE and work standalone. It is possible to get this to work using
both weld SE and weld EE but it is a pain. F.x. when deployed under glassfish weld will
fail unless I include a few weld SE dummy classes.... Weld should either combine weld SE
and weld EE OR there should at least be some support for having weld ignoring some of my
classes/packages depending on which environment it is running under.
--
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
11:29 p.m.
New subject: [JBoss JIRA] Commented: (WELD-521) Introduce a way to exclude classes or packages from scanning
[
https://jira.jboss.org/browse/WELD-521?page=com.atlassian.jira.plugin.sys...
]
Pete Muir commented on WELD-521:
--------------------------------
Yeah, the two approaches I had already got on my list were system property based and
class-availability based.
Let's start with that. It's easy to add stuff. Hard to take it way.
Introduce a way to exclude classes or packages from scanning
------------------------------------------------------------
Key: WELD-521
URL: https://jira.jboss.org/browse/WELD-521
Project: Weld
Issue Type: Feature Request
Components: Bootstrap and Metamodel API
Environment: Java SE and Java EE + weld
Reporter: Morten Christensen
Attachments: weld-se-ee-passifier.jar
Better support for dual SE and EE applications. I have some weld-using jar's that can
be deployed on a Java EE and work standalone. It is possible to get this to work using
both weld SE and weld EE but it is a pain. F.x. when deployed under glassfish weld will
fail unless I include a few weld SE dummy classes.... Weld should either combine weld SE
and weld EE OR there should at least be some support for having weld ignoring some of my
classes/packages depending on which environment it is running under.
--
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
12:51 a.m.
New subject: [JBoss JIRA] Commented: (WELD-521) Introduce a way to exclude classes or packages from scanning
[
https://jira.jboss.org/browse/WELD-521?page=com.atlassian.jira.plugin.sys...
]
Morten Christensen commented on WELD-521:
-----------------------------------------
I don't know what you and Gavin did not like about static methods, but at least here
is one approach which will support all needs incl. my two scenarios. Why do you think it
will be easier/better to support system properties + class-availability ?
Introduce a way to exclude classes or packages from scanning
------------------------------------------------------------
Key: WELD-521
URL: https://jira.jboss.org/browse/WELD-521
Project: Weld
Issue Type: Feature Request
Components: Bootstrap and Metamodel API
Environment: Java SE and Java EE + weld
Reporter: Morten Christensen
Attachments: weld-se-ee-passifier.jar
Better support for dual SE and EE applications. I have some weld-using jar's that can
be deployed on a Java EE and work standalone. It is possible to get this to work using
both weld SE and weld EE but it is a pain. F.x. when deployed under glassfish weld will
fail unless I include a few weld SE dummy classes.... Weld should either combine weld SE
and weld EE OR there should at least be some support for having weld ignoring some of my
classes/packages depending on which environment it is running under.
--
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
2:32 p.m.
New subject: [JBoss JIRA] Commented: (WELD-521) Introduce a way to exclude classes or packages from scanning
[
https://jira.jboss.org/browse/WELD-521?page=com.atlassian.jira.plugin.sys...
]
Pete Muir commented on WELD-521:
--------------------------------
Because it is one less hoop for a user to jump through. Normally it's better to
address specific use cases, not generalities.
Introduce a way to exclude classes or packages from scanning
------------------------------------------------------------
Key: WELD-521
URL: https://jira.jboss.org/browse/WELD-521
Project: Weld
Issue Type: Feature Request
Components: Bootstrap and Metamodel API
Environment: Java SE and Java EE + weld
Reporter: Morten Christensen
Attachments: weld-se-ee-passifier.jar
Better support for dual SE and EE applications. I have some weld-using jar's that can
be deployed on a Java EE and work standalone. It is possible to get this to work using
both weld SE and weld EE but it is a pain. F.x. when deployed under glassfish weld will
fail unless I include a few weld SE dummy classes.... Weld should either combine weld SE
and weld EE OR there should at least be some support for having weld ignoring some of my
classes/packages depending on which environment it is running under.
--
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
3:14 p.m.
New subject: [JBoss JIRA] Commented: (WELD-521) Introduce a way to exclude classes or packages from scanning
[
https://jira.jboss.org/browse/WELD-521?page=com.atlassian.jira.plugin.sys...
]
Morten Christensen commented on WELD-521:
-----------------------------------------
I do not agree with your premise. Generalities that are both very expressive and at the
same time also simple is one aspect of "beautiful" designs (e.x.
"e=m*c^2" from physics). I am not saying that static properties are comparable
to this example but they are both simple and expressive.
Introduce a way to exclude classes or packages from scanning
------------------------------------------------------------
Key: WELD-521
URL: https://jira.jboss.org/browse/WELD-521
Project: Weld
Issue Type: Feature Request
Components: Bootstrap and Metamodel API
Environment: Java SE and Java EE + weld
Reporter: Morten Christensen
Attachments: weld-se-ee-passifier.jar
Better support for dual SE and EE applications. I have some weld-using jar's that can
be deployed on a Java EE and work standalone. It is possible to get this to work using
both weld SE and weld EE but it is a pain. F.x. when deployed under glassfish weld will
fail unless I include a few weld SE dummy classes.... Weld should either combine weld SE
and weld EE OR there should at least be some support for having weld ignoring some of my
classes/packages depending on which environment it is running under.
--
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
3:50 p.m.
New subject: [JBoss JIRA] Commented: (WELD-521) Introduce a way to exclude classes or packages from scanning
[
https://jira.jboss.org/browse/WELD-521?page=com.atlassian.jira.plugin.sys...
]
Pete Muir commented on WELD-521:
--------------------------------
Yeah, you hit the nail on the head. We don't agree that calling a static method is
that simple or that expressive for the average user compared to supporting specific use
cases.
Introduce a way to exclude classes or packages from scanning
------------------------------------------------------------
Key: WELD-521
URL: https://jira.jboss.org/browse/WELD-521
Project: Weld
Issue Type: Feature Request
Components: Bootstrap and Metamodel API
Environment: Java SE and Java EE + weld
Reporter: Morten Christensen
Attachments: weld-se-ee-passifier.jar
Better support for dual SE and EE applications. I have some weld-using jar's that can
be deployed on a Java EE and work standalone. It is possible to get this to work using
both weld SE and weld EE but it is a pain. F.x. when deployed under glassfish weld will
fail unless I include a few weld SE dummy classes.... Weld should either combine weld SE
and weld EE OR there should at least be some support for having weld ignoring some of my
classes/packages depending on which environment it is running under.
--
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
3:52 p.m.
New subject: [JBoss JIRA] Commented: (WELD-521) Introduce a way to exclude classes or packages from scanning
[
https://jira.jboss.org/browse/WELD-521?page=com.atlassian.jira.plugin.sys...
]
Pete Muir commented on WELD-521:
--------------------------------
BTW e=mcc is not a generality, it's a truth.
Introduce a way to exclude classes or packages from scanning
------------------------------------------------------------
Key: WELD-521
URL: https://jira.jboss.org/browse/WELD-521
Project: Weld
Issue Type: Feature Request
Components: Bootstrap and Metamodel API
Environment: Java SE and Java EE + weld
Reporter: Morten Christensen
Attachments: weld-se-ee-passifier.jar
Better support for dual SE and EE applications. I have some weld-using jar's that can
be deployed on a Java EE and work standalone. It is possible to get this to work using
both weld SE and weld EE but it is a pain. F.x. when deployed under glassfish weld will
fail unless I include a few weld SE dummy classes.... Weld should either combine weld SE
and weld EE OR there should at least be some support for having weld ignoring some of my
classes/packages depending on which environment it is running under.
--
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
6:53 p.m.
New subject: [JBoss JIRA] Updated: (WELD-521) Introduce a way to exclude classes or packages from scanning
[
https://jira.jboss.org/browse/WELD-521?page=com.atlassian.jira.plugin.sys...
]
Pete Muir updated WELD-521:
---------------------------
Attachment: WELD-521.patch
Work so far
Introduce a way to exclude classes or packages from scanning
------------------------------------------------------------
Key: WELD-521
URL: https://jira.jboss.org/browse/WELD-521
Project: Weld
Issue Type: Feature Request
Components: Bootstrap and Metamodel API
Environment: Java SE and Java EE + weld
Reporter: Morten Christensen
Attachments: WELD-521.patch, weld-se-ee-passifier.jar
Better support for dual SE and EE applications. I have some weld-using jar's that can
be deployed on a Java EE and work standalone. It is possible to get this to work using
both weld SE and weld EE but it is a pain. F.x. when deployed under glassfish weld will
fail unless I include a few weld SE dummy classes.... Weld should either combine weld SE
and weld EE OR there should at least be some support for having weld ignoring some of my
classes/packages depending on which environment it is running under.
--
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
4:40 p.m.
New subject: [JBoss JIRA] Updated: (WELD-521) Introduce a way to exclude classes or packages from scanning
[
https://jira.jboss.org/browse/WELD-521?page=com.atlassian.jira.plugin.sys...
]
Pete Muir updated WELD-521:
---------------------------
Fix Version/s: 1.1.0.BETA1
Introduce a way to exclude classes or packages from scanning
------------------------------------------------------------
Key: WELD-521
URL: https://jira.jboss.org/browse/WELD-521
Project: Weld
Issue Type: Feature Request
Components: Bootstrap and Metamodel API
Environment: Java SE and Java EE + weld
Reporter: Morten Christensen
Fix For: 1.1.0.BETA1
Attachments: WELD-521.patch, weld-se-ee-passifier.jar
Better support for dual SE and EE applications. I have some weld-using jar's that can
be deployed on a Java EE and work standalone. It is possible to get this to work using
both weld SE and weld EE but it is a pain. F.x. when deployed under glassfish weld will
fail unless I include a few weld SE dummy classes.... Weld should either combine weld SE
and weld EE OR there should at least be some support for having weld ignoring some of my
classes/packages depending on which environment it is running under.
--
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
1:59 a.m.
New subject: [JBoss JIRA] Commented: (WELD-521) Introduce a way to exclude classes or packages from scanning
[
https://jira.jboss.org/browse/WELD-521?page=com.atlassian.jira.plugin.sys...
]
Pete Muir commented on WELD-521:
--------------------------------
Work so far is now at http://github.com/pmuir/weld-core/tree/WELD-521
Introduce a way to exclude classes or packages from scanning
------------------------------------------------------------
Key: WELD-521
URL: https://jira.jboss.org/browse/WELD-521
Project: Weld
Issue Type: Feature Request
Components: Bootstrap and Metamodel API
Environment: Java SE and Java EE + weld
Reporter: Morten Christensen
Fix For: 1.1.0.BETA1
Attachments: WELD-521.patch, weld-se-ee-passifier.jar
Better support for dual SE and EE applications. I have some weld-using jar's that can
be deployed on a Java EE and work standalone. It is possible to get this to work using
both weld SE and weld EE but it is a pain. F.x. when deployed under glassfish weld will
fail unless I include a few weld SE dummy classes.... Weld should either combine weld SE
and weld EE OR there should at least be some support for having weld ignoring some of my
classes/packages depending on which environment it is running under.
--
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
8:58 p.m.
New subject: [JBoss JIRA] Closed: (WELD-521) Introduce a way to exclude classes or packages from scanning
[
https://jira.jboss.org/browse/WELD-521?page=com.atlassian.jira.plugin.sys...
]
Pete Muir closed WELD-521.
--------------------------
Assignee: Pete Muir
Resolution: Done
Introduce a way to exclude classes or packages from scanning
------------------------------------------------------------
Key: WELD-521
URL: https://jira.jboss.org/browse/WELD-521
Project: Weld
Issue Type: Feature Request
Components: Bootstrap and Metamodel API
Environment: Java SE and Java EE + weld
Reporter: Morten Christensen
Assignee: Pete Muir
Fix For: 1.1.0.BETA1
Attachments: WELD-521.patch, weld-se-ee-passifier.jar
Better support for dual SE and EE applications. I have some weld-using jar's that can
be deployed on a Java EE and work standalone. It is possible to get this to work using
both weld SE and weld EE but it is a pain. F.x. when deployed under glassfish weld will
fail unless I include a few weld SE dummy classes.... Weld should either combine weld SE
and weld EE OR there should at least be some support for having weld ignoring some of my
classes/packages depending on which environment it is running under.
--
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
5053
days inactive
5164
days old
37 comments
2 participants
participants (2)
-
Morten Christensen (JIRA) -
Pete Muir (JIRA)