May 2013 - jboss-jira - Jboss List Archives

[JBoss JIRA] (DROOLS-153) KieBuilder requires KieModule to contain a KBase to build

by Mario Fusco (JIRA)

[ https://issues.jboss.org/browse/DROOLS-153?page=com.atlassian.jira.plugin... ] Mario Fusco resolved DROOLS-153. -------------------------------- Fix Version/s: 6.0.0.Beta3 Resolution: Done > KieBuilder requires KieModule to contain a KBase to build > ---------------------------------------------------------- > > Key: DROOLS-153 > URL: https://issues.jboss.org/browse/DROOLS-153 > Project: Drools > Issue Type: Bug > Security Level: Public(Everyone can see) > Affects Versions: 6.0.0.Beta2 > Reporter: Michael Anstis > Assignee: Mario Fusco > Fix For: 6.0.0.Beta3 > > > KieBuilder does not build (NPE) if a KJAR depends on another JAR where the parent (i.e. the one depending on the other) does not contain at least one KBase definition in kmodule.xml. > See kie-ci/KieModuleBuilderTest.testKieModuleUsingPOMMissingKBaseDefinition() at http://github.com/droolsjbpm/drools/commit/1f9065e46 > This test is @Ignored at the moment. -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira

13 years, 1 month

1
0
0 / 0

[JBoss JIRA] (DROOLS-153) KieBuilder requires KieModule to contain a KBase to build

by Mario Fusco (JIRA)

[ https://issues.jboss.org/browse/DROOLS-153?page=com.atlassian.jira.plugin... ] Mario Fusco reassigned DROOLS-153: ---------------------------------- Assignee: Mario Fusco (was: Mark Proctor) > KieBuilder requires KieModule to contain a KBase to build > ---------------------------------------------------------- > > Key: DROOLS-153 > URL: https://issues.jboss.org/browse/DROOLS-153 > Project: Drools > Issue Type: Bug > Security Level: Public(Everyone can see) > Affects Versions: 6.0.0.Beta2 > Reporter: Michael Anstis > Assignee: Mario Fusco > > KieBuilder does not build (NPE) if a KJAR depends on another JAR where the parent (i.e. the one depending on the other) does not contain at least one KBase definition in kmodule.xml. > See kie-ci/KieModuleBuilderTest.testKieModuleUsingPOMMissingKBaseDefinition() at http://github.com/droolsjbpm/drools/commit/1f9065e46 > This test is @Ignored at the moment. -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira

13 years, 1 month

1
0
0 / 0

[JBoss JIRA] (AS7-887) Support legacy ServiceMBeans in SAR deployments

by rajesh k (JIRA)

[ https://issues.jboss.org/browse/AS7-887?page=com.atlassian.jira.plugin.sy... ] rajesh k commented on AS7-887: ------------------------------ Thank you, I downloaded last successful build (wildfly-8.x.zip) from wildFly-latest-master. Pl kindly share required jars i can apply to EAP 6.0.1 to fix this issue. Regards, Rajesh. > Support legacy ServiceMBeans in SAR deployments > ----------------------------------------------- > > Key: AS7-887 > URL: https://issues.jboss.org/browse/AS7-887 > Project: Application Server 7 > Issue Type: Enhancement > Components: JMX > Reporter: Matt Drees > Assignee: Eduardo Martins > Fix For: EAP 6.1.0.Alpha (7.2.0.Final) > > > It looks like the current SAR deployment code (jboss-as-sar) will deploy simple MBeans just fine. However, users may expect to be able to deploy older ServiceMBeans from previous Jboss AS versions. Currently, attempting to do this results in a ClassNotFoundException, since the org.jboss.system.ServiceMBean interface doesn't exist anymore. > Ideally this would also involve supporting ServiceMBeans that extend org.jboss.system.ServiceMBeanSupport, which also doesn't exist anymore. -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira

13 years, 1 month

1
0
0 / 0

[JBoss JIRA] (WFLY-1414) Undertow suppresses JAX-RS error message

by Juergen Zimmermann (JIRA)

Juergen Zimmermann created WFLY-1414: ---------------------------------------- Summary: Undertow suppresses JAX-RS error message Key: WFLY-1414 URL: https://issues.jboss.org/browse/WFLY-1414 Project: WildFly Issue Type: Bug Components: REST, Web (Undertow) Affects Versions: 8.0.0.Alpha2 Reporter: Juergen Zimmermann Assignee: Stuart Douglas I'm using a snapshot of WildFly 8.0.0.Alpha2 containing Undertow 1.0.0.Alpha17. My RESTful Web Service in a war is using an ExceptionMapper (see below) which converts an exception into a 404 error code and also an error message. Now I try to submit a GET request resulting in an exception to be mapped. I get the 404 error code, but NOT the error message. Instead I'm getting the contents of the error page which is declared in web.xml for a 404 error. In EAP 6.1.Beta I'm getting the error message produced by the exception mapper. The exception mapper class: @Provider @ApplicationScoped public class NotFoundExceptionMapper implements ExceptionMapper<NotFoundException> { @Override public Response toResponse(NotFoundException e) { final String msg = e.getMessage(); final Response response = Response.status(NOT_FOUND) .type(TEXT_PLAIN) .entity(msg) .build(); return response; } } -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira

13 years, 1 month

1
0
0 / 0

[JBoss JIRA] (WFLY-1368) NumberFormatException in UndertowDeploymentInfoService when war is deployed

by Juergen Zimmermann (JIRA)

[ https://issues.jboss.org/browse/WFLY-1368?page=com.atlassian.jira.plugin.... ] Juergen Zimmermann commented on WFLY-1368: ------------------------------------------ I just cloned WildFly containing Undertow 1.0.0.Alpha17: the issue still exists. > NumberFormatException in UndertowDeploymentInfoService when war is deployed > --------------------------------------------------------------------------- > > Key: WFLY-1368 > URL: https://issues.jboss.org/browse/WFLY-1368 > Project: WildFly > Issue Type: Bug > Components: Web (Undertow) > Affects Versions: 8.0.0.Alpha1 > Reporter: Juergen Zimmermann > Assignee: Stuart Douglas > Attachments: web.xml > > > I compiled WildFly on a Windows box (Win7, x64, JDK 1.7.0_21 32bit). Starting the WildFly appserver without any app works fine. > Next I tried to deploy a war. However, I get the stacktrace below caused by a NumberFormatException. > 14:59:29,806 ERROR [org.jboss.msc.service.fail] MSC000001: Failed to start service jboss.undertow.deployment.default-host./shop2.UndertowDeploymentInfoService: org.jboss.msc.service.StartException in service jboss.undertow.deployment.default-host./shop2.UndertowDeploymentInfoService: Failed to start service > at org.jboss.msc.service.ServiceControllerImpl$StartTask.run(ServiceControllerImpl.java:1930) [jboss-msc-1.1.2.Final.jar:1.1.2.Final] > at java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1145) [rt.jar:1.7.0_21] > at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:615) [rt.jar:1.7.0_21] > at java.lang.Thread.run(Thread.java:722) [rt.jar:1.7.0_21] > Caused by: java.lang.NumberFormatException: null > at java.lang.Integer.parseInt(Integer.java:454) [rt.jar:1.7.0_21] > at java.lang.Integer.parseInt(Integer.java:527) [rt.jar:1.7.0_21] > at org.wildfly.extension.undertow.deployment.UndertowDeploymentInfoService.createServletConfig(UndertowDeploymentInfoService.java:513) > at org.wildfly.extension.undertow.deployment.UndertowDeploymentInfoService.start(UndertowDeploymentInfoService.java:200) > at org.jboss.msc.service.ServiceControllerImpl$StartTask.startService(ServiceControllerImpl.java:1974) [jboss-msc-1.1.2.Final.jar:1.1.2.Final] > at org.jboss.msc.service.ServiceControllerImpl$StartTask.run(ServiceControllerImpl.java:1907) [jboss-msc-1.1.2.Final.jar:1.1.2.Final] > ... 3 more -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira

13 years, 1 month

1
0
0 / 0

[JBoss JIRA] (WFLY-1413) org.wildfly:wildfly-spec-api references hibernate-jpa-2.0-api instead of hibernate-jpa-2.1-api

by Scott Marlow (JIRA)

[ https://issues.jboss.org/browse/WFLY-1413?page=com.atlassian.jira.plugin.... ] Scott Marlow reassigned WFLY-1413: ---------------------------------- Assignee: Shelly McGowan (was: Scott Marlow) > org.wildfly:wildfly-spec-api references hibernate-jpa-2.0-api instead of hibernate-jpa-2.1-api > ---------------------------------------------------------------------------------------------- > > Key: WFLY-1413 > URL: https://issues.jboss.org/browse/WFLY-1413 > Project: WildFly > Issue Type: Bug > Components: JPA / Hibernate > Affects Versions: 8.0.0.Alpha2 > Reporter: Juergen Zimmermann > Assignee: Shelly McGowan > > The maven artifact org.wildfly:wildfly-spec-api references hibernate-jpa-2.0-api instead of hibernate-jpa-2.1-api which is currently available at https://repository.jboss.org/nexus/content/groups/public/org/hibernate/ja... -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira

13 years, 1 month

1
0
0 / 0

[JBoss JIRA] (AS7-887) Support legacy ServiceMBeans in SAR deployments

by Guy Kaisin (JIRA)

[ https://issues.jboss.org/browse/AS7-887?page=com.atlassian.jira.plugin.sy... ] Guy Kaisin commented on AS7-887: -------------------------------- Hi, this link should be useful: https://ci.jboss.org/hudson/job/WildFly-latest-master/ Regards, Guy > Support legacy ServiceMBeans in SAR deployments > ----------------------------------------------- > > Key: AS7-887 > URL: https://issues.jboss.org/browse/AS7-887 > Project: Application Server 7 > Issue Type: Enhancement > Components: JMX > Reporter: Matt Drees > Assignee: Eduardo Martins > Fix For: EAP 6.1.0.Alpha (7.2.0.Final) > > > It looks like the current SAR deployment code (jboss-as-sar) will deploy simple MBeans just fine. However, users may expect to be able to deploy older ServiceMBeans from previous Jboss AS versions. Currently, attempting to do this results in a ClassNotFoundException, since the org.jboss.system.ServiceMBean interface doesn't exist anymore. > Ideally this would also involve supporting ServiceMBeans that extend org.jboss.system.ServiceMBeanSupport, which also doesn't exist anymore. -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira

13 years, 1 month

1
0
0 / 0

[JBoss JIRA] (WFLY-1413) org.wildfly:wildfly-spec-api references hibernate-jpa-2.0-api instead of hibernate-jpa-2.1-api

by Juergen Zimmermann (JIRA)

Juergen Zimmermann created WFLY-1413: ---------------------------------------- Summary: org.wildfly:wildfly-spec-api references hibernate-jpa-2.0-api instead of hibernate-jpa-2.1-api Key: WFLY-1413 URL: https://issues.jboss.org/browse/WFLY-1413 Project: WildFly Issue Type: Bug Components: JPA / Hibernate Affects Versions: 8.0.0.Alpha2 Reporter: Juergen Zimmermann Assignee: Scott Marlow The maven artifact org.wildfly:wildfly-spec-api references hibernate-jpa-2.0-api instead of hibernate-jpa-2.1-api which is currently available at https://repository.jboss.org/nexus/content/groups/public/org/hibernate/ja... -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira

13 years, 1 month

1
0
0 / 0

[JBoss JIRA] (AS7-887) Support legacy ServiceMBeans in SAR deployments

by rajesh k (JIRA)

[ https://issues.jboss.org/browse/AS7-887?page=com.atlassian.jira.plugin.sy... ] rajesh k commented on AS7-887: ------------------------------ Pl kindly tell me which corrected jars i can use for Jboss EAP 6.0.1. Can you pl send any nightly build link if you have. Thanks Rajesh > Support legacy ServiceMBeans in SAR deployments > ----------------------------------------------- > > Key: AS7-887 > URL: https://issues.jboss.org/browse/AS7-887 > Project: Application Server 7 > Issue Type: Enhancement > Components: JMX > Reporter: Matt Drees > Assignee: Eduardo Martins > Fix For: EAP 6.1.0.Alpha (7.2.0.Final) > > > It looks like the current SAR deployment code (jboss-as-sar) will deploy simple MBeans just fine. However, users may expect to be able to deploy older ServiceMBeans from previous Jboss AS versions. Currently, attempting to do this results in a ClassNotFoundException, since the org.jboss.system.ServiceMBean interface doesn't exist anymore. > Ideally this would also involve supporting ServiceMBeans that extend org.jboss.system.ServiceMBeanSupport, which also doesn't exist anymore. -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira

13 years, 1 month

1
0
0 / 0

[JBoss JIRA] (WFLY-1412) Hibernate Metamodel Generator is not aware of persistence.xml for JPA 2.1

by Juergen Zimmermann (JIRA)

[ https://issues.jboss.org/browse/WFLY-1412?page=com.atlassian.jira.plugin.... ] Juergen Zimmermann commented on WFLY-1412: ------------------------------------------ https://hibernate.atlassian.net/browse/METAGEN-92 > Hibernate Metamodel Generator is not aware of persistence.xml for JPA 2.1 > ------------------------------------------------------------------------- > > Key: WFLY-1412 > URL: https://issues.jboss.org/browse/WFLY-1412 > Project: WildFly > Issue Type: Bug > Components: JPA / Hibernate > Affects Versions: 8.0.0.Alpha2 > Reporter: Juergen Zimmermann > Assignee: Scott Marlow > > I'm using a snapshot of WildFly Alpha2. > The latest usable version of the Hibernate Metamodel Generator is 1.2.0.Final which is only aware of JPA 2.1. If I use a persistence.xml with the new namespace for JPA 2.1, then I get the following (serious?) warning during compilation. I'm not sure whether this is a WildFly or a Hibernate warning. > [WARNING] Hibernate JPA 2 Static-Metamodel Generator 1.2.0.Final > [WARNING] Error unmarshalling /META-INF/persistence.xml with exception : > javax.xml.bind.UnmarshalException > - with linked exception: > [org.xml.sax.SAXParseException; lineNumber: 12; columnNumber: 28; cvc-elt.1: Deklaration des Elements "persistence" kann nicht gefunden werden.] > > This is the beginning of persistence.xml: > <?xml version="1.0"?> >  > <persistence xmlns="http://xmlns.jcp.org/xml/ns/persistence" > xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance" > xsi:schemaLocation="http://xmlns.jcp.org/xml/ns/persistence http://xmlns.jcp.org/xml/ns/persistence/persistence_2_1.xsd" > version="2.1">  > <persistence-unit name="de.shop.PU"> -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira

13 years, 1 month

1
0
0 / 0

2026

2025

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

2009

2008

2007

2006

jboss-jira May 2013