This is an automated email from the ASF dual-hosted git repository.
dblevins pushed a commit to branch master
in repository https://gitbox.apache.org/repos/asf/tomee.git
The following commit(s) were added to refs/heads/master by this push:
new d758bf1 [TOMEE-2669] [Translation] mp-jsonb-configuration example to
Spanish
new 9af2e65 Merge pull request #562 from cchacin/TOMEE-2673-2
d758bf1 is described below
commit d758bf1abb7a92155ec51f142e275b73ee072cec
Author: Carlos Chacin <[email protected]>
AuthorDate: Mon Sep 9 00:04:56 2019 -0700
[TOMEE-2669] [Translation] mp-jsonb-configuration example to Spanish
---
examples/mp-jsonb-configuration/README.adoc | 87 +++++++++------
.../{README.adoc => README_es.adoc} | 121 ++++++++++++---------
2 files changed, 127 insertions(+), 81 deletions(-)
diff --git a/examples/mp-jsonb-configuration/README.adoc
b/examples/mp-jsonb-configuration/README.adoc
index d508ed6..f997e2a 100644
--- a/examples/mp-jsonb-configuration/README.adoc
+++ b/examples/mp-jsonb-configuration/README.adoc
@@ -4,25 +4,45 @@
= JSON-B Configuration
This examples shows how to customize jsonb for a JAX-RS Application.
-JSONB is the new javaee-api:8.0 standard for json
+JSONB is the new `javaee-api:8.0` standard for json
serialization/deserialization. Few annotations are needed and
-JsonbConfig offers many configurations.
+`JsonbConfig` offers many configurations.
== Run and test Endpoint
-the application can be run with `mvn clean install tomee:run' if port
-8080 is available you can invoke the following endpoint: (GET)
-http://localhost:8080/mp-jsonb-configuration/api/users that should
-respond with the following json: [ \{ ``Id'':1, ``Name'':``user 1'',
-``Registration'':``2018 - 12 - 28'' }, \{ ``Id'':2, ``Name'':``user 2'',
-``Registration'':``2018 - 12 - 28'' }]
+the application can be run with `mvn clean install tomee:run` if port
+8080 is available you can invoke the following endpoint:
+
+[source,bash]
+----
+$ curl -X GET http://localhost:8080/mp-jsonb-configuration/api/users
+----
+
+that should respond with the following json:
+
+[source,bash]
+----
+[
+ {
+ "Id":1,
+ "Name":"user 1",
+ "Registration":"2018 - 12 - 28"
+ },
+ {
+ "Id":2,
+ "Name":"user 2",
+ "Registration":"2018 - 12 - 28"
+ }
+]
+----
== @ApplicationPath
JAXRS entry point class, as follows jaxrs will load all the annotated
-@Path classes and methods without specifying them.
+`@Path` classes and methods without specifying them.
-....
+[source,java]
+----
import javax.ws.rs.ApplicationPath;
import javax.ws.rs.core.Application;
@@ -30,13 +50,14 @@ import javax.ws.rs.core.Application;
public class JAXRSApplication extends Application {
}
-....
+----
== @Path Rest resource
Simple jaxrs class with a GET endpoint
-....
+[source,java]
+----
import java.util.ArrayList;
import java.util.List;
@@ -66,14 +87,15 @@ public class UserService {
return users;
}
}
-....
+----
== JSONB Configuration
-Implementing ContextResolver<> you can customize jaxrs defaults, in this
+Implementing `ContextResolver<>`` you can customize jaxrs defaults, in this
example we are going to customize JSONB serialization/deserialization
-....
+[source,java]
+----
import javax.json.bind.Jsonb;
import javax.json.bind.JsonbBuilder;
import javax.json.bind.JsonbConfig;
@@ -101,15 +123,16 @@ public class JSONBConfiguration implements
ContextResolver<Jsonb> {
}
}
-....
+----
-JsonbConfig offers many configurations.
+`JsonbConfig` offers many configurations.
== Accessing the rest endpoint
-The test spin up an openejb webapp and invoke the users endpoint
+The test spin up an openejb webapp and invoke the `/users` endpoint
-....
+[source,java]
+----
import java.io.IOException;
import java.text.SimpleDateFormat;
import java.util.Date;
@@ -150,16 +173,17 @@ public class UserServiceTest {
}
}
-....
+----
== Running
Running the example can be done from maven with a simple `mvn clean
install' command run from the `mp-jsonb-configuration' directory.
-When run you should see output similar to the following.
+When run you should see output similar to the following:
-....
+[source,java]
+----
-------------------------------------------------------
T E S T S
-------------------------------------------------------
@@ -177,8 +201,8 @@ INFO - Creating ServerService(id=httpejbd)
INFO - Created ServicePool 'httpejbd' with (10) core threads, limited to (200)
threads with a queue of (9)
INFO - Initializing network services
INFO - ** Bound Services **
-INFO - NAME IP PORT
-INFO - httpejbd 127.0.0.1 4204
+INFO - NAME IP PORT
+INFO - httpejbd 127.0.0.1 4204
INFO - -------
INFO - Ready!
INFO - Configuring enterprise application:
/home/federico/Documents/PRIVATO/Apache/tomee/examples/mp-jsonb-configuration/UserServiceTest
@@ -253,19 +277,20 @@ Tests run: 1, Failures: 0, Errors: 0, Skipped: 0, Time
elapsed: 2.203 sec
Results :
Tests run: 1, Failures: 0, Errors: 0, Skipped: 0
-
-....
+
+----
=== Inside the jar
-javaee-api:8.0 brings in all the dependencies needed to spin up a
+`javaee-api:8.0` brings in all the dependencies needed to spin up a
working REST application.
If we look at the jar built by maven, we’ll see the application itself
is quite small:
-....
-$ jar tvf target/mp-jsonb-configuration-8.0.0-SNAPSHOT.war
+[source,bash]
+----
+$ jar tvf target/mp-jsonb-configuration-8.0.0-SNAPSHOT.war
0 Fri Dec 28 19:36:10 CET 2018 META-INF/
134 Fri Dec 28 19:36:08 CET 2018 META-INF/MANIFEST.MF
0 Fri Dec 28 19:36:08 CET 2018 WEB-INF/
@@ -284,8 +309,8 @@ $ jar tvf target/mp-jsonb-configuration-8.0.0-SNAPSHOT.war
0 Fri Dec 28 19:36:10 CET 2018
META-INF/maven/org.superbiz/mp-jsonb-configuration/
1791 Fri Dec 28 19:10:44 CET 2018
META-INF/maven/org.superbiz/mp-jsonb-configuration/pom.xml
128 Fri Dec 28 19:36:08 CET 2018
META-INF/maven/org.superbiz/mp-jsonb-configuration/pom.properties
-....
+----
This single jar could be deployed any any compliant Java EE
implementation. In TomEE you’d simply place it in the
-`tomee.home/webapps/` directory.
+`${tomee.home}/webapps/` directory.
diff --git a/examples/mp-jsonb-configuration/README.adoc
b/examples/mp-jsonb-configuration/README_es.adoc
similarity index 81%
copy from examples/mp-jsonb-configuration/README.adoc
copy to examples/mp-jsonb-configuration/README_es.adoc
index d508ed6..79ecbbe 100644
--- a/examples/mp-jsonb-configuration/README.adoc
+++ b/examples/mp-jsonb-configuration/README_es.adoc
@@ -1,28 +1,48 @@
:index-group: Unrevised
:jbake-type: page
:jbake-status: status=published
-= JSON-B Configuration
+= Configurando JSON-B
-This examples shows how to customize jsonb for a JAX-RS Application.
-JSONB is the new javaee-api:8.0 standard for json
-serialization/deserialization. Few annotations are needed and
-JsonbConfig offers many configurations.
+Este ejemplo muestra cómo personalizar jsonb para una aplicación JAX-RS.
+JSONB es el nuevo estándar `javaee-api: 8.0` para la serialización /
+deserialización de json. Se necesitan pocas anotaciones y `JsonbConfig`
+ofrece muchas configuraciones.
-== Run and test Endpoint
+== Ejecuta y prueba el Endpoint
-the application can be run with `mvn clean install tomee:run' if port
-8080 is available you can invoke the following endpoint: (GET)
-http://localhost:8080/mp-jsonb-configuration/api/users that should
-respond with the following json: [ \{ ``Id'':1, ``Name'':``user 1'',
-``Registration'':``2018 - 12 - 28'' }, \{ ``Id'':2, ``Name'':``user 2'',
-``Registration'':``2018 - 12 - 28'' }]
+la aplicación se puede ejecutar con `mvn clean install tomee: run` si el puerto
+8080 está disponible, puede invocar el siguiente endpoint:
+
+[source,bash]
+----
+$ curl -X GET http://localhost:8080/mp-jsonb-configuration/api/users
+----
+
+que debería responder con el siguiente json:
+
+[source,bash]
+----
+[
+ {
+ "Id":1,
+ "Name":"user 1",
+ "Registration":"2018 - 12 - 28"
+ },
+ {
+ "Id":2,
+ "Name":"user 2",
+ "Registration":"2018 - 12 - 28"
+ }
+]
+----
== @ApplicationPath
-JAXRS entry point class, as follows jaxrs will load all the annotated
-@Path classes and methods without specifying them.
+La clase de punto de entrada JAXRS, de la siguiente manera los jaxrs cargarán
+todos las clases y métodos anotados con `@ Path` sin especificarlos.
-....
+[source,java]
+----
import javax.ws.rs.ApplicationPath;
import javax.ws.rs.core.Application;
@@ -30,13 +50,14 @@ import javax.ws.rs.core.Application;
public class JAXRSApplication extends Application {
}
-....
+----
-== @Path Rest resource
+== @Path Recurso Rest
-Simple jaxrs class with a GET endpoint
+Clase jaxrs simple con un método GET
-....
+[source,java]
+----
import java.util.ArrayList;
import java.util.List;
@@ -66,14 +87,16 @@ public class UserService {
return users;
}
}
-....
+----
-== JSONB Configuration
+== Configuració JSONB
-Implementing ContextResolver<> you can customize jaxrs defaults, in this
-example we are going to customize JSONB serialization/deserialization
+Implementando `ContextResolver <>` puede personalizar los valores
+predeterminados de jaxrs, en este ejemplo, vamos a personalizar la
+serialización / deserialización JSONB
-....
+[source,java]
+----
import javax.json.bind.Jsonb;
import javax.json.bind.JsonbBuilder;
import javax.json.bind.JsonbConfig;
@@ -101,15 +124,16 @@ public class JSONBConfiguration implements
ContextResolver<Jsonb> {
}
}
-....
+----
-JsonbConfig offers many configurations.
+`JsonbConfig` ofrece muchas configuraciones.
-== Accessing the rest endpoint
+== Accediendo al recurso Rest
-The test spin up an openejb webapp and invoke the users endpoint
+La prueba activa una aplicación web openejb e invoca el recurso rest `/users`
-....
+[source,java]
+----
import java.io.IOException;
import java.text.SimpleDateFormat;
import java.util.Date;
@@ -150,16 +174,16 @@ public class UserServiceTest {
}
}
-....
+----
-== Running
+== Ejecutando
-Running the example can be done from maven with a simple `mvn clean
-install' command run from the `mp-jsonb-configuration' directory.
+Ejecutando el ejemplo se puede hacer desde maven con un simple comando `mvn
clean install` ejecutado desde el directorio `mp-jsonb-configuration`.
-When run you should see output similar to the following.
+Cuando se ejecute, debería ver una salida similar a la siguiente:
-....
+[source,java]
+----
-------------------------------------------------------
T E S T S
-------------------------------------------------------
@@ -177,8 +201,8 @@ INFO - Creating ServerService(id=httpejbd)
INFO - Created ServicePool 'httpejbd' with (10) core threads, limited to (200)
threads with a queue of (9)
INFO - Initializing network services
INFO - ** Bound Services **
-INFO - NAME IP PORT
-INFO - httpejbd 127.0.0.1 4204
+INFO - NAME IP PORT
+INFO - httpejbd 127.0.0.1 4204
INFO - -------
INFO - Ready!
INFO - Configuring enterprise application:
/home/federico/Documents/PRIVATO/Apache/tomee/examples/mp-jsonb-configuration/UserServiceTest
@@ -253,19 +277,18 @@ Tests run: 1, Failures: 0, Errors: 0, Skipped: 0, Time
elapsed: 2.203 sec
Results :
Tests run: 1, Failures: 0, Errors: 0, Skipped: 0
-
-....
-=== Inside the jar
+----
+
+=== Dentro del jar
-javaee-api:8.0 brings in all the dependencies needed to spin up a
-working REST application.
+`javaee-api: 8.0` incorpora todas las dependencias necesarias para activar una
aplicación REST que funcione.
-If we look at the jar built by maven, we’ll see the application itself
-is quite small:
+Si miramos el jar construido por maven, veremos que la aplicación en sí es
bastante pequeña:
-....
-$ jar tvf target/mp-jsonb-configuration-8.0.0-SNAPSHOT.war
+[source,bash]
+----
+$ jar tvf target/mp-jsonb-configuration-8.0.0-SNAPSHOT.war
0 Fri Dec 28 19:36:10 CET 2018 META-INF/
134 Fri Dec 28 19:36:08 CET 2018 META-INF/MANIFEST.MF
0 Fri Dec 28 19:36:08 CET 2018 WEB-INF/
@@ -284,8 +307,6 @@ $ jar tvf target/mp-jsonb-configuration-8.0.0-SNAPSHOT.war
0 Fri Dec 28 19:36:10 CET 2018
META-INF/maven/org.superbiz/mp-jsonb-configuration/
1791 Fri Dec 28 19:10:44 CET 2018
META-INF/maven/org.superbiz/mp-jsonb-configuration/pom.xml
128 Fri Dec 28 19:36:08 CET 2018
META-INF/maven/org.superbiz/mp-jsonb-configuration/pom.properties
-....
+----
-This single jar could be deployed any any compliant Java EE
-implementation. In TomEE you’d simply place it in the
-`tomee.home/webapps/` directory.
+Este jar individual podría desplegarse en cualquier implementación Java EE que
cumpla con los requisitos. En TomEE simplemente lo colocaría en el directorio
`${tomee.home}/webapps/`.
