[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
17 years, 8 months
[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
17 years, 8 months
[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
17 years, 8 months