July 2008 - jboss-user - Jboss List Archives

[Beginners Corner] - Re: Starting JBoss server independently

by PeterJ

Use the nohup command. View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=4167128#4167128 Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=4167128

18 years, 1 month

1
0
0 / 0

[Installation, Configuration & DEPLOYMENT] - Re: Host name issue while deploying WebService

by PeterJ

Try editing the webServiceHost property for the WSServerConfig bean in the server/xxx/deploy/jbossws.sar/jbossws.beans/META-INF/jboss-beans.xml file. The problem with changing the binding address in individual files is that that you have to change all of the addresses in all of the files. And then remembed ot also set -b to that same host. It is usually preferred to leave the config files as they are and only use the -b option. Having said that there are situations in which using 0.0.0.0 as the binding address causes weird problems (it has been a while since I dealt with this so I don't recall what the issues were) but using "-b hostname" ("-b STD42515" in your case) should not cause any issues. View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=4167127#4167127 Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=4167127

18 years, 1 month

1
0
0 / 0

[JBoss Tools (users)] - Re: XHTML files and content assist with custom tags

by max.andersen＠jboss.com

campi - please elaborate what you mean by "jboss tools standard" ? There is no such thing - we just understand normal TLD's View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=4167126#4167126 Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=4167126

18 years, 1 month

1
0
0 / 0

[JBoss Tools (users)] - Re: Problems with the Visual Page Editor with Tools 2.1.0 GA

by max.andersen＠jboss.com

p.s. about updating JBDS with random version of jboss tools is doable in most cases by just putting in the plugins/features into the plugins/features directory but it is totally untested by us so I cannot gurantee it. View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=4167124#4167124 Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=4167124

18 years, 1 month

1
0
0 / 0

[JBoss Tools (users)] - Re: Problems with the Visual Page Editor with Tools 2.1.0 GA

by max.andersen＠jboss.com

did you try JBDS 1.1 ? btw. would be great with screenshots in jira. View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=4167123#4167123 Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=4167123

18 years, 1 month

1
0
0 / 0

[JNDI/Naming/Network] - Re: Weblogic EJB lookup fails from JBoss

by PeterJ

Considering that you are using WebLogic client code to access an EJB in WebLogic, and it is that client code that is giving that error message, you really should be asking this on a WebLogic forum or asking WebLogic support. View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=4167122#4167122 Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=4167122

18 years, 1 month

1
0
0 / 0

[Beginners Corner] - Re: File Permissions created by Jboss 4.2.x

by PeterJ

First, I will assume that you created a mew Linux account named "jboss" and that you are running the app server using that account. I will also assume that you changed ownership of jboss_home (and all of the files and directories it contains) to "jboss". Then I will also assume that you used chmod to provide the correct access. Given all of those assumptions, any new file created within jboss_home has the same restrictions as what you set up already. Things you never mentioned in you post: where is the file being create? What restrictions do you have set for the existing files? What restrictions to you want for the new file (if you want different restrictions than the existing files.) Also by "We have to restrict read access for others in linux" do you mean you want other to only be able to read the file (no write access), or that you do not want others to be able to read the file. I could interpret your statement either way, though I would lean towards not allowing anyone to read the file. View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=4167121#4167121 Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=4167121

18 years, 1 month

1
0
0 / 0

[Security & JAAS/JBoss] - Re: JBOSS LDAP Authentification

by indra_joy

I m using LdapLogin Module and Parameters are also pretty standard as below <application-policy name="testLDAP"> <login-module code="org.jboss.security.auth.spi.LdapLoginModule" flag="required"> <module-option name="java.naming.factory.initial"> com.sun.jndi.ldap.LdapCtxFactory </module-option> <module-option name="java.naming.provider.url"> ldap://ldaphost.exampledc=example.com:1389/ </module-option> <module-option name="java.naming.security.authentication"> simple </module-option> <module-option name="principalDNPrefix">uid=</module-option> <module-option name="principalDNSuffix"> ,ou=People,dc=example,dc=com </module-option> <module-option name="rolesCtxDN"> ou=Roles,dc=example,dc=com </module-option> <module-option name="uidAttributeID">member</module-option> <module-option name="matchOnUserDN">true</module-option> <module-option name="roleAttributeID">cn</module-option> <module-option name="roleAttributeIsDN">false </module-option> </login-module> </application-policy> View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=4167120#4167120 Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=4167120

18 years, 1 month

1
0
0 / 0

[JBoss Portal] - Re: Unexpected behaviour of login/logout in JBoss Portal

by PeterJ

The behavior you are asking for is the way it used to work. But the results are not what you imagine. If the page you are viewing is restricted to certain roles, then when you logged out, the next thing you saw was the login page because you no longer had access to the page you were one. And the only way out of the situation was to log back in, go to a page that was not restricted, and log out again. It was a huge hassle. The current behavior is much better. And desiring a different behavior does not make the current behavior a defect. You can always suggest a different behavior and request it as a new feature. View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=4167119#4167119 Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=4167119

18 years, 1 month

1
0
0 / 0

[JBossWS] - Use of PostCreate in JaxWS WebService implementation class

by adinn

JSR 109 appears (to me at least) to suggest that the @PostCreate and @PreDestroy annotations can be used to annotate lifecycle methods of either an EJB or a POJO, so long as the EJB/POJO is tagged with a WebService annotation. Here is the relevant text from version 1.2 anonymous wrote : | 5.3.2.4.2.1 The optional @PostConstruct or @PreDestroy annotations | A Service Implementation Bean may use javax.annotation.PostConstruct or javax.annotation.PreDestroy annotation on methods for lifecycle event callbacks. The methods annotated with javax.annotation.PostConstruct or javax.annotation.PreDestroy annotation allow the web container to notify a Service Implementation Bean instance of impending changes in its state. The bean may use the notification to prepare its internal state for the transition. If the bean implements methods that are annotated with javax.annotation.PostConstruct or javax.annotation.PreDestroy annotations then the container is required to call them in the manner described below. | . . . | This is all subsumed under section 5.3.2.4 'Web container programming model' and is distinct from the case described in section 5.2.3.3 'EJB container programming model' which is why I take it to be referring to use of POJOs annotated with @WebService. I tried to use this feature in a service implementation class running under JBossWS Native 3.0.2 on AS 5.0.0.CR1 and the life cycle methods were not invoked. Is this because I am reading JSR 109 wrong I am reading JSR 109 correct but JBossWS Native 3.0.2 does not (yet) implement lifecycle methods I am reading JSR 109 correct and JBossWS Native 3.0.2 does implement lifecycle methods but there is a bug small print may apply Any clarification would be most gratefully received View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=4167118#4167118 Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=4167118

18 years, 1 month

1
0
0 / 0

2026

2025

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

2009

2008

2007

2006

jboss-user July 2008