[Installation, Configuration & DEPLOYMENT] - Re: deploy a war file with Jboss to a permanent location
by Mazarj
heyyy, thanks for helping
I'm a little bit lost
can u please help mewhat should I do?
(my application is sabswing.war)
I have this at the end of server/default/conf/jboss-service.xml
<!-- URLs are comma separated and resolve relative to the server home URL
unless the given path is absolute. If the URL ends in "/" it is
considered a collection and scanned, otherwise it is simply deployed;
this follows RFC2518 convention and allows discrimination between
collections and directories that are simply unpacked archives.
URLs may be local (file:) or remote (http:). Scanning is supported
for remote URLs but unpacked deployment units are not.
Example URLs:
deploy/
scans ${jboss.server.url}/deploy/, which is local or remote
depending on the URL used to boot the server
${jboss.server.home}/deploy/
scans ${jboss.server.home)/deploy, which is always local
file:/var/opt/myapp.ear
deploy myapp.ear from a local location
file:/var/opt/apps/
scans the specified directory
http://www.test.com/netboot/myapp.ear
deploys myapp.ear from a remote location
http://www.test.com/netboot/apps/
scans the specified WebDAV location
-->
deploy/
<!-- Indicates if the scanner should recursively scan directories that
contain no "." in their names. This can be used to group applications
and services that must be deployed and that have the same
logical function in the same directory i.e.
deploy/JMX/
deploy/JMS/
...
-->
True
I need ur help
thanks in advance
View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=4077817#4077817
Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=4077817
18Â years, 8Â months
[JBoss Portal] - Re: UserFriendly URLs: Can we have an '_' instead of '+' in
by bvogt
we have a solution based on portal 2.4 / AS 4.0.5...
...luckily live, since yesterday evening...
In portal 2.4.1 (and hopefully in 2.6 too) you have to differentiate between page localization and page identification.
The name you edit in the management portlet is used for building the portal URLs.
With this kept in mind we did:
1. decided, that page names are treated as keys to be looked up in property files - all localization is done within this set of locaization files
2. provided a custom navigation portlet which retrieves the page name and localizes it
3. due to the lack of knowledge how to define a page interceptor for page related tasks... we set the localized page name into the portlet session with APPLICATION_SCOPE
4. in the theme's index.jsp we retrieve the localized page name out of the session and set it within the title tag.
Yes, you're right, 3. and 4. are somewhat like a hack, but it works...
View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=4077814#4077814
Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=4077814
18Â years, 8Â months