[webbeans-dev] MC Int (was Re: mc int deployer)
by Pete Muir
Took a look at tests - thanks for doing those :-)
On 23 Dec 2008, at 10:55, Ales Justin wrote:
>>> The getIntegrationJar is wrong.
>> Yes, I ended up using it to push webbeans-ri.jar onto the app
>> classpath.
>
> We need multiple entries to add dynamically:
> * wb-api
> * wb-ri-spi
> * wb-ri-impl
> * wb-jbossas-int
>
> I'll fix the class, you fix the build.
Doesn't look like you did this?
>
>
>>> And I think we should be scoping CL in webbeans.deployer,
>>> since otherwise it's shared across whole AS - not Seam like.
>> Again, good idea, probably obviate the need for the above.
>
> This is now fixed, since wb-mc-int doesn't make use of wb.
> And it shouldn't!
>
> If wb-jbossas-int needs some more structured info from wb-mc-int
> it should do so by defining proper api in wb-mc-int.
> But since it's mostly classes and urls wb-mc-int should provide,
> we should be fine.
Yes, agreed.
>
>
> This CL scoping should be part of the other emails you and Stan sent
> around.
> I'll have a look at what can be done in the next days ...
Let us know when you have info.
>
>
>>> This looks like a hack / bad practice, leaving it to TCL w/o the
>>> cl == null check.
>>> e.g. think OSGi ;-)
>> That one uses the CL from the DU, but there are other instances in
>> WB - I have an open JIRA ;-)
>
> Which JIRA?
https://jira.jboss.org/jira/browse/WBRI-70
Basically, I want to always delegate CL to the container SPI, so that
it can work well e.g. in OSGi. But I do initially need to use the CL
to load the the SPI impl class. What is the best way to do that, that
will be portable?
Something like this?
if (Thread.currentThread().getContextClassLoader() != null) {
classForName(name, Thread.currentThread().getContextClassLoader());
} else {
classForName(name, WebBeansBootstrap.class.getClassLoader());
}
>
> btw: is there a forum for WB?
User forum: http://seamframework.org/Community/WebBeansUsers
> If not, we should create on on jboss.org,
> so this kind of discussions are placed there.
Dev discussions on this list. BTW non-subscribers can post here, i
just have to allow them to post once as the moderator.
15 years, 4 months
[webbeans-dev] Alpha1
by Pete Muir
Please hold off committing until I give the all clear, I'm about to
start testing and tagging.
15 years, 4 months
[webbeans-dev] numberguess and translator build/deploy/tests passed using JDK 1.7
by Arbi Sookazian
Hello,
So I did some build/deploy/functional testing tonight using the Web Beans RI alpha version.
I downloaded and extracted JBoss 5.0.0.GA.
I also downloaded webbeans-ri-distribution-1.0.0-SNAPSHOT and tried my best to follow the directions in the readme.txt files. There are a couple of things worth noting here (sorry if this has already been noted):
1) C:\temp\webbeans-1.0.0-SNAPSHOT\readme.txt states to "run ant install" but in fact I ran ant update. Here is the target for that out of the build.xml:
<target name="update" depends="install-jboss-ejb3-update, install-webbeans.deployer" description="Update JBoss 5 for the Web Beans RI" />
2) In C:\temp\webbeans-1.0.0-SNAPSHOT\examples\readme.txt it states run "ant -f ../build.xml install-jboss5 in the examples directory".
When you do that you get "Buildfile: ..\build.xml does not exist!"
Also, I was able to run "ant clean, deploy" in the numberguess folder and translator folder and deploy/run the apps successfully using Java(TM) SE Runtime Environment (build 1.7.0-ea-b40).
Good stuff!
Any news for upcoming add'l example apps like booking, etc.?
15 years, 4 months
[webbeans-dev] the change to java 6 broke my build
by Gavin King
gavin-kings-macbook-pro:webbeans-ri gavin$ javac -version
javac 1.6.0_07
gavin-kings-macbook-pro:webbeans-ri gavin$ mvn clean install
[INFO] Scanning for projects...
[INFO] Reactor build order:
[INFO] Web Beans
[INFO] Web Beans API
[INFO] Web Beans RI Service Provider Interfaces
[INFO] Web Beans RI
WAGON_VERSION: 1.0-beta-2
[INFO] ----------------------------------------------------------------------------
[INFO] Building Web Beans
[INFO] task-segment: [clean, install]
[INFO] ----------------------------------------------------------------------------
[INFO] [clean:clean]
[INFO] [site:attach-descriptor]
[INFO] Preparing source:jar
[WARNING] Removing: jar from forked lifecycle, to prevent recursive invocation.
[INFO] No goals needed for project - skipping
[INFO] [source:jar {execution: attach-sources}]
[INFO] [install:install]
[INFO] Installing /Users/gavin/Documents/workspace/webbeans-ri/pom.xml
to /Users/gavin/.m2/repository/org/jboss/webbeans/parent/1.0.0-SNAPSHOT/parent-1.0.0-SNAPSHOT.pom
[INFO] ----------------------------------------------------------------------------
[INFO] Building Web Beans API
[INFO] task-segment: [clean, install]
[INFO] ----------------------------------------------------------------------------
[INFO] [clean:clean]
[INFO] Deleting directory
/Users/gavin/Documents/workspace/webbeans-ri/webbeans-api/target
[INFO] [resources:resources]
[WARNING] Using platform encoding (MacRoman actually) to copy filtered
resources, i.e. build is platform dependent!
[INFO] Copying 1 resource
[INFO] [compiler:compile]
[INFO] Compiling 67 source files to
/Users/gavin/Documents/workspace/webbeans-ri/webbeans-api/target/classes
[INFO] ------------------------------------------------------------------------
[ERROR] BUILD FAILURE
[INFO] ------------------------------------------------------------------------
[INFO] Compilation failure
Failure executing javac, but could not parse the error:
javac: invalid target release: 1.6
Usage: javac <options> <source files>
where possible options include:
-g Generate all debugging info
-g:none Generate no debugging info
-g:{lines,vars,source} Generate only some debugging info
-nowarn Generate no warnings
-verbose Output messages about what the compiler is doing
-deprecation Output source locations where deprecated
APIs are used
-classpath <path> Specify where to find user class files
-cp <path> Specify where to find user class files
-sourcepath <path> Specify where to find input source files
-bootclasspath <path> Override location of bootstrap class files
-extdirs <dirs> Override location of installed extensions
-endorseddirs <dirs> Override location of endorsed standards path
-d <directory> Specify where to place generated class files
-encoding <encoding> Specify character encoding used by source files
-source <release> Provide source compatibility with specified release
-target <release> Generate class files for specific VM version
-version Version information
-help Print a synopsis of standard options
-X Print a synopsis of nonstandard options
-J<flag> Pass <flag> directly to the runtime system
Failure executing javac, but could not parse the error:
javac: invalid target release: 1.6
Usage: javac <options> <source files>
where possible options include:
-g Generate all debugging info
-g:none Generate no debugging info
-g:{lines,vars,source} Generate only some debugging info
-nowarn Generate no warnings
-verbose Output messages about what the compiler is doing
-deprecation Output source locations where deprecated
APIs are used
-classpath <path> Specify where to find user class files
-cp <path> Specify where to find user class files
-sourcepath <path> Specify where to find input source files
-bootclasspath <path> Override location of bootstrap class files
-extdirs <dirs> Override location of installed extensions
-endorseddirs <dirs> Override location of endorsed standards path
-d <directory> Specify where to place generated class files
-encoding <encoding> Specify character encoding used by source files
-source <release> Provide source compatibility with specified release
-target <release> Generate class files for specific VM version
-version Version information
-help Print a synopsis of standard options
-X Print a synopsis of nonstandard options
-J<flag> Pass <flag> directly to the runtime system
[INFO] ------------------------------------------------------------------------
[INFO] For more information, run Maven with the -e switch
[INFO] ------------------------------------------------------------------------
[INFO] Total time: 4 seconds
[INFO] Finished at: Mon Dec 22 12:06:36 EST 2008
[INFO] Final Memory: 14M/25M
[INFO] ------------------------------------------------------------------------
gavin-kings-macbook-pro:webbeans-ri gavin$
--
Gavin King
gavin.king(a)gmail.com
http://in.relation.to/Bloggers/Gavin
http://hibernate.org
http://seamframework.org
15 years, 4 months
[webbeans-dev] Fwd: Removal of pluggability contracts
by Gavin King
---------- Forwarded message ----------
From: Gavin King <gavin(a)hibernate.org>
Date: Sun, Dec 21, 2008 at 3:03 PM
Subject: Re: Removal of pluggability contracts
To: Java Community Process JSR #299 Expert List <JSR-299-EG(a)jcp.org>,
Michael Keith <michael.keith(a)oracle.com>, Jim Knutson
<knutson(a)us.ibm.com>
A couple of issues have come up as part of this:
SFSBs with no web bean remove method
================================
We have an open issue w.r.t destruction of SFSBs which have no web
bean remove method. Now that the requirement for pluggability is gone,
I think we should simply say that in this case, the container must
destroy the SFSB when its context ends *without* calling any remove
method.
I will go ahead and make that change unless there is someone who
objects to this.
Name of "Manager" interface
======================
The word "manager" is no longer used in the spec, except as the name
of the interface that is now used mostly as an SPI. Should we change
the name of this interface? Alternatives include:
Container
Directory
Factory
Injector
Thoughts?
Terminology for "child containers"
=========================
I changed "child manager" to "child container", however I'm not really
happy with this terminology. I think we need a new word to use when
talking about the hierarchical model. Something like "module" or
"assembly" makes sense, but I'm afraid that those are already pretty
overloaded terms.
Suggestions?
On Sat, Dec 20, 2008 at 3:53 PM, Gavin King <gavin(a)hibernate.org> wrote:
> Folks, here is the first draft of the spec with pluggability contracts removed.
>
> Notice the following language changes:
>
> Web Bean manager -> container
> initialization time -> deployment time
>
> The biggest concrete changes are to chapters 1 and 11. (However, there
> is a sprinkling of removed sections throughout the spec.)
>
> Please review this and let me know what you think
>
> --
> Gavin King
> gavin.king(a)gmail.com
> http://in.relation.to/Bloggers/Gavin
> http://hibernate.org
> http://seamframework.org
>
--
Gavin King
gavin.king(a)gmail.com
http://in.relation.to/Bloggers/Gavin
http://hibernate.org
http://seamframework.org
--
Gavin King
gavin.king(a)gmail.com
http://in.relation.to/Bloggers/Gavin
http://hibernate.org
http://seamframework.org
15 years, 4 months