ラベル Java の投稿を表示しています。 すべての投稿を表示
ラベル Java の投稿を表示しています。 すべての投稿を表示

2019年2月25日月曜日

WildFly 15

月日が過ぎ去るのは早く、知らないうちに 15 まで WildFly のバージョンが上がっていた。

junnichi@vt04:/tmp$ docker run jboss/wildfly
=========================================================================

  JBoss Bootstrap Environment

  JBOSS_HOME: /opt/jboss/wildfly

  JAVA: /usr/lib/jvm/java/bin/java

  JAVA_OPTS:  -server -Xms64m -Xmx512m -XX:MetaspaceSize=96M -XX:MaxMetaspaceSize=256m -Djava.net.preferIPv4Stack=true -Djboss.modules.system.pkgs=org.jboss.byteman -Djava.awt.headless=true  --add-exports=java.base/sun.nio.ch=ALL-UNNAMED --add-exports=jdk.unsupported/sun.misc=ALL-UNNAMED --add-exports=jdk.unsupported/sun.reflect=ALL-UNNAMED --add-modules=java.se

=========================================================================

13:15:40,585 INFO  [org.jboss.modules] (main) JBoss Modules version 1.8.7.Final
13:15:41,287 INFO  [org.jboss.msc] (main) JBoss MSC version 1.4.5.Final
13:15:41,299 INFO  [org.jboss.threads] (main) JBoss Threads version 2.3.2.Final
13:15:41,490 INFO  [org.jboss.as] (MSC service thread 1-2) WFLYSRV0049: WildFly Full 15.0.1.Final (WildFly Core 7.0.0.Final) starting
13:15:42,714 INFO  [org.wildfly.security] (ServerService Thread Pool -- 27) ELY00001: WildFly Elytron version 1.7.0.Final
13:15:43,555 INFO  [org.jboss.as.controller.management-deprecated] (Controller Boot Thread) WFLYCTL0028: Attribute 'security-realm' in the resource at address '/core-service=management/management-interface=http-interface' is deprecated, and may be removed in a future version. See the attribute description in the output of the read-resource-description operation to learn more about the deprecation.
13:15:43,608 INFO  [org.jboss.as.controller.management-deprecated] (ServerService Thread Pool -- 34) WFLYCTL0028: Attribute 'security-realm' in the resource at address '/subsystem=undertow/server=default-server/https-listener=https' is deprecated, and may be removed in a future version. See the attribute description in the output of the read-resource-description operation to learn more about the deprecation.
13:15:43,725 INFO  [org.jboss.as.server] (Controller Boot Thread) WFLYSRV0039: Creating http management service using socket-binding (management-http)
13:15:43,754 INFO  [org.xnio] (MSC service thread 1-5) XNIO version 3.6.5.Final
13:15:43,766 INFO  [org.xnio.nio] (MSC service thread 1-5) XNIO NIO Implementation Version 3.6.5.Final
13:15:43,833 INFO  [org.jboss.as.clustering.infinispan] (ServerService Thread Pool -- 49) WFLYCLINF0001: Activating Infinispan subsystem.
13:15:43,879 INFO  [org.wildfly.extension.microprofile.config.smallrye._private] (ServerService Thread Pool -- 58) WFLYCONF0001: Activating WildFly MicroProfile Config Subsystem
13:15:43,866 INFO  [org.jboss.as.jaxrs] (ServerService Thread Pool -- 51) WFLYRS0016: RESTEasy version 3.6.2.Final
13:15:43,903 INFO  [org.wildfly.extension.microprofile.opentracing] (ServerService Thread Pool -- 61) WFLYTRACEXT0001: Activating MicroProfile OpenTracing Subsystem
13:15:43,913 INFO  [org.jboss.as.naming] (ServerService Thread Pool -- 62) WFLYNAM0001: Activating Naming Subsystem
13:15:43,916 INFO  [org.jboss.as.security] (ServerService Thread Pool -- 68) WFLYSEC0002: Activating Security Subsystem
13:15:43,920 INFO  [org.jboss.as.connector] (MSC service thread 1-3) WFLYJCA0009: Starting JCA Subsystem (WildFly/IronJacamar 1.4.11.Final)
13:15:43,914 INFO  [org.jboss.as.jsf] (ServerService Thread Pool -- 56) WFLYJSF0007: Activated the following JSF Implementations: [main]
13:15:43,929 INFO  [org.wildfly.extension.microprofile.health.smallrye] (ServerService Thread Pool -- 59) WFLYHEALTH0001: Activating Eclipse MicroProfile Health Subsystem
13:15:43,936 INFO  [org.jboss.as.mail.extension] (MSC service thread 1-2) WFLYMAIL0002: Unbound mail session [java:jboss/mail/Default]
13:15:43,954 INFO  [org.wildfly.extension.microprofile.metrics.smallrye] (ServerService Thread Pool -- 60) WFLYMETRICS0001: Activating Eclipse MicroProfile Metrics Subsystem
13:15:43,950 INFO  [org.jboss.as.security] (MSC service thread 1-5) WFLYSEC0001: Current PicketBox version=5.0.3.Final
13:15:43,951 WARN  [org.jboss.as.txn] (ServerService Thread Pool -- 70) WFLYTX0013: The node-identifier attribute on the /subsystem=transactions is set to the default value. This is a danger for environments running multiple servers. Please make sure the attribute value is unique.
13:15:43,952 INFO  [org.wildfly.extension.io] (ServerService Thread Pool -- 50) WFLYIO001: Worker 'default' has auto-configured to 12 core threads with 96 task threads based on your 6 available processors
13:15:44,010 INFO  [org.jboss.as.webservices] (ServerService Thread Pool -- 72) WFLYWS0002: Activating WebServices Extension
13:15:44,041 INFO  [org.jboss.as.naming] (MSC service thread 1-3) WFLYNAM0003: Starting Naming Service
13:15:44,050 INFO  [org.jboss.as.mail.extension] (MSC service thread 1-3) WFLYMAIL0001: Bound mail session [java:jboss/mail/Default]
13:15:44,049 INFO  [org.jboss.as.connector.subsystems.datasources] (ServerService Thread Pool -- 42) WFLYJCA0004: Deploying JDBC-compliant driver class org.h2.Driver (version 1.4)
13:15:44,063 INFO  [org.wildfly.extension.undertow] (MSC service thread 1-6) WFLYUT0003: Undertow 2.0.15.Final starting
13:15:44,072 INFO  [org.jboss.remoting] (MSC service thread 1-1) JBoss Remoting version 5.0.8.Final
13:15:44,078 INFO  [org.jboss.as.connector.deployers.jdbc] (MSC service thread 1-4) WFLYJCA0018: Started Driver service with driver-name = h2
13:15:44,092 INFO  [io.smallrye.metrics] (MSC service thread 1-2) Converted [2] config entries and added [4] replacements
13:15:44,097 INFO  [io.smallrye.metrics] (MSC service thread 1-2) Converted [3] config entries and added [18] replacements
13:15:44,221 INFO  [org.jboss.as.connector.subsystems.datasources] (MSC service thread 1-5) WFLYJCA0010: Unbound data source [java:jboss/datasources/ExampleDS]
13:15:44,346 INFO  [org.jboss.as.ejb3] (MSC service thread 1-3) WFLYEJB0482: Strict pool mdb-strict-max-pool is using a max instance size of 24 (per class), which is derived from the number of CPUs on this host.
13:15:44,352 INFO  [org.jboss.as.ejb3] (MSC service thread 1-2) WFLYEJB0481: Strict pool slsb-strict-max-pool is using a max instance size of 96 (per class), which is derived from thread worker pool sizing.
13:15:44,419 INFO  [org.wildfly.extension.undertow] (ServerService Thread Pool -- 71) WFLYUT0014: Creating file handler for path '/opt/jboss/wildfly/welcome-content' with options [directory-listing: 'false', follow-symlink: 'false', case-sensitive: 'true', safe-symlink-paths: '[]']
13:15:44,433 INFO  [org.wildfly.extension.undertow] (MSC service thread 1-2) WFLYUT0012: Started server default-server.
13:15:44,448 INFO  [org.wildfly.extension.undertow] (MSC service thread 1-6) WFLYUT0018: Host default-host starting
13:15:44,565 INFO  [org.wildfly.extension.undertow] (MSC service thread 1-8) WFLYUT0006: Undertow HTTP listener default listening on 0.0.0.0:8080
13:15:44,673 INFO  [org.jboss.as.ejb3] (MSC service thread 1-2) WFLYEJB0493: EJB subsystem suspension complete
13:15:44,750 INFO  [org.jboss.as.connector.subsystems.datasources] (MSC service thread 1-1) WFLYJCA0001: Bound data source [java:jboss/datasources/ExampleDS]
13:15:44,939 INFO  [org.jboss.as.patching] (MSC service thread 1-2) WFLYPAT0050: WildFly Full cumulative patch ID is: base, one-off patches include: none
13:15:44,964 WARN  [org.jboss.as.domain.management.security] (MSC service thread 1-6) WFLYDM0111: Keystore /opt/jboss/wildfly/standalone/configuration/application.keystore not found, it will be auto generated on first use with a self signed certificate for host localhost
13:15:44,973 INFO  [org.jboss.as.server.deployment.scanner] (MSC service thread 1-7) WFLYDS0013: Started FileSystemDeploymentService for directory /opt/jboss/wildfly/standalone/deployments
13:15:45,070 INFO  [org.wildfly.extension.undertow] (MSC service thread 1-5) WFLYUT0006: Undertow HTTPS listener https listening on 0.0.0.0:8443
13:15:45,155 INFO  [org.jboss.ws.common.management] (MSC service thread 1-6) JBWS022052: Starting JBossWS 5.2.4.Final (Apache CXF 3.2.5.jbossorg-1)
13:15:45,248 INFO  [org.jboss.as.server] (Controller Boot Thread) WFLYSRV0212: Resuming server
13:15:45,252 INFO  [org.jboss.as] (Controller Boot Thread) WFLYSRV0060: Http management interface listening on http://127.0.0.1:9990/management
13:15:45,252 INFO  [org.jboss.as] (Controller Boot Thread) WFLYSRV0051: Admin console listening on http://127.0.0.1:9990
13:15:45,253 INFO  [org.jboss.as] (Controller Boot Thread) WFLYSRV0025: WildFly Full 15.0.1.Final (WildFly Core 7.0.0.Final) started in 5135ms - Started 309 of 530 services (321 services are lazy, passive or on-demand)

2016年2月1日月曜日

WildFly 10 !

WildFly 10.0.0.Final がリリースされたのでいつもの起動テスト。

Windows 10 で WildFly 10 を起動します。

8秒・・・・遅いと思ったけど、前のバージョンのログ観てもそんなもんだった。

Calling "C:\usr\local\jboss\wildfly-10.0.0.Final\bin\standalone.conf.bat"
JAVA_HOME is not set. Unexpected results may occur.
Set JAVA_HOME to the directory of your local JDK to avoid this message.
===============================================================================

  JBoss Bootstrap Environment

  JBOSS_HOME: "C:\usr\local\jboss\wildfly-10.0.0.Final"

  JAVA: "java"

  JAVA_OPTS: "-Dprogram.name=standalone.bat -Xms64M -Xmx512M -XX:MetaspaceSize=96M -XX:MaxMetaspaceSize=256m -Djava.net.preferIPv4Stack=true -Djboss.modules.system.pkgs=org.jboss.byteman"

===============================================================================

14:26:53,780 INFO  [org.jboss.modules] (main) JBoss Modules version 1.5.1.Final
14:26:54,499 INFO  [org.jboss.msc] (main) JBoss MSC version 1.2.6.Final
14:26:54,633 INFO  [org.jboss.as] (MSC service thread 1-8) WFLYSRV0049: WildFly Full 10.0.0.Final (WildFly Core 2.0.10.Final) starting
14:26:57,439 INFO  [org.jboss.as.server] (Controller Boot Thread) WFLYSRV0039: Creating http management service using socket-binding (management-http)
14:26:57,471 INFO  [org.xnio] (MSC service thread 1-6) XNIO version 3.3.4.Final
14:26:57,486 INFO  [org.xnio.nio] (MSC service thread 1-6) XNIO NIO Implementation Version 3.3.4.Final
14:26:57,642 WARN  [org.jboss.as.txn] (ServerService Thread Pool -- 54) WFLYTX0013: Node identifier property is set to the default value. Please make sure it is unique.
14:26:57,674 INFO  [org.wildfly.extension.io] (ServerService Thread Pool -- 37) WFLYIO001: Worker 'default' has auto-configured to 8 core threads with 64 task threads based on your 4 available processors
14:26:57,689 INFO  [org.jboss.as.webservices] (ServerService Thread Pool -- 56) WFLYWS0002: Activating WebServices Extension
14:26:57,721 INFO  [org.jboss.as.security] (ServerService Thread Pool -- 53) WFLYSEC0002: Activating Security Subsystem
14:26:57,721 INFO  [org.jboss.as.clustering.infinispan] (ServerService Thread Pool -- 38) WFLYCLINF0001: Activating Infinispan subsystem.
14:26:57,705 INFO  [org.jboss.as.naming] (ServerService Thread Pool -- 46) WFLYNAM0001: Activating Naming Subsystem
14:26:57,799 INFO  [org.jboss.as.security] (MSC service thread 1-3) WFLYSEC0001: Current PicketBox version=4.9.4.Final
14:26:57,814 INFO  [org.wildfly.extension.undertow] (MSC service thread 1-4) WFLYUT0003: Undertow 1.3.15.Final starting
14:26:57,814 INFO  [org.wildfly.extension.undertow] (ServerService Thread Pool -- 55) WFLYUT0003: Undertow 1.3.15.Final starting
14:26:57,877 INFO  [org.jboss.as.connector] (MSC service thread 1-8) WFLYJCA0009: Starting JCA Subsystem (WildFly/IronJacamar 1.3.2.Final)
14:26:57,846 INFO  [org.jboss.as.jsf] (ServerService Thread Pool -- 44) WFLYJSF0007: Activated the following JSF Implementations: [main]
14:26:58,080 INFO  [org.jboss.remoting] (MSC service thread 1-6) JBoss Remoting version 4.0.18.Final
14:26:58,205 INFO  [org.jboss.as.connector.subsystems.datasources] (ServerService Thread Pool -- 33) WFLYJCA0004: Deploying JDBC-compliant driver class org.h2.Driver (version 1.3)
14:26:58,221 INFO  [org.jboss.as.connector.deployers.jdbc] (MSC service thread 1-1) WFLYJCA0018: Started Driver service with driver-name = h2
14:26:58,267 INFO  [org.jboss.as.mail.extension] (MSC service thread 1-6) WFLYMAIL0001: Bound mail session [java:jboss/mail/Default]
14:26:58,267 INFO  [org.jboss.as.naming] (MSC service thread 1-3) WFLYNAM0003: Starting Naming Service
14:26:58,564 INFO  [org.wildfly.extension.undertow] (ServerService Thread Pool -- 55) WFLYUT0014: Creating file handler for path 'C:\usr\local\jboss\wildfly-10.0.0.Final/welcome-content' with options [directory-listing: 'false', follow-symlink: 'false', case-sensitive: 'true', safe-symlink-paths: '[]']
14:26:58,721 INFO  [org.wildfly.extension.undertow] (MSC service thread 1-2) WFLYUT0012: Started server default-server.
14:26:58,846 INFO  [org.wildfly.extension.undertow] (MSC service thread 1-4) WFLYUT0018: Host default-host starting
14:26:58,908 INFO  [org.jboss.as.ejb3] (MSC service thread 1-1) WFLYEJB0481: Strict pool slsb-strict-max-pool is using a max instance size of 64 (per class), which is derived from thread worker pool sizing.
14:26:58,908 INFO  [org.jboss.as.ejb3] (MSC service thread 1-3) WFLYEJB0482: Strict pool mdb-strict-max-pool is using a max instance size of 16 (per class), which is derived from the number of CPUs on this host.
14:26:59,033 INFO  [org.wildfly.extension.undertow] (MSC service thread 1-8) WFLYUT0006: Undertow HTTP listener default listening on 127.0.0.1:8080
14:26:59,471 INFO  [org.jboss.as.connector.subsystems.datasources] (MSC service thread 1-4) WFLYJCA0001: Bound data source [java:jboss/datasources/ExampleDS]
14:26:59,502 INFO  [org.jboss.as.server.deployment.scanner] (MSC service thread 1-7) WFLYDS0013: Started FileSystemDeploymentService for directory C:\usr\local\jboss\wildfly-10.0.0.Final\standalone\deployments
14:26:59,971 INFO  [org.infinispan.factories.GlobalComponentRegistry] (MSC service thread 1-5) ISPN000128: Infinispan version: Infinispan 'Mahou' 8.1.0.Final
14:26:59,971 INFO  [org.infinispan.factories.GlobalComponentRegistry] (MSC service thread 1-4) ISPN000128: Infinispan version: Infinispan 'Mahou' 8.1.0.Final
14:26:59,971 INFO  [org.infinispan.factories.GlobalComponentRegistry] (MSC service thread 1-6) ISPN000128: Infinispan version: Infinispan 'Mahou' 8.1.0.Final
14:26:59,986 INFO  [org.infinispan.factories.GlobalComponentRegistry] (MSC service thread 1-7) ISPN000128: Infinispan version: Infinispan 'Mahou' 8.1.0.Final
14:27:00,434 INFO  [org.jboss.ws.common.management] (MSC service thread 1-3) JBWS022052: Starting JBossWS 5.1.3.Final (Apache CXF 3.1.4)
14:27:01,055 INFO  [org.jboss.as] (Controller Boot Thread) WFLYSRV0060: Http management interface listening on http://127.0.0.1:9990/management
14:27:01,055 INFO  [org.jboss.as] (Controller Boot Thread) WFLYSRV0051: Admin console listening on http://127.0.0.1:9990
14:27:01,055 INFO  [org.jboss.as] (Controller Boot Thread) WFLYSRV0025: WildFly Full 10.0.0.Final (WildFly Core 2.0.10.Final) started in 8041ms - Started 267 of 553 services (371 services are lazy, passive or on-demand)

2015年4月24日金曜日

Ubuntu Server に、JDK 8 を apt だけで入れる

Ubuntu Server 14.04LTS には、OpenJDK 8 が無かった・・・・ので、Sun JDK 8 でも入れてみる。
そもそも Ubuntu Server に、add-apt-repository が入っていないのは、品質担保のため?

  • インストール
# apt-get install software-properties-common
# add-apt-repository ppa:webupd8team/java
# apt-get -y -q update
# echo oracle-java8-installer shared/accepted-oracle-license-v1-1 select true | /usr/bin/debconf-set-selections
# apt-get -y -q install oracle-java8-installer
# update-java-alternatives -s java-8-oracle
  • 動作確認
# java -version
java version "1.8.0_45"
Java(TM) SE Runtime Environment (build 1.8.0_45-b14)
Java HotSpot(TM) 64-Bit Server VM (build 25.45-b02, mixed mode)
 元ネタはこの辺です。
http://askubuntu.com/questions/464755/how-to-install-openjdk-8-on-14-04-lts
http://www.webupd8.org/2012/09/install-oracle-java-8-in-ubuntu-via-ppa.html

2014年2月14日金曜日

OpenShift に WildFly が登場してた。

いつの間に。
CR1のカードリッジなのか。少しまつと、1.0.0.Final のに変わるかな?


2014年2月12日水曜日

ようやく出たね WildFly 8.0.0.Final

先ほどリリースされたのを確認できたので、とりあえず起動まで。
EE7 が普及してほしいので、早くEAPが出るといいなー。


2013年12月25日水曜日

WildFly 8.0.0.CR1

ようやく出てたのでとりあえずいつものブート。
久しぶりに、ZIP 版が生きてましたw



Final は1月末みたいですね。
https://issues.jboss.org/browse/WFLY?selectedTab=com.atlassian.jira.plugin.system.project%3Aroadmap-panel&_sscc=t


2013年11月13日水曜日

RESTEasy の Bean Validation

そんなの API で受けてから手動でやりなさいよ!と言われるかもしれないけどできることなら冗長なコードは排除したい。

そんなあなたに ExceptionMapper を使う方法を。

使い方が変わったようなので新旧書いときます。(大体同じようなことはしてますが全く同じではないので注意)

※RESTEasy 2.3 の方は EJB との組み合わせに問題がある・・・・ので、できれば RESTEasy 3 の方がおすすめです。

□WildFly 8.0.0.Beta1 & RESTEasy 3.0.4.Final
@Provider
public class ValidationExceptionHandler implements
        ExceptionMapper<ResteasyViolationException> {

    @Override
    @Produces(MediaType.APPLICATION_JSON)
    public Response toResponse(ResteasyViolationException exception) {

        ValidateMessage errors = new ValidateMessage();

        for (ResteasyConstraintViolation violation : exception.getViolations()) {
            errors.getMessages().add(
                    new Message(String.format("%s:%s:%s:%s", violation
                            .getPath(), violation.getConstraintType().name(),
                            violation.getValue(), violation.getMessage())));
        }

        return Response.status(Status.BAD_REQUEST).entity(errors).build();
    }
}
□JBoss AS 7.1.x & RESTEasy 2.3.x
@Provider
public class ValidationExceptionHandler implements
        ExceptionMapper<MethodConstraintViolationException> {

    @Override
    @Produces({ MediaType.APPLICATION_JSON })
    public Response toResponse(MethodConstraintViolationException ex) {
        ValidateMessage errors = new ValidateMessage();

        for (MethodConstraintViolation<?> violation : ex
                .getConstraintViolations()) {
            errors.getMessages().add(
                    new Message(String.format("%s:%s:%s:%s", violation
                            .getMethod().getName(), violation
                            .getParameterName(), violation.getInvalidValue(),
                            violation.getMessage())));
        }

        return Response.status(Status.BAD_REQUEST).entity(errors).build();
    }
}

□JSON 出力のためのドメインクラス
@XmlRootElement(name = "validate_message")
public class ValidateMessage implements Serializable {
    private static final long serialVersionUID = 1L;

    private List<Message> messages = new ArrayList<Message>();

    public static class Message {

        private String message;

        public Message() {
        }

        public Message(String message) {
            this.message = message;
        }

        public String getMessage() {
            return message;
        }

        public void setMessage(String message) {
            this.message = message;
        }

    }

    @XmlElementWrapper(name = "messages")
    @XmlElement(name = "message")
    public List<Message> getMessages() {
        return messages;
    }

    public void setMessages(List<Message> messages) {
        this.messages = messages;
    }
}

□pom.xml(RESTEasy 3.0.4.Final)
        <dependency>
            <groupId>org.jboss.resteasy</groupId>
            <artifactId>resteasy-validator-provider-11</artifactId>
            <version>3.0.4.Final</version>
            <scope>provided</scope>
        </dependency>
 □pom.xml(RESTEasy 2.3.x)
        <dependency>
            <groupId>org.jboss.resteasy</groupId>
            <artifactId>resteasy-hibernatevalidator-provider</artifactId>
            <version>2.3.7.Final</version>
        </dependency>

2013年9月26日木曜日

SwitchYard on OpenShift

デモビデオが出てたので貼っときます。
http://vimeo.com/75402902#

え。でも、OpenShift の SwitchYard って 0.4 じゃなかった?

・・・・と思ったら、0.8 に上がってました。なぜ 1.0 じゃない?w

あ、ここに纏められるみたいですね^^
https://community.jboss.org/wiki/SwitchYardVideoSeries

2013年7月29日月曜日

JBDS7

今朝、村形軍曹から、JBDS7 が出てるよ、と。

・・・・本当だ^^
http://planet.jboss.org/post/jboss_tools_4_1_and_developer_studio_7_go_ga

JBDS7 Beta2 からアップデートしてみる。








できた。


とりあえず、AS7.2~WildFlyを利用している人は更新必須ですかね~

2013年6月25日火曜日

GlassFish 4.0

いつの間にかリリースされてた。
https://glassfish.java.net/download.html

2013年6月24日月曜日

WildFly 8.0.0.Alpha2

リリースされてますね~
http://www.wildfly.org/download/
https://github.com/wildfly/wildfly/tree/8.0.0.Alpha2

あー、なんか Alpha1 で作ってたプロジェクトはそのままじゃ動かんな~w

2013年6月13日木曜日

OpenShift!

正式発表された、OpenShift にスモールサイズのインスタンスを作ってみたよ!
URL こういうの意外と取れるのねw

http://hoge-fuga.rhcloud.com/

さて・・・・置くモノが無いなw

2013年6月4日火曜日

Java EE 7 is Final!

気づくのが遅くなってしまいましたが、EE 7 spec が Final Release になっていました。
http://jcp.org/en/jsr/detail?id=342


あとは、個人的に気にしている spec を列挙しときます。(自分用のメモ)

WebSocket(JSR356)
http://www.jcp.org/en/jsr/detail?id=356

EJB 3.2(JSR345)
http://jcp.org/en/jsr/detail?id=345

JMS 2.0(JSR343)
http://jcp.org/en/jsr/detail?id=343

JAX-RS 2.0(JSR339)
http://jcp.org/en/jsr/detail?id=339

2013年5月18日土曜日

WildFly 8.0.0.Alpha1 をビルド

WildFly 8.0.0.Alpha1 のタグ付けがされたようなので、早速ビルドしてみたよ!

$ cd /path/to
$ git clone https://github.com/wildfly/wildfly.git
$ cd wildfly
$ git tag
7.0.0.Alpha1
7.0.0.Alpha1-final
7.0.0.Beta1
7.0.0.Beta1-prerelease
7.0.0.Beta2
7.0.0.Beta2-prerelease
7.0.0.Beta3
7.0.0.CR1
7.0.0.Final
7.0.0.Final-prerelease
7.0.0.Final-prerelease2
7.0.0.Final-prerelease3
7.0.1.Final
7.0.2.Final
7.0.2.Final-prerelease
7.0.2.SP1-prerelease
7.1.0.Alpha1
7.1.0.Beta1
7.1.0.Beta1b
7.1.0.Beta1b-prerelease
7.1.0.CR1
7.1.0.CR1b
7.1.0.Final
7.1.0.Final-prerelease
7.1.0.Final-prerelease2
7.1.1.Final
7.1.2-prerelease
7.1.2.Final
7.1.3.Beta1
7.1.3.CR1
7.1.3.Final
7.2.0.Final
7.2.0.Final-prerelease1
7.2.0.Final-testsuite-fix
8.0.0.Alpha1

$ git checkout -b new 8.0.0.Alpha1
$ JAVA_HOME=/usr/lib/jvm/java-7-openjdk-i386 ./build.sh -DskipTests

ビルドが終わったら、以下のようにしてインストール先にバイナリを移動します。

$ mv build/target/wildfly-8.0.0.Alpha1/ /usr/local/jboss/

で、起動

$ cd /usr/local/jboss/wildfly-8.0.0.Alpha1
$  JAVA_HOME=/usr/lib/jvm/java-7-openjdk-i386 ./standalone.sh

 以下が表示されれば起動完了!

15:40:49,486 INFO  [org.jboss.as] (Controller Boot Thread) JBAS015874: WildFly 8.0.0.Alpha1 "WildFly" started in 5917ms - Started 154 of 191 services (57 services are lazy, passive or on-demand)
 

2013年5月9日木曜日

WildFly

とりあえず初めての起動。





2013年4月30日火曜日

Java EE 7 リリーススケジュール

5/13 予定のリリーススケジュールの詳細。
https://java.net/projects/javaee-spec/pages/Home#Java_EE_7_Schedule
http://den2sn.hatenablog.com/entry/2013/04/25/075201

予定だと、もう JSR356 は spec release されてもおかしくないんだけど、遅れているのかな?

2013年4月11日木曜日

Atmosphere-jsr356

Atomosphere の JSR356 対応版の github を発見。
https://github.com/Atmosphere/atmosphere-jsr356

今のところ、クラスが2つ入っているだけのラッパーみたいだけど、JBoss でも JSR356 できそうな?

GlassFish4 WebSocket

はい。

WebSocket を JSR356 で実装したいので、しばらくおとなしく GlassFish4 でも使うことにします。

参考ページ乗せますが、既に spec 自体が変わっていてそのままは使えません。
素直に最新 spec 読むのが一番ですw
http://jcp.org/en/jsr/detail?id=356
http://d.hatena.ne.jp/m-prog/20121027/1351324887
https://blogs.oracle.com/arungupta/entry/websocket_applications_using_java_jsr
http://yoshio3.com/2012/11/12/websocket-twitter-timeline-sample/

早く、JBoss でも JSR356 が取り込まれることを期待しますw

2013年4月4日木曜日

JBDS6.0.1

入れてみたけど、AS 7.2 対応はまだみたい。