December 2011 - jboss-dev-forums - Jboss List Archives

Unable to deploy JBoss BRMS 5.2.0 on IBM Websphere v8.0

by Tinu Bansal

Hi I am working on JBoss BRMS 5.2.0. I am trying to deploy it on IBM Websphere Application Server v8.0. I am struck with a problem and unable to resolve it. The problem is as mentioned below: When I am deploying BRMS 5.2 on Websphere 8, I am getting the following exception : com.ibm.ws.webcontainer.webapp.WebApp logServletError SRVE0293E: [Servlet Error]-[GenericServletWrapper]: java.lang.ClassNotFoundException: class java.lang.ClassNotFoundException: org.jboss.seam.web.ContextFilter Presently, I am using default seam jars provided in the BRMS setup : jboss-seam-2.2.4.EAP5.jar and : jboss-seam-remoting-2.2.4.EAP5.jar I have tried it with different versions of Seam Jars also. However, it is giving class not found exception in every case. Could you please help me out in resolving the issue? The Development Environment Specifications are as mentioned below: 1. Operating System : Microsoft Windows 7 2. IDE : IBM Rational Application Developer (Version 8.0.3) --> RAD8 3. Application Server : IBM Websphere Application Server (Version 8.0) --> WAS8 4. Module : JBoss BRMS (Version 5.2.0) --> jboss-brms.war ---------------------------------------------------------------------------------------------------------------------------------------------- I have tested 3 Scenarios: 1. Running the original jboss-brms.war on WAS8 2. Adding slf4j-api-1.6.0.jar and slf4j-log12-1.6.0.jar to the "lib" folder at "IBM\WebSphere\AppServer\lib" And running the jboss-brms.war on WAS8, after restarting the server. 3. Adding slf4j-api-1.6.0.jar and slf4j-log12-1.6.0.jar to the "lib" folder of "jboss-brms.war" And running the jboss-brms.war on WAS8, after restarting the server. ----------------------------------------------------------- Scenario 1----------------------------------------------------------------------- Scenario 1 : Running the original jboss-brms.war on WAS8. I am getting the following exceptions : [12/13/11 15:01:54:381 IST] 0000003c AlarmThreadMo W UTLS0008W: The return of alarm thread "Non-deferrable Alarm : 0" (00000004) to the alarm thread pool has been delayed for 10652 milliseconds. This may be preventing normal alarm function within the application server. The alarm listener stack trace is as follows: [12/13/11 15:02:01:594 IST] 00000004 AlarmThreadMo W UTLS0009W: Alarm Thread "Non-deferrable Alarm : 0" (00000004) previously reported to be delayed has now completed. It was active for approximately 17955 milliseconds. [12/13/11 15:02:07:166 IST] 0000001f annotation W com.ibm.ws.webcontainer.annotation.WASAnnotationHelper collectClasses SRVE8000W: Skipped class that failed to initialize for annotation scanning. java.lang.ClassNotFoundException: org.jboss.seam.servlet.SeamListener [12/13/11 15:02:07:248 IST] 0000001f annotation W com.ibm.ws.webcontainer.annotation.WASAnnotationHelper collectClasses SRVE8000W: Skipped class that failed to initialize for annotation scanning. java.lang.ClassNotFoundException: org.jboss.seam.web.ContextFilter [12/13/11 15:02:07:486 IST] 0000001f InjectionProc W CWNEN0047W: Resource annotations on the fields of the net.sf.webdav.WebDavServletBean class will be ignored. The annotations could not be obtained because of the exception : java.lang.NoClassDefFoundError: org.slf4j.Logger The complete stack trace is in the attached log files. Log files attached for Scenario 1 : Scenario1.zip --> SystemOut.log.txt , SystemErr.log.txt --> 2 files ----------------------------------------------------------- Scenario 2----------------------------------------------------------------------- Scenario 2 : Adding slf4j-api-1.6.0.jar and slf4j-log12-1.6.0.jar to the "lib" folder at "IBM\WebSphere\AppServer\lib" And running the jboss-brms.war on WAS8, after restarting the server. I am getting the following exceptions : Same as Scenario 1 The complete stack trace is in the attached log files. Log files attached for Scenario 2 : Scenario2.zip --> SystemOut.log.txt , SystemErr.log.txt --> 2 files ----------------------------------------------------------- Scenario 3----------------------------------------------------------------------- Scenario 3 : Adding slf4j-api-1.6.0.jar and slf4j-log12-1.6.0.jar to the "lib" folder of "jboss-brms.war" And running the jboss-brms.war on WAS8, after restarting the server. I am getting the following exceptions : [12/13/11 15:53:35:206 IST] 00000055 AlarmThreadMo W UTLS0008W: The return of alarm thread "Non-deferrable Alarm : 1" (00000016) to the alarm thread pool has been delayed for 18286 milliseconds. This may be preventing normal alarm function within the application server. The alarm listener stack trace is as follows: at com.ibm.ws.util.ThreadPool$Worker.disableHungThreadDetection(ThreadPool.java:1710) [12/13/11 15:53:41:083 IST] 00000043 annotation W com.ibm.ws.webcontainer.annotation.WASAnnotationHelper collectClasses SRVE8000W: Skipped class that failed to initialize for annotation scanning. java.lang.ClassNotFoundException: org.jboss.seam.servlet.SeamListener [12/13/11 15:53:41:318 IST] 00000043 annotation W com.ibm.ws.webcontainer.annotation.WASAnnotationHelper collectClasses SRVE8000W: Skipped class that failed to initialize for annotation scanning. java.lang.ClassNotFoundException: org.jboss.seam.web.ContextFilter [12/13/11 15:53:49:176 IST] 00000043 SystemErr R SLF4J: Class path contains multiple SLF4J bindings. [12/13/11 15:53:49:211 IST] 00000043 SystemErr R SLF4J: Found binding in [bundleresource://213.fwk34567131:1/org/slf4j/impl/StaticLoggerBinder.class] [12/13/11 15:53:49:212 IST] 00000043 SystemErr R SLF4J: Found binding in [wsjar:file:/C:/Users/tinu_bansal/Desktop/AllWorkspaces/IBMWorkspaces/Workspace29/.metadata/.plugins/org.eclipse.wst.server.core/tmp1/jboss-brms/WEB-INF/lib/slf4j-log4j12-1.6.0.jar!/org/slf4j/impl/StaticLoggerBinder.class] [12/13/11 15:53:49:212 IST] 00000043 SystemErr R SLF4J: See http://www.slf4j.org/codes.html#multiple_bindings for an explanation. The complete stack trace is in the attached log files. Log files attached for Scenario 3 : Scenario3.zip --> SystemOut.log.txt , SystemErr.log.txt -->2 files Regards Tinu +918686177200 **************** CAUTION - Disclaimer ***************** This e-mail contains PRIVILEGED AND CONFIDENTIAL INFORMATION intended solely for the use of the addressee(s). If you are not the intended recipient, please notify the sender by e-mail and delete the original message. Further, you are not to copy, disclose, or distribute this e-mail or its contents to any other person and any such actions are unlawful. This e-mail may contain viruses. Infosys has taken every reasonable precaution to minimize this risk, but is not liable for any damage you may sustain as a result of any virus in this e-mail. You should carry out your own virus checks before opening the e-mail or attachment. Infosys reserves the right to monitor and review the content of all messages sent to or from this e-mail address. Messages sent to or from this e-mail address may be stored on the Infosys e-mail system. ***INFOSYS******** End of Disclaimer ********INFOSYS***

14 years

1
0
0 / 0

[JBoss Web Services Development] - Need to send a Secure XML message

by Kavitha Kannan

Kavitha Kannan [http://community.jboss.org/people/kaviamar] created the discussion "Need to send a Secure XML message" To view the discussion, visit: http://community.jboss.org/message/641206#641206 -------------------------------------------------------------- Hi, I am new to the development of web services.. I am given a task of creating a Request xml as given below.. <SOAP-ENV:Envelope xmlns:SOAP-ENV= http://www.w3.org/2003/05/soap-envelope http://www.w3.org/2003/05/soap-envelope xmlns:xsd= http://www.w3.org/2001/XMLSchema http://www.w3.org/2001/XMLSchema xmlns:a=" http://www.w3.org/2005/08/addressing http://www.w3.org/2005/08/addressing" xmlns:xsi=" http://www.w3.org/2001/XMLSchema-instance http://www.w3.org/2001/XMLSchema-instance"> <SOAP-ENV:Header> <a:Action s:mustUnderstand="1"> http://www.microsoftonline.com/MOSI/1/0/action/AddDomain http://www.microsoftonline.com/MOSI/1/0/action/AddDomain </a:Action> <BecContext xmlns=" http://becwebservice.microsoftonline.com/ http://becwebservice.microsoftonline.com/"> </BecContext> <a:MessageID> urn:uuid:7feaf58d-93bd-4597-aecd-be7f768f5bbb </a:MessageID> <a:ReplyTo> <a:Address> http://www.w3.org/2005/08/addressing/anonymous http://www.w3.org/2005/08/addressing/anonymous</a:Address> </a:ReplyTo> <a:To s:mustUnderstand="1" u:Id="_1"> https://qa1mosi.redmond.corp.microsoft.com:11443/Syndication/DomainManage... https://qa1mosi.redmond.corp.microsoft.com:11443/Syndication/DomainManage... </a:To> <wsse:Security SOAP-ENV:mustUnderstand="true" xmlns:wsse=" http://docs.oasis-open.org/wss/2004/01/oasis-200401 http://docs.oasis-open.org/wss/2004/01/oasis-200401- wss-wssecurity-secext-1.0.xsd"> <u:Timestamp u:Id="_0"> <u:Created>2011-02-15T22:58:34.861Z</u:Created> <u:Expires>2011-02-15T23:03:34.861Z</u:Expires> </u:Timestamp> <ds:Signature xmlns:ds=" http://www.w3.org/2000/09/xmldsig http://www.w3.org/2000/09/xmldsig#"> <ds:SignedInfo> <ds:CanonicalizationMethod Algorithm=" http://www.w3.org/2001/10/xml-exc-c14n#"/ http://www.w3.org/2001/10/xml-exc-c14n#"/> <ds:SignatureMethod Algorithm=" http://www.w3.org/2000/09/xmldsig#rsa-sha1"/ http://www.w3.org/2000/09/xmldsig#rsa-sha1"/> <ds:Reference URI="#id-3307594"> <ds:Transforms> <ds:Transform Algorithm=" http://www.w3.org/2001/10/xml-exc-c14n#"/ http://www.w3.org/2001/10/xml-exc-c14n#"/> </ds:Transforms> <ds:DigestMethod Algorithm=" http://www.w3.org/2000/09/xmldsig#sha1"/ http://www.w3.org/2000/09/xmldsig#sha1"/> <ds:DigestValue> ACM0FDySGCZLmajV1etsrHqU4GY= </ds:DigestValue> </ds:Reference> </ds:SignedInfo> <ds:SignatureValue> yuc7jAgrak53B+oP6AFJDzNg16fPAtbQjmgYyUlY1OfOLNvwmNtOohP5g 0XVu521sWTqaWYKrg3sOaa4DQgbkw== </ds:SignatureValue> <ds:KeyInfo Id="KeyId-22700073"> <wsse:SecurityTokenReference wsu:Id="STRId-12245160" xmlns:wsu=" http://docs.oasis-open.org/wss/2004/01/oasis http://docs.oasis-open.org/wss/2004/01/oasis- 200401-wss-wssecurity-utility-1.0.xsd"> <ds:X509IssuerSerial> <ds:X509IssuerName> CN=dims </ds:X509IssuerName> <ds:X509SerialNumber> 44369778256217224370984914847992022613 </ds:X509SerialNumber> </ds:X509IssuerSerial> </wsse:SecurityTokenReference> </ds:KeyInfo> </ds:Signature> </wsse:Security> </SOAP-ENV:Header> <SOAP-ENV:Body wsu:Id="id-3307594" xmlns:wsu=" http://docs.oasis-open.org/wss/2004/01/oasis http://docs.oasis-open.org/wss/2004/01/oasis- 200401-wss-wssecurity-utility-1.0.xsd"> <sayHello xmlns=" http://jeffhanson.com/services/helloworld http://jeffhanson.com/services/helloworld"> <value xmlns=""> Hello world! </value> </sayHello> </SOAP-ENV:Body> </SOAP-ENV:Envelope> Could anybody please help me in telling what all the things i need to do for development of the above XML. Thanks in advance.. -------------------------------------------------------------- Reply to this message by going to Community [http://community.jboss.org/message/641206#641206] Start a new discussion in JBoss Web Services Development at Community [http://community.jboss.org/choose-container!input.jspa?contentType=1&cont...]

14 years

1
0
0 / 0

[EJB Development] - java client use ejb remote service, exception(jboss5.0 + jdk1.6)

by princesshan1977 princesshan1977

princesshan1977 princesshan1977 [http://community.jboss.org/people/princesshan1977] created the discussion "java client use ejb remote service, exception(jboss5.0 + jdk1.6)" To view the discussion, visit: http://community.jboss.org/message/641181#641181 -------------------------------------------------------------- I use myeclise + jboss-5.1.0.GA + jdk1.6 service code like this @Remote public interface IHelloEJBService { public String sayHelloEJB(String name); } @Stateless public class HelloEJBService implements IHelloEJBService { public String sayHelloEJB(String name) { // TODO Auto-generated method stub String msg = "hello" + name + ", Welcome to EJB world!"; System.out.print(msg); return msg; } } then I deploy the service。 I create a new java client project，code like this public class TestClient { private static Context context; /** * @param args */ public static void main(String[] args) { try { Context ctx = getInitialContext(); Object object = ctx.lookup("HelloEJBService/remote"); IHelloEJBService service= (IHelloEJBService)PortableRemoteObject.narrow(object, IHelloEJBService.class); System.out.println(service.sayHelloEJB("Client ")); } catch(Exception e) { e.printStackTrace(); } } protected static Context getInitialContext() throws Exception { if(context == null) { Hashtable props = new Hashtable(); props.put(Context.INITIAL_CONTEXT_FACTORY, "org.jnp.interfaces.NamingContextFactory"); props.put(Context.URL_PKG_PREFIXES, "org.jboss.naming:org.jnp.interfaces"); props.put(Context.PROVIDER_URL, "jnp://localhost:1099"); context = new InitialContext(props); } return context; } } I copy all jars of D:\jboss-5.1.0.GA\client\ to client project and add all to classpath. run the client code ，occur exception javax.naming.NamingException: Could not dereference object [Root exception is java.lang.reflect.UndeclaredThrowableException] at org.jnp.interfaces.NamingContext.getObjectInstanceWrapFailure(NamingContext.java:1504) at org.jnp.interfaces.NamingContext.lookup(NamingContext.java:822) at org.jnp.interfaces.NamingContext.lookup(NamingContext.java:686) at javax.naming.InitialContext.lookup(InitialContext.java:392) at TestClient.main(TestClient.java:18) Caused by: java.lang.reflect.UndeclaredThrowableException at $Proxy0.createProxyBusiness(Unknown Source) at org.jboss.ejb3.proxy.impl.objectfactory.session.SessionProxyObjectFactory.createProxy(SessionProxyObjectFactory.java:129) at org.jboss.ejb3.proxy.impl.objectfactory.session.stateless.StatelessSessionProxyObjectFactory.getProxy(StatelessSessionProxyObjectFactory.java:79) at org.jboss.ejb3.proxy.impl.objectfactory.ProxyObjectFactory.getObjectInstance(ProxyObjectFactory.java:158) at javax.naming.spi.NamingManager.getObjectInstance(NamingManager.java:304) at org.jnp.interfaces.NamingContext.getObjectInstance(NamingContext.java:1479) at org.jnp.interfaces.NamingContext.getObjectInstanceWrapFailure(NamingContext.java:1496) ... 4 more Caused by: java.lang.ClassNotFoundException: com.test.ejb.IHelloEJBService at org.jboss.remoting.serialization.ClassLoaderUtility.loadClass(ClassLoaderUtility.java:103) at org.jboss.remoting.loading.RemotingClassLoader.loadClass(RemotingClassLoader.java:86) at java.lang.ClassLoader.loadClassInternal(ClassLoader.java:320) at java.lang.Class.forName0(Native Method) at java.lang.Class.forName(Class.java:247) at org.jboss.remoting.loading.ObjectInputStreamWithClassLoader.resolveProxyClass(ObjectInputStreamWithClassLoader.java:253) at java.io.ObjectInputStream.readProxyDesc(ObjectInputStream.java:1531) at java.io.ObjectInputStream.readClassDesc(ObjectInputStream.java:1493) at java.io.ObjectInputStream.readOrdinaryObject(ObjectInputStream.java:1732) at java.io.ObjectInputStream.readObject0(ObjectInputStream.java:1329) at java.io.ObjectInputStream.readObject(ObjectInputStream.java:351) at org.jboss.aop.joinpoint.InvocationResponse.readExternal(InvocationResponse.java:119) at java.io.ObjectInputStream.readExternalData(ObjectInputStream.java:1792) at java.io.ObjectInputStream.readOrdinaryObject(ObjectInputStream.java:1751) at java.io.ObjectInputStream.readObject0(ObjectInputStream.java:1329) at java.io.ObjectInputStream.defaultReadFields(ObjectInputStream.java:1947) at java.io.ObjectInputStream.readSerialData(ObjectInputStream.java:1871) at java.io.ObjectInputStream.readOrdinaryObject(ObjectInputStream.java:1753) at java.io.ObjectInputStream.readObject0(ObjectInputStream.java:1329) at java.io.ObjectInputStream.readObject(ObjectInputStream.java:351) at org.jboss.remoting.serialization.impl.java.JavaSerializationManager.receiveObjectVersion2_2(JavaSerializationManager.java:238) at org.jboss.remoting.serialization.impl.java.JavaSerializationManager.receiveObject(JavaSerializationManager.java:138) at org.jboss.remoting.marshal.serializable.SerializableUnMarshaller.read(SerializableUnMarshaller.java:123) at org.jboss.remoting.transport.socket.MicroSocketClientInvoker.versionedRead(MicroSocketClientInvoker.java:1220) at org.jboss.remoting.transport.socket.MicroSocketClientInvoker.transport(MicroSocketClientInvoker.java:850) at org.jboss.remoting.MicroRemoteClientInvoker.invoke(MicroRemoteClientInvoker.java:165) at org.jboss.remoting.Client.invoke(Client.java:1724) at org.jboss.remoting.Client.invoke(Client.java:629) at org.jboss.aspects.remoting.InvokeRemoteInterceptor.invoke(InvokeRemoteInterceptor.java:60) at org.jboss.aop.joinpoint.MethodInvocation.invokeNext(MethodInvocation.java:102) at org.jboss.ejb3.proxy.impl.remoting.IsLocalProxyFactoryInterceptor.invoke(IsLocalProxyFactoryInterceptor.java:72) at org.jboss.aop.joinpoint.MethodInvocation.invokeNext(MethodInvocation.java:102) at org.jboss.aspects.remoting.PojiProxy.invoke(PojiProxy.java:62) at $Proxy0.createProxyBusiness(Unknown Source) at org.jboss.ejb3.proxy.impl.objectfactory.session.SessionProxyObjectFactory.createProxy(SessionProxyObjectFactory.java:129) at org.jboss.ejb3.proxy.impl.objectfactory.session.stateless.StatelessSessionProxyObjectFactory.getProxy(StatelessSessionProxyObjectFactory.java:79) at org.jboss.ejb3.proxy.impl.objectfactory.ProxyObjectFactory.getObjectInstance(ProxyObjectFactory.java:158) at javax.naming.spi.NamingManager.getObjectInstance(NamingManager.java:304) at org.jnp.interfaces.NamingContext.getObjectInstance(NamingContext.java:1479) at org.jnp.interfaces.NamingContext.getObjectInstanceWrapFailure(NamingContext.java:1496) at org.jnp.interfaces.NamingContext.lookup(NamingContext.java:822) at org.jnp.interfaces.NamingContext.lookup(NamingContext.java:686) at javax.naming.InitialContext.lookup(InitialContext.java:392) at TestClient.main(TestClient.java:18) at org.jboss.aspects.remoting.InvokeRemoteInterceptor.invoke(InvokeRemoteInterceptor.java:72) at org.jboss.aop.joinpoint.MethodInvocation.invokeNext(MethodInvocation.java:102) at org.jboss.ejb3.proxy.impl.remoting.IsLocalProxyFactoryInterceptor.invoke(IsLocalProxyFactoryInterceptor.java:72) at org.jboss.aop.joinpoint.MethodInvocation.invokeNext(MethodInvocation.java:102) at org.jboss.aspects.remoting.PojiProxy.invoke(PojiProxy.java:62) ... 11 more -------------------------------------------------------------- Reply to this message by going to Community [http://community.jboss.org/message/641181#641181] Start a new discussion in EJB Development at Community [http://community.jboss.org/choose-container!input.jspa?contentType=1&cont...]

14 years

1
0
0 / 0

Issue regarding JBoss BRMS 5.2.0 deployment on IBM Websphere 8.0

by Tinu Bansal

Hi I am working on JBoss BRMS 5.2.0. I am trying to deploy it on IBM Websphere Application Server v8.0. I am struck with a problem and unable to resolve it. The problem is as mentioned below: When I am deploying BRMS 5.2 on Websphere 8, I am getting the following exception : com.ibm.ws.webcontainer.webapp.WebApp logServletError SRVE0293E: [Servlet Error]-[GenericServletWrapper]: java.lang.ClassNotFoundException: class java.lang.ClassNotFoundException: org.jboss.seam.web.ContextFilter Presently, I am using default seam jars provided in the BRMS setup : jboss-seam-2.2.4.EAP5.jar and : jboss-seam-remoting-2.2.4.EAP5.jar I have tried it with different versions of Seam Jars also. However, it is giving class not found exception in every case. Could you please help me out in resolving the issue? The Development Environment Specifications are as mentioned below: 1. Operating System : Microsoft Windows 7 2. IDE : IBM Rational Application Developer (Version 8.0.3) 3. Application Server : IBM Websphere Application Server (Version 8.0) 4. Module : JBoss BRMS (Version 5.2.0) I have attached the log file along with this mail, named "Error Log". Please guide me to resolve this issue. I shall be very thankful to you. Regards Tinu +918686177200 **************** CAUTION - Disclaimer ***************** This e-mail contains PRIVILEGED AND CONFIDENTIAL INFORMATION intended solely for the use of the addressee(s). If you are not the intended recipient, please notify the sender by e-mail and delete the original message. Further, you are not to copy, disclose, or distribute this e-mail or its contents to any other person and any such actions are unlawful. This e-mail may contain viruses. Infosys has taken every reasonable precaution to minimize this risk, but is not liable for any damage you may sustain as a result of any virus in this e-mail. You should carry out your own virus checks before opening the e-mail or attachment. Infosys reserves the right to monitor and review the content of all messages sent to or from this e-mail address. Messages sent to or from this e-mail address may be stored on the Infosys e-mail system. ***INFOSYS******** End of Disclaimer ********INFOSYS***

14 years

1
1
0 / 0

[JBoss ESB Development] - destination filename for fs notifier

by tic

tic [http://community.jboss.org/people/tic] created the discussion "destination filename for fs notifier" To view the discussion, visit: http://community.jboss.org/message/641156#641156 -------------------------------------------------------------- Hi, I'm new to jboss esb and have been tasked with evaluating it as a replacement to our legacy middleware application. I'm trying the very simple use case of moving a file from one local dir to another. But I can seem to dynamically set the file name the fs notifier uses. It only accepts a constant URI. Is it possible to set the destination filename for local filesystem operations ? Many thanks. -------------------------------------------------------------- Reply to this message by going to Community [http://community.jboss.org/message/641156#641156] Start a new discussion in JBoss ESB Development at Community [http://community.jboss.org/choose-container!input.jspa?contentType=1&cont...]

14 years, 1 month

1
0
0 / 0

[JBoss AS 7 Development] - Re: Spring-WS 1.5.9 on JBoss AS 7

by Alessio Soldano

Alessio Soldano [http://community.jboss.org/people/asoldano] created the discussion "Re: Spring-WS 1.5.9 on JBoss AS 7" To view the discussion, visit: http://community.jboss.org/message/641015#641015 -------------------------------------------------------------- Hi, > Melloware Inc wrote: > > Alessio, > > Thanks for responding. To answer your question: > > 1. I have turned on TRACE level logging but Jboss is eating the exception. They are just throwing... > > throw new SoapException("Unable to create message factory for SOAP:" + ex.getMessage); > > ...and no stack trace, so I can see the root error. Did you also add a logger category for org.jboss.modules package? > 2. I thought someone might suggest installing CXF and Spring as a Jboss7 module. However that defeats the purpose of a portable WAR file. If I have Jetty 8, Tomcat 7 and Jboss 7AS in my organization now I need to build custom WAR files and deployments for each platform. I would prefer not to have to know that Jboss 7 AS is the destination platform when I build my WAR file. Plus it will require the Unix Admins here (I am not allowed to touch Production Servers) to have to tweak Jboss 7AS to put CXF and Spring as modules in the environment etc. I want to keep configuration of the actual container to a minimum. Well, generally speaking when deploying on JBoss AS you should consider you're deploying against a Java EE container that comes with webservices functionalities, hence you're not supposed to provide your own ws impl. If you want to use JBoss AS 7 as a "simple" web container, an idea might be to disable the webservices subsystem in the standalone configuration you're using. I didn't try that, but I guess that might work for you in this case. There're multiple reasons for having the CXF libs included in the AS, most of them basically comes from JavaEE certification requirements. To be honest, there's even https://issues.jboss.org/browse/AS7-537 https://issues.jboss.org/browse/AS7-537 (part of https://issues.jboss.org/browse/AS7-388 https://issues.jboss.org/browse/AS7-388) which is about filtering out Apache CXF libs in user deployments to avoid clashes. Generally speaking, a portable application should be built using standards only. So write a standard jaxws application with no direct reference to Apache CXF, Spring, etc. and you won't have portability problems (you'd just have to apply minor changes to web.xml descriptor for stuff not covered by spec there, but nowadays you can even get rid of web.xml...). If you're directly leveraging specific implementation / libs / tools, unfortunately you need to deal with this kind of issues. -------------------------------------------------------------- Reply to this message by going to Community [http://community.jboss.org/message/641015#641015] Start a new discussion in JBoss AS 7 Development at Community [http://community.jboss.org/choose-container!input.jspa?contentType=1&cont...]

14 years, 1 month

2
1
0 / 0

[JBoss Web Services Development] - cxf.xml doesn't work under JBoss 6.1

by Tao Sang

Tao Sang [http://community.jboss.org/people/tao_dl] created the discussion "cxf.xml doesn't work under JBoss 6.1" To view the discussion, visit: http://community.jboss.org/message/637679#637679 -------------------------------------------------------------- Dear Forum, Currently under JBoss 6.1, I have a problem by calling web service over https (SSL), which has a self-signed certificate. By using a dummy (certificate)TrustManager, I got one step further with following errors: Caused by: java.io.IOException: The https URL hostname does not match the Common Name (CN) on the server certificate. To disable this check (NOT recommended for production) set the CXF client TLS configuration property "disableCNCheck" to true. I googled and found that I need to set a cxf client configuration file with the project. Then I created a cxf.xml with following content and left it in the folder: *myProject-ejb\src\main\resources\* : *<beans xmlns=" http://www.springframework.org/schema/beans http://www.springframework.org/schema/beans"* * xmlns:xsi=" http://www.w3.org/2001/XMLSchema-instance http://www.w3.org/2001/XMLSchema-instance"* * xmlns:http-conf=" http://cxf.apache.org/transports/http/configuration http://cxf.apache.org/transports/http/configuration" * * xsi:schemaLocation="* * http://cxf.apache.org/configuration/security http://cxf.apache.org/configuration/security* * http://cxf.apache.org/schemas/configuration/security.xsd http://cxf.apache.org/schemas/configuration/security.xsd* * http://cxf.apache.org/transports/http/configuration http://cxf.apache.org/transports/http/configuration* * http://cxf.apache.org/schemas/configuration/http-conf.xsd http://cxf.apache.org/schemas/configuration/http-conf.xsd* * http://www.springframework.org/schema/beans http://www.springframework.org/schema/beans* * http://www.springframework.org/schema/beans/spring-beans.xsd http://www.springframework.org/schema/beans/spring-beans.xsd">* *<http-conf:conduit name="{ https://server.company.com:8443/ https://server.company.com:8443/}WebService.http-conduit">* * <http-conf:tlsClientParameters secureSocketProtocol="SSL" disableCNCheck="true"/>* *</http-conf:conduit>* *<http-conf:conduit name="*.http-conduit">* * <http-conf:tlsClientParameters disableCNCheck="true" secureSocketProtocol="SSL"/>* *</http-conf:conduit>* *</beans>* However, I always get the above errors. Did I do something wrong? I saw that the cxf.xml file has been copied into the root folder of the *myProject-ejb.jar* file, but I don't know if the cxf.file really works. How can I check if the cxf.xml is working? Thanks in advance! Tao -------------------------------------------------------------- Reply to this message by going to Community [http://community.jboss.org/message/637679#637679] Start a new discussion in JBoss Web Services Development at Community [http://community.jboss.org/choose-container!input.jspa?contentType=1&cont...]

14 years, 1 month

2
2
0 / 0

[jBPM Development] - Re: Table data loss after re-deploy application

by Chris Melas

Chris Melas [http://community.jboss.org/people/melc] created the discussion "Re: Table data loss after re-deploy application" To view the discussion, visit: http://community.jboss.org/message/641010#641010 -------------------------------------------------------------- Hi, Why don't you comment out the line, <property name="hibernate.hbm2ddl.auto" value="create" /> after the first deployment? Regarding the task service from the default ant script of jbpm, that attempts to insert users and groups, you can simply handle the exceptions with try catch in the code of the class DemoTaskService.java. -------------------------------------------------------------- Reply to this message by going to Community [http://community.jboss.org/message/641010#641010] Start a new discussion in jBPM Development at Community [http://community.jboss.org/choose-container!input.jspa?contentType=1&cont...]

14 years, 1 month

1
0
0 / 0

[JBoss AS7 Development] - Deploying liferay on JBoss 7

by Chander Shivdasani

Chander Shivdasani [http://community.jboss.org/people/chandershivdasani] created the discussion "Deploying liferay on JBoss 7" To view the discussion, visit: http://community.jboss.org/message/620202#620202 -------------------------------------------------------------- I've been trying to deploy Liferay on JBoss 7 and have been failing miserably. I followed the usual steps: * Downloaded Jboss 7 and liferay.war * I copied liferay.way at JBOSS_HOME/standalone/deployments * And i ran JBOSS_HOME/bin/standalone.sh I've been getting following errors. Did anyone try doing this before? I would be nice if any of you can share the instructions. 12:06:02,088 WARN [org.jboss.as.server.deployment] (MSC service thread 1-47) Class Path entry ../bin/ in "/content/liferay.war/WEB-INF/lib/jurt.jar" does not point to a valid jar for a Class-Path reference. 12:06:02,088 WARN [org.jboss.as.server.deployment] (MSC service thread 1-47) Class Path entry jaxp-api.jar in "/content/liferay.war/WEB-INF/lib/saaj-api.jar" does not point to a valid jar for a Class-Path reference. 12:06:02,089 WARN [org.jboss.as.server.deployment] (MSC service thread 1-47) Class Path entry jax-qname.jar in "/content/liferay.war/WEB-INF/lib/saaj-api.jar" does not point to a valid jar for a Class-Path reference. 12:06:02,089 WARN [org.jboss.as.server.deployment] (MSC service thread 1-47) Class Path entry activation.jar in "/content/liferay.war/WEB-INF/lib/saaj-api.jar" does not point to a valid jar for a Class-Path reference. 12:06:02,089 WARN [org.jboss.as.server.deployment] (MSC service thread 1-47) Class Path entry servlet.jar in "/content/liferay.war/WEB-INF/lib/saaj-api.jar" does not point to a valid jar for a Class-Path reference. 12:06:02,089 WARN [org.jboss.as.server.deployment] (MSC service thread 1-47) Class Path entry lib/ant.jar in "/content/liferay.war/WEB-INF/lib/truezip.jar" does not point to a valid jar for a Class-Path reference. 12:06:02,090 WARN [org.jboss.as.server.deployment] (MSC service thread 1-47) Class Path entry lib/lcrypto-jdk14-135.jar in "/content/liferay.war/WEB-INF/lib/truezip.jar" does not point to a valid jar for a Class-Path reference. 12:06:02,250 ERROR [org.jboss.msc.service.fail] (MSC service thread 1-47) MSC00001: Failed to start service jboss.deployment.unit."liferay.war".PARSE: org.jboss.msc.service.StartException in service jboss.deployment.unit."liferay.war".PARSE: Failed to process phase PARSE of deployment "liferay.war" at org.jboss.as.server.deployment.DeploymentUnitPhaseService.start(DeploymentUnitPhaseService.java:121) at org.jboss.msc.service.ServiceControllerImpl$StartTask.run(ServiceControllerImpl.java:1765) at org.jboss.msc.service.ServiceControllerImpl$ClearTCCLTask.run(ServiceControllerImpl.java:2291) at java.util.concurrent.ThreadPoolExecutor$Worker.runTask(ThreadPoolExecutor.java:886) [:1.6.0_23] at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:908) [:1.6.0_23] at java.lang.Thread.run(Thread.java:661) [:1.6.0_23] Caused by: org.jboss.as.server.deployment.DeploymentUnitProcessingException: Failed to parse "/content/liferay.war/WEB-INF/jboss-web.xml" at org.jboss.as.web.deployment.JBossWebParsingDeploymentProcessor.deploy(JBossWebParsingDeploymentProcessor.java:66) at org.jboss.as.server.deployment.DeploymentUnitPhaseService.start(DeploymentUnitPhaseService.java:115) ... 5 more Caused by: javax.xml.stream.XMLStreamException: ParseError at [row,col]:[5,2] Message: Unexpected element 'class-loading' encountered at org.jboss.metadata.parser.util.MetaDataElementParser.unexpectedElement(MetaDataElementParser.java:109) at org.jboss.metadata.parser.jbossweb.JBossWebMetaDataParser.parse(JBossWebMetaDataParser.java:182) at org.jboss.as.web.deployment.JBossWebParsingDeploymentProcessor.deploy(JBossWebParsingDeploymentProcessor.java:64) ... 6 more 12:06:02,267 INFO [org.jboss.as.server.controller] (DeploymentScanner-threads - 2) Deployment of "liferay.war" was rolled back with failure message {"Failed services" => {"jboss.deployment.unit.\"liferay.war\".PARSE" => "org.jboss.msc.service.StartException in service jboss.deployment.unit.\"liferay.war\".PARSE: Failed to process phase PARSE of deployment \"liferay.war\""}} 12:06:02,268 INFO [org.jboss.as.controller] (DeploymentScanner-threads - 2) Service status report Services which failed to start: service jboss.deployment.unit."liferay.war".PARSE: org.jboss.msc.service.StartException in service jboss.deployment.unit."liferay.war".PARSE: Failed to process phase PARSE of deployment "liferay.war" -------------------------------------------------------------- Reply to this message by going to Community [http://community.jboss.org/message/620202#620202] Start a new discussion in JBoss AS7 Development at Community [http://community.jboss.org/choose-container!input.jspa?contentType=1&cont...]

14 years, 1 month

4
3
0 / 0

[jBPM Development] - Deploying jBPM 5.1 in weblogic 10

by Ramanan Pathmaraj

Ramanan Pathmaraj [http://community.jboss.org/people/ramanan.pathmaraj] created the discussion "Deploying jBPM 5.1 in weblogic 10" To view the discussion, visit: http://community.jboss.org/message/636890#636890 -------------------------------------------------------------- Hi, I am evaluating jBPM 5.1 and I am new to jBPM. I successfully created a sample application using the demo utilities. Now I want to deploy my sample application in Weblogic. Please help me how to deploy jBPM 5.1 in weblogic. Do we have any document or guide to deploy jBPM 5.1 in weblogic? Regards, Ramanan -------------------------------------------------------------- Reply to this message by going to Community [http://community.jboss.org/message/636890#636890] Start a new discussion in jBPM Development at Community [http://community.jboss.org/choose-container!input.jspa?contentType=1&cont...]

14 years, 1 month

2
4
0 / 0

2026

2025

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

2009

2008

2007

2006

jboss-dev-forums December 2011