I have successfully used the stand-alone implementation of remoting 1.0.1 beta
in a prototype and now want to replace the stand-alone server with JBoss AS
4.0.1
Research / trial and error led me to the need to replace jboss-common.jar in
{JBOSS_HOME}\lib with the one distributed with the stand-alone remoting
package. However, this causes a number of other issues; the first one being:
23:26:18,713 WARN [XMLLoginConfigImpl] End loadConfig, failed to load config:
file:/C:/jboss-4.0.1/server/default/conf/login-config.xml
org.jboss.security.auth.login.ParseException: Encountered "<?xml" at line 1,
column 1.
Was expecting one of:
...
at
org.jboss.security.auth.login.SunConfigParser.generateParseException(SunConfigParser.java:389)
at
org.jboss.security.auth.login.SunConfigParser.jj_consume_token(SunConfigParser.java:327)
at
org.jboss.security.auth.login.SunConfigParser.config(SunConfigParser.java:98)
I've tried replacing all 4.0.1 jar files with those delivered in the
stand-alone remoting package but can't get past this error.
Presumably there is more to it than this? Is it possible to user JBoss AS
4.0.1 (or a slightly modified version)? What is the recommended application
server version to use for remoting for new development?
View the original post :
http://www.jboss.org/index.html?module=bb&op=viewtopic&p=3866382#3866382
Reply to the post :
http://www.jboss.org/index.html?module=bb&op=posting&mode=reply&p=3866382
-------------------------------------------------------
SF email is sponsored by - The IT Product Guide
Read honest & candid reviews on hundreds of IT Products from real users.
Discover which products truly live up to the hype. Start reading now.
http://ads.osdn.com/?ad_id=6595&alloc_id=14396&op=click
_______________________________________________
JBoss-Development mailing list
[email protected]
https://lists.sourceforge.net/lists/listinfo/jboss-development
