[JBossWS] - Re: Document Literal style
by zeeshan.javeed
Hi,
I have generated the code using WSCONSUME and after modifying existing code, when I try to run the old client I got Null Pointer Exception. I generated the new client using the newly generated wsdl file and the new client works fine.
I debuged more and here is the request send by old client.
| POST /wipe/service HTTP/1.1
|
| Content-Type: text/xml; charset=utf-8
|
| Accept: text/xml, text/html, image/gif, image/jpeg, *; q=.2, */*; q=.2
|
| Content-Length: 655
|
| SOAPAction: ""
|
| User-Agent: Java/1.5.0_13
|
| Host: 127.0.0.1:8080
|
| Connection: keep-alive
|
|
|
| <?xml version="1.0" encoding="UTF-8"?>
| <env:Envelope xmlns:env="http://schemas.xmlsoap.org/soap/envelope/" xmlns:xsd="http://www.w3.org/2001/XMLSchema" xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance" xmlns:enc="http://schemas.xmlsoap.org/soap/encoding/" xmlns:ns0="http://ips.iplabs.de/types">
| <env:Body>
| <ns0:startSession>
| <TSession_1>
| <clientLogInfo></clientLogInfo>
| <clientName>testJavaClient</clientName>
| <clientVersion>0.5</clientVersion>
| <errorCode>0</errorCode>
| <errorMessage></errorMessage>
| <localeID>de_DE</localeID>
| <opID>20000100</opID>
| <sessionID></sessionID>
| <wipeVersion>1.1</wipeVersion>
| </TSession_1>
| </ns0:startSession>
| </env:Body>
| </env:Envelope>
|
The request generated by the new client is as
| POST /wipe/service?datatype=JBossWSMessage HTTP/1.1
|
| SOAPAction: ""
|
| Content-Type: text/xml; charset=UTF-8
|
| User-Agent: Java/1.5.0_13
|
| Host: 127.0.0.1:8080
|
| Accept: text/html, image/gif, image/jpeg, *; q=.2, */*; q=.2
|
| Connection: keep-alive
|
| Content-Length: 475
|
|
|
| <env:Envelope xmlns:env='http://schemas.xmlsoap.org/soap/envelope/'>
| <env:Header></env:Header>
| <env:Body>
| <ns1:startSession xmlns:ns1="http://ips.iplabs.de/types">
| <arg0>
| <clientLogInfo></clientLogInfo>
| <clientName>testJavaClient</clientName>
| <clientVersion>0.5</clientVersion>
| <errorCode>0</errorCode>
| <errorMessage></errorMessage>
| <localeID>de_DE</localeID>
| <opID>10000011</opID>
| <sessionID></sessionID>
| <wipeVersion>1.0</wipeVersion>
| </arg0>
| </ns1:startSession>
| </env:Body></env:Envelope
|
|
Any information , what is going wrong here.
The interface file code related to startSession is :
|
| /**
| * This class was generated by the JAX-WS RI.
| * JAX-WS RI 2.1.1-b03-
| * Generated source version: 2.0
| *
| */
| @WebService(name = "Wipe", targetNamespace = "http://ips.iplabs.de/")
| public interface Wipe {
|
|
| /**
| *
| * @param tSession1
| * @return
| * returns de.iplabs.ips.types.TSession
| */
| @WebMethod
| @WebResult(name = "result", targetNamespace = "")
| @RequestWrapper(localName = "startSession", targetNamespace = "http://ips.iplabs.de/types", className = "de.iplabs.ips.types.StartSession")
| @ResponseWrapper(localName = "startSessionResponse", targetNamespace = "http://ips.iplabs.de/types", className = "de.iplabs.ips.types.StartSessionResponse")
| public TSession startSession(
| @WebParam(name = "TSession_1", targetNamespace = "")
| TSession tSession1);
| }
|
|
and the respective implementation is as :
| @WebService(name = "Wipe", targetNamespace = "http://ips.iplabs.de/types")
| public class WipeImpl implements Wipe
| {
|
|
| /**
| *
| * @param tSession1
| * @return
| * returns de.iplabs.ips.types.TSession
| */
| @WebMethod
| public TSession startSession(TSession session)
| {
| if(session != null)
| {
| log.debug("Start session with version: " +
| return getVersion(session).startSession(session);
| }
| else
| {
| log.error("Session is null");
| return null;
| }
| }
|
| }
|
|
Plz guide me, what is going wrong. I have to update server while mainting the compatibility between old client and server.
Regards,
Zeeshan
View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=4117455#4117455
Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=4117455
18 years
[JBossWS] - Re: charset problem with jbossws 2.0.2 and .net clients
by EverlastX1
This is the debug message of the response of the Test(String ping) function from the jboss logs.
The interesting thing about it is that at the point were the logs were created the values are encoded already in utf-8.
So the second encoding step is happening somewhere further beyond this point.
2008-01-05 21:54:36,921 DEBUG [org.jboss.ws.core.EndpointInvocation] setReturnValue: [Ljava.lang.String;
| 2008-01-05 21:54:36,921 DEBUG [org.jboss.ws.core.jaxws.handler.MessageContextJAXWS] Begin response processing
| 2008-01-05 21:54:36,921 DEBUG [org.jboss.ws.core.soap.MessageContextAssociation] popMessageContext: org.jboss.ws.core.jaxws.handler.SOAPMessageContextJAXWS@eb91ec (Thread http-127.0.0.1-8080-13)
| 2008-01-05 21:54:36,921 DEBUG [org.jboss.ws.core.soap.MessageContextAssociation] pushMessageContext: org.jboss.ws.core.jaxws.handler.SOAPMessageContextJAXWS@159318b (Thread http-127.0.0.1-8080-13)
| 2008-01-05 21:54:36,921 DEBUG [org.jboss.ws.core.jaxws.binding.SOAP11BindingJAXWS] bindResponseMessage: {http://WebSevices.test.Company.de/}test
| 2008-01-05 21:54:36,921 DEBUG [org.jboss.ws.core.EndpointInvocation] getReturnValue
| 2008-01-05 21:54:36,921 DEBUG [org.jboss.ws.core.EndpointInvocation] transformPayloadValue: [Ljava.lang.String; -> [Ljava.lang.String;
| 2008-01-05 21:54:36,921 DEBUG [org.jboss.ws.core.jaxrpc.ParameterWrapping] wrapResponseParameter: de.Company.test.WebSevices.jaxws.TestResponse
| 2008-01-05 21:54:36,921 DEBUG [org.jboss.ws.core.EndpointInvocation] setReturnValue: org.jboss.ws.core.soap.SOAPBodyElementDoc
| 2008-01-05 21:54:36,921 DEBUG [org.jboss.ws.core.jaxws.handler.HandlerDelegateJAXWS] callResponseHandlerChain: PRE
| 2008-01-05 21:54:36,921 DEBUG [org.jboss.ws.core.jaxws.handler.HandlerDelegateJAXWS] callResponseHandlerChain: ENDPOINT
| 2008-01-05 21:54:36,921 DEBUG [org.jboss.ws.core.jaxws.handler.HandlerDelegateJAXWS] callResponseHandlerChain: POST
| 2008-01-05 21:54:36,921 DEBUG [org.jboss.ws.core.jaxws.handler.HandlerDelegateJAXWS] closeHandlerChain
| 2008-01-05 21:54:36,921 DEBUG [org.jboss.ws.core.jaxws.handler.HandlerChainExecutor] close
| 2008-01-05 21:54:36,921 DEBUG [org.jboss.ws.core.jaxws.handler.HandlerDelegateJAXWS] closeHandlerChain
| 2008-01-05 21:54:36,921 DEBUG [org.jboss.ws.core.jaxws.handler.HandlerChainExecutor] close
| 2008-01-05 21:54:36,921 DEBUG [org.jboss.ws.core.jaxws.handler.HandlerDelegateJAXWS] closeHandlerChain
| 2008-01-05 21:54:36,921 DEBUG [org.jboss.ws.core.jaxws.handler.HandlerChainExecutor] close
| 2008-01-05 21:54:36,921 DEBUG [org.jboss.wsf.stack.jbws.RequestHandlerImpl] END handleRequest: jboss.ws:context=SKMS_Server-SKMS_Server,endpoint=ServerAgentEndpointBean
| 2008-01-05 21:54:36,921 DEBUG [org.jboss.ws.core.soap.SOAPContentElement] -----------------------------------
| 2008-01-05 21:54:36,921 DEBUG [org.jboss.ws.core.soap.SOAPContentElement] Transitioning from OBJECT_VALID to XML_VALID
| 2008-01-05 21:54:36,921 DEBUG [org.jboss.ws.core.soap.ObjectContent] getXMLFragment from Object [xmlType={http://WebSevices.test.Company.de/}testResponse,javaType=class de.Company.test.WebSevices.jaxws.TestResponse]
| 2008-01-05 21:54:36,921 DEBUG [org.jboss.ws.core.jaxws.JAXBSerializer] serialize: [xmlName={http://WebSevices.test.Company.de/}testResponse,xmlType={http://WebSevices.test.Company.de/}testResponse]
| 2008-01-05 21:54:36,921 DEBUG [org.jboss.ws.core.jaxws.JAXBSerializer] serialized: <ns2:testResponse xmlns:ns2="http://WebSevices.test.Company.de/"><return>Greetings from J with ü -- ö</return><return>from .NET with ü -- ö</return></ns2:testResponse>
| 2008-01-05 21:54:36,921 DEBUG [org.jboss.ws.core.soap.ObjectContent] xmlFragment: [source=<ns2:testResponse xmlns:ns2="http://WebSevices.test.Company.de/"><return>Greetings from J with ü -- ö</return><return>from .NET with ü -- ö</return></ns2:testResponse>]
| 2008-01-05 21:54:36,921 DEBUG [org.jboss.ws.core.soap.SOAPContentElement] -----------------------------------
|
View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=4117361#4117361
Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=4117361
18 years
[JBossWS] - charset problem with jbossws 2.0.2 and .net clients
by EverlastX1
Good evening ladies and gentleman,
I am struggling sending special character like the German üö from the .net client to the jboss server.
I have the following reproducible scenario:
jboss 4.22
jbossws 2.0.2GA
.Net Client
.net is pinging the following String to jboss:
""from .NET with ü -- ö""
Jboss is receiving this string and post back an array with following to values
"from .NET with ü -- ö" the String .net sended just post it back
"Greetings from J with ü -- ö"
.net output is:
Sending: from .NET with ü -- ö
Recived from Jboss Value 1: Greetings from J with ü -- ö
Recived from Jboss Value 2: from .NET with ü -- ö
the jboss output is:
2008-01-05 21:54:36,921 DEBUG [de.Company.test.WebSevices.ServerAgentEndpointBean] from .Net recived: from .NET with ü -- ö
The interesting thing is happening when the protocol sniffer is on:
in the Sniffer: .NET is Sending
POST /SKMS_Server-SKMS_Server/ServerAgentEndpointBean HTTP/1.1
| User-Agent: Mozilla/4.0 (compatible; MSIE 6.0; MS Web Services Client Protocol 2.0.50727.1433)
| Content-Type: text/xml; charset=utf-8
| SOAPAction: ""
| Host: 127.0.0.1:8080
| Content-Length: 359
| Expect: 100-continue
| Connection: Keep-Alive
| <?xml version="1.0" encoding="utf-8"?>
| <soap:Envelope xmlns:soap="http://schemas.xmlsoap.org/soap/envelope/"xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance" xmlns:xsd="http://www.w3.org/2001/XMLSchema">
| <soap:Body>
| <test xmlns="http://WebSevices.test.company.de/">
| <TestString xmlns="">from .NET with ü -- ö</TestString>
| </test>
| </soap:Body>
| </soap:Envelope>
|
|
in the Sniffer: Jboss Server is sending back!
| HTTP/1.1 200 OK
| Server: Apache-Coyote/1.1
| X-Powered-By: Servlet 2.4; JBoss-4.2.2.GA (build: SVNTag=JBoss_4_2_2_GA date=200710221139)/Tomcat-5.5
| Content-Type: text/xml;charset=UTF-8
| Transfer-Encoding: chunked
| Date: Sat, 05 Jan 2008 20:54:36 GMT
|
| <env:Envelope xmlns:env='http://schemas.xmlsoap.org/soap/envelope/'>
| <env:Header></env:Header><env:Body>
| <ns2:testResponse xmlns:ns2="http://WebSevices.test.company.de/">
| <return>Greetings from J with �¼ -- �¶</return><return>from .NET with �¼ --
| �¶
| </return></ns2:testResponse></env:Body></env:Envelope>
|
The .NET Client Code
| test test_remote = new WebReference.test();
| String tesString = "from .NET with ü -- ö";
| test_remote.TestString = tesString;
|
| string[] result = new WebReference.ServerAgentEndpoint().test(test_remote);
|
| Console.WriteLine("Sending: " + tesString);
| Console.WriteLine("Recived from Jboss Value 1: " + result[0]);
| Console.WriteLine("Recived from Jboss Value 2: " + result[1]);
|
The Java Code is:
| @WebMethod
| public String[] test (@WebParam(name="TestString") String str){
| String[] result = new String[]{"Greetings from J with ü -- ö",str};
| log.debug("from .Net recived: " + str);
| log.debug("This will be the result by Jboss to .Net" + result.toString());
| return result;
| }
|
|
|
As I see it from the sniffer the .Net client is sendig the data right to jboss encoding the content with utf-8 and jboss is decoding it right.
When jboss is sending data to .net the data are encoded twice with utf-8
you can see it in the sniffer.
.net is sending: from .NET with ü -- ö" <<-- sniffer: encoded once with utf-8
The line "from J with �¼ -- �¶" <<-- sniffer: utf-8 over utf-8
.net did it right and encoded it to "from J with ü -- ö" <<-- decoded the string but still one utf-8 encoding is left.
so i guess something is wrong with the utf-8 encoding in jboss or jbossws?
can anybody verify my problem?
greetings
V.
View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=4117341#4117341
Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=4117341
18 years
[JBossWS] - Re: Writing a client - no examples for BindingProvider based
by mjhammel
I got a little further now. First, http://weblogs.java.net/blog/ss141213/archive/2005/12/dont_use_persis_1.html explains the problem a bit - you can't use injection in Web apps, which I assume translates to Web Services. So I used the technique listed in the blog.
This worked, eventually, after I added a couple of lines to my persistence.xml, as suggested by the JBOSS App Server entity config documentation (http://docs.jboss.org/ejb3/app-server/reference/build/reference/en/html/e...).
updated persistence.xml
<persistence>
|
| <persistence-unit name="Crunch">
| <jta-data-source>java:/CrunchDS</jta-data-source>
| <properties>
| <property name="hibernate.dialect" value="org.hibernate.dialect.MySQLDialect"/>
| <property name="hibernate.connection.driver_class" value="com.mysql.jdbc.Driver"/>
| <property name="hibernate.connection.url" value="jdbc:mysql://localhost/crunch"/>
| <property name="hibernate.connection.username" value="root"/>
| <property name="jboss.entity.manager.jndi.name" value="java:/CrunchPersistence"/>
| <property name="jboss.entity.manager.factory.jndi.name" value="java:/CrunchFactory"/>
| </properties>
| </persistence-unit>
| </persistence>
The two jndi related properties bound the names specified in the property to the application so that they could be referenced an InitialContext.lookup() (see code below).
Now I can see the Session Bean retrieving the data from the database, but then it immediately complains about some "lazy" thing:
17:11:24,689 INFO [STDOUT] Subscriber.find(): em is not null; returning subscriber for guid = CRUNCH-DEFAULT-SUPERUSER
| 17:11:25,015 INFO [STDOUT] Subscriber name : SuperUser
| 17:11:25,015 INFO [STDOUT] Subscriber email: admin@localhost
| 17:11:25,176 ERROR [LazyInitializationException] failed to lazily initialize a collection of role: com.cei.crunch.ejb.Subscriber.crunchroleses, no session or session was closed
It should be noted that "crunchroleses" is a field in a generated class. The class, com.cei.crunch.ejb.Subscriber, is generated by the reverse engineering process provided through Hibernate in order to generate EJB code for an existing database. So maybe there is some (yet more) additional configuration of Hibernate that needs to be done.
My Web Services code now looks like this:
package com.cei.crunch.server.ws.SubscriberServices;
|
| import javax.ejb.*;
| import javax.jws.WebService;
| import javax.jws.WebMethod;
| import javax.jws.soap.SOAPBinding;
| import javax.persistence.*;
| import javax.naming.InitialContext;
|
| import com.cei.crunch.server.util.SubscriberUtil;
| import com.cei.crunch.ejb.Subscriber;
|
| /* Make this an EJB3 service endpoint. */
| @Stateless
| @Remote(SubscriberServices.class)
|
| /* Make this an Web Services endpoint. */
| @WebService(endpointInterface = "com.cei.crunch.server.ws.SubscriberServices.SubscriberServicesEndpoint")
| @SOAPBinding(style = SOAPBinding.Style.RPC)
|
| /**
| * The .Crunch interface to Subscriber Services
| */
| public class SubscriberServices implements SubscriberServicesEndpoint {
|
| @WebMethod
| public Subscriber findSubscriber(String guid)
| {
| Subscriber s;
| SubscriberUtil su = new SubscriberUtil();
|
| s = su.find(guid);
| if ( s == null )
| System.out.println("su.find() returned null.");
| return s;
| }
|
| }
My Session Bean code, which is called by the Web Services code above, looks like this:
package com.cei.crunch.server.util;
|
| import javax.ejb.*;
| import javax.jws.soap.SOAPBinding;
| import javax.persistence.*;
| import javax.naming.InitialContext;
| import javax.transaction.UserTransaction;
| import javax.annotation.Resource;
|
| import com.cei.crunch.ejb.Subscriber;
|
| /* Make this an EJB3 service endpoint. */
| @Stateless
|
| /**
| * The .Crunch interface to Subscriber Services
| */
| public class SubscriberUtil implements SubscriberUtilInterface {
|
| @Resource
| private UserTransaction utx;
|
| public Subscriber find(String guid)
| {
| InitialContext ctx = null;
| EntityManager em = null;
| try {
| ctx = new InitialContext();
| em = (EntityManager) ctx.lookup("java:/CrunchPersistence");
| }
| catch (Exception e)
| {
| // throw new WebServiceException(ex);
| System.out.println("Subscriber.find(): context lookup failure.");
| e.printStackTrace();
| return null;
| }
|
| if ( em == null )
| {
| System.out.println("Subscriber.find(): em is null; can't find subscriber");
| return null;
| }
| else
| {
| Subscriber s = null;
| System.out.println("Subscriber.find(): em is not null; returning subscriber for guid = " + guid);
| try {
| utx = (UserTransaction) ctx.lookup("java:/comp/UserTransaction");
| utx.begin();
| s = em.find(Subscriber.class, guid);
| utx.commit();
| }
| catch (Exception e)
| {
| System.out.println("Subscriber.find(): find problem.");
| e.printStackTrace();
| }
| if ( s != null )
| {
| System.out.println("Subscriber name : " + s.getFirstname());
| System.out.println("Subscriber email: " + s.getEmailAddress());
| }
| return s;
| }
| }
|
| }
You'll note that I manually create a UserTransaction here. This is because if I don't do this, no transaction is injected into the Session Bean by the @Resource (I don't know why). And if I don't create the UserTransaction before referencing the EntityManager (em), I get a null pointer exception when I do reference it.
My best guess at this is that the UserTransaction is in the wrong place - it may need to go in the Web Services class before it calls the Session Bean. However, that's pretty much a WAG at this point.
View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=4117235#4117235
Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=4117235
18 years
[JBossWS] - Re: Writing a client - no examples for BindingProvider based
by mjhammel
anonymous wrote : The application server includes a webservice stack (JBossWS) you can of course use without any further installation. However you would probably want to upgrade the ws stack since JBossWS is released more often than the application server.
Okay. I'll look into doing this. I downloaded the binary dist and found the Install doc.
anonymous wrote : This seems to me an issue with the libraries in your classpath. Check for example that jaxb-api.jar is in your classpath.
That fixed it. The compile completed, although running the client needed more classpath fixups (some jars included in the classpath for the old version of the build for 4.0.5GA needed to be removed as well).
Thanks for the tips. I'm much closer now. My client actually connects to the web service endpoint and passes in an argument (which the web service prints to the console), but the EntityManager is not being injected. I was going to move this question to another forum but now I'm not sure which forum it belongs in: JBossWS, Persistance/Hibernate or EJB3.0? So for now I'll post here.
Here is my web service code, based on the EJB3.0 TrailBlazer examples (http://trailblazer.demo.jboss.com/EJB3Trail/):
package com.cei.crunch.server.SubscriberServices;
|
| import javax.ejb.*;
| import javax.jws.WebService;
| import javax.jws.WebMethod;
| import javax.jws.soap.SOAPBinding;
| import javax.persistence.*;
| import javax.naming.InitialContext;
|
| import com.cei.crunch.ejb.Subscriber;
| import com.cei.crunch.ejb.Subscribersession;
|
| /* Make this an EJB3 service endpoint. */
| @Stateless
| @Remote(SubscriberServices.class)
|
| /* Make this an Web Services endpoint. */
| @WebService(endpointInterface = "com.cei.crunch.server.SubscriberServices.SubscriberServicesEndpoint")
| @SOAPBinding(style = SOAPBinding.Style.RPC)
|
| /**
| * The .Crunch interface to Subscriber Services
| */
| public class SubscriberServices implements SubscriberServicesEndpoint {
|
| @PersistenceContext (unitName="Crunch")
| EntityManager em;
|
| public void createSubscriber(Subscriber subscriber)
| {
| if ( em != null )
| em.persist(subscriber);
| else
| System.out.println("SubscriberServices: em is null; can't create subscriber");
| }
|
| @WebMethod
| public Subscriber findSubscriber(String guid)
| {
| System.out.println("findSubscriber: guid = " + guid);
| if ( em == null )
| {
| System.out.println("SubscriberServices: em is null; can't find subscriber");
| return null;
| }
| else
| return em.find(Subscriber.class, guid);
| }
|
| public void createSubscriberSession(Subscribersession session)
| {
| em.persist(session);
| }
|
| public Subscribersession findSubscriberSession(String guid)
| {
| return em.find(Subscribersession.class, guid);
| }
| }
My client code looks the same as in my original post. When the client is run the server console prints out the inbound guid and then prints that em is null.
12:12:28,276 INFO [STDOUT] findSubscriber: guid = CRUNCH-DEFAULT-SUPERUSER
| 12:12:28,276 INFO [STDOUT] SubscriberServices: em is null; can't find subscriber
My persistence.xml looks like this:
<persistence>
| <persistence-unit name="Crunch">
| <jta-data-source>java:/CrunchDS</jta-data-source>
| <properties>
| <property name="hibernate.dialect" value="org.hibernate.dialect.MySQLDialect"/>
| <property name="hibernate.connection.driver_class" value="com.mysql.jdbc.Driver"/>
| <property name="hibernate.connection.url" value="jdbc:mysql://localhost/crunch"/>
| <property name="hibernate.connection.username" value="root"/>
| </properties>
| </persistence-unit>
| </persistence>
I've read in a few places that PersistenceContext injection doesn't work in web services (even to the point that the relevant spec says it's not supported, apparently), but I'm confused on what the alternative is supposed to be.
View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=4117180#4117180
Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=4117180
18 years
[JBossWS] - how to get password in handler
by jalaja
hi
i am using jax-ws handlers,i have set username and paddword property in client side
Map context = ((BindingProvider) hello).getRequestContext();
context.put(BindingProvider.USERNAME_PROPERTY, "user");
context.put(BindingProvider.PASSWORD_PROPERTY, "pass");
in the handler i want to access username and password
i am able to get username
public boolean handleMessage(MessageContext context) {
javax.servlet.http.HttpServletRequest httpServletRequest = ((javax.servlet.http.HttpServletRequest)context.get(MessageContext.SERVLET_REQUEST));
System.out.println("user name"+httpServletRequest.getRemoteUser());
System.out.println("principle"+httpServletRequest.getUserPrincipal());
return true;
}
i am getting fallowing output from the handler
user name user
user username="user" password="pass" roles="basicUser"
but i need password alone ....
how to get password alone...which property i have to use
View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=4117016#4117016
Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=4117016
18 years