added features in weld-translator example
by Arbi Sookazian
http://github.com/asookazian/weld-examples
Key points:
1) added event fire + observer
2) added JPA persist to insert into hsqldb
3) add the weld-pastecode-ds.xml to server/default/deploy in JBoss 6.0.0.M2
4) setup for JRebel 3 via the javarebel-maven-plugin in ejb module POM:
<build>
<finalName>weld-translator</finalName>
<plugins>
<plugin>
<groupId>org.zeroturnaround</groupId>
<artifactId>javarebel-maven-plugin</artifactId>
<version>1.0.5</version>
<executions>
<execution>
<id>generate-rebel-xml</id>
<phase>process-resources</phase>
<goals>
<goal>generate</goal>
</goals>
</execution>
</executions>
</plugin>
</plugins>
</build>
The above plugin generates the rebel.xml file which is used by JRebel to
know which directories/files to monitor for hot redeploy when the bytecode
is modified (new .class files generated on local fileserver). You need one
rebel.xml for each JAR and WAR that you want to hot redeploy enable. In
this case there's only one for the ejb JAR.
I added the 2nd commandButton to test the adding/deleting of local interface
session bean methods (foo2) which is working ok thus far via JRebel 3 hot
reload. Follow the tutorial I wrote here:
http://community.jboss.org/wiki/JRebel3withSeam2xtutorial
VM args: -Drebel.log=true -noverify -javaagent:/opt/jrebel/jrebel/jrebel.jar
-Drebel.jboss_plugin=true -Drebel.allow_bytecode_proxy=true -Drebel.log=true
-Dprogram.name="JBossTools: JBoss 6.0 Runtime" -Xms256m -Xmx768m
-XX:MaxPermSize=256m -Djava.net.preferIPv4Stack=true
-Dsun.rmi.dgc.client.gcInterval=3600000
-Dsun.rmi.dgc.server.gcInterval=3600000
-Djava.endorsed.dirs="/opt/jboss/jboss-6.0.0.20100216-M2/lib/endorsed"
use nightly version of JRebel:
http://www.zeroturnaround.com/jrebel/next-releases/
Enjoy.
16 years
Custom bean implementations
by Stuart Douglas
Unless I am missing something it does not seem to be possible for a custom dependant scoped Bean implementation to get information about it's injection point.
If this is the case, is this something that could be addressed in the maintenance release?
Stuart
16 years
Re: [weld-dev] Maven Archetype Bill of Materials - How should we handle minor variations in point releases of Java EE 6 containers?
by Shelly McGowan
Pete,
This morning I released the jboss-javaee_6.0_spec, 1.0.0.Beta3.
http://repository.jboss.org/maven2/org/jboss/spec/jboss-javaee_6.0_spec/1...
This release contains fix for JBEE-33 - update to use JACC 1.4.
Shelly McGowan
JBoss, by Red Hat
----- Original Message -----
From: "Pete Muir" <pmuir(a)redhat.com>
To: "Steven Boscarine" <steven.boscarine(a)childrens.harvard.edu>
Cc: "Weld-Dev List" <weld-dev(a)lists.jboss.org>, smcgowan(a)redhat.com
Sent: Tuesday, April 13, 2010 8:00:35 AM GMT -05:00 US/Canada Eastern
Subject: Re: [weld-dev] Maven Archetype Bill of Materials - How should we handle minor variations in point releases of Java EE 6 containers?
Shelly has pointed us at http://repository.jboss.org/maven2//org/jboss/spec/jboss-javaee_6.0_spec/... which works great as a jboss-6.0.0-bom. Unfortunately, Sun control the javax namespace, and don't publish a BOM for Java EE, so producing one of these is much harder.
I suggest we stick with the JBoss one for now, along with instructions on how to create one for other app servers.
WDYT?
On 12 Apr 2010, at 16:47, Steven Boscarine wrote:
> Hello All,
> The Weld archetypes need to be updated to reflect the latest Weld 1.0.1
> release.
>
> Presently, we're using the weld-extensions-bom
>
> <dependency>
> <groupId>org.jboss.weld</groupId>
> <artifactId>weld-extensions-bom</artifactId>
> <version>1.0.0-CR2</version>
> <type>pom</type>
> <scope>import</scope>
> </dependency>
>
> The immediate issue is that the archetypes need to reflect the changes.
>
> The hairier issue is dealing with minor point release differences
>
> Now there's 2 variants of weld in the wild, via 2 Java EE containers.
> Glassfish has weld-1.0.0 and JBoss 6 will have 1.0.1. Should this be
> reflected via different BOMs?
>
> Should there be a weld-jboss-6.0.0-bom? glassfish-v3-bom? Presumably,
> down the road, there will be more variants as other APIs have minor
> point increases.
>
> If not, does anyone have suggestions for dealing with trivial variations
> in versions between container point releases?
>
> Thanks,
> Steven
> _______________________________________________
> weld-dev mailing list
> weld-dev(a)lists.jboss.org
> https://lists.jboss.org/mailman/listinfo/weld-dev
16 years
Move weld-wicket to seam-wicket?
by Pete Muir
Hi all,
Since we've started developing Seam 3, I've started to think that the Wicket support is a better fit for Seam rather than Weld. Most of the Weld sub projects handle integrating Weld into other environments (such as Java SE) or provide support for using Weld (e.g. Weld extensions, archetypes).
There wasn't a consensus in our meeting yesterday, so I wanted to open it up for discussion.
Pete
16 years
Spec clarification needed
by Pete Muir
Given these beans and decorators (enabled)
interface Animal {
String hello();
}
class Cat implements Animal {
@Inject private InjectionPoint injectionPoint;
public String hello() {
return "hello";
}
public InjectionPoint getInjectionPoint() {
return injectionPoint;
}
}
@Decorator
class AnimalDecorator implements Animal {
@Inject @Delegate
private Animal bean;
public String hello() {
return bean.hello() + " world!";
}
}
class Cattery {
@Inject Cat cat;
Cat getCat() {
return cat;
}
}
Should
cattery.getCat().getInjectionPoint().isDelegate() return true or false?
I believe it should return true, as Cat is being decorated, and hence injected into the decorator delegate injection point.
Ref is https://jira.jboss.org/jira/browse/CDITCK-138
16 years
TCK 1.0.2.CR1
by Pete Muir
All
I will be releasing this next week. This release comes earlier than planned as a number of issues have been filed since 1.0.1 Final that would be good to get into a release.
Jozef/Marius/David/Others - if you have a few minutes spare, it would be great if you can pick up and resolve an issue or two that is open - all of them should have been marked as confirmed issues by me, and if the fix is non-obvious, I tried to note what the fix should be. Anything left on (probably) Tuesday I will get done.
Thanks!
16 years
Weld reference guide translations
by Pete Muir
Hi all,
I've been reviewing our translations for Weld - and I'm looking for your help in bringing the translations up to date :-)
it-IT: 63% untranslated, 29% fuzzy, 6% translated
zh-CN: 70% untranslated, 24% fuzzy, 5% translated
zh-TW: 72% untranslated, 23% fuzzy, 5% translated
es-ES: 72% untranslated, 23% fuzzy, 5% translated
ko-KR: 72% untranslated, 23% fuzzy, 5% translated
de-DE: 71% untranslated, 24% fuzzy, 5% translated
pt-BR: 47% untranslated, 18% fuzzy, 35% translated
For our existing translators, I've updated the notes on how to translate the Weld docs - http://www.seamframework.org/Weld/TranslatingWeldIntoYourOwnLanguage.
If you are lurking and interested in translating, then please get in contact!
Pete
16 years
