[JBoss JIRA] (WFLY-4171) Provide an html5 archetype for wildfly
by Fred Bricon (JIRA)
[ https://issues.jboss.org/browse/WFLY-4171?page=com.atlassian.jira.plugin.... ]
Fred Bricon commented on WFLY-4171:
-----------------------------------
Same issue in profile aerogearci-jbossas-managed-7... which needs to be renamed to something wildfly
> Provide an html5 archetype for wildfly
> --------------------------------------
>
> Key: WFLY-4171
> URL: https://issues.jboss.org/browse/WFLY-4171
> Project: WildFly
> Issue Type: Feature Request
> Reporter: Fred Bricon
> Assignee: Rafael Benevides
>
> We'd like to provide a Wildfly-ified version of the html5 archetype in JBoss Central, for JBoss Tools and Developer Studio, The current versions we serve right now are :
> * org.jboss.aerogear.archetypes:jboss-html5-mobile-archetype:7.1.3.Final
> * org.jboss.archetype.wfk:jboss-html5-mobile-archetype:2.6.0.Final
--
This message was sent by Atlassian JIRA
(v6.3.11#6341)
11 years, 5 months
[JBoss JIRA] (WFLY-4171) Provide an html5 archetype for wildfly
by Fred Bricon (JIRA)
[ https://issues.jboss.org/browse/WFLY-4171?page=com.atlassian.jira.plugin.... ]
Fred Bricon edited comment on WFLY-4171 at 1/20/15 5:26 PM:
------------------------------------------------------------
In the HTML5 archetypes, annoying warnings that could be avoided on :
{noformat}
<profile>
<id>arq-wildfly-managed</id>
<dependencies>
<dependency>
<groupId>org.wildfly</groupId>
<artifactId>wildfly-arquillian-container-managed</artifactId>
<version>${version.arquillian.container}</version>
<scope>test</scope>
</dependency>
</dependencies>
...
<profile>
<!-- An optional Arquillian testing profile that executes tests
in a remote WildFly instance -->
<!-- Run with: mvn clean test -Parq-wildfly-remote -->
<id>arq-wildfly-remote</id>
<dependencies>
<dependency>
<groupId>org.wildfly</groupId>
<artifactId>wildfly-arquillian-container-remote</artifactId>
<version>${version.arquillian.container}</version>
<scope>test</scope>
</dependency>
</dependencies>
</profile>
{noformat}
This expression (${version.arquillian.container}) evaluates to 8.0.0.Final The property is defined in foo.bar:blank:0.0.1-SNAPSHOT
warning Overriding managed version 8.2.0.Final for wildfly-arquillian-container-managed
<version.arquillian.container>8.0.0.Final</version.arquillian.container> can be removed altogether
was (Author: fbricon):
Annoying warnings that could be avoided on :
{noformat}
<profile>
<id>arq-wildfly-managed</id>
<dependencies>
<dependency>
<groupId>org.wildfly</groupId>
<artifactId>wildfly-arquillian-container-managed</artifactId>
<version>${version.arquillian.container}</version>
<scope>test</scope>
</dependency>
</dependencies>
...
<profile>
<!-- An optional Arquillian testing profile that executes tests
in a remote WildFly instance -->
<!-- Run with: mvn clean test -Parq-wildfly-remote -->
<id>arq-wildfly-remote</id>
<dependencies>
<dependency>
<groupId>org.wildfly</groupId>
<artifactId>wildfly-arquillian-container-remote</artifactId>
<version>${version.arquillian.container}</version>
<scope>test</scope>
</dependency>
</dependencies>
</profile>
{noformat}
This expression (${version.arquillian.container}) evaluates to 8.0.0.Final The property is defined in foo.bar:blank:0.0.1-SNAPSHOT
warning Overriding managed version 8.2.0.Final for wildfly-arquillian-container-managed
<version.arquillian.container>8.0.0.Final</version.arquillian.container> can be removed altogether
> Provide an html5 archetype for wildfly
> --------------------------------------
>
> Key: WFLY-4171
> URL: https://issues.jboss.org/browse/WFLY-4171
> Project: WildFly
> Issue Type: Feature Request
> Reporter: Fred Bricon
> Assignee: Rafael Benevides
>
> We'd like to provide a Wildfly-ified version of the html5 archetype in JBoss Central, for JBoss Tools and Developer Studio, The current versions we serve right now are :
> * org.jboss.aerogear.archetypes:jboss-html5-mobile-archetype:7.1.3.Final
> * org.jboss.archetype.wfk:jboss-html5-mobile-archetype:2.6.0.Final
--
This message was sent by Atlassian JIRA
(v6.3.11#6341)
11 years, 5 months
[JBoss JIRA] (WFLY-4171) Provide an html5 archetype for wildfly
by Fred Bricon (JIRA)
[ https://issues.jboss.org/browse/WFLY-4171?page=com.atlassian.jira.plugin.... ]
Fred Bricon commented on WFLY-4171:
-----------------------------------
Annoying warnings that could be avoided on :
{noformat}
<profile>
<id>arq-wildfly-managed</id>
<dependencies>
<dependency>
<groupId>org.wildfly</groupId>
<artifactId>wildfly-arquillian-container-managed</artifactId>
<version>${version.arquillian.container}</version>
<scope>test</scope>
</dependency>
</dependencies>
...
<profile>
<!-- An optional Arquillian testing profile that executes tests
in a remote WildFly instance -->
<!-- Run with: mvn clean test -Parq-wildfly-remote -->
<id>arq-wildfly-remote</id>
<dependencies>
<dependency>
<groupId>org.wildfly</groupId>
<artifactId>wildfly-arquillian-container-remote</artifactId>
<version>${version.arquillian.container}</version>
<scope>test</scope>
</dependency>
</dependencies>
</profile>
{noformat}
This expression (${version.arquillian.container}) evaluates to 8.0.0.Final The property is defined in foo.bar:blank:0.0.1-SNAPSHOT
warning Overriding managed version 8.2.0.Final for wildfly-arquillian-container-managed
<version.arquillian.container>8.0.0.Final</version.arquillian.container> can be removed altogether
> Provide an html5 archetype for wildfly
> --------------------------------------
>
> Key: WFLY-4171
> URL: https://issues.jboss.org/browse/WFLY-4171
> Project: WildFly
> Issue Type: Feature Request
> Reporter: Fred Bricon
> Assignee: Rafael Benevides
>
> We'd like to provide a Wildfly-ified version of the html5 archetype in JBoss Central, for JBoss Tools and Developer Studio, The current versions we serve right now are :
> * org.jboss.aerogear.archetypes:jboss-html5-mobile-archetype:7.1.3.Final
> * org.jboss.archetype.wfk:jboss-html5-mobile-archetype:2.6.0.Final
--
This message was sent by Atlassian JIRA
(v6.3.11#6341)
11 years, 5 months
[JBoss JIRA] (WFCORE-511) "Reload" support for embedded server
by Brian Stansberry (JIRA)
[ https://issues.jboss.org/browse/WFCORE-511?page=com.atlassian.jira.plugin... ]
Brian Stansberry commented on WFCORE-511:
-----------------------------------------
There probably should be a reload method in the embedded server API (e.g. StandaloneServer) as well, so the caller can invoke that and the StandaloneServer handles the reload and blocking until the new MCC is available.
> "Reload" support for embedded server
> ------------------------------------
>
> Key: WFCORE-511
> URL: https://issues.jboss.org/browse/WFCORE-511
> Project: WildFly Core
> Issue Type: Feature Request
> Components: Server
> Reporter: Brian Stansberry
>
> The current embedded server stuff doesn't handle a server reload. It creates a ModelControllerClient and then holds it forever. But the ModelController backed by that MCC will be invalid after a reload.
> Key thing is to register a listener with the ControlledProcessStateService, and in callbacks deal with the reload and establish a new MCC. Nice to have is to make the MCC returned by StandaloneServer.getModelControllerClient() a facade that delegates to whatever the current "live" MCC is.
--
This message was sent by Atlassian JIRA
(v6.3.11#6341)
11 years, 5 months
[JBoss JIRA] (WFLY-4174) Xalan Linkage error : TransformerConfigurationException
by Yu Feng (JIRA)
[ https://issues.jboss.org/browse/WFLY-4174?page=com.atlassian.jira.plugin.... ]
Yu Feng commented on WFLY-4174:
-------------------------------
I want to add something -- I see the same error, but in different scenarios. I have two servers A and B in the cluster. There is some XSL processing work in the server. When A processes it or when B processes it, it all works fine. But when I start using Infinispan's DistributedExecutorService to distribute work in the cluster, the error happen and it only happens on remote server. E.g. if server A is executing and distribute the same task to A and B, A works fine (including the XSL work), and B always gets error. If server B is executing, then B works fine and A gets this Linkage error. Any ideas?
> Xalan Linkage error : TransformerConfigurationException
> -------------------------------------------------------
>
> Key: WFLY-4174
> URL: https://issues.jboss.org/browse/WFLY-4174
> Project: WildFly
> Issue Type: Bug
> Components: Class Loading
> Affects Versions: 8.2.0.Final
> Environment: Wildfly 8.1 & 8.2-Final
> JDK 1.7.0_45 & 1.7.0_71
> Windows & Linux
> Reporter: Stephen Kay
> Assignee: David Lloyd
> Priority: Critical
>
> Please note that this bug wasn't present on JBoss 7.1 / same WAR artifact
> This is full staktrace from our applicaion.
> 11:13:32,130 SEVERE ch.mitsa.credoc.ui.views.messages.MessagesTable (default task-9) Error getting message payload: : javax.xml.transform.TransformerConfigurationException: Translet class loaded, but unable to create translet instance.
> at com.sun.org.apache.xalan.internal.xsltc.trax.TemplatesImpl.defineTransletClasses(TemplatesImpl.java:369) rt.jar:1.7.0_71
> at com.sun.org.apache.xalan.internal.xsltc.trax.TemplatesImpl.getTransletInstance(TemplatesImpl.java:383) rt.jar:1.7.0_71
> at com.sun.org.apache.xalan.internal.xsltc.trax.TemplatesImpl.newTransformer(TemplatesImpl.java:418) rt.jar:1.7.0_71
> at com.sun.org.apache.xalan.internal.xsltc.trax.TransformerFactoryImpl.newTransformer(TransformerFactoryImpl.java:765) rt.jar:1.7.0_71
> at _redirected.TransformerFactory.newTransformer(_TransformerFactory.java:132) jboss-modules.jar:1.3.3.Final
> at ch.mitsa.credoc.format.swift.impl.SwiftFormatter.getPrettyPrintedPayload(SwiftFormatter.java:196)
> at ch.mitsa.credoc.engine.service.OutputService.getPrettyPrintedMessage(OutputService.java:54)
> at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method) rt.jar:1.7.0_71
> at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:57) rt.jar:1.7.0_71
> at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43) rt.jar:1.7.0_71
> at java.lang.reflect.Method.invoke(Method.java:606) rt.jar:1.7.0_71
> at org.jboss.as.ee.component.ManagedReferenceMethodInterceptor.processInvocation(ManagedReferenceMethodInterceptor.java:52)
> at org.jboss.invocation.InterceptorContext.proceed(InterceptorContext.java:309)
> at org.jboss.invocation.WeavedInterceptor.processInvocation(WeavedInterceptor.java:53)
> at org.jboss.as.ee.component.interceptors.UserInterceptorFactory$1.processInvocation(UserInterceptorFactory.java:63)
> at org.jboss.invocation.InterceptorContext.proceed(InterceptorContext.java:309)
> at org.jboss.invocation.InterceptorContext$Invocation.proceed(InterceptorContext.java:407)
> at org.jboss.as.weld.ejb.Jsr299BindingsInterceptor.doMethodInterception(Jsr299BindingsInterceptor.java:82) wildfly-weld-8.2.0.Final.jar:8.2.0.Final
> (...)
--
This message was sent by Atlassian JIRA
(v6.3.11#6341)
11 years, 5 months
[JBoss JIRA] (WFLY-4273) EJBClient message "Unsupported message received with header 0xffffffff" generated when reconnecting to a non-clustered server
by Richard Achmatowicz (JIRA)
[ https://issues.jboss.org/browse/WFLY-4273?page=com.atlassian.jira.plugin.... ]
Richard Achmatowicz updated WFLY-4273:
--------------------------------------
Fix Version/s: 9.0.0.Beta1
> EJBClient message "Unsupported message received with header 0xffffffff" generated when reconnecting to a non-clustered server
> -----------------------------------------------------------------------------------------------------------------------------
>
> Key: WFLY-4273
> URL: https://issues.jboss.org/browse/WFLY-4273
> Project: WildFly
> Issue Type: Bug
> Components: EJB
> Affects Versions: 8.0.0.Final
> Reporter: Richard Achmatowicz
> Assignee: Richard Achmatowicz
> Fix For: 9.0.0.Beta1
>
>
> The EJBClient protocol handler on the server side, org.jboss.as.ejb3.remote.protocol.versionone.VersionOneProtocolChannelReceiver, will send out a full cluster topology report to a connecting EJBClient. This will happen in particular when the client reconnects after a server which was initially up went down and came up again.
> If the server is not clustered, the report gets sent out anyway, and erroneously with an empty message body. This message gets processed on the client side by org.jboss.ejb.client.remoting.ChannelAssociation.processResponse() which cannot recognize the message header. The exception results.
> One way to fix this is to only send out the cluster topology message if the node is actually clustered.
>
--
This message was sent by Atlassian JIRA
(v6.3.11#6341)
11 years, 5 months
[JBoss JIRA] (WFLY-4271) Wildfly BOM wrong dependencies
by Vsevolod Golovanov (JIRA)
[ https://issues.jboss.org/browse/WFLY-4271?page=com.atlassian.jira.plugin.... ]
Vsevolod Golovanov updated WFLY-4271:
-------------------------------------
Description:
1. The BOM {{org.wildfly.bom:jboss-javaee-7.0-with-all:8.2.1.Final}} (indirectly) imports {{org.jboss.resteasy:resteasy-jaxrs-all:3.0.10.Final}} that has the following dependencies:
{code}
<version.io.undertow>1.0.1.Final</version.io.undertow>
...
<dependency>
<groupId>io.undertow</groupId>
<artifactId>undertow-servlet</artifactId>
<version>${version.io.undertow}</version>
</dependency>
<dependency>
<groupId>io.undertow</groupId>
<artifactId>undertow-core</artifactId>
<version>${version.io.undertow}</version>
</dependency>
{code}
The version should be 1.1.0.Final. The wrong version ends up being the effective one in dependencyManagement, messes up debugging in Eclipse, and probably compiling in Eclipse.
2. {{org.wildfly.bom:jboss-bom-parent:8.2.1.Final}}:
{code}
<version.org.hibernate-jpamodelgen>4.3.5.Final</version.org.hibernate-jpamodelgen>
{code}
, which affects {{org.wildfly.bom:jboss-javaee-7.0-with-hibernate:8.2.1.Final}}:
{code}
<dependency>
<groupId>org.hibernate</groupId>
<artifactId>hibernate-jpamodelgen</artifactId>
<version>${version.org.hibernate-jpamodelgen}</version>
</dependency>
{code}
Hibernate 4.3.7.Final from SourceForge has jpamodelgen 4.3.7.Final supplied.
Hoping for a BOM 8.2.2.Final release, because our project POMs are complex enough without workarounds for such errors.
was:
1. The BOM {{org.wildfly.bom:jboss-javaee-7.0-with-all:8.2.1.Final}} (indirectly) imports {{org.jboss.resteasy:resteasy-jaxrs-all:3.0.10.Final}} that has the following dependencies:
{code}
<version.io.undertow>1.0.1.Final</version.io.undertow>
...
<dependency>
<groupId>io.undertow</groupId>
<artifactId>undertow-servlet</artifactId>
<version>${version.io.undertow}</version>
</dependency>
<dependency>
<groupId>io.undertow</groupId>
<artifactId>undertow-core</artifactId>
<version>${version.io.undertow}</version>
</dependency>
{code}
The version should be 1.1.0.Final. The wrong version messes up debugging in Eclipse, and probably compiling in Eclipse.
2. {{org.wildfly.bom:jboss-bom-parent:8.2.1.Final}}:
{code}
<version.org.hibernate-jpamodelgen>4.3.5.Final</version.org.hibernate-jpamodelgen>
{code}
, which affects {{org.wildfly.bom:jboss-javaee-7.0-with-hibernate:8.2.1.Final}}:
{code}
<dependency>
<groupId>org.hibernate</groupId>
<artifactId>hibernate-jpamodelgen</artifactId>
<version>${version.org.hibernate-jpamodelgen}</version>
</dependency>
{code}
Hibernate 4.3.7.Final from SourceForge has jpamodelgen 4.3.7.Final supplied.
Hoping for a BOM 8.2.2.Final release, because our project POMs are complex enough without workarounds for such errors.
> Wildfly BOM wrong dependencies
> ------------------------------
>
> Key: WFLY-4271
> URL: https://issues.jboss.org/browse/WFLY-4271
> Project: WildFly
> Issue Type: Bug
> Affects Versions: 8.2.0.Final
> Environment: Wildfly 8.2.0.Final, BOM org.wildfly.bom:jboss-javaee-7.0-with-all:8.2.1.Final
> Reporter: Vsevolod Golovanov
> Assignee: Tomaz Cerar
>
> 1. The BOM {{org.wildfly.bom:jboss-javaee-7.0-with-all:8.2.1.Final}} (indirectly) imports {{org.jboss.resteasy:resteasy-jaxrs-all:3.0.10.Final}} that has the following dependencies:
> {code}
> <version.io.undertow>1.0.1.Final</version.io.undertow>
> ...
> <dependency>
> <groupId>io.undertow</groupId>
> <artifactId>undertow-servlet</artifactId>
> <version>${version.io.undertow}</version>
> </dependency>
> <dependency>
> <groupId>io.undertow</groupId>
> <artifactId>undertow-core</artifactId>
> <version>${version.io.undertow}</version>
> </dependency>
> {code}
> The version should be 1.1.0.Final. The wrong version ends up being the effective one in dependencyManagement, messes up debugging in Eclipse, and probably compiling in Eclipse.
> 2. {{org.wildfly.bom:jboss-bom-parent:8.2.1.Final}}:
> {code}
> <version.org.hibernate-jpamodelgen>4.3.5.Final</version.org.hibernate-jpamodelgen>
> {code}
> , which affects {{org.wildfly.bom:jboss-javaee-7.0-with-hibernate:8.2.1.Final}}:
> {code}
> <dependency>
> <groupId>org.hibernate</groupId>
> <artifactId>hibernate-jpamodelgen</artifactId>
> <version>${version.org.hibernate-jpamodelgen}</version>
> </dependency>
> {code}
> Hibernate 4.3.7.Final from SourceForge has jpamodelgen 4.3.7.Final supplied.
> Hoping for a BOM 8.2.2.Final release, because our project POMs are complex enough without workarounds for such errors.
--
This message was sent by Atlassian JIRA
(v6.3.11#6341)
11 years, 5 months