Weld SVN: r6696 - archetypes/javaee6-webapp/trunk/src/main/webapp/WEB-INF.
by weld-commits＠lists.jboss.org
Author: dan.j.allen
Date: 2010-07-17 13:00:56 -0400 (Sat, 17 Jul 2010)
New Revision: 6696
Modified:
archetypes/javaee6-webapp/trunk/src/main/webapp/WEB-INF/web.xml
Log:
update comment
Modified: archetypes/javaee6-webapp/trunk/src/main/webapp/WEB-INF/web.xml
===================================================================
--- archetypes/javaee6-webapp/trunk/src/main/webapp/WEB-INF/web.xml 2010-07-17 16:58:10 UTC (rev 6695)
+++ archetypes/javaee6-webapp/trunk/src/main/webapp/WEB-INF/web.xml 2010-07-17 17:00:56 UTC (rev 6696)
@@ -5,7 +5,7 @@
http://java.sun.com/xml/ns/javaee/web-app_3_0.xsd">
<!-- This is an optional parameter, but it makes troubleshooting errors much easier -->
- <!-- You should delete it before final deployment -->
+ <!-- You should delete it before final deployment! -->
<context-param>
<param-name>javax.faces.PROJECT_STAGE</param-name>
<param-value>Development</param-value>
@@ -24,8 +24,10 @@
<url-pattern>*.jsf</url-pattern>
</servlet-mapping>
- <!-- This section is option. -->
+ <!-- This section is optional. We are allowing index.jsf to handle the root URL (i.e., /). -->
<welcome-file-list>
+ <welcome-file>index.jsp</welcome-file>
+ <welcome-file>index.html</welcome-file>
<welcome-file>index.jsf</welcome-file>
</welcome-file-list>
</web-app>
14 years, 3 months
Weld SVN: r6695 - archetypes/javaee6-webapp/trunk/src/test/java/com/mycompany.
by weld-commits＠lists.jboss.org
Author: dan.j.allen
Date: 2010-07-17 12:58:10 -0400 (Sat, 17 Jul 2010)
New Revision: 6695
Modified:
archetypes/javaee6-webapp/trunk/src/test/java/com/mycompany/MemberRegistrationTest.java
Log:
use jdk14 logging bridge instead
Modified: archetypes/javaee6-webapp/trunk/src/test/java/com/mycompany/MemberRegistrationTest.java
===================================================================
--- archetypes/javaee6-webapp/trunk/src/test/java/com/mycompany/MemberRegistrationTest.java 2010-07-17 16:56:12 UTC (rev 6694)
+++ archetypes/javaee6-webapp/trunk/src/test/java/com/mycompany/MemberRegistrationTest.java 2010-07-17 16:58:10 UTC (rev 6695)
@@ -24,7 +24,7 @@
.addClasses(Member.class, MemberRegistration.class, MemberRepository.class, MemberRepositoryProducer.class)
.addLibraries(
MavenArtifactResolver.resolve("org.slf4j:slf4j-api:1.5.10"),
- MavenArtifactResolver.resolve("org.slf4j:slf4j-simple:1.5.10")
+ MavenArtifactResolver.resolve("org.slf4j:slf4j-jdk14:1.5.10")
)
.addWebResource("test-persistence.xml", "classes/META-INF/persistence.xml")
.addWebResource(new ByteArrayAsset(new byte[0]), "beans.xml");
14 years, 3 months
Weld SVN: r6694 - in archetypes/javaee6-webapp/trunk/src/test: resources and 1 other directory.
by weld-commits＠lists.jboss.org
Author: dan.j.allen
Date: 2010-07-17 12:56:12 -0400 (Sat, 17 Jul 2010)
New Revision: 6694
Added:
archetypes/javaee6-webapp/trunk/src/test/java/com/mycompany/MavenArtifactResolver.java
Modified:
archetypes/javaee6-webapp/trunk/src/test/java/com/mycompany/MemberRegistrationTest.java
archetypes/javaee6-webapp/trunk/src/test/resources/arquillian.xml
Log:
fix Arquillian test in JBoss AS
Added: archetypes/javaee6-webapp/trunk/src/test/java/com/mycompany/MavenArtifactResolver.java
===================================================================
--- archetypes/javaee6-webapp/trunk/src/test/java/com/mycompany/MavenArtifactResolver.java (rev 0)
+++ archetypes/javaee6-webapp/trunk/src/test/java/com/mycompany/MavenArtifactResolver.java 2010-07-17 16:56:12 UTC (rev 6694)
@@ -0,0 +1,47 @@
+package com.mycompany;
+
+import java.io.File;
+
+/**
+ * A temporary resolver that converts a Maven artifact reference
+ * into a {@link java.io.File} object.
+ *
+ * <p>This approach is an interim solution for Maven projects
+ * until the open feature request to add formally add artifacts
+ * to a test (ARQ-66) is implementated.</p>
+ *
+ * <p>The testCompile goal will resolve any test dependencies and
+ * put them in your local Maven repository. By the time the test
+ * executes, you can be sure that the JAR files you need will be
+ * in your local repository.</p>
+ *
+ * <p>Example usage:</p>
+ *
+ * <pre>
+ * WebArchive war = ShrinkWrap.create("test.war", WebArchive.class)
+ * .addLibrary(MavenArtifactResolver.resolve("commons-lang:commons-lang:2.5"));
+ * </pre>
+ *
+ * @author Dan Allen
+ */
+public class MavenArtifactResolver
+{
+ private static final String LOCAL_MAVEN_REPO =
+ System.getProperty("user.home") + File.separatorChar +
+ ".m2" + File.separatorChar + "repository";
+
+ public static File resolve(String groupId, String artifactId, String version)
+ {
+ return new File(LOCAL_MAVEN_REPO + File.separatorChar +
+ groupId.replace(".", File.separator) + File.separatorChar +
+ artifactId + File.separatorChar +
+ version + File.separatorChar +
+ artifactId + "-" + version + ".jar");
+ }
+
+ public static File resolve(String qualifiedArtifactId)
+ {
+ String[] segments = qualifiedArtifactId.split(":");
+ return resolve(segments[0], segments[1], segments[2]);
+ }
+}
Modified: archetypes/javaee6-webapp/trunk/src/test/java/com/mycompany/MemberRegistrationTest.java
===================================================================
--- archetypes/javaee6-webapp/trunk/src/test/java/com/mycompany/MemberRegistrationTest.java 2010-07-17 16:52:44 UTC (rev 6693)
+++ archetypes/javaee6-webapp/trunk/src/test/java/com/mycompany/MemberRegistrationTest.java 2010-07-17 16:56:12 UTC (rev 6694)
@@ -22,7 +22,10 @@
public static Archive<?> createTestArchive() {
return ShrinkWrap.create(WebArchive.class, "test.war")
.addClasses(Member.class, MemberRegistration.class, MemberRepository.class, MemberRepositoryProducer.class)
- .addPackage(Logger.class.getPackage())
+ .addLibraries(
+ MavenArtifactResolver.resolve("org.slf4j:slf4j-api:1.5.10"),
+ MavenArtifactResolver.resolve("org.slf4j:slf4j-simple:1.5.10")
+ )
.addWebResource("test-persistence.xml", "classes/META-INF/persistence.xml")
.addWebResource(new ByteArrayAsset(new byte[0]), "beans.xml");
}
Modified: archetypes/javaee6-webapp/trunk/src/test/resources/arquillian.xml
===================================================================
--- archetypes/javaee6-webapp/trunk/src/test/resources/arquillian.xml 2010-07-17 16:52:44 UTC (rev 6693)
+++ archetypes/javaee6-webapp/trunk/src/test/resources/arquillian.xml 2010-07-17 16:56:12 UTC (rev 6694)
@@ -1,18 +1,25 @@
<?xml version="1.0" encoding="UTF-8"?>
<arquillian xmlns="http://jboss.com/arquillian"
xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance"
+ xmlns:jbossas-remote="urn:arq:org.jboss.arquillian.container.jbossas.remote_6"
xmlns:glassfish-embedded="urn:arq:org.jboss.arquillian.container.glassfish.embedded_3">
<!-- Uncomment to have test archives exported to the file system for inspection -->
<!--
<engine>
- <deploymentExportPath>/tmp/</deploymentExportPath>
+ <deploymentExportPath>target/</deploymentExportPath>
</engine>
-->
+ <!-- Required configuration for an embedded GlassFish instance -->
<glassfish-embedded:container>
<glassfish-embedded:bindHttpPort>7070</glassfish-embedded:bindHttpPort>
<glassfish-embedded:sunResourcesXml>src/test/resources-glassfish-embedded/sun-resources.xml</glassfish-embedded:sunResourcesXml>
- </glassfish-embedded:container>
+ </glassfish-embedded:container>
+ <!-- Example configuration for a remote JBoss AS instance -->
+ <jbossas-remote:container>
+ <jbossas-remote:remoteServerHttpPort>8080</jbossas-remote:remoteServerHttpPort>
+ </jbossas-remote:container>
+
</arquillian>
14 years, 3 months
Weld SVN: r6693 - doc/trunk/reference/src/main/docbook/it-IT.
by weld-commits＠lists.jboss.org
Author: nico.ben
Date: 2010-07-17 12:52:44 -0400 (Sat, 17 Jul 2010)
New Revision: 6693
Modified:
doc/trunk/reference/src/main/docbook/it-IT/decorators.po
Log:
Italian translation
Modified: doc/trunk/reference/src/main/docbook/it-IT/decorators.po
===================================================================
--- doc/trunk/reference/src/main/docbook/it-IT/decorators.po 2010-07-17 16:12:56 UTC (rev 6692)
+++ doc/trunk/reference/src/main/docbook/it-IT/decorators.po 2010-07-17 16:52:44 UTC (rev 6693)
@@ -6,7 +6,7 @@
"Project-Id-Version: master.xml\n"
"Report-Msgid-Bugs-To: http://bugs.kde.org\n"
"POT-Creation-Date: 2010-05-01T13:53:42\n"
-"PO-Revision-Date: 2009-11-23 21:13+0100\n"
+"PO-Revision-Date: 2010-07-17 18:52+0100\n"
"Last-Translator: Nicola Benaglia <nico.benaz(a)gmail.com>\n"
"Language-Team: none\n"
"MIME-Version: 1.0\n"
@@ -20,47 +20,14 @@
#. Tag: para
#, fuzzy, no-c-format
-msgid ""
-"Interceptors are a powerful way to capture and separate concerns which are "
-"<emphasis>orthogonal</emphasis> to the application (and type system). Any "
-"interceptor is able to intercept invocations of any Java type. This makes "
-"them perfect for solving technical concerns such as transaction management, "
-"security and call logging. However, by nature, interceptors are unaware of "
-"the actual semantics of the events they intercept. Thus, interceptors "
-"aren't an appropriate tool for separating business-related concerns."
-msgstr ""
-"Gli interceptor sono un potente modo per catturare e separare i concern (N.d."
-"T. un concern è un particolare concetto o area di interesse) che sono "
-"<emphasis>ortogonali</emphasis> al sistema tipo. Qualsiasi interceptor è "
-"capace di intercettare le invocazioni di qualsiasi tipo Java. Questo li "
-"rende perfetti per risolvere concern tecnici quali gestione delle "
-"transazioni e la sicurezza. Comunque, per natura, gli interceptor non sono "
-"consapevoli dell'attuale semantica degli eventi che intercettano. Quindi gli "
-"interceptor non sono il giusto strumento per separare i concern di tipo "
-"business."
+msgid "Interceptors are a powerful way to capture and separate concerns which are <emphasis>orthogonal</emphasis> to the application (and type system). Any interceptor is able to intercept invocations of any Java type. This makes them perfect for solving technical concerns such as transaction management, security and call logging. However, by nature, interceptors are unaware of the actual semantics of the events they intercept. Thus, interceptors aren't an appropriate tool for separating business-related concerns."
+msgstr "Gli interceptor sono un potente modo per catturare e separare i concern (N.d.T. un concern è un particolare concetto o area di interesse) che sono <emphasis>ortogonali</emphasis> al sistema tipo. Qualsiasi interceptor è capace di intercettare le invocazioni di qualsiasi tipo Java. Questo li rende perfetti per risolvere concern tecnici quali gestione delle transazioni e la sicurezza. Comunque, per natura, gli interceptor non sono consapevoli dell'attuale semantica degli eventi che intercettano. Quindi gli interceptor non sono il giusto strumento per separare i concern di tipo business."
# ...concerns that cut across many disparate types = ?
#. Tag: para
#, fuzzy, no-c-format
-msgid ""
-"The reverse is true of <emphasis>decorators</emphasis>. A decorator "
-"intercepts invocations only for a certain Java interface, and is therefore "
-"aware of all the semantics attached to that interface. Since decorators "
-"directly implement operations with business semantics, it makes them the "
-"perfect tool for modeling some kinds of business concerns. It also means "
-"that a decorator doesn't have the generality of an interceptor. "
-"Decorators aren't able to solve technical concerns that cut across many "
-"disparate types. Interceptors and decorators, though similar in many ways, "
-"are complementary. Let's look at some cases where decorators fit the "
-"bill."
-msgstr ""
-"Il contrario è vero per i <emphasis>decoratori</emphasis>. Un decoratore "
-"intercetta le invocazioni solamente per una certa interfaccia Java, e quindi "
-"è consapevole della semantica legata a questa. Ciò rende i decoratori uno "
-"strumento perfetto per modellare alcuni tipi di concern di business. E "
-"significa pure che un decoratore non ha la generalità di un interceptor. I "
-"decoratori non sono capaci di risolvere i concern tecnici che agiscono per "
-"diversi tipi."
+msgid "The reverse is true of <emphasis>decorators</emphasis>. A decorator intercepts invocations only for a certain Java interface, and is therefore aware of all the semantics attached to that interface. Since decorators directly implement operations with business semantics, it makes them the perfect tool for modeling some kinds of business concerns. It also means that a decorator doesn't have the generality of an interceptor. Decorators aren't able to solve technical concerns that cut across many disparate types. Interceptors and decorators, though similar in many ways, are complementary. Let's look at some cases where decorators fit the bill."
+msgstr "Il contrario è vero per i <emphasis>decoratori</emphasis>. Un decoratore intercetta le invocazioni solamente per una certa interfaccia Java, e quindi è consapevole della semantica legata a questa. Ciò rende i decoratori uno strumento perfetto per modellare alcuni tipi di concern di business. E significa pure che un decoratore non ha la generalità di un interceptor. I decoratori non sono capaci di risolvere i concern tecnici che agiscono per diversi tipi."
#. Tag: para
#, no-c-format
@@ -69,53 +36,28 @@
#. Tag: para
#, fuzzy, no-c-format
-msgid ""
-"Several different beans in our system implement the <literal>Account</"
-"literal> interface. However, we have a common legal requirement that; for "
-"any kind of account, large transactions must be recorded by the system in a "
-"special log. This is a perfect job for a decorator."
-msgstr ""
-"Parecchi Web Beans del nostro sistema implementano l'interfaccia "
-"<literal>Account</literal>. Abbiamo come comune requisito legale, per ogni "
-"tipo di account, che le transazioni lunghe vengano registrate dal sistema in "
-"uno speciale log. Questo è un lavoro perfetto per un decoratore."
+msgid "Several different beans in our system implement the <literal>Account</literal> interface. However, we have a common legal requirement that; for any kind of account, large transactions must be recorded by the system in a special log. This is a perfect job for a decorator."
+msgstr "Parecchi Web Beans del nostro sistema implementano l'interfaccia <literal>Account</literal>. Abbiamo come comune requisito legale, per ogni tipo di account, che le transazioni lunghe vengano registrate dal sistema in uno speciale log. Questo è un lavoro perfetto per un decoratore."
#. Tag: para
#, fuzzy, no-c-format
-msgid ""
-"A decorator is a bean (possibly even an abstract class) that implements the "
-"type it decorates and is annotated <literal>@Decorator</literal>."
-msgstr ""
-"Un decorator è un semplice Web Beans che implementa il tipo che decora ed è "
-"annotato con <literal>@Decorator</literal>.\""
+msgid "A decorator is a bean (possibly even an abstract class) that implements the type it decorates and is annotated <literal>@Decorator</literal>."
+msgstr "Un decorator è un semplice Web Beans che implementa il tipo che decora ed è annotato con <literal>@Decorator</literal>.\""
#. Tag: para
#, no-c-format
-msgid ""
-"The decorator implements the methods of the decorated type that it wants to "
-"intercept."
+msgid "The decorator implements the methods of the decorated type that it wants to intercept."
msgstr ""
#. Tag: para
#, fuzzy, no-c-format
-msgid ""
-"Unlike other beans, a decorator may be an abstract class. Therefore, if "
-"there's nothing special the decorator needs to do for a particular "
-"method of the decorated interface, you don't need to implement that "
-"method."
-msgstr ""
-"Diversamente dai semplici Web Beans, un decoratore può essere una classe "
-"astratta. Se un decoratore non ha niente da fare per un particolare metodo, "
-"allora non occorre implementare quel metodo."
+msgid "Unlike other beans, a decorator may be an abstract class. Therefore, if there's nothing special the decorator needs to do for a particular method of the decorated interface, you don't need to implement that method."
+msgstr "Diversamente dai semplici Web Beans, un decoratore può essere una classe astratta. Se un decoratore non ha niente da fare per un particolare metodo, allora non occorre implementare quel metodo."
#. Tag: para
#, fuzzy, no-c-format
-msgid ""
-"Interceptors for a method are called before decorators that apply to the "
-"method."
-msgstr ""
-"Gli interceptor per un metodo sono chiamati prima dei decoratori che vengono "
-"applicati a tali metodo."
+msgid "Interceptors for a method are called before decorators that apply to the method."
+msgstr "Gli interceptor per un metodo sono chiamati prima dei decoratori che vengono applicati a tali metodo."
#. Tag: title
#, no-c-format
@@ -124,61 +66,40 @@
#. Tag: para
#, no-c-format
-msgid ""
-"Decorators have a special injection point, called the <emphasis>delegate "
-"injection point</emphasis>, with the same type as the beans they decorate, "
-"and the annotation <literal>@Delegate</literal>. There must be exactly one "
-"delegate injection point, which can be a constructor parameter, initializer "
-"method parameter or injected field."
+msgid "Decorators have a special injection point, called the <emphasis>delegate injection point</emphasis>, with the same type as the beans they decorate, and the annotation <literal>@Delegate</literal>. There must be exactly one delegate injection point, which can be a constructor parameter, initializer method parameter or injected field."
msgstr ""
#. Tag: para
-#, fuzzy, no-c-format
+#, no-c-format
msgid "A decorator is bound to any bean which:"
-msgstr "Un decorator è legato ad un qualsiasi Web Bean che:"
+msgstr "Un decorator è legato ad un qualsiasi bean che:"
#. Tag: para
-#, fuzzy, no-c-format
+#, no-c-format
msgid "has the type of the delegate injection point as a bean type, and"
-msgstr "ha il tipo di attributo delegate come un tipo API, e"
+msgstr "ha il tipo di punto injection delegate come un tipo bean, e"
#. Tag: para
-#, fuzzy, no-c-format
+#, no-c-format
msgid "has all qualifiers that are declared at the delegate injection point."
-msgstr ""
-"ha tutti i tipi di binding che sono dichiarati dall'attributo delegate."
+msgstr "ha tutti i qualificatori che sono dichiarati nel punto injection delegate."
#. Tag: para
-#, fuzzy, no-c-format
-msgid ""
-"This delegate injection point specifies that the decorator is bound to all "
-"beans that implement <literal>Account</literal>:"
-msgstr ""
-"Quest'attributo delegate specifica che ildecorator è legao a tutti i Web "
-"Beans che implementano <literal>Account</literal>:"
+#, no-c-format
+msgid "This delegate injection point specifies that the decorator is bound to all beans that implement <literal>Account</literal>:"
+msgstr "Questo punto di injection delegate specifica che il decoratore è legato a tutti i beans che implementano <literal>Account</literal>:"
# E' corretto tradurre BOUND con LEGATO in questo particolare contesto?
# ....rivedere alcune frasi sopra.
#. Tag: para
-#, fuzzy, no-c-format
-msgid ""
-"A delegate injection point may specify any number of qualifier annotations. "
-"The decorator will only be bound to beans with the same qualifiers."
-msgstr ""
-"Un attributo delegato può specificare un'annotazione di binding. E quindi il "
-"decoratore verrà associato a Web Beans con lo stesso binding."
+#, no-c-format
+msgid "A delegate injection point may specify any number of qualifier annotations. The decorator will only be bound to beans with the same qualifiers."
+msgstr "Un punto di injection delegate può specificare un qualsiasi numero di annotazioni qualifier. Il decoratore verrà associato ai bean con gli stessi qualificatori."
#. Tag: para
-#, fuzzy, no-c-format
-msgid ""
-"The decorator may invoke the delegate object, which has much the same effect "
-"as calling <literal>InvocationContext.proceed()</literal> from an "
-"interceptor. The main difference is that the decorator can invoke "
-"<emphasis>any</emphasis> business method on the delegate object."
-msgstr ""
-"Il decoratore può invocare l'attributo delegate, il ché ha lo stesso effetto "
-"come chiamare <literal>InvocationContext.proceed()</literal> da un "
-"interceptor."
+#, no-c-format
+msgid "The decorator may invoke the delegate object, which has much the same effect as calling <literal>InvocationContext.proceed()</literal> from an interceptor. The main difference is that the decorator can invoke <emphasis>any</emphasis> business method on the delegate object."
+msgstr "Il decoratore può invocare l'oggetto delegate, il ché ha lo stesso effetto come chiamare <literal>InvocationContext.proceed()</literal> da un interceptor. La principale differenza è che il decoratore può invocare <emphasis>qualsiasi</emphasis> metodo di business sull'oggetto delegate."
#. Tag: title
#, no-c-format
@@ -187,39 +108,24 @@
#. Tag: para
#, no-c-format
-msgid ""
-"By default, all decorators are disabled. We need to <emphasis>enable</"
-"emphasis> our decorator in the <literal>beans.xml</literal> descriptor of a "
-"bean archive. This activation only applies to the beans in that archive."
+msgid "By default, all decorators are disabled. We need to <emphasis>enable</emphasis> our decorator in the <literal>beans.xml</literal> descriptor of a bean archive. This activation only applies to the beans in that archive."
msgstr ""
# Rivedere la frase?
#. Tag: para
-#, fuzzy, no-c-format
-msgid ""
-"This declaration serves the same purpose for decorators that the "
-"<literal><interceptors></literal> declaration serves for "
-"interceptors:"
-msgstr ""
-"Per i decoratori questa dichiarazione provvede alle stesse finalità di "
-"quanto la dichiarazione <literal><Interceptors></literal> fa per gli "
-"interceptor."
+#, no-c-format
+msgid "This declaration serves the same purpose for decorators that the <literal><interceptors></literal> declaration serves for interceptors:"
+msgstr "Questa dichiarazione provvede per i decoratori alle stesse finalità di quanto la dichiarazione <literal><interceptors></literal> fa per gli interceptor."
#. Tag: para
#, no-c-format
-msgid ""
-"it enables us to specify a total ordering for all decorators in our system, "
-"ensuring deterministic behavior, and"
-msgstr ""
-"Consente di specificare un ordinamento totale per tutti i decoratori del "
-"sistema, assicurando un comportamento deterministico, e"
+msgid "it enables us to specify a total ordering for all decorators in our system, ensuring deterministic behavior, and"
+msgstr "Consente di specificare un ordinamento totale per tutti i decoratori del sistema, assicurando un comportamento deterministico, e"
#. Tag: para
#, no-c-format
msgid "it lets us enable or disable decorator classes at deployment time."
-msgstr ""
-"consente di abilitare o disabilitare le classi decorato durante la fase di "
-"deploy."
+msgstr "consente di abilitare o disabilitare le classi decorato durante la fase di deploy."
#~ msgid ""
#~ "<![CDATA[public interface Account {\n"
@@ -235,7 +141,6 @@
#~ " public void withdraw(BigDecimal amount);\n"
#~ " public void deposit(BigDecimal amount);\n"
#~ "}]]>"
-
#~ msgid ""
#~ "<![CDATA[@Decorator\n"
#~ "public abstract class LargeTransactionDecorator\n"
@@ -248,7 +153,6 @@
#~ " implements Account {\n"
#~ " ...\n"
#~ "}]]>"
-
#~ msgid ""
#~ "<![CDATA[@Decorator\n"
#~ "public abstract class LargeTransactionDecorator\n"
@@ -281,7 +185,6 @@
#~ " ...\n"
#~ " }\n"
#~ "}]]>"
-
#~ msgid ""
#~ "<![CDATA[@Decorator\n"
#~ "public abstract class LargeTransactionDecorator\n"
@@ -296,13 +199,10 @@
#~ " @Inject @Delegate @Any Account account;\n"
#~ " ...\n"
#~ "}]]>"
-
#~ msgid "<![CDATA[@Inject @Delegate @Any Account account;]]>"
#~ msgstr "<![CDATA[@Inject @Delegate @Any Account account;]]>"
-
#~ msgid "<![CDATA[@Inject @Delegate @Foreign Account account;]]>"
#~ msgstr "<![CDATA[@Inject @Delegate @Foreign Account account;]]>"
-
#~ msgid ""
#~ "<![CDATA[@Decorator\n"
#~ "public abstract class LargeTransactionDecorator\n"
@@ -347,7 +247,6 @@
#~ " }\n"
#~ " }\n"
#~ "}]]>"
-
#~ msgid ""
#~ "<![CDATA[<beans\n"
#~ " xmlns=\"http://java.sun.com/xml/ns/javaee\"\n"
@@ -370,7 +269,6 @@
#~ " <class>org.mycompany.myapp.LargeTransactionDecorator</class>\n"
#~ " </decorators>\n"
#~ "</beans>]]>"
-
#~ msgid ""
#~ "All decorators have a <emphasis>delegate attribute</emphasis>. The type "
#~ "and binding types of the delegate attribute determine which Web Beans the "
@@ -381,10 +279,10 @@
#~ "tipo ed i tipi di binding dell'attributo delegato determinano a quali Web "
#~ "Beans è legato il decoratore. Il tipo di attributo delegato deve "
#~ "implementare o estendere tutte le interfacce implementate dal decoratore."
-
#~ msgid ""
#~ "We need to <emphasis>enable</emphasis> our decorator in <literal>web-"
#~ "beans.xml</literal>."
#~ msgstr ""
#~ "Occorre <emphasis>abilitare</emphasis> il decoratore in <literal>web-"
#~ "beans.xml</literal>."
+
14 years, 3 months
Weld SVN: r6692 - archetypes/javaee6-webapp/trunk.
by weld-commits＠lists.jboss.org
Author: sboscarine
Date: 2010-07-17 12:12:56 -0400 (Sat, 17 Jul 2010)
New Revision: 6692
Modified:
archetypes/javaee6-webapp/trunk/pom.xml
Log:
fix merge error?
Modified: archetypes/javaee6-webapp/trunk/pom.xml
===================================================================
--- archetypes/javaee6-webapp/trunk/pom.xml 2010-07-17 16:12:18 UTC (rev 6691)
+++ archetypes/javaee6-webapp/trunk/pom.xml 2010-07-17 16:12:56 UTC (rev 6692)
@@ -226,7 +226,6 @@
<fileName>${project.build.directory}/${project.build.finalName}.war</fileName>
<!-- JNDI Datasource that connects to in-memory HSQLDB to demonstrate JPA -->
<fileName>src/main/resources-jbossas/default-ds.xml</fileName>
- <fileName>${project.build.directory}/${project.build.finalName}.war</fileName>
</fileNames>
</configuration>
</plugin>
14 years, 3 months
Weld SVN: r6691 - archetypes/javaee6-webapp/trunk/src/test/resources.
by weld-commits＠lists.jboss.org
Author: dan.j.allen
Date: 2010-07-17 12:12:18 -0400 (Sat, 17 Jul 2010)
New Revision: 6691
Modified:
archetypes/javaee6-webapp/trunk/src/test/resources/arquillian.xml
Log:
remove unused Arquillian configuration
Modified: archetypes/javaee6-webapp/trunk/src/test/resources/arquillian.xml
===================================================================
--- archetypes/javaee6-webapp/trunk/src/test/resources/arquillian.xml 2010-07-17 16:10:21 UTC (rev 6690)
+++ archetypes/javaee6-webapp/trunk/src/test/resources/arquillian.xml 2010-07-17 16:12:18 UTC (rev 6691)
@@ -1,9 +1,7 @@
<?xml version="1.0" encoding="UTF-8"?>
<arquillian xmlns="http://jboss.com/arquillian"
xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance"
- xmlns:jbasmanaged="urn:arq:org.jboss.arquillian.container.jbossas.managed_6"
- xmlns:gfembed="urn:arq:org.jboss.arquillian.container.glassfish.embedded_3"
- xmlns:gfremote="urn:arq:org.jboss.arquillian.container.glassfish.remote_3">
+ xmlns:glassfish-embedded="urn:arq:org.jboss.arquillian.container.glassfish.embedded_3">
<!-- Uncomment to have test archives exported to the file system for inspection -->
<!--
@@ -12,17 +10,9 @@
</engine>
-->
- <jbasmanaged:container>
- <jbasmanaged:jbossHome>/home/dallen/opt/jboss-as-tests</jbasmanaged:jbossHome>
- </jbasmanaged:container>
-
- <gfembed:container>
- <gfembed:bindHttpPort>7070</gfembed:bindHttpPort>
- <gfembed:sunResourcesXml>src/test/resources-glassfish-embedded/sun-resources.xml</gfembed:sunResourcesXml>
- </gfembed:container>
+ <glassfish-embedded:container>
+ <glassfish-embedded:bindHttpPort>7070</glassfish-embedded:bindHttpPort>
+ <glassfish-embedded:sunResourcesXml>src/test/resources-glassfish-embedded/sun-resources.xml</glassfish-embedded:sunResourcesXml>
+ </glassfish-embedded:container>
- <gfremote:container>
- <gfremote:remoteServerHttpPort>7070</gfremote:remoteServerHttpPort>
- </gfremote:container>
-
</arquillian>
14 years, 3 months
Weld SVN: r6690 - archetypes/javaee6-webapp/trunk/src/main/webapp/META-INF.
by weld-commits＠lists.jboss.org
Author: sboscarine
Date: 2010-07-17 12:10:21 -0400 (Sat, 17 Jul 2010)
New Revision: 6690
Modified:
archetypes/javaee6-webapp/trunk/src/main/webapp/META-INF/context.xml
Log:
Updated comments
Modified: archetypes/javaee6-webapp/trunk/src/main/webapp/META-INF/context.xml
===================================================================
--- archetypes/javaee6-webapp/trunk/src/main/webapp/META-INF/context.xml 2010-07-17 16:03:31 UTC (rev 6689)
+++ archetypes/javaee6-webapp/trunk/src/main/webapp/META-INF/context.xml 2010-07-17 16:10:21 UTC (rev 6690)
@@ -1,5 +1,6 @@
<?xml version="1.0" encoding="UTF-8"?>
<!-- This optional file is used by JBoss AS to get around an issue involving serialization of sessions between container restarts -->
+<!-- This file can be removed if you're using other containers, like Glassfish. -->
<Context>
<!-- disable storage of sessions across restarts by setting the pathname to an empty value -->
<Manager pathname=""/>
14 years, 3 months
Weld SVN: r6689 - archetypes/javaee6-webapp/trunk.
by weld-commits＠lists.jboss.org
Author: dan.j.allen
Date: 2010-07-17 12:03:31 -0400 (Sat, 17 Jul 2010)
New Revision: 6689
Modified:
archetypes/javaee6-webapp/trunk/readme.txt
Log:
update docs
Modified: archetypes/javaee6-webapp/trunk/readme.txt
===================================================================
--- archetypes/javaee6-webapp/trunk/readme.txt 2010-07-17 15:56:03 UTC (rev 6688)
+++ archetypes/javaee6-webapp/trunk/readme.txt 2010-07-17 16:03:31 UTC (rev 6689)
@@ -10,22 +10,25 @@
get your foot in the door developing with Java EE 6. This project is setup to
allow you to create a compliant Java EE 6 application using JSF 2.0, CDI 1.0,
EJB 3.1, JPA 2.0 and Bean Validation 1.0) that can run on a certified
- application server (Complete or Web Profile). It includes a persistence unit
- and some sample persistence and transaction code to help you get your feet wet
+ application server (Full or Web Profile). It includes a persistence unit and
+ some sample persistence and transaction code to help you get your feet wet
with database access in enterprise Java.
System requirements
===================
All you need to run this project is Java 5.0 (Java SDK 1.5) or greator and
- Maven 2.0.10 or greater. This application is setup to be run on a Java EE 6
- application server. We've tested it on GlassFish 3.0.1 and JBoss AS 6.0.0.M3.
+ Maven 2.0.10 or greater. However, we strongly recommend Java 6.0 and Maven 3.
+ This application is configured to be run on a Java EE 6 application server.
+ We've tested it on both GlassFish 3.0.1 and JBoss AS 6.0.0.M3.
- Please note that Maven 2 project needs to use the JBoss Nexus Maven repository
+ NOTE:
+ This project retrieves artifacts from the JBoss Community Maven repository
because there are certain Java EE API JARs that are not yet publised to the
- Maven Central Repository (see https://jira.jboss.org/jira/browse/WELD-222)
- The testing framework used by the project, Arquillian, is also only available
- in the JBoss repository.
+ Maven Central Repository (see https://jira.jboss.org/jira/browse/WELD-222).
+ The integration testing framework used by the project, Arquillian, is also
+ only available in the JBoss Community Maven repository. This repository is a
+ superset of Maven central.
Deploying the application
=========================
@@ -34,7 +37,7 @@
mvn package
- If you want To deploy the application on JBoss AS (standalone), make sure that
+ If you want to deploy the application on JBoss AS (standalone), make sure that
your JBOSS_HOME environment variable points to a JBoss AS 6.0 installation.
Alternatively, you can set the location of JBoss AS using the following
@@ -68,10 +71,12 @@
This will deploy two artifacts, target/jboss-javaee6-webapp-src.war and
default-ds.xml.
+ IMPORTANT:
+ Don't forget to deploy default-ds.xml!
+
NOTE:
- If you deploy the WAR manually, don't forget to also deploy default-ds.xml!
- The default-ds.xml file installs a data source named jdbc/__default, so both
- JBoss AS and GlassFish have a data source with the same name.
+ The default-ds.xml file installs a data source named jdbc/__default, so that
+ both JBoss AS and GlassFish have a data source with the same name.
You can also set jboss.home on the commandline:
@@ -105,11 +110,14 @@
./asadmin start-database
./asadmin start-domain domain1
+ IMPORTANT:
+ Don't forget to start the JavaDB database!
+
NOTE:
- NetBeans starts the Derby database automatically when it starts up GlassFish.
- If you have the GlassFish Tools Eclipse plug-in, you have to enable this
- feature. Select Window > Preferences > GlassFish Server Preferences and check
- "Start JavaDB database process when Starting GlassFish Server"
+ NetBeans starts the database automatically when it starts up GlassFish. If you
+ have the GlassFish Tools Eclipse plug-in, you have to enable this feature.
+ Select Window > Preferences > GlassFish Server Preferences and check the
+ option "Start JavaDB database process when > Starting GlassFish Server"
Now you can either deploy the target/jboss-javaee6-webapp-src.war through the
web-based GlassFish admininstration console, or you can again use asadmin:
@@ -118,7 +126,7 @@
To undeploy the application, run:
- ./asadmin undeploy jboss-javaee6-webapp-src
+ ./asadmin undeploy jboss-javaee6-webapp-src
Running the Arquillian tests
============================
@@ -143,7 +151,7 @@
Consult the Arquillian reference documentation to register profiles for any
supported container.
- http://docs.jboss.org/arquillian/reference/latest/en-US/html/containers.h...
+ http://docs.jboss.org/arquillian/reference/latest/en-US/html/containers.h...
Importing the project into an IDE
=================================
@@ -180,7 +188,7 @@
You can verify your configuration by referring to the Hibernate JPA documentation.
- http://docs.jboss.org/hibernate/stable/jpamodelgen/reference/en-US/html_s...
+ http://docs.jboss.org/hibernate/stable/jpamodelgen/reference/en-US/html_s...
Once the project is imported into the IDE, you can execute the Maven commands
through the IDE controls to deploy the application to a container.
14 years, 3 months
Weld SVN: r6688 - archetypes/javaee6-webapp/trunk.
by weld-commits＠lists.jboss.org
Author: dan.j.allen
Date: 2010-07-17 11:56:03 -0400 (Sat, 17 Jul 2010)
New Revision: 6688
Modified:
archetypes/javaee6-webapp/trunk/readme.txt
Log:
note about Eclipse GlassFish Tools Bundle
Modified: archetypes/javaee6-webapp/trunk/readme.txt
===================================================================
--- archetypes/javaee6-webapp/trunk/readme.txt 2010-07-17 15:45:05 UTC (rev 6687)
+++ archetypes/javaee6-webapp/trunk/readme.txt 2010-07-17 15:56:03 UTC (rev 6688)
@@ -106,7 +106,10 @@
./asadmin start-domain domain1
NOTE:
- NetBeans will start the Derby database automatically when it starts GlassFish.
+ NetBeans starts the Derby database automatically when it starts up GlassFish.
+ If you have the GlassFish Tools Eclipse plug-in, you have to enable this
+ feature. Select Window > Preferences > GlassFish Server Preferences and check
+ "Start JavaDB database process when Starting GlassFish Server"
Now you can either deploy the target/jboss-javaee6-webapp-src.war through the
web-based GlassFish admininstration console, or you can again use asadmin:
@@ -150,7 +153,7 @@
already have an IDE project.
If you created the project from the commandline using archetype:generate, then
- you need to bring the project into your IDE. If you are using NetBeans 6.8 or
+ you need to import the project into your IDE. If you are using NetBeans 6.8 or
IntelliJ IDEA 9, then all you have to do is open the project as an existing
project. Both of these IDEs recognize Maven 2 projects natively.
@@ -160,6 +163,9 @@
m2eclipse plugin and required dependencies. Once that's installed, you'll be
ready to import the project into Eclipse.
+ NOTE:
+ We strongly recommend Eclipse Helios (3.6) - http://www.eclipse.org/helios
+
Select File > Import... and select "Existing Maven Projects" and navigate to
your project directory. Click Finish and m2eclipse will take it from there.
@@ -179,6 +185,10 @@
Once the project is imported into the IDE, you can execute the Maven commands
through the IDE controls to deploy the application to a container.
+ To deploy to GlassFish from Eclipse, you'll need the GlassFish Tools Bundle,
+ available at the update site http://download.java.net/glassfish/eclipse/helios
+ or from the Help > Eclipse Marketplace...
+
Downloading the sources and Javadocs
====================================
14 years, 3 months
Weld SVN: r6687 - archetypes/javaee6-webapp/trunk.
by weld-commits＠lists.jboss.org
Author: dan.j.allen
Date: 2010-07-17 11:45:05 -0400 (Sat, 17 Jul 2010)
New Revision: 6687
Modified:
archetypes/javaee6-webapp/trunk/readme.txt
Log:
add note about Derby
Modified: archetypes/javaee6-webapp/trunk/readme.txt
===================================================================
--- archetypes/javaee6-webapp/trunk/readme.txt 2010-07-17 15:41:08 UTC (rev 6686)
+++ archetypes/javaee6-webapp/trunk/readme.txt 2010-07-17 15:45:05 UTC (rev 6687)
@@ -105,6 +105,9 @@
./asadmin start-database
./asadmin start-domain domain1
+ NOTE:
+ NetBeans will start the Derby database automatically when it starts GlassFish.
+
Now you can either deploy the target/jboss-javaee6-webapp-src.war through the
web-based GlassFish admininstration console, or you can again use asadmin:
14 years, 3 months