wildfly-8

I have been trying to configure mysql as a datasource in wildfly. I am not sure what i am missing out, i get an error on startup . I have the mysql-connector-java-5.0.8-bin.jar and the module.xml in the folder: "/wildfly-8.1.0.Final/modules/system/layers/base/com/mysql/main" below are the files module.xml <module xmlns="urn:jboss:module:1.1" name="com.mysql"> <resources> <resource-root path="mysql-connector-java-5.0.8.jar"/> <!-- Insert resources here --> </resources> <dependencies> <module name="javax.api"/> <module name="javax.transaction.api"/> <module name="javax.servlet.api" optional=

I am trying to create REST service using Spring.When I try to access that service it returns proper data but shows - Exception handling request to /RESTServ/user/2: org.springframework.web.util.NestedServletException: Request processing failed; nested exception is java.lang.NullPointerException at org.springframework.web.servlet.FrameworkServlet.processRequest(FrameworkServlet.java:982) [spring-webmvc-4.2.3.RELEASE.jar:4.2.3.RELEASE] at org.springframework.web.servlet.FrameworkServlet.doGet(FrameworkServlet.java:861) [spring-webmvc-4.2.3.RELEASE.jar:4.2.3.RELEASE] at javax.servlet.http

In my web server application I have a method, which modifies an xml document and looks similar to that: @POST @Path("somePath") @Consumes({"application/xml", "application/zip"}) public Response modifyXml() { //some processing } The consumed zip archive contains the xml file which needs to be modified and some other files. How can I distinguish between consumed xml file and the archive inside the method and which kind of method parameter should I use to represent this consumed resource? One solution is to just read from an InputStream . You could wrap the InputStream in a ZipInputStream . With

We have multiple Java web apps packaged as WARs all packaged in an EAR. Our RESTful services are built using JAX-RS and in version specific WARs. We'd like to add static content for each of these version specific WARs, but use the root context (of the WAR) for both the static content and the RESTful service API calls, such that all of the following URLs will work: {hostname}/v1/swagger.yaml <-- Static Content describing the v1 API {hostname}/v1/orders/{uid} <-- JAX-RS RESTful API (v1) {hostname}/v2/swagger.yaml <-- Static Content describing the v2 API {hostname}/v2/orders/{uid} <-- JAX-RS

I have created simple EAR application using Maven archetype: wildfly-javaee7-webapp-ear-blank-archetype/8.2.0.Final http://s17.postimg.org/cy8zbpiu7/Zrzut_ekranu_z_2015_02_13_23_15_10.png My log from starting wildFly: Java HotSpot(TM) 64-Bit Server VM warning: ignoring option MaxPermSize=256m; support was removed in 8.0 23:08:04,244 INFO [org.jboss.modules] (main) JBoss Modules version 1.3.3.Final 23:08:04,690 INFO [org.jboss.msc] (main) JBoss MSC version 1.2.2.Final 23:08:04,787 INFO [org.jboss.as] (MSC service thread 1-8) JBAS015899: WildFly 8.2.0.Final "Tweek" starting 23:08:06,596 INFO

Background I am trying to use bouncy castle library to decrypt private keys in my war. Now I tested the code first in a standalone app and it worked fine. Now when I am testing it as a webapp in Wildfly8.0 am facing some issues with Bouncy castle. The Wildfly 8.0 am using has bouncy castle provider module installed. The BC version being used in v1.46. The code that I have developed uses v1.51. I have followed the steps mentioned here: https://developer.jboss.org/thread/175395 bouncycastle + JBoss AS7: JCE cannot authenticate the provider BC - Specifically followed instructions provided in For

I want secure connection for my web application. So, i want to configure ssl for my wildfly 8.2.0 server. I have created and stored .keystore file in standalone/configuration folder. $ keytool -genkey -alias foo -keyalg RSA -keystore foo.keystore -validity 10950 Enter keystore password: secret Have to add : <subsystem xmlns="urn:jboss:domain:web:1.1" default-virtual-server="default-host" native="false"> <connector name="http" protocol="HTTP/1.1" scheme="http" socket-binding="http" redirect-port="443" /> <connector name="https" scheme="https" protocol="HTTP/1.1" socket-binding="https" enable