This raises many more questions. ONE)
I am using a custom security domain, how come it never gets called when I attempt to invoke this web service? Is this in anyway affected by the fact that I am calling this endpoint from a non-J2EE environement, as shown in the JBoss 4.0.0. Getting Started documentation? I never tested that web services example, but now I am beginning to wonder if it works. TWO) Is there an actual application policy named JBossWS that I must set? Or is JBossWS just a a place-holder for my custom application policy that I am using. <application-policy name="JBossWS"> THREE) Will I need to modify the jboss.net and jboss.net-uddi aplication policies, or are those legacy configurations from jboss 3.2.X ? FOUR) How do I insure that my non-J2EE Java Client gets passed through the authentication mechanisms(application policies in the login-config.xml)? I really am trying to setup a simple web services example with my stateless session bean, as shown in the Getting Started Documentation. View the original post : http://www.jboss.org/index.html?module=bb&op=viewtopic&p=3855512#3855512 Reply to the post : http://www.jboss.org/index.html?module=bb&op=posting&mode=reply&p=3855512 ------------------------------------------------------- This SF.Net email is sponsored by: InterSystems CACHE FREE OODBMS DOWNLOAD - A multidimensional database that combines robust object and relational technologies, making it a perfect match for Java, C++,COM, XML, ODBC and JDBC. www.intersystems.com/match8 _______________________________________________ JBoss-Development mailing list [EMAIL PROTECTED] https://lists.sourceforge.net/lists/listinfo/jboss-development
