April 2008 - jboss-dev-forums - Jboss List Archives

[Design of JBoss Remoting, Unified Invokers] - Re: NoSuchObjectException on Server Restart (RMIClientInvoke

by ron.sigal＠jboss.com

Response on Remoting users forum (http://www.jboss.com/index.html?module=bb&op=viewtopic&p=4146972#4146972). View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=4146973#4146973 Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=4146973

16 years, 6 months

1
0
0 / 0

[Design of AOP on JBoss (Aspects/JBoss)] - Re: Classloading problems with ClassProxyFactory

by flavia.rainone＠jboss.com

Hm... interesting. I'll try to run the test locally and see if I can get any further. View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=4146968#4146968 Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=4146968

16 years, 6 months

1
0
0 / 0

[Design of AOP on JBoss (Aspects/JBoss)] - Re: Classloading problems with ClassProxyFactory

by bstansberry＠jboss.com

My test fails on Windows XP as well. Not every time, but most. FYI, here's how to run that test 1) Build the AS and its testsuite from trunk. 2) In on window start the AS with the all config 3) From the root of the testsuite module: ./run.sh -Dtest=org.jboss.test.cluster.classloader.leak.test.ReplicableClassesClassloaderLeakUnitTestCase one-test There's 2 methods, one uses aopc-prepared classes, the other doesn't. The former fails. But when I analyze the heap, all I see are chains leading to weak references. View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=4146958#4146958 Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=4146958

16 years, 6 months

1
0
0 / 0

[Design of JBoss Web Services] - POJO not getting exposed as webservice

by amit.sfbay

This is the first time I am creating a WS using JBoss. When I add web service annotation(s) on my EJB, it does show up in the JBossWS/Services web page. When I put the same on a POJO(not an EJB component), it does not. Any ideas what I might be doing wrong? View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=4146950#4146950 Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=4146950

16 years, 6 months

1
0
0 / 0

[Design of AOP on JBoss (Aspects/JBoss)] - Re: Classloading problems with ClassProxyFactory

by bstansberry＠jboss.com

Yep; Fedora 7 and Sun JVM. I've got my tests 98% down to a usable-by-others form. I'm going to grab a bite to eat, get them to 100%, check them in, try them on Windows XP and post back. View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=4146916#4146916 Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=4146916

16 years, 6 months

1
0
0 / 0

[Design of EJB 3.0] - Re: WS EJB invocation

by heiko.braun＠jboss.com

I don't know why, but for some reason the Ejb3Deployment of jar seems to pretend a parent ear scope. View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=4146915#4146915 Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=4146915

16 years, 6 months

1
0
0 / 0

[Design of EJB 3.0] - WS EJB invocation

by heiko.braun＠jboss.com

Web service invocations have been done by locating the ejb container and executing #localInvoke(...) on it. We used to locate the container by object name: | kernel.getInstalledContext( objectName.getCanonicalName() ) | With the latest codebase I see that the objectname for a simple jar deployment changed from jboss.j2ee:name=Ejb3WSEndpointImpl,service=EJB3,jar=webservices-ejb3.jar to jboss.j2ee:ear=webservices-ejb3.jar,jar=webservices-ejb3.jar,name=Ejb3WSEndpointImpl,service=EJB3 which used to be the case when an ejb.jar was deployed inside an ear. I am currently wondering - why that changed (bug?) - and if there is better way to do this at all. View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=4146911#4146911 Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=4146911

16 years, 6 months

1
0
0 / 0

[Design of AOP on JBoss (Aspects/JBoss)] - Re: Classloading problems with ClassProxyFactory

by flavia.rainone＠jboss.com

Hi, Brian! Are you using Linux? If yes, are you using the Sun's jvm? If you have answered yes to both questions, you might be facing a situation similar to the one we are facing with our memory leak tests. Some of them fail only on Linux when using Sun's jvm. If we try running them on Windows XP, or on a different jvm (say, JRockit), they don't fail. The situation is very similar to yours: the class loader is never collected and the references to classes are held through weak references only. I haven't managed to figure out why yet. View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=4146910#4146910 Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=4146910

16 years, 6 months

1
0
0 / 0

[Design of Security on JBoss] - Re: Security Injection in AS5

by sguilhen＠redhat.com

Yes, I can. What I want to achieve is what Adrian suggested in his first post in this thread: anonymous wrote : | make security domains deployable inside the MC by writing a BeanMetaDataFactory | | <bean name="Whatever" ...> | <property name="securityDomain><inject name="jbossmq" property="securityDomain"/></property> | </bean> | | <application-policy xmlns="urn:jboss-security-beans:1.0" name="jbossmq"> | <authentication> | <login-module code = "org.jboss.security.auth.spi.DatabaseServerLoginModule" | flag = "required"> | <module-option name = "unauthenticatedIdentity">guest</module-option> | <module-option name = "dsJndiName">java:/DefaultDS</module-option> | <module-option name = "principalsQuery">SELECT PASSWD FROM JMS_USERS WHERE USERID=?</module-option> | <module-option name = "rolesQuery">SELECT ROLEID, 'Roles' FROM JMS_ROLES WHERE USERID=?</module-option> | </login-module> | </authentication> | </application-policy> | I've started by taking a look at the aop-mc integration, as AOP had to define their beans and metadata factories to make it possible to use the aop elements in the -beans.xml files. So I've created a module, security-mc-int under the microcontainer project (not sure it should be there, just using the same approach AOP has taken), defined the beans, defined the security-beans.xsd, and started the implementation of the metadata factory. This factory is responsible for providing the metadata that is used to create the beans from the information parsed. An example of the beans that would result from the factory follows: | <bean name="jbossmq" class="org.jboss.security.microcontainer.beans.ApplicationPolicyBean> | <property name="authenticationPolicy"><inject bean="jbossmq$AuthPolicy"/></property> | </bean> | | <bean name="jbossmq$AuthPolicy" class="org.jboss.security.microcontainer.beans.AuthenticationPolicyBean"> | <property name="loginModules"> | <list> | <inject bean="jbossmq$LoginModule1"/> | <inject bean="jbossmq$LoginModule2"/> | </list> | </property> | </bean> | | <bean name="jbossmq$LoginModule1" class="org.jboss.security.microcontainer.beans.LoginModuleBean"> | <property name="flag">required</property> | <property name="code">org.jboss.security.auth.spi.UsersRolesLoginModule</property> | <property name="moduleOptions"> | <map keyClass="java.lang.String" valueClass="java.lang.String"> | <entry> | <key>usersProperties</key> | <value>jboss-users.properties</value> | </entry> | <entry> | <key>rolesProperties</key> | <value>jboss-roles.properties</value> | </entry> | </map> | <property> | </bean> | | <bean name="jbossmq$LoginModule2" class="org.jboss.security.microcontainer.beans.LoginModuleBean"> | <property name="flag">optional</property> | <property name="code">org.jboss.security.auth.spi.DataBaseServerLoginModule</property> | <property name="moduleOptions"> | <map keyClass="java.lang.String" valueClass="java.lang.String"> | <entry> | <key>principalsQuery</key> | <value>SELECT PASSWD FROM USERS WHERE USER_ID=?</value> | </entry> | <entry> | <key>rolesQuery</key> | <value>SELECT ROLE_ID, 'Roles' FROM ROLES WHERE USER_ID=?</value> | </entry> | </map> | <property> | </bean> | The top-level ApplicationPolicyBean would, after being initialized, push the ApplicationPolicy to the security layer to register the new policy (along with the login modules configuration). I still have to figure out a couple of things. First, can I add post-installation behavior to my beans just by implementing the install and uninstall methods or is it necessary to configure an aop lifecycle for that? Second, I don't expect things to magically happen just by defining the metadata factory. Somehow I must bind it to the schema being parsed (that is, somehow the MC must know which factory to use when facing an application-policy element). View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=4146902#4146902 Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=4146902

16 years, 6 months

1
0
0 / 0

[Design of JBoss Web Services] - Unlocking WS-Security in Metro

by alessio.soldano＠jboss.com

Hi Folks, I've just committed some tests showing how to use ws-security with the jbossws-metro stack (http://fisheye.jboss.com/changelog/JBossWS/?cs=6713). Documentation will come on the wiki. However the tests requiring keystore/trustore files (i.e. those involving signature and encryption) are currently disabled since the metro sources we're currently using do not scan the client/server application jars for the keystore/trustore files. This means we have to provide absolute paths to the filesystem in the configuration files to tell the stack where those files are. I found out on the wsit fisheye that more recent releases also scan the jar's META-INF folder and that's why I created JIRA-2158. I've also disabled the UsernameTokenProfile test since it's not possible to enable username token without using a transport security (i.e. https) or -again- message level protection (i.e. sign & encrypt). The problem with https is the same we currently have for the interop usernametoken+http tests which are excluded because they require a proper jboss-web tomcat configuration along with the references to the keystore/trustore to be used for ssl. Does anybody have an interesting idea about this? View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=4146888#4146888 Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=4146888

16 years, 6 months

1
0
0 / 0

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

2009

2008

2007

2006

jboss-dev-forums April 2008