[jboss-user] [Installation, Configuration DEPLOYMENT] - Re: How to set substitution values?
genman wrote : You can set these properties using this:
|
http://www.redhat.com/docs/manuals/jboss/jboss-eap-4.2/doc/Server_Configuration_Guide/Additional_Services-System_Properties_Management.html
Great! Thank you, Elias.
genman wrote : To deploy the same .war file with a different context ... I'm
not sure if this is allowed or not. You could have ${it.site.root2} or
something
I guess this is not possible, since the service you suggested seems to apply
AS-wide. Anyway, that's a great start to me. Thank you again.
View the original post :
http://www.jboss.com/index.html?module=bbop=viewtopicp=4071535#4071535
Reply to the post :
http://www.jboss.com/index.html?module=bbop=postingmode=replyp=4071535
___
jboss-user mailing list
jboss-user@lists.jboss.org
https://lists.jboss.org/mailman/listinfo/jboss-user
[jboss-user] [Installation, Configuration DEPLOYMENT] - How to set substitution values?
I have a question which is probably a newby one.
When I develop some EAR, I'm used to assign some of the properties and
attributes through substitution macros (in example: ${it.site.root} in the
context-root of a module in the application.xml).
This lets me change some values depending whether I am deploying it on a
staging or on a production server, in example.
I'm used to define the values of these macros among the runtime options I
specify to start jboss. Unfortunately, this seems suboptimal to me, because:
- I need to modify the jboss startup script to do this;
- I need to restart JBoss in order to change these macros;
- I can't simply deploy the same app with two different names to have two
different instances.
Is there any better way to do this? I tried to discover a way by meself,
browsing the docs, but I don't think I found anything of useful.
Thanks,
View the original post :
http://www.jboss.com/index.html?module=bbop=viewtopicp=4070072#4070072
Reply to the post :
http://www.jboss.com/index.html?module=bbop=postingmode=replyp=4070072
___
jboss-user mailing list
jboss-user@lists.jboss.org
https://lists.jboss.org/mailman/listinfo/jboss-user
[jboss-user] [JBoss Seam] - Avoiding conversationId in links
Dears, I'm working on a very simple site adopting seam-1.2.1.GA. The site must be easily indexable by search engines and uses a lot of links with parameters because is basically a tree navigator where items (i.e.: page contents) are keyed by two parameters. Due to the indexability requirement, I would like to avoid any conversationId parameter in my links, since it is going to let search engines think a referenced page changed when it is not. Removing the conversationId shouldn't lead to any problem since I'm not using conversations at all in this site. Is there any way to disable the output of the conversationId parameter page- or site-wide, or do I have to put a s:conversationPropagation type=none/ in every and each link? Thanks, View the original post : http://www.jboss.com/index.html?module=bbop=viewtopicp=4069641#4069641 Reply to the post : http://www.jboss.com/index.html?module=bbop=postingmode=replyp=4069641 ___ jboss-user mailing list jboss-user@lists.jboss.org https://lists.jboss.org/mailman/listinfo/jboss-user
[jboss-user] [JBoss Seam] - page parameters trouble
Dears, I'm trying to use the page parameters feature in seam, but I see that defining whatever kind of action (through h:commandButton/ in example) in a page yields erratic behaviour when parameters are switched from outside the app itself (in example, from a a href=... / from another page). The problem is easily shown in framed pages. In my case, I have a left frame which is meant to navigate the content of the right frame. Loading through the left frame a right page with different parameters with respect to the shown one, the GET with the new parameters is correctly issued by the browser, but the parameters that Seam sets to the new page are the old ones. I'm experiencing this problem with both jboss-seam-1.1.0.GA and jboss-seam-CVS-20070111. I looked for a solution to this problem both in Seam's Jira and in this forum, but didn't find any. Is there any way to circumvent the problem? Also, if mine is the first report of such a problem, I can supply a testcase in Jira. Regards, Giampaolo Tomassoni View the original post : http://www.jboss.com/index.html?module=bbop=viewtopicp=4001544#4001544 Reply to the post : http://www.jboss.com/index.html?module=bbop=postingmode=replyp=4001544 ___ jboss-user mailing list jboss-user@lists.jboss.org https://lists.jboss.org/mailman/listinfo/jboss-user
[jboss-user] [JBossWS] - virtually hosting a webservice
Dears, I had a check to the docs and this forum looking for a way to define the virtual-host on which to publish a given set of webservices made in the jsr-181's EJB3 style. I see I can control the context-root thanks to a @PortComponent(contextRoot=...) annotation. That's fine (apart the fact you have to define it for every and each WS). But what about the virtual-host? Thanks, giampaolo View the original post : http://www.jboss.com/index.html?module=bbop=viewtopicp=3977487#3977487 Reply to the post : http://www.jboss.com/index.html?module=bbop=postingmode=replyp=3977487 ___ jboss-user mailing list jboss-user@lists.jboss.org https://lists.jboss.org/mailman/listinfo/jboss-user
[jboss-user] [JBossWS] - Re: virtually hosting a webservice
maeste wrote : I think your problem will be solved in jbossws-1.0.4 resolving JBWS-1178. Mmmh, I'm not shure that is going to solve my problem. What I'm looking for is a way to publish the JSR-181-complian EJB3 WS services (EJBs with WS annotations) packaged on an .ejb3 archive all on a specific virtual host. I don't see a way to do this with jbossws-1.0.3 because I can't find a suitable annotations (one that lets me specify, say, a virtualHost attribute) and the soap:address element is somehow hidden to a JSR-181 EJB3 endpoint. But an idea arises thanks to your web page: what if I'm going to ship with my .ear a jbossws.sar service carring a modified version of jbossws.beans/META-INF/jboss-beans.xml? Or, even better, is there any way to override the standard jbossws.beans/META-INF/jboss-beans.xml content from an ear or an ejb3? Thanks, giampaolo View the original post : http://www.jboss.com/index.html?module=bbop=viewtopicp=3977708#3977708 Reply to the post : http://www.jboss.com/index.html?module=bbop=postingmode=replyp=3977708 ___ jboss-user mailing list jboss-user@lists.jboss.org https://lists.jboss.org/mailman/listinfo/jboss-user
[jboss-user] [JBossWS] - Re: Access ejb 3.0 exposed web service using https
It seems that jbossws-1.0.3 fixed this: @PortComponent settings seems to be
correctly mapped to transport-guarantee and auth-method entries in the
generated web.xml.
I have another problem anyway: how can I control the virtual-host entry in
the generated jboss-web.xml?
I didn't find any useful annotation about it. Besides, I would prefer to
control this by an xml file since I'm using stuff like this
virtual-host${it.myorg.mycustomer.host}/virtual-host in order to get
staging simple.
Also, I would prefer to avoid building a web app for this because:
1) I would have to sync the site's web.xml everytime I add/remove an exposed
bean;
2) I'm not shure that jbossws is able to detect the fact I'm deploing a war
for my WSes, so I guess I would get two publications: one under the
${jboss.bind.address} virtual host, and the other under the wanted one
(${it.myorg.mycustomer.host}).
Regards,
View the original post :
http://www.jboss.com/index.html?module=bbop=viewtopicp=3977247#3977247
Reply to the post :
http://www.jboss.com/index.html?module=bbop=postingmode=replyp=3977247
___
jboss-user mailing list
jboss-user@lists.jboss.org
https://lists.jboss.org/mailman/listinfo/jboss-user
[jboss-user] [JBoss Seam] - Method not found: isManagedPersistenceContexts
Now what with AS 4.0.4 + Seam 1.0.1!?! My silly piece of web application did start correctly before... Anyone knows? Regards, Giampaolo 17:02:22,015 ERROR [[/paul]] Exception sending context initialized event to listener instance of class org.jboss.seam.servlet.SeamListener | java.lang.IllegalArgumentException: no property for configuration setting: org.jboss.seam.core.init.managedPersistenceContexts | at org.jboss.seam.Component.initInitializers(Component.java:311) | at org.jboss.seam.Component.init(Component.java:209) | at org.jboss.seam.Component.init(Component.java:159) | at org.jboss.seam.Component.init(Component.java:154) | at org.jboss.seam.Component.init(Component.java:149) | at org.jboss.seam.init.Initialization.addComponent(Initialization.java:381) | at org.jboss.seam.init.Initialization.addComponents(Initialization.java:255) | at org.jboss.seam.init.Initialization.init(Initialization.java:195) | at org.jboss.seam.servlet.SeamListener.contextInitialized(SeamListener.java:32) | at org.apache.catalina.core.StandardContext.listenerStart(StandardContext.java:3729) | at org.apache.catalina.core.StandardContext.start(StandardContext.java:4187) | at org.apache.catalina.core.ContainerBase.addChildInternal(ContainerBase.java:759) | at org.apache.catalina.core.ContainerBase.addChild(ContainerBase.java:739) | at org.apache.catalina.core.StandardHost.addChild(StandardHost.java:524) | at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method) | at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:39) | at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25) | at java.lang.reflect.Method.invoke(Method.java:585) | at org.apache.commons.modeler.BaseModelMBean.invoke(BaseModelMBean.java:503) | at org.jboss.mx.server.RawDynamicInvoker.invoke(RawDynamicInvoker.java:164) | at org.jboss.mx.server.MBeanServerImpl.invoke(MBeanServerImpl.java:659) | at org.apache.catalina.core.StandardContext.init(StandardContext.java:5116) | at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method) | at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:39) | at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25) | at java.lang.reflect.Method.invoke(Method.java:585) | at org.apache.commons.modeler.BaseModelMBean.invoke(BaseModelMBean.java:503) | at org.jboss.mx.server.RawDynamicInvoker.invoke(RawDynamicInvoker.java:164) | at org.jboss.mx.server.MBeanServerImpl.invoke(MBeanServerImpl.java:659) | at org.jboss.web.tomcat.tc5.TomcatDeployer.performDeployInternal(TomcatDeployer.java:297) | at org.jboss.web.tomcat.tc5.TomcatDeployer.performDeploy(TomcatDeployer.java:103) | at org.jboss.web.AbstractWebDeployer.start(AbstractWebDeployer.java:371) | at org.jboss.web.WebModule.startModule(WebModule.java:83) | at org.jboss.web.WebModule.startService(WebModule.java:61) | at org.jboss.system.ServiceMBeanSupport.jbossInternalStart(ServiceMBeanSupport.java:289) | at org.jboss.system.ServiceMBeanSupport.jbossInternalLifecycle(ServiceMBeanSupport.java:245) | at sun.reflect.GeneratedMethodAccessor51.invoke(Unknown Source) | at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25) | at java.lang.reflect.Method.invoke(Method.java:585) | at org.jboss.mx.interceptor.ReflectedDispatcher.invoke(ReflectedDispatcher.java:155) | at org.jboss.mx.server.Invocation.dispatch(Invocation.java:94) | at org.jboss.mx.server.Invocation.invoke(Invocation.java:86) | at org.jboss.mx.server.AbstractMBeanInvoker.invoke(AbstractMBeanInvoker.java:264) | at org.jboss.mx.server.MBeanServerImpl.invoke(MBeanServerImpl.java:659) | at org.jboss.system.ServiceController$ServiceProxy.invoke(ServiceController.java:978) | at $Proxy0.start(Unknown Source) | at org.jboss.system.ServiceController.start(ServiceController.java:417) | at sun.reflect.GeneratedMethodAccessor5.invoke(Unknown Source) | at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25) | at java.lang.reflect.Method.invoke(Method.java:585) | at org.jboss.mx.interceptor.ReflectedDispatcher.invoke(ReflectedDispatcher.java:155) | at org.jboss.mx.server.Invocation.dispatch(Invocation.java:94) | at org.jboss.mx.server.Invocation.invoke(Invocation.java:86) | at org.jboss.mx.server.AbstractMBeanInvoker.invoke(AbstractMBeanInvoker.java:264) | at org.jboss.mx.server.MBeanServerImpl.invoke(MBeanServerImpl.java:659) | at org.jboss.mx.util.MBeanProxyExt.invoke(MBeanProxyExt.java:210) | at $Proxy39.start(Unknown Source) | at
