[Installation, Configuration & Deployment] - Need of an application parameter definition
by gousenbl
I work with several ear packages deployed in the deploy directory.
In the application, I need to define and use different variables:
1. variables with a WAR scope: these variables are defined in the web.xml of the corresponding WAR file and are accessible only in that WAR file,
2. variables with an application scope: these variables should be defined somewhere in the EAR and should be accessible only in the EAR where they are defined. The other EARs should not have access to it.
3. variables with a JVM scope: these variables are defined in the properties-services.xml in the deploy directory and are accessible in the whole instance of JBOSS. All the EARs can access these variables.
For points 1 and 3, it is OK, JBOSS can handle it.
For point 2, I have an issue. JBOSS doesn't handle it. In BEA Weblogic for example, there is a BEA specific configuration descriptor, which is included in the EAR, that allows to define application variables. These variables cover the requiments I have.
Will JBOSS handle such variable in a near future? If yes, when? If no, how can I implement that scenario?
View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=4013621#4013621
Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=4013621
19Â years, 2Â months
[JCA/JBoss] - ActiveMQ JCA connector and Spring 2 application conflict in
by luciano61
If I try to deploy the ActiveMQ JCA resource adapter (activemq-rar-4.1.0-incubator.rar) side by side with a Spring 2 war in JBoss 4.0.5 , I get the following error on server startup:
ERROR
[org.springframework.web.context.ContextLoader] Context initialization
failed
org.springframework.beans.factory.BeanDefinitionStoreException:
Unexpected exception parsing XML document from ServletContext resource
[/WEB-INF/applicationContext.xml]; nested exception is
java.lang.IllegalArgumentException: Class
[org.apache.xbean.spring.context.v2.XBeanNamespaceHandler] does not
implement the NamespaceHandler interface
Caused by:
java.lang.IllegalArgumentException: Class
[org.apache.xbean.spring.context.v2.XBeanNamespaceHandler] does not
implement the NamespaceHandler interface
at org.springframework.beans.factory.xml.DefaultNamespaceHandlerResolver.initHandle\
rMappings(DefaultNamespaceHandlerResolver.java:119)
at org.springframework.beans.factory.xml.DefaultNamespaceHandlerResolver.(Def\
aultNamespaceHandlerResolver.java:96)
at org.springframework.beans.factory.xml.DefaultNamespaceHandlerResolver.(Def\
aultNamespaceHandlerResolver.java:82)
at org.springframework.beans.factory.xml.XmlBeanDefinitionReader.createDefaultNames\
paceHandlerResolver(XmlBeanDefinitionReader.java:526)
at org.springframework.beans.factory.xml.XmlBeanDefinitionReader.createReaderContex\
t(XmlBeanDefinitionReader.java:515)
at org.springframework.beans.factory.xml.XmlBeanDefinitionReader.registerBeanDefini\
tions(XmlBeanDefinitionReader.java:495)
at org.springframework.beans.factory.xml.XmlBeanDefinitionReader.doLoadBeanDefiniti\
ons(XmlBeanDefinitionReader.java:390)
at org.springframework.beans.factory.xml.XmlBeanDefinitionReader.loadBeanDefinition\
s(XmlBeanDefinitionReader.java:340)
at org.springframework.beans.factory.xml.XmlBeanDefinitionReader.loadBeanDefinition\
s(XmlBeanDefinitionReader.java:317)
at org.springframework.beans.factory.support.AbstractBeanDefinitionReader.loadBeanD\
efinitions(AbstractBeanDefinitionReader.java:125)
at org.springframework.beans.factory.support.AbstractBeanDefinitionReader.loadBeanD\
efinitions(AbstractBeanDefinitionReader.java:141)
at org.springframework.web.context.support.XmlWebApplicationContext.loadBeanDefinit\
ions(XmlWebApplicationContext.java:123)
at org.springframework.web.context.support.XmlWebApplicationContext.loadBeanDefinit\
ions(XmlWebApplicationContext.java:91)
at org.springframework.context.support.AbstractRefreshableApplicationContext.refres\
hBeanFactory(AbstractRefreshableApplicationContext.java:94)
at org.springframework.context.support.AbstractApplicationContext.refresh(AbstractA\
pplicationContext.java:292)
at org.springframework.web.context.support.AbstractRefreshableWebApplicationContext\
.refresh(AbstractRefreshableWebApplicationContext.java:156)
at org.springframework.web.context.ContextLoader.createWebApplicationContext(Contex\
tLoader.java:246)
at org.springframework.web.context.ContextLoader.initWebApplicationContext(ContextL\
oader.java:184)
at org.springframework.web.context.ContextLoaderListener.contextInitialized(Context\
LoaderListener.java:49)
The problem is reproducible with any Spring 2 app (like the jpetstore sample of Spring 2.0.2 distribution), not only mine, to try yourself these are the steps:
1)Install a fresh Jboss (I tested 4.0.3 and 4.0.5) and verify it starts without problems
2)Stop JBoss
3)Put the activemq-rar-4.1.0-incubator.rar and jpetstore.war in the deploy JBoss dir
4)Start JBoss and you will see my stack trace
The only workaround I found is to remove the Spring 2 jar from the ActiveMQ rar, but as I think is a classloader problem, there isn't a correct way of insulating JCA connector from apps?
I tryed also to put the activemq .rar inside an .ear file as described here
[url]http://www.jboss.org/index.html?module=bb&op=viewtopic&p=3992480
but nothing changed.
Luciano[/url]
View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=4013618#4013618
Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=4013618
19Â years, 2Â months
[JBoss Seam] - tomahawk extension filter and seam fileUpload
by milesif
Hi everbody,
In my seam application I use tomahawk components so I had to put in my web.xml the following rows
| <filter>
| <filter-name>extensionsFilter</filter-name>
| <filter-class>
| org.apache.myfaces.component.html.util.ExtensionsFilter
| </filter-class>
| </filter>
|
| <filter-mapping>
| <filter-name>extensionsFilter</filter-name>
| <url-pattern>*.seam</url-pattern>
| </filter-mapping>
|
| <filter-mapping>
| <filter-name>extensionsFilter</filter-name>
| <servlet-name>Faces Servlet</servlet-name>
| </filter-mapping>
|
To use <s:fileUpload> I also added
| <filter>
| <filter-name>Seam Multipart Filter</filter-name>
| <filter-class>
| org.jboss.seam.servlet.SeamMultipartFilter
| </filter-class>
| <init-param>
| <param-name>createTempFiles</param-name>
| <param-value>true</param-value>
| </init-param>
| </filter>
|
| <filter-mapping>
| <filter-name>Seam Multipart Filter</filter-name>
| <url-pattern>*.seam</url-pattern>
| </filter-mapping>
|
The problem is that seam upload seems to work fine only if I comment Tomahawk extensionFilter, but that makes unavailable some Tomahawk's components (tree2 for example) .
I tried different ordering of filters inside my web.xml (I don't know if that makes sense....), but I could not make tomahawk components and seam fileUpload work together.
Do you have an idea where is the problem ?
Many Thanks in advance
Ciao Francesco
View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=4013611#4013611
Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=4013611
19Â years, 2Â months