[Tomcat, HTTPD, Servlets & JSP] - Re: Create plugin for a web application
by loopix
Ok, thanks very much, now I'm on the good road :)
So, my last idea is:
- a plugin will be a .war file (it's easy to develop it on Eclipse, separately)
- the web application base will load a directories with .war files
- a .war files is unpackaged and will be a part of "web_plugin.war" modules (exploded archive) which is empty at the start of the application (first time or not, ...)
So, I got 2 web modules:
- web_base
- web_plugin
the second module will be filled by all files contained into .war files on a specific directories .. I think that idea must work, but actually, I must open a gived WAR file .. unpack it, copy files to web_plugin.war and update the application (if needed). All of that work must be hardcoded in Java, so ... first: try to deploy a helloworld plugin which contains only a html page ...
For now, don't know how to open a .war files with a .war application :D
View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=4116543#4116543
Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=4116543
18 years, 3 months
[JBoss Seam] - Re: Problem upgrading to Seam 2.0.1.CR1
by seamdev
In addition to seam I am using jars from jaxws version: 2.1.2 (dated 2007-09-17).
Here are the content of lib folder in war file:
| activation.jar antlr.jar
| cglib.jar
| commons-beanutils.jar commons-collections.jar
| commons-digester.jar commons-logging.jar
| dom4j.jar el-api.jar
| el-ri.jar FastInfoset.jar
| hibernate-annotations.jar hibernate-commons-annotations.jar
| hibernate-entitymanager.jar hibernate-search.jar
| hibernate-validator.jar hibernate.jar
| http.jar mywsclient.jar
| javassist.jar jaxb-api.jar
| jaxb-impl.jar jaxb-xjc.jar
| jaxws-api.jar jaxws-rt.jar
| jaxws-tools.jar jboss-common-core.jar
| jboss-container.jar jboss-dependency.jar
| jboss-deployers.jar jboss-el.jar
| jboss-embedded-api.jar jboss-jmx.jar
| jboss-kernel.jar jboss-logging-spi.jar
| jboss-seam-debug.jar jboss-seam-gen.jar
| jboss-seam-ioc.jar jboss-seam-mail.jar
| jboss-seam-pdf.jar jboss-seam-remoting.jar
| jboss-seam-ui.jar jboss-seam.jar
| jboss-system.jar jsf-api.jar
| jsf-facelets.jar jsf-impl.jar
| jsr173_api.jar jsr181-api.jar
| jsr250-api.jar jstl.jar
| persistence-api.jar readme.txt
| resolver.jar richfaces-api.jar
| richfaces-impl.jar richfaces-ui.jar
| saaj-api.jar saaj-impl.jar
| search.jar servlet-api.jar
| servlet.jar sjsxp.jar
| stax-ex.jar streambuffer.jar
|
View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=4116536#4116536
Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=4116536
18 years, 3 months
[Microcontainer] - Re: migrating from ServiceMBeanSupport
by alesj
"jhalliday" wrote : From the sounds of things it would be feasible to declare a bean with class=org.jboss.system.microcontainer.jmx.ServiceControllerLifecycleCallback in the jboss-service.xml file and inject the legacy JMX kernel into it, then reference that in the TransactionManager bean xml?
Exactly.
This is what solves your problem:
| <bean name="MBeanExporter" class="org.jboss.system.microcontainer.jmx.ServiceControllerLifecycleCallback">
| <property name="serviceController"><inject bean="JMXKernel" property="serviceController"/></property>
| </bean>
|
| <bean name="TransactionManager" class="org.jboss.tm.RealTransactionManager">
| <annotation>@org.jboss.aop.microcontainer.aspects.jmx.JMX(name="jboss:service=TransactionManager", exposedInterface=org.jboss.test.system.controller.integration.support.MockTransactionManagerMBean.class, registerDirectly=true)</annotation>
| <property name="transactionTimeout">300</property>
| <property name="objectStoreDir">${jboss.server.data.dir}/tx-object-store</property>
| <install bean="MBeanExporter" method="install">
| <parameter><inject fromContext="context"/></parameter>
| </install>
| <uninstall bean="MBeanExporter" method="uninstall">
| <parameter><inject fromContext="context"/></parameter>
| </uninstall>
| </bean>
|
And since the AOP kicks in later, this bean won't be picked up twice for JMX registry - conclusion from Adrian's comment.
View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=4116533#4116533
Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=4116533
18 years, 3 months