Deploy Mashup server as WAR

Yes It can be deployed on any servlet container. In the standalone server we deploy our self on embedded tomcat. Thanks, Keith.

great!! many thanks!! :-) But, how can I produce the WAR? I tried using the source and maven but doesn't work, I get a lot of missing packages :-(

But, how can I produce the WAR? I tried using the source and maven but doesn't work, I get a lot of missing packages :-(

After I build all using maven I get iside the path wso2-mashup-server-src\modules\distribution\target the following dirs: dist dist-lib temp wso2mashup-distribution-1.5.2-src zips and this 2 files wso2-mashup-server-1.5.2.zip wso2-mashup-server-1.5.2-src.zip but I can't find the war :-( I was wondering the war isn't inside the dist directory.

No one knows how to produce a war deployable under WebSphere?

Well the war is not created by default during the build process. But you can package it up that way. As we are moving onto the carbon Platform this will be available in the 2.0 release. Thanks, Keith.

I imported into netbean the project and created the war dist. But when I run the project it says ( see the stack trace below), any idea? By the way when the 2.0 will be available? The error reported was; Can't find bundle for base name UI, locale it_IT The following technical information is also available regarding this error; java.util.ResourceBundle.throwMissingResourceException(ResourceBundle.java:1521) java.util.ResourceBundle.getBundleImpl(ResourceBundle.java:1260) java.util.ResourceBundle.getBundle(ResourceBundle.java:715) org.apache.jsp.index_jsp._jspService(index_jsp.java from :102) org.apache.jasper.runtime.HttpJspBase.service(HttpJspBase.java:109) javax.servlet.http.HttpServlet.service(HttpServlet.java:847) org.apache.jasper.servlet.JspServletWrapper.service(JspServletWrapper.java:403) org.apache.jasper.servlet.JspServlet.serviceJspFile(JspServlet.java:473) org.apache.jasper.servlet.JspServlet.service(JspServlet.java:366) javax.servlet.http.HttpServlet.service(HttpServlet.java:847) org.apache.catalina.core.ApplicationFilterChain.servletService(ApplicationFilterChain.java:431) org.apache.catalina.core.StandardWrapperValve.preInvoke(StandardWrapperValve.java:462) org.apache.catalina.core.StandardWrapperValve.invoke(StandardWrapperValve.java:139) org.apache.catalina.core.StandardContextValve.invoke(StandardContextValve.java:186) org.apache.catalina.core.StandardPipeline.doInvoke(StandardPipeline.java:719) org.apache.catalina.core.StandardPipeline.doInvoke(StandardPipeline.java:657) com.sun.enterprise.web.WebPipeline.invoke(WebPipeline.java:96) com.sun.enterprise.web.PESessionLockingStandardPipeline.invoke(PESessionLockingStandardPipeline.java:98) org.apache.catalina.core.StandardHostValve.invoke(StandardHostValve.java:187) org.apache.catalina.core.StandardPipeline.doInvoke(StandardPipeline.java:719) org.apache.catalina.core.StandardPipeline.doInvoke(StandardPipeline.java:657) org.apache.catalina.core.StandardPipeline.invoke(StandardPipeline.java:651) org.apache.catalina.core.ContainerBase.invoke(ContainerBase.java:1030) org.apache.catalina.core.StandardEngineValve.invoke(StandardEngineValve.java:142) org.apache.catalina.core.StandardPipeline.doInvoke(StandardPipeline.java:719) org.apache.catalina.core.StandardPipeline.doInvoke(StandardPipeline.java:657) org.apache.catalina.core.StandardPipeline.invoke(StandardPipeline.java:651) org.apache.catalina.core.ContainerBase.invoke(ContainerBase.java:1030) org.apache.catalina.connector.CoyoteAdapter.doService(CoyoteAdapter.java:325) org.apache.catalina.connector.CoyoteAdapter.service(CoyoteAdapter.java:242) com.sun.enterprise.v3.services.impl.ContainerMapper.service(ContainerMapper.java:180) com.sun.grizzly.http.DefaultProcessorTask.invokeAdapter(DefaultProcessorTask.java:633) com.sun.grizzly.http.DefaultProcessorTask.doProcess(DefaultProcessorTask.java:570) com.sun.grizzly.http.DefaultProcessorTask.process(DefaultProcessorTask.java:827) com.sun.grizzly.http.DefaultProtocolFilter.execute(DefaultProtocolFilter.java:152) com.sun.enterprise.v3.services.impl.GlassfishProtocolChain.executeProtocolFilter(GlassfishProtocolChain.java:71) com.sun.grizzly.DefaultProtocolChain.execute(DefaultProtocolChain.java:103) com.sun.grizzly.DefaultProtocolChain.execute(DefaultProtocolChain.java:89) com.sun.grizzly.http.HttpProtocolChain.execute(HttpProtocolChain.java:76) com.sun.grizzly.ProtocolChainContextTask.doCall(ProtocolChainContextTask.java:67) com.sun.grizzly.SelectionKeyContextTask.call(SelectionKeyContextTask.java:56) com.sun.grizzly.util.WorkerThreadImpl.processTask(WorkerThreadImpl.java:325) com.sun.grizzly.util.WorkerThreadImpl.run(WorkerThreadImpl.java:184)

We add directories such as conf to the classpath. This is done by the startup script. This is probebly due to that. We expect to have 2.o out in mid June. Thanks, Keith.

It seems there is more than a simple task to create a deployable war starting from the sources because of the in-depth customization made. do I have to wait for the 2.0? There is no way to have a deployable war built before? Many thanks for the support Simonluca