[JBoss Seam] - No action called
by vikramchhetryy
Hi all,
I want to view details of a user by clicking on a link. But when I click the link nothing happens. I went accross the seam-booking example but couldnt figure out the problem.
My Code
XHTML
| <h:column>
| <f:facet name="header">Action</f:facet>
| <s:link id="editCallCenterAgent" value="Edit" action="callCenterAgentEdit.editSelectedCallCenterAgentDetails(details)" />
| </h:column>
|
Stateful bean:
public class CallCenterAgentEditAction implements CallCenterAgentEdit {
|
| @Logger
| private Log log;
|
| @In
| FacesMessages facesMessages;
|
| /*@In(required=false) @Out
| private Account account;*/
|
| @Begin
| public void editSelectedCallCenterAgentDetails(Account acc) {
| log.info("Inside editSelectedCallCenterAgentDetails method "
| + acc.getPerson().getStrFirstName());
| getSelectedCallCenterAgentDetails(acc.getStrUserName());
| log.info("Exiting editSelectedCallCenterAgentDetails method");
| }
|
| public void getSelectedCallCenterAgentDetails(String userName) {
| log.info("Inside getSelectedCallCenterAgentDetails method " + userName);
|
| log.info("Exiting getSelectedCallCenterAgentDetails method");
| }
|
| @End
| public void updateCallCenterAgentDetails() {
| log.info("Inside updateCallCenterAgentDetails method");
|
| log.info("Exiting updateCallCenterAgentDetails method");
| }
|
| @Remove
| public void destroy() {
| }
|
| @End
| public void cancel() {
| }
|
| }
|
Call any one tell me whats going wrong? Do I need to do something more to get it working?
Any help would be appreciated.
-VIkram
View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=4118568#4118568
Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=4118568
18 years, 6 months
[JBoss Seam] - Re: Design question with Rich GWT Ajax Client
by sdegardin
I have a working solution ....
in my ContextualHttpRequest, I call the same code as in SeamPhaseListener for JSF.
before proceeding the request :
anonymous wrote :
| void begin()
| {
| try
| {
| if ( !Transaction.instance().isActiveOrMarkedRollback() )
| {
| //log.debug("beginning transaction prior to phase: " + phaseId);
| Transaction.instance().begin();
| }
| }
| catch (Exception e)
| {
| throw new IllegalStateException("Could not start transaction", e);
| }
| }
|
at the end :
anonymous wrote :
| void commitOrRollback()
| {
| try
| {
| if ( Transaction.instance().isActive() )
| {
| //log.debug("committing transaction after phase: " + phaseId);
| Transaction.instance().commit();
| }
| else if ( Transaction.instance().isRolledBackOrMarkedRollback() )
| {
| //log.debug("rolling back transaction after phase: " + phaseId);
| Transaction.instance().rollback();
| }
| }
| catch (Exception e)
| {
| throw new IllegalStateException("Could not commit transaction", e);
| }
| }
|
|
I'm sure there are issue with this solution but it works for the begining ...
View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=4118567#4118567
Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=4118567
18 years, 6 months
[EJB 3.0] - DataSource resource injection
by francis1970
Hi all!
sorry for bothering again about injection.
I'm unable to inject a Datasource resource into my EJB.
n my EJB I use:
@Resource(mappedName="java:jdbc/MyDS")
| protected DataSource dataSource;
in my .ds file I use the following
<jndi-name>jdbc/MyDS</jndi-name>
When I try to use the Datasource I get
java.lang.RuntimeException: Unable to inject jndi dependency: env/oracle.ejb30.HelloTestBean/dataSource into property oracle.ejb30.HelloTestBean.dataSource: jdbc not bound
Should I insert a resource-ref also in jboss.xml ? or in ejb-jar.xml too ??
I really hope I don't need to use ejb-jar.xml anymore since I'm fed up with it..........
Thanks for your feedback.......
By the way I'm using JBoss 4.2.x
Thanks
Francesco
View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=4118566#4118566
Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=4118566
18 years, 6 months
[EJB/JBoss] - @ApplicationException(rollback=false) does roll back @PreUpd
by skeyewalk
I have encountered a very unfortunate and strange difference in the way JBoss application server 4.2.2 treats exceptions raised from inside EJB callback methods marked with @PrePersist and @PreUpdate.
My exception is a RuntimeException, and is marked for rollback=false. I use it to report back validation errors. The validation is triggered in the @PrePersist and @PreUpdate callback methods. However, while this behaves very nicely for the persist method, the update does not appear to take the @ApplicationException annotation into account. So the transaction is rolled back and my exception is wrapped inside a javax.persistence.PersistenceException and then inside a javax.transaction.RollbackException, blowing up my whole concept.
I have also tried configuring the ApplicationException in the ejb-jar.xml, but the result was identical.
Here's the exception class:
@ApplicationException(rollback=false)
| public class ValidationExceptionRuntimeWrapper extends RuntimeException
| {
| private static final long serialVersionUID = 1L;
|
| private ValidationException validationException;
|
|
| public ValidationExceptionRuntimeWrapper(ValidationException validationException)
| {
| this.validationException = validationException;
| }
|
| public ValidationException getValidationException()
| {
| return validationException;
| }
|
| public void setValidationException(ValidationException validationException)
| {
| this.validationException = validationException;
| }
|
| }
|
Has anyone seen this before or knows how to explain this?
I would be so grateful for any help!!
View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=4118553#4118553
Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=4118553
18 years, 6 months
[Persistence, JBoss/CMP, Hibernate, Database] - configuration of hiberante events
by mars1412
I am trying to create some eventlisteners for hibernate:
http://www.hibernate.org/hib_docs/reference/en/html/events.html#objectsta...
but my listeners seem not to fire.
I think, it's just a configuration issue.
I created a simple listener, by overriding the default hibernate update event listener:
public class HibernateUpdateEventListener extends DefaultUpdateEventListener {
| @Override
| public void onSaveOrUpdate(SaveOrUpdateEvent event) {
| System.err.println("update-event listener fired");
|
| super.onSaveOrUpdate(event);
| }
| }
|
the configuration in my hibernate.cfg.xml file:
| <event type="update">
| <listener class="com.twentyfouract.web.session.util.HibernateUpdateEventListener"/>
| </event>
this file will be located in my.ear/my.jar/hibernate.cfg.xml (in the same direcotry, as the seam.properties file)
* is this the correct place fo the hibernate.cfg.xml file?
| * do I need some other configuration?
| * might this intefere with some other configuration files, like persistence.xml, ejb-jar.xml?
|
When I now call update() the entity, I expect the message to be written to stderr, which does not happen.
the entity values in the database have changed, but the logmessage does not show up
I also tried the same with DefaultSaveEventListener and calling em.persist() which creates a new entity in the database, but does not show my events logmessage
maybe it's just some configuration problem - I am using SEAM: see also my original post in the SEAM forum:
http://www.jboss.com/index.html?module=bb&op=viewtopic&p=4118460#4118460
View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=4118548#4118548
Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=4118548
18 years, 6 months
[Installation, Configuration & DEPLOYMENT] - LDAP-binding via ExternalContext: how to auto-reconnect ?
by axismundi
We are binding an LDAP-server into the JNDI-context.
It works properly until redeployment.
After redeployment the connection is lost and no new connection is being established.
How to specify to auto-reconnect after connection was lost??
<!-- Bind remote LDAP server -->
| <mbean code="org.jboss.naming.ExternalContext"
| name="jboss.jndi:service=ExternalContext,jndiName=external/ldap/acme">
| <attribute name="JndiName">external/ldap/acme</attribute>
| <attribute name="Properties">
| java.naming.factory.initial=com.sun.jndi.ldap.LdapCtxFactory
| java.naming.provider.url=ldap://server:389/o=acme
| java.naming.security.principal=cn=ReadOnlyAdmin,o=swm
| java.naming.security.authentication=simple
| java.naming.security.credentials=password
| com.sun.jndi.ldap.connect.pool=true
| com.sun.jndi.ldap.connect.timeout=5000
| </attribute>
| <attribute name="InitialContext">javax.naming.ldap.InitialLdapContext</attribute>
| <attribute name="RemoteAccess">false</attribute>
| </mbean>
View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=4118542#4118542
Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=4118542
18 years, 6 months
[JBossWS] - Using the jboss-ws-security with signature breaks when the l
by MichaW
We have developed a webservice and want to use a signature as security. This sometimes gives an error: Signature is invalid.
It appears to be related to the loglevel of the org.jboss.ws package.
We have done some testing with different levels of logging on that package. Here is what we get:
Client log level: DEBUG and service log level: INFO throws exception on the client side.
Client log level: DEBUG and service log level: DEBUG works fine.
Client log level: INFO and service log level: DEBUG throws exception on the service side.
Client log level: INFO and service log level: INFO throws exception on the service side.
We have tested this with different environments
application server: jboss-4.2.1.GA or jboss-4.2.2.GA
ws: jbossws-native-2.0.2.GA or jbossws-native-2.0.1.GA
jboss-wsse-server.xml:
<?xml version="1.0" encoding="UTF-8"?>
<jboss-ws-security xmlns="http://www.jboss.com/ws-security/config"
xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance"
xsi:schemaLocation="http://www.jboss.com/ws-security/config http://www.jboss.com/ws-security/schema/jboss-ws-security_1_0.xsd">
<key-store-file>WEB-INF/wsse.keystore</key-store-file>
<key-store-password>jbossws</key-store-password>
<trust-store-file>WEB-INF/wsse.truststore</trust-store-file>
<trust-store-password>jbossws</trust-store-password>
</jboss-ws-security>
jboss-wsse-client.xml:
<?xml version="1.0" encoding="UTF-8"?>
<jboss-ws-security xmlns="http://www.jboss.com/ws-security/config"
xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance"
xsi:schemaLocation="http://www.jboss.com/ws-security/config http://www.jboss.com/ws-security/schema/jboss-ws-security_1_0.xsd">
<key-store-file>WEB-INF/wsse.keystore</key-store-file>
<key-store-password>jbossws</key-store-password>
<trust-store-file>WEB-INF/wsse.truststore</trust-store-file>
<trust-store-password>jbossws</trust-store-password>
</jboss-ws-security>
Service side exception:
09:54:04,781 WARN [Reference] Verification failed for URI "#element-64-1199955244687-5289337"
09:54:04,781 INFO [Reference] Verification successful for URI "#timestamp"
09:59:56,562 ERROR [WSSecurityDispatcher] Internal error occured handling inbound message:
org.jboss.ws.extensions.security.FailedCheckException: Signature is invalid.
at org.jboss.ws.extensions.security.SignatureVerificationOperation.process(SignatureVerificationOperation.java:59)
at org.jboss.ws.extensions.security.SecurityDecoder.decode(SecurityDecoder.java:123)
at org.jboss.ws.extensions.security.SecurityDecoder.decode(SecurityDecoder.java:185)
at org.jboss.ws.extensions.security.WSSecurityDispatcher.handleInbound(WSSecurityDispatcher.java:147)
at org.jboss.ws.extensions.security.jaxws.WSSecurityHandler.handleInboundSecurity(WSSecurityHandler.java:78)
at org.jboss.ws.extensions.security.jaxws.WSSecurityHandlerServer.handleInbound(WSSecurityHandlerServer.java:41)
at org.jboss.ws.core.jaxws.handler.GenericHandler.handleMessage(GenericHandler.java:55)
at org.jboss.ws.core.jaxws.handler.HandlerChainExecutor.handleMessage(HandlerChainExecutor.java:295)
at org.jboss.ws.core.jaxws.handler.HandlerChainExecutor.handleMessage(HandlerChainExecutor.java:140)
at org.jboss.ws.core.jaxws.handler.HandlerDelegateJAXWS.callRequestHandlerChain(HandlerDelegateJAXWS.java:87)
at org.jboss.ws.core.server.ServiceEndpointInvoker.callRequestHandlerChain(ServiceEndpointInvoker.java:126)
at org.jboss.ws.core.server.ServiceEndpointInvoker.invoke(ServiceEndpointInvoker.java:170)
at org.jboss.wsf.stack.jbws.RequestHandlerImpl.processRequest(RequestHandlerImpl.java:414)
at org.jboss.wsf.stack.jbws.RequestHandlerImpl.handleRequest(RequestHandlerImpl.java:273)
at org.jboss.wsf.stack.jbws.RequestHandlerImpl.doPost(RequestHandlerImpl.java:190)
at org.jboss.wsf.stack.jbws.RequestHandlerImpl.handleHttpRequest(RequestHandlerImpl.java:123)
at org.jboss.wsf.stack.jbws.EndpointServlet.service(EndpointServlet.java:84)
at javax.servlet.http.HttpServlet.service(HttpServlet.java:803)
at org.apache.catalina.core.ApplicationFilterChain.internalDoFilter(ApplicationFilterChain.java:290)
at org.apache.catalina.core.ApplicationFilterChain.doFilter(ApplicationFilterChain.java:206)
at org.jboss.web.tomcat.filters.ReplyHeaderFilter.doFilter(ReplyHeaderFilter.java:96)
at org.apache.catalina.core.ApplicationFilterChain.internalDoFilter(ApplicationFilterChain.java:235)
at org.apache.catalina.core.ApplicationFilterChain.doFilter(ApplicationFilterChain.java:206)
at org.apache.catalina.core.StandardWrapperValve.invoke(StandardWrapperValve.java:230)
at org.apache.catalina.core.StandardContextValve.invoke(StandardContextValve.java:175)
at org.jboss.web.tomcat.security.SecurityAssociationValve.invoke(SecurityAssociationValve.java:179)
at org.jboss.web.tomcat.security.JaccContextValve.invoke(JaccContextValve.java:84)
at org.apache.catalina.core.StandardHostValve.invoke(StandardHostValve.java:128)
at org.apache.catalina.valves.ErrorReportValve.invoke(ErrorReportValve.java:104)
at org.jboss.web.tomcat.service.jca.CachedConnectionValve.invoke(CachedConnectionValve.java:157)
at org.apache.catalina.core.StandardEngineValve.invoke(StandardEngineValve.java:109)
at org.apache.catalina.connector.CoyoteAdapter.service(CoyoteAdapter.java:241)
at org.apache.coyote.http11.Http11Processor.process(Http11Processor.java:844)
at org.apache.coyote.http11.Http11Protocol$Http11ConnectionHandler.process(Http11Protocol.java:580)
at org.apache.tomcat.util.net.JIoEndpoint$Worker.run(JIoEndpoint.java:447)
at java.lang.Thread.run(Thread.java:595)
09:59:56,562 ERROR [HandlerChainExecutor] Exception during handler processing
org.jboss.ws.core.CommonSOAPFaultException: Signature is invalid.
at org.jboss.ws.extensions.security.WSSecurityDispatcher.convertToFault(WSSecurityDispatcher.java:105)
at org.jboss.ws.extensions.security.WSSecurityDispatcher.handleInbound(WSSecurityDispatcher.java:177)
at org.jboss.ws.extensions.security.jaxws.WSSecurityHandler.handleInboundSecurity(WSSecurityHandler.java:78)
at org.jboss.ws.extensions.security.jaxws.WSSecurityHandlerServer.handleInbound(WSSecurityHandlerServer.java:41)
at org.jboss.ws.core.jaxws.handler.GenericHandler.handleMessage(GenericHandler.java:55)
at org.jboss.ws.core.jaxws.handler.HandlerChainExecutor.handleMessage(HandlerChainExecutor.java:295)
at org.jboss.ws.core.jaxws.handler.HandlerChainExecutor.handleMessage(HandlerChainExecutor.java:140)
at org.jboss.ws.core.jaxws.handler.HandlerDelegateJAXWS.callRequestHandlerChain(HandlerDelegateJAXWS.java:87)
at org.jboss.ws.core.server.ServiceEndpointInvoker.callRequestHandlerChain(ServiceEndpointInvoker.java:126)
at org.jboss.ws.core.server.ServiceEndpointInvoker.invoke(ServiceEndpointInvoker.java:170)
at org.jboss.wsf.stack.jbws.RequestHandlerImpl.processRequest(RequestHandlerImpl.java:414)
at org.jboss.wsf.stack.jbws.RequestHandlerImpl.handleRequest(RequestHandlerImpl.java:273)
at org.jboss.wsf.stack.jbws.RequestHandlerImpl.doPost(RequestHandlerImpl.java:190)
at org.jboss.wsf.stack.jbws.RequestHandlerImpl.handleHttpRequest(RequestHandlerImpl.java:123)
at org.jboss.wsf.stack.jbws.EndpointServlet.service(EndpointServlet.java:84)
at javax.servlet.http.HttpServlet.service(HttpServlet.java:803)
at org.apache.catalina.core.ApplicationFilterChain.internalDoFilter(ApplicationFilterChain.java:290)
at org.apache.catalina.core.ApplicationFilterChain.doFilter(ApplicationFilterChain.java:206)
at org.jboss.web.tomcat.filters.ReplyHeaderFilter.doFilter(ReplyHeaderFilter.java:96)
at org.apache.catalina.core.ApplicationFilterChain.internalDoFilter(ApplicationFilterChain.java:235)
at org.apache.catalina.core.ApplicationFilterChain.doFilter(ApplicationFilterChain.java:206)
at org.apache.catalina.core.StandardWrapperValve.invoke(StandardWrapperValve.java:230)
at org.apache.catalina.core.StandardContextValve.invoke(StandardContextValve.java:175)
at org.jboss.web.tomcat.security.SecurityAssociationValve.invoke(SecurityAssociationValve.java:179)
at org.jboss.web.tomcat.security.JaccContextValve.invoke(JaccContextValve.java:84)
at org.apache.catalina.core.StandardHostValve.invoke(StandardHostValve.java:128)
at org.apache.catalina.valves.ErrorReportValve.invoke(ErrorReportValve.java:104)
at org.jboss.web.tomcat.service.jca.CachedConnectionValve.invoke(CachedConnectionValve.java:157)
at org.apache.catalina.core.StandardEngineValve.invoke(StandardEngineValve.java:109)
at org.apache.catalina.connector.CoyoteAdapter.service(CoyoteAdapter.java:241)
at org.apache.coyote.http11.Http11Processor.process(Http11Processor.java:844)
at org.apache.coyote.http11.Http11Protocol$Http11ConnectionHandler.process(Http11Protocol.java:580)
at org.apache.tomcat.util.net.JIoEndpoint$Worker.run(JIoEndpoint.java:447)
at java.lang.Thread.run(Thread.java:595)
09:59:56,562 ERROR [SOAPFaultHelperJAXWS] SOAP request exception
javax.xml.ws.WebServiceException: org.jboss.ws.core.CommonSOAPFaultException: Signature is invalid.
at org.jboss.ws.core.jaxws.handler.HandlerChainExecutor.processHandlerFailure(HandlerChainExecutor.java:276)
at org.jboss.ws.core.jaxws.handler.HandlerChainExecutor.handleMessage(HandlerChainExecutor.java:155)
at org.jboss.ws.core.jaxws.handler.HandlerDelegateJAXWS.callRequestHandlerChain(HandlerDelegateJAXWS.java:87)
at org.jboss.ws.core.server.ServiceEndpointInvoker.callRequestHandlerChain(ServiceEndpointInvoker.java:126)
at org.jboss.ws.core.server.ServiceEndpointInvoker.invoke(ServiceEndpointInvoker.java:170)
at org.jboss.wsf.stack.jbws.RequestHandlerImpl.processRequest(RequestHandlerImpl.java:414)
at org.jboss.wsf.stack.jbws.RequestHandlerImpl.handleRequest(RequestHandlerImpl.java:273)
at org.jboss.wsf.stack.jbws.RequestHandlerImpl.doPost(RequestHandlerImpl.java:190)
at org.jboss.wsf.stack.jbws.RequestHandlerImpl.handleHttpRequest(RequestHandlerImpl.java:123)
at org.jboss.wsf.stack.jbws.EndpointServlet.service(EndpointServlet.java:84)
at javax.servlet.http.HttpServlet.service(HttpServlet.java:803)
at org.apache.catalina.core.ApplicationFilterChain.internalDoFilter(ApplicationFilterChain.java:290)
at org.apache.catalina.core.ApplicationFilterChain.doFilter(ApplicationFilterChain.java:206)
at org.jboss.web.tomcat.filters.ReplyHeaderFilter.doFilter(ReplyHeaderFilter.java:96)
at org.apache.catalina.core.ApplicationFilterChain.internalDoFilter(ApplicationFilterChain.java:235)
at org.apache.catalina.core.ApplicationFilterChain.doFilter(ApplicationFilterChain.java:206)
at org.apache.catalina.core.StandardWrapperValve.invoke(StandardWrapperValve.java:230)
at org.apache.catalina.core.StandardContextValve.invoke(StandardContextValve.java:175)
at org.jboss.web.tomcat.security.SecurityAssociationValve.invoke(SecurityAssociationValve.java:179)
at org.jboss.web.tomcat.security.JaccContextValve.invoke(JaccContextValve.java:84)
at org.apache.catalina.core.StandardHostValve.invoke(StandardHostValve.java:128)
at org.apache.catalina.valves.ErrorReportValve.invoke(ErrorReportValve.java:104)
at org.jboss.web.tomcat.service.jca.CachedConnectionValve.invoke(CachedConnectionValve.java:157)
at org.apache.catalina.core.StandardEngineValve.invoke(StandardEngineValve.java:109)
at org.apache.catalina.connector.CoyoteAdapter.service(CoyoteAdapter.java:241)
at org.apache.coyote.http11.Http11Processor.process(Http11Processor.java:844)
at org.apache.coyote.http11.Http11Protocol$Http11ConnectionHandler.process(Http11Protocol.java:580)
at org.apache.tomcat.util.net.JIoEndpoint$Worker.run(JIoEndpoint.java:447)
at java.lang.Thread.run(Thread.java:595)
Caused by: org.jboss.ws.core.CommonSOAPFaultException: Signature is invalid.
at org.jboss.ws.extensions.security.WSSecurityDispatcher.convertToFault(WSSecurityDispatcher.java:105)
at org.jboss.ws.extensions.security.WSSecurityDispatcher.handleInbound(WSSecurityDispatcher.java:177)
at org.jboss.ws.extensions.security.jaxws.WSSecurityHandler.handleInboundSecurity(WSSecurityHandler.java:78)
at org.jboss.ws.extensions.security.jaxws.WSSecurityHandlerServer.handleInbound(WSSecurityHandlerServer.java:41)
at org.jboss.ws.core.jaxws.handler.GenericHandler.handleMessage(GenericHandler.java:55)
at org.jboss.ws.core.jaxws.handler.HandlerChainExecutor.handleMessage(HandlerChainExecutor.java:295)
at org.jboss.ws.core.jaxws.handler.HandlerChainExecutor.handleMessage(HandlerChainExecutor.java:140)
... 27 more
09:59:56,562 ERROR [SOAPFaultHelperJAXWS] SOAP request exception
javax.xml.ws.WebServiceException: org.jboss.ws.core.CommonSOAPFaultException: Signature is invalid.
at org.jboss.ws.core.jaxws.handler.HandlerChainExecutor.processHandlerFailure(HandlerChainExecutor.java:276)
at org.jboss.ws.core.jaxws.handler.HandlerChainExecutor.handleMessage(HandlerChainExecutor.java:155)
at org.jboss.ws.core.jaxws.handler.HandlerDelegateJAXWS.callRequestHandlerChain(HandlerDelegateJAXWS.java:87)
at org.jboss.ws.core.server.ServiceEndpointInvoker.callRequestHandlerChain(ServiceEndpointInvoker.java:126)
at org.jboss.ws.core.server.ServiceEndpointInvoker.invoke(ServiceEndpointInvoker.java:170)
at org.jboss.wsf.stack.jbws.RequestHandlerImpl.processRequest(RequestHandlerImpl.java:414)
at org.jboss.wsf.stack.jbws.RequestHandlerImpl.handleRequest(RequestHandlerImpl.java:273)
at org.jboss.wsf.stack.jbws.RequestHandlerImpl.doPost(RequestHandlerImpl.java:190)
at org.jboss.wsf.stack.jbws.RequestHandlerImpl.handleHttpRequest(RequestHandlerImpl.java:123)
at org.jboss.wsf.stack.jbws.EndpointServlet.service(EndpointServlet.java:84)
at javax.servlet.http.HttpServlet.service(HttpServlet.java:803)
at org.apache.catalina.core.ApplicationFilterChain.internalDoFilter(ApplicationFilterChain.java:290)
at org.apache.catalina.core.ApplicationFilterChain.doFilter(ApplicationFilterChain.java:206)
at org.jboss.web.tomcat.filters.ReplyHeaderFilter.doFilter(ReplyHeaderFilter.java:96)
at org.apache.catalina.core.ApplicationFilterChain.internalDoFilter(ApplicationFilterChain.java:235)
at org.apache.catalina.core.ApplicationFilterChain.doFilter(ApplicationFilterChain.java:206)
at org.apache.catalina.core.StandardWrapperValve.invoke(StandardWrapperValve.java:230)
at org.apache.catalina.core.StandardContextValve.invoke(StandardContextValve.java:175)
at org.jboss.web.tomcat.security.SecurityAssociationValve.invoke(SecurityAssociationValve.java:179)
at org.jboss.web.tomcat.security.JaccContextValve.invoke(JaccContextValve.java:84)
at org.apache.catalina.core.StandardHostValve.invoke(StandardHostValve.java:128)
at org.apache.catalina.valves.ErrorReportValve.invoke(ErrorReportValve.java:104)
at org.jboss.web.tomcat.service.jca.CachedConnectionValve.invoke(CachedConnectionValve.java:157)
at org.apache.catalina.core.StandardEngineValve.invoke(StandardEngineValve.java:109)
at org.apache.catalina.connector.CoyoteAdapter.service(CoyoteAdapter.java:241)
at org.apache.coyote.http11.Http11Processor.process(Http11Processor.java:844)
at org.apache.coyote.http11.Http11Protocol$Http11ConnectionHandler.process(Http11Protocol.java:580)
at org.apache.tomcat.util.net.JIoEndpoint$Worker.run(JIoEndpoint.java:447)
at java.lang.Thread.run(Thread.java:595)
Caused by: org.jboss.ws.core.CommonSOAPFaultException: Signature is invalid.
at org.jboss.ws.extensions.security.WSSecurityDispatcher.convertToFault(WSSecurityDispatcher.java:105)
at org.jboss.ws.extensions.security.WSSecurityDispatcher.handleInbound(WSSecurityDispatcher.java:177)
at org.jboss.ws.extensions.security.jaxws.WSSecurityHandler.handleInboundSecurity(WSSecurityHandler.java:78)
at org.jboss.ws.extensions.security.jaxws.WSSecurityHandlerServer.handleInbound(WSSecurityHandlerServer.java:41)
at org.jboss.ws.core.jaxws.handler.GenericHandler.handleMessage(GenericHandler.java:55)
at org.jboss.ws.core.jaxws.handler.HandlerChainExecutor.handleMessage(HandlerChainExecutor.java:295)
at org.jboss.ws.core.jaxws.handler.HandlerChainExecutor.handleMessage(HandlerChainExecutor.java:140)
... 27 more
Client side exception:
10:07:37,578 WARN [Reference] Verification failed for URI "#element-49-1199956057062-17250248"
10:07:37,593 INFO [Reference] Verification successful for URI "#timestamp"
10:07:37,593 ERROR [WSSecurityDispatcher] Internal error occured handling inbound message:
org.jboss.ws.extensions.security.FailedCheckException: Signature is invalid.
at org.jboss.ws.extensions.security.SignatureVerificationOperation.process(SignatureVerificationOperation.java:59)
at org.jboss.ws.extensions.security.SecurityDecoder.decode(SecurityDecoder.java:123)
at org.jboss.ws.extensions.security.SecurityDecoder.decode(SecurityDecoder.java:185)
at org.jboss.ws.extensions.security.WSSecurityDispatcher.handleInbound(WSSecurityDispatcher.java:147)
at org.jboss.ws.extensions.security.jaxws.WSSecurityHandler.handleInboundSecurity(WSSecurityHandler.java:78)
at org.jboss.ws.extensions.security.jaxws.WSSecurityHandlerClient.handleInbound(WSSecurityHandlerClient.java:40)
at org.jboss.ws.core.jaxws.handler.GenericHandler.handleMessage(GenericHandler.java:55)
at org.jboss.ws.core.jaxws.handler.HandlerChainExecutor.handleMessage(HandlerChainExecutor.java:295)
at org.jboss.ws.core.jaxws.handler.HandlerChainExecutor.handleMessage(HandlerChainExecutor.java:140)
at org.jboss.ws.core.jaxws.client.ClientImpl.callResponseHandlerChain(ClientImpl.java:168)
at org.jboss.ws.core.CommonClient.invoke(CommonClient.java:363)
at org.jboss.ws.core.jaxws.client.ClientImpl.invoke(ClientImpl.java:243)
at org.jboss.ws.core.jaxws.client.ClientProxy.invoke(ClientProxy.java:164)
at org.jboss.ws.core.jaxws.client.ClientProxy.invoke(ClientProxy.java:150)
at $Proxy80.zoekPeilpuntenWoning(Unknown Source)
at nl.denhaag.gbd.services.peilpuntenservice.client.PeilpuntenServiceClient.zoekPeilpuntenWoning(PeilpuntenServiceClient.java:292)
at nl.denhaag.gbd.services.peilpuntenservice.client.PeilpuntenServiceClient.zoekPeilpuntenWoning(PeilpuntenServiceClient.java:211)
at nl.denhaag.gbd.mgov.common.manager.core.WoningManagerWS.zoekPeilpuntenVoorWijkObjectSoortQuery(WoningManagerWS.java:206)
at nl.denhaag.gbd.mgov.common.manager.core.WoningManagerWS.zoekPeilpunten(WoningManagerWS.java:90)
at nl.denhaag.gbd.mgov.pp.won.opnm.component.PPOpnemenWoningenZoeken.executeQuery(PPOpnemenWoningenZoeken.java:178)
at nl.denhaag.gbd.mgov.pp.won.opnm.component.PPOpnemenWoningenZoeken.getQueryResult(PPOpnemenWoningenZoeken.java:153)
at nl.denhaag.gbd.mgov.common.component.ZoekComponent.processRequest(ZoekComponent.java:509)
at com.novell.afw.component.core.EboComponentContainer.performInteraction(EboComponentContainer.java:128)
at com.novell.afw.component.core.EboComponentContainer.performBlockingInteraction(EboComponentContainer.java:154)
at com.novell.afw.portal.proxy.EboPortletContainerProxy.performBlockingInteraction(EboPortletContainerProxy.java:185)
at com.novell.afw.portal.aggregation.EboPortletProxyHelper.callPortletActionRequest(EboPortletProxyHelper.java:468)
at com.novell.afw.portal.aggregation.EboPortalAggregationControllerImpl.checkAndHandleActionURLType(EboPortalAggregationControllerImpl.java:1
75)
at com.novell.afw.portal.aggregation.EboPortalAggregationControllerImpl.initiateRendering(EboPortalAggregationControllerImpl.java:1249)
at com.novell.afw.portal.aggregation.EboPortalAggregationControllerImpl.renderPortalPIDResponse(EboPortalAggregationControllerImpl.java:871)
at com.novell.afw.portal.aggregation.EboPortalAggregationServlet.handlePIDPagesRequest(EboPortalAggregationServlet.java:801)
at com.novell.afw.portal.aggregation.EboPortalAggregationServlet.callService(EboPortalAggregationServlet.java:210)
at com.novell.afw.portal.aggregation.EboPortalAggregationServlet.doPost(EboPortalAggregationServlet.java:83)
at javax.servlet.http.HttpServlet.service(HttpServlet.java:710)
at javax.servlet.http.HttpServlet.service(HttpServlet.java:803)
at org.apache.catalina.core.ApplicationFilterChain.internalDoFilter(ApplicationFilterChain.java:290)
at org.apache.catalina.core.ApplicationFilterChain.doFilter(ApplicationFilterChain.java:206)
at nl.denhaag.gbd.filter.GZIPFilter.doFilter(GZIPFilter.java:34)
at org.apache.catalina.core.ApplicationFilterChain.internalDoFilter(ApplicationFilterChain.java:235)
at org.apache.catalina.core.ApplicationFilterChain.doFilter(ApplicationFilterChain.java:206)
at com.novell.afw.portal.xforms.EboXFormClientDetectionFilter.doFilter(EboXFormClientDetectionFilter.java:85)
at org.apache.catalina.core.ApplicationFilterChain.internalDoFilter(ApplicationFilterChain.java:235)
at org.apache.catalina.core.ApplicationFilterChain.doFilter(ApplicationFilterChain.java:206)
at nl.denhaag.gbd.filter.HeaderFilter.doFilter(HeaderFilter.java:70)
at org.apache.catalina.core.ApplicationFilterChain.internalDoFilter(ApplicationFilterChain.java:235)
at org.apache.catalina.core.ApplicationFilterChain.doFilter(ApplicationFilterChain.java:206)
at nl.denhaag.gbd.security.auth.spi.UserFilter.doFilter(UserFilter.java:108)
at org.apache.catalina.core.ApplicationFilterChain.internalDoFilter(ApplicationFilterChain.java:235)
at org.apache.catalina.core.ApplicationFilterChain.doFilter(ApplicationFilterChain.java:206)
at org.jboss.web.tomcat.filters.ReplyHeaderFilter.doFilter(ReplyHeaderFilter.java:96)
at org.apache.catalina.core.ApplicationFilterChain.internalDoFilter(ApplicationFilterChain.java:235)
at org.apache.catalina.core.ApplicationFilterChain.doFilter(ApplicationFilterChain.java:206)
at org.apache.catalina.core.StandardWrapperValve.invoke(StandardWrapperValve.java:230)
at org.apache.catalina.core.StandardContextValve.invoke(StandardContextValve.java:175)
at org.jboss.web.tomcat.security.SecurityAssociationValve.invoke(SecurityAssociationValve.java:179)
at org.apache.catalina.authenticator.AuthenticatorBase.invoke(AuthenticatorBase.java:433)
at org.jboss.web.tomcat.security.JaccContextValve.invoke(JaccContextValve.java:84)
at org.apache.catalina.core.StandardHostValve.invoke(StandardHostValve.java:128)
at org.apache.catalina.valves.ErrorReportValve.invoke(ErrorReportValve.java:104)
at org.jboss.web.tomcat.service.jca.CachedConnectionValve.invoke(CachedConnectionValve.java:157)
at org.apache.catalina.core.StandardEngineValve.invoke(StandardEngineValve.java:109)
at org.apache.catalina.connector.CoyoteAdapter.service(CoyoteAdapter.java:241)
at org.apache.coyote.http11.Http11Processor.process(Http11Processor.java:844)
at org.apache.coyote.http11.Http11Protocol$Http11ConnectionHandler.process(Http11Protocol.java:580)
at org.apache.tomcat.util.net.JIoEndpoint$Worker.run(JIoEndpoint.java:447)
at java.lang.Thread.run(Thread.java:595)
10:07:37,671 ERROR [HandlerChainExecutor] Exception during handler processing
org.jboss.ws.core.CommonSOAPFaultException: Signature is invalid.
at org.jboss.ws.extensions.security.WSSecurityDispatcher.convertToFault(WSSecurityDispatcher.java:105)
at org.jboss.ws.extensions.security.WSSecurityDispatcher.handleInbound(WSSecurityDispatcher.java:177)
at org.jboss.ws.extensions.security.jaxws.WSSecurityHandler.handleInboundSecurity(WSSecurityHandler.java:78)
at org.jboss.ws.extensions.security.jaxws.WSSecurityHandlerClient.handleInbound(WSSecurityHandlerClient.java:40)
at org.jboss.ws.core.jaxws.handler.GenericHandler.handleMessage(GenericHandler.java:55)
at org.jboss.ws.core.jaxws.handler.HandlerChainExecutor.handleMessage(HandlerChainExecutor.java:295)
at org.jboss.ws.core.jaxws.handler.HandlerChainExecutor.handleMessage(HandlerChainExecutor.java:140)
at org.jboss.ws.core.jaxws.client.ClientImpl.callResponseHandlerChain(ClientImpl.java:168)
at org.jboss.ws.core.CommonClient.invoke(CommonClient.java:363)
at org.jboss.ws.core.jaxws.client.ClientImpl.invoke(ClientImpl.java:243)
at org.jboss.ws.core.jaxws.client.ClientProxy.invoke(ClientProxy.java:164)
at org.jboss.ws.core.jaxws.client.ClientProxy.invoke(ClientProxy.java:150)
at $Proxy80.zoekPeilpuntenWoning(Unknown Source)
at nl.denhaag.gbd.services.peilpuntenservice.client.PeilpuntenServiceClient.zoekPeilpuntenWoning(PeilpuntenServiceClient.java:292)
at nl.denhaag.gbd.services.peilpuntenservice.client.PeilpuntenServiceClient.zoekPeilpuntenWoning(PeilpuntenServiceClient.java:211)
at nl.denhaag.gbd.mgov.common.manager.core.WoningManagerWS.zoekPeilpuntenVoorWijkObjectSoortQuery(WoningManagerWS.java:206)
at nl.denhaag.gbd.mgov.common.manager.core.WoningManagerWS.zoekPeilpunten(WoningManagerWS.java:90)
at nl.denhaag.gbd.mgov.pp.won.opnm.component.PPOpnemenWoningenZoeken.executeQuery(PPOpnemenWoningenZoeken.java:178)
at nl.denhaag.gbd.mgov.pp.won.opnm.component.PPOpnemenWoningenZoeken.getQueryResult(PPOpnemenWoningenZoeken.java:153)
at nl.denhaag.gbd.mgov.common.component.ZoekComponent.processRequest(ZoekComponent.java:509)
at com.novell.afw.component.core.EboComponentContainer.performInteraction(EboComponentContainer.java:128)
at com.novell.afw.component.core.EboComponentContainer.performBlockingInteraction(EboComponentContainer.java:154)
at com.novell.afw.portal.proxy.EboPortletContainerProxy.performBlockingInteraction(EboPortletContainerProxy.java:185)
at com.novell.afw.portal.aggregation.EboPortletProxyHelper.callPortletActionRequest(EboPortletProxyHelper.java:468)
at com.novell.afw.portal.aggregation.EboPortalAggregationControllerImpl.checkAndHandleActionURLType(EboPortalAggregationControllerImpl.java:1
75)
at com.novell.afw.portal.aggregation.EboPortalAggregationControllerImpl.initiateRendering(EboPortalAggregationControllerImpl.java:1249)
at com.novell.afw.portal.aggregation.EboPortalAggregationControllerImpl.renderPortalPIDResponse(EboPortalAggregationControllerImpl.java:871)
at com.novell.afw.portal.aggregation.EboPortalAggregationServlet.handlePIDPagesRequest(EboPortalAggregationServlet.java:801)
at com.novell.afw.portal.aggregation.EboPortalAggregationServlet.callService(EboPortalAggregationServlet.java:210)
at com.novell.afw.portal.aggregation.EboPortalAggregationServlet.doPost(EboPortalAggregationServlet.java:83)
at javax.servlet.http.HttpServlet.service(HttpServlet.java:710)
at javax.servlet.http.HttpServlet.service(HttpServlet.java:803)
at org.apache.catalina.core.ApplicationFilterChain.internalDoFilter(ApplicationFilterChain.java:290)
at org.apache.catalina.core.ApplicationFilterChain.doFilter(ApplicationFilterChain.java:206)
at nl.denhaag.gbd.filter.GZIPFilter.doFilter(GZIPFilter.java:34)
at org.apache.catalina.core.ApplicationFilterChain.internalDoFilter(ApplicationFilterChain.java:235)
at org.apache.catalina.core.ApplicationFilterChain.doFilter(ApplicationFilterChain.java:206)
at com.novell.afw.portal.xforms.EboXFormClientDetectionFilter.doFilter(EboXFormClientDetectionFilter.java:85)
at org.apache.catalina.core.ApplicationFilterChain.internalDoFilter(ApplicationFilterChain.java:235)
at org.apache.catalina.core.ApplicationFilterChain.doFilter(ApplicationFilterChain.java:206)
at nl.denhaag.gbd.filter.HeaderFilter.doFilter(HeaderFilter.java:70)
at org.apache.catalina.core.ApplicationFilterChain.internalDoFilter(ApplicationFilterChain.java:235)
at org.apache.catalina.core.ApplicationFilterChain.doFilter(ApplicationFilterChain.java:206)
at nl.denhaag.gbd.security.auth.spi.UserFilter.doFilter(UserFilter.java:108)
at org.apache.catalina.core.ApplicationFilterChain.internalDoFilter(ApplicationFilterChain.java:235)
at org.apache.catalina.core.ApplicationFilterChain.doFilter(ApplicationFilterChain.java:206)
at org.jboss.web.tomcat.filters.ReplyHeaderFilter.doFilter(ReplyHeaderFilter.java:96)
at org.apache.catalina.core.ApplicationFilterChain.internalDoFilter(ApplicationFilterChain.java:235)
at org.apache.catalina.core.ApplicationFilterChain.doFilter(ApplicationFilterChain.java:206)
at org.apache.catalina.core.StandardWrapperValve.invoke(StandardWrapperValve.java:230)
at org.apache.catalina.core.StandardContextValve.invoke(StandardContextValve.java:175)
at org.jboss.web.tomcat.security.SecurityAssociationValve.invoke(SecurityAssociationValve.java:179)
at org.apache.catalina.authenticator.AuthenticatorBase.invoke(AuthenticatorBase.java:433)
at org.jboss.web.tomcat.security.JaccContextValve.invoke(JaccContextValve.java:84)
at org.apache.catalina.core.StandardHostValve.invoke(StandardHostValve.java:128)
at org.apache.catalina.valves.ErrorReportValve.invoke(ErrorReportValve.java:104)
at org.jboss.web.tomcat.service.jca.CachedConnectionValve.invoke(CachedConnectionValve.java:157)
at org.apache.catalina.core.StandardEngineValve.invoke(StandardEngineValve.java:109)
at org.apache.catalina.connector.CoyoteAdapter.service(CoyoteAdapter.java:241)
at org.apache.coyote.http11.Http11Processor.process(Http11Processor.java:844)
at org.apache.coyote.http11.Http11Protocol$Http11ConnectionHandler.process(Http11Protocol.java:580)
at org.apache.tomcat.util.net.JIoEndpoint$Worker.run(JIoEndpoint.java:447)
at java.lang.Thread.run(Thread.java:595)
10:07:37,796 ERROR [SOAPFaultHelperJAXWS] SOAP request exception
javax.xml.ws.WebServiceException: org.jboss.ws.core.CommonSOAPFaultException: Signature is invalid.
at org.jboss.ws.core.jaxws.handler.HandlerChainExecutor.processHandlerFailure(HandlerChainExecutor.java:276)
at org.jboss.ws.core.jaxws.handler.HandlerChainExecutor.handleMessage(HandlerChainExecutor.java:155)
at org.jboss.ws.core.jaxws.client.ClientImpl.callResponseHandlerChain(ClientImpl.java:168)
at org.jboss.ws.core.CommonClient.invoke(CommonClient.java:363)
at org.jboss.ws.core.jaxws.client.ClientImpl.invoke(ClientImpl.java:243)
at org.jboss.ws.core.jaxws.client.ClientProxy.invoke(ClientProxy.java:164)
at org.jboss.ws.core.jaxws.client.ClientProxy.invoke(ClientProxy.java:150)
at $Proxy80.zoekPeilpuntenWoning(Unknown Source)
at nl.denhaag.gbd.services.peilpuntenservice.client.PeilpuntenServiceClient.zoekPeilpuntenWoning(PeilpuntenServiceClient.java:292)
at nl.denhaag.gbd.services.peilpuntenservice.client.PeilpuntenServiceClient.zoekPeilpuntenWoning(PeilpuntenServiceClient.java:211)
at nl.denhaag.gbd.mgov.common.manager.core.WoningManagerWS.zoekPeilpuntenVoorWijkObjectSoortQuery(WoningManagerWS.java:206)
at nl.denhaag.gbd.mgov.common.manager.core.WoningManagerWS.zoekPeilpunten(WoningManagerWS.java:90)
at nl.denhaag.gbd.mgov.pp.won.opnm.component.PPOpnemenWoningenZoeken.executeQuery(PPOpnemenWoningenZoeken.java:178)
at nl.denhaag.gbd.mgov.pp.won.opnm.component.PPOpnemenWoningenZoeken.getQueryResult(PPOpnemenWoningenZoeken.java:153)
at nl.denhaag.gbd.mgov.common.component.ZoekComponent.processRequest(ZoekComponent.java:509)
at com.novell.afw.component.core.EboComponentContainer.performInteraction(EboComponentContainer.java:128)
at com.novell.afw.component.core.EboComponentContainer.performBlockingInteraction(EboComponentContainer.java:154)
at com.novell.afw.portal.proxy.EboPortletContainerProxy.performBlockingInteraction(EboPortletContainerProxy.java:185)
at com.novell.afw.portal.aggregation.EboPortletProxyHelper.callPortletActionRequest(EboPortletProxyHelper.java:468)
at com.novell.afw.portal.aggregation.EboPortalAggregationControllerImpl.checkAndHandleActionURLType(EboPortalAggregationControllerImpl.java:1
75)
at com.novell.afw.portal.aggregation.EboPortalAggregationControllerImpl.initiateRendering(EboPortalAggregationControllerImpl.java:1249)
at com.novell.afw.portal.aggregation.EboPortalAggregationControllerImpl.renderPortalPIDResponse(EboPortalAggregationControllerImpl.java:871)
at com.novell.afw.portal.aggregation.EboPortalAggregationServlet.handlePIDPagesRequest(EboPortalAggregationServlet.java:801)
at com.novell.afw.portal.aggregation.EboPortalAggregationServlet.callService(EboPortalAggregationServlet.java:210)
at com.novell.afw.portal.aggregation.EboPortalAggregationServlet.doPost(EboPortalAggregationServlet.java:83)
at javax.servlet.http.HttpServlet.service(HttpServlet.java:710)
at javax.servlet.http.HttpServlet.service(HttpServlet.java:803)
at org.apache.catalina.core.ApplicationFilterChain.internalDoFilter(ApplicationFilterChain.java:290)
at org.apache.catalina.core.ApplicationFilterChain.doFilter(ApplicationFilterChain.java:206)
at nl.denhaag.gbd.filter.GZIPFilter.doFilter(GZIPFilter.java:34)
at org.apache.catalina.core.ApplicationFilterChain.internalDoFilter(ApplicationFilterChain.java:235)
at org.apache.catalina.core.ApplicationFilterChain.doFilter(ApplicationFilterChain.java:206)
at com.novell.afw.portal.xforms.EboXFormClientDetectionFilter.doFilter(EboXFormClientDetectionFilter.java:85)
at org.apache.catalina.core.ApplicationFilterChain.internalDoFilter(ApplicationFilterChain.java:235)
at org.apache.catalina.core.ApplicationFilterChain.doFilter(ApplicationFilterChain.java:206)
at nl.denhaag.gbd.filter.HeaderFilter.doFilter(HeaderFilter.java:70)
at org.apache.catalina.core.ApplicationFilterChain.internalDoFilter(ApplicationFilterChain.java:235)
at org.apache.catalina.core.ApplicationFilterChain.doFilter(ApplicationFilterChain.java:206)
at nl.denhaag.gbd.security.auth.spi.UserFilter.doFilter(UserFilter.java:108)
at org.apache.catalina.core.ApplicationFilterChain.internalDoFilter(ApplicationFilterChain.java:235)
at org.apache.catalina.core.ApplicationFilterChain.doFilter(ApplicationFilterChain.java:206)
at org.jboss.web.tomcat.filters.ReplyHeaderFilter.doFilter(ReplyHeaderFilter.java:96)
at org.apache.catalina.core.ApplicationFilterChain.internalDoFilter(ApplicationFilterChain.java:235)
at org.apache.catalina.core.ApplicationFilterChain.doFilter(ApplicationFilterChain.java:206)
at org.apache.catalina.core.StandardWrapperValve.invoke(StandardWrapperValve.java:230)
at org.apache.catalina.core.StandardContextValve.invoke(StandardContextValve.java:175)
at org.jboss.web.tomcat.security.SecurityAssociationValve.invoke(SecurityAssociationValve.java:179)
at org.apache.catalina.authenticator.AuthenticatorBase.invoke(AuthenticatorBase.java:433)
at org.jboss.web.tomcat.security.JaccContextValve.invoke(JaccContextValve.java:84)
at org.apache.catalina.core.StandardHostValve.invoke(StandardHostValve.java:128)
at org.apache.catalina.valves.ErrorReportValve.invoke(ErrorReportValve.java:104)
at org.jboss.web.tomcat.service.jca.CachedConnectionValve.invoke(CachedConnectionValve.java:157)
at org.apache.catalina.core.StandardEngineValve.invoke(StandardEngineValve.java:109)
at org.apache.catalina.connector.CoyoteAdapter.service(CoyoteAdapter.java:241)
at org.apache.coyote.http11.Http11Processor.process(Http11Processor.java:844)
at org.apache.coyote.http11.Http11Protocol$Http11ConnectionHandler.process(Http11Protocol.java:580)
at org.apache.tomcat.util.net.JIoEndpoint$Worker.run(JIoEndpoint.java:447)
at java.lang.Thread.run(Thread.java:595)
Caused by: org.jboss.ws.core.CommonSOAPFaultException: Signature is invalid.
at org.jboss.ws.extensions.security.WSSecurityDispatcher.convertToFault(WSSecurityDispatcher.java:105)
at org.jboss.ws.extensions.security.WSSecurityDispatcher.handleInbound(WSSecurityDispatcher.java:177)
at org.jboss.ws.extensions.security.jaxws.WSSecurityHandler.handleInboundSecurity(WSSecurityHandler.java:78)
at org.jboss.ws.extensions.security.jaxws.WSSecurityHandlerClient.handleInbound(WSSecurityHandlerClient.java:40)
at org.jboss.ws.core.jaxws.handler.GenericHandler.handleMessage(GenericHandler.java:55)
at org.jboss.ws.core.jaxws.handler.HandlerChainExecutor.handleMessage(HandlerChainExecutor.java:295)
at org.jboss.ws.core.jaxws.handler.HandlerChainExecutor.handleMessage(HandlerChainExecutor.java:140)
... 56 more
View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=4118541#4118541
Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=4118541
18 years, 6 months
[Persistence, JBoss/CMP, Hibernate, Database] - Problems with @Past validator
by mahbe
Hi,
I use Hibernate as JPA implementation with JBoss Seam. The underlying database is MS SQLSERVER 2000. Recently I added Hibernate Validation and used the builtin @Past validator. But since then, a few tables where no longer generated with hbm2ddl. Then I detected that all tables those tables used an @Past annotation on a field:
10:04:57,375 INFO [SchemaExport] Running hbm2ddl schema export
| 10:04:57,375 INFO [SchemaExport] exporting generated schema to database
| 10:04:57,437 ERROR [SchemaExport] Unsuccessful: create table Lizenz ([...], erwerbsDatum datetime not null check (erwerbsDatum < current_date), [...])
| 10:04:57,437 ERROR [SchemaExport] Falsche Syntax in der Naehe des current_date-Schluesselwortes. [<- means in English: 'wrong syntax near current_date keyword']
| [...]
| 10:04:57,828 INFO [SchemaExport] schema export complete
Is this a bug in Hibernate Validator or hbm2ddl? Probably in association with MS SQLSERVER?
Best Regards, Matthias
View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=4118537#4118537
Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=4118537
18 years, 6 months
[JBoss Seam] - s:selectItems and convertEnum and order of enum retention
by tony.herstell@gmail.com
Given
| <h:selectOneRadio id="booking_duration_selection" value="#{bookingController.duration}" layout="pageDirection">
| <s:selectItems value="#{bookingController.getBookingDurationsKind()}" var="bookingDurationKind" label="#{messages[bookingDurationKind.inlLabel]}"/>
| <s:convertEnum />
| <a4j:support event="onclick" reRender="bookingCourseType, resourceAddButtons, resourceAddedTable" />
| </h:selectOneRadio>
|
Backed by
| public enum BookingDurationsKind {
| ONE_HOUR_PRIVATE ("booking_1hrprivate"),
| ONE_HOUR_OPEN ("booking_1hropen"),
| COURSE ("booking_course");
| private final String inlLabel;
| BookingDurationsKind(String inlLabel) {
| this.inlLabel = inlLabel;
| }
| public String getInlLabel() { return inlLabel; }
| }
|
Can I somehow retain the order of the enum when its displayed as checkboxes? There is no attribute etc...
On the screen I get:
| Open 1 Hour Booking (anyone may book the same slot within system limit of 6 people!)
| Private 1 Hour Booking
| Course Booking
|
Where private booking should be topmost.
View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=4118526#4118526
Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=4118526
18 years, 6 months
[JBoss Seam] - Seam Mail loads libraries every time I send a mail
by MSchmidke
Hello all,
today I am trying out Seam's mail facilities.
The first thing I notice:
Every time I send a mail, a whole bunch of "Added Library from" lines is logged. I know those lines appear when I first access a Seam page after server restart, but when mailing, they appear everytime.
I fear that there is something wrong. Do you have any hint what I have to keep in mind when using mail?
Perhaps the reason lies in the way I call Seam mail. It is not directly from a JSF action method, but it is from a jBPM Mail Action class. Of course, some JSF action will be somewhere some thousand stack levels above as the root cause of the mail being send.
| 09:20:26,981 ERROR [STDERR] 10.01.2008 09:20:26 com.sun.facelets.compiler.TagLibraryConfig loadImplicit
| INFO: Added Library from: jar:file:/D:/apps/JBoss-4.2.1-argos/server/default/deploy/Argos3Ear.ear/Argos3Web.war/WEB-INF/lib/jboss-seam-ui.jar!/META-INF/s.taglib.xml
| 09:20:26,997 ERROR [STDERR] 10.01.2008 09:20:26 com.sun.facelets.compiler.TagLibraryConfig loadImplicit
| INFO: Added Library from: jar:file:/D:/apps/JBoss-4.2.1-argos/server/default/deploy/Argos3Ear.ear/Argos3Web.war/WEB-INF/lib/jsf-facelets_patch.jar!/META-INF/jsf-core.taglib.xml
| 09:20:26,997 ERROR [STDERR] 10.01.2008 09:20:26 com.sun.facelets.compiler.TagLibraryConfig loadImplicit
| INFO: Added Library from: jar:file:/D:/apps/JBoss-4.2.1-argos/server/default/deploy/Argos3Ear.ear/Argos3Web.war/WEB-INF/lib/jsf-facelets_patch.jar!/META-INF/jstl-fn.taglib.xml
| 09:20:27,044 ERROR [STDERR] 10.01.2008 09:20:27 com.sun.facelets.compiler.TagLibraryConfig loadImplicit
| INFO: Added Library from: jar:file:/D:/apps/JBoss-4.2.1-argos/server/default/deploy/Argos3Ear.ear/Argos3Web.war/WEB-INF/lib/jboss-seam-mail.jar!/META-INF/seam-mail.taglib.xml
| 09:20:27,075 ERROR [STDERR] 10.01.2008 09:20:27 com.sun.facelets.compiler.TagLibraryConfig loadImplicit
| INFO: Added Library from: jar:file:/D:/apps/JBoss-4.2.1-argos/server/default/deploy/Argos3Ear.ear/Argos3Web.war/WEB-INF/lib/richfaces-ui-3.1.2.GA.jar!/META-INF/richfaces.taglib.xml
| 09:20:27,090 ERROR [STDERR] 10.01.2008 09:20:27 com.sun.facelets.compiler.TagLibraryConfig loadImplicit
| INFO: Added Library from: jar:file:/D:/apps/JBoss-4.2.1-argos/server/default/deploy/Argos3Ear.ear/Argos3Web.war/WEB-INF/lib/richfaces-ui-3.1.2.GA.jar!/META-INF/rich.taglib.xml
| 09:20:27,137 ERROR [STDERR] 10.01.2008 09:20:27 com.sun.facelets.compiler.TagLibraryConfig loadImplicit
| INFO: Added Library from: jar:file:/D:/apps/JBoss-4.2.1-argos/server/default/deploy/Argos3Ear.ear/Argos3Web.war/WEB-INF/lib/richfaces-ui-3.1.2.GA.jar!/META-INF/a4j.taglib.xml
| 09:20:27,153 ERROR [STDERR] 10.01.2008 09:20:27 com.sun.facelets.compiler.TagLibraryConfig loadImplicit
| INFO: Added Library from: jar:file:/D:/apps/JBoss-4.2.1-argos/server/default/deploy/Argos3Ear.ear/Argos3Web.war/WEB-INF/lib/jsf-facelets_patch.jar!/META-INF/jsf-html.taglib.xml
| 09:20:27,153 ERROR [STDERR] 10.01.2008 09:20:27 com.sun.facelets.compiler.TagLibraryConfig loadImplicit
| INFO: Added Library from: jar:file:/D:/apps/JBoss-4.2.1-argos/server/default/deploy/Argos3Ear.ear/Argos3Web.war/WEB-INF/lib/jsf-facelets_patch.jar!/META-INF/jsf-ui.taglib.xml
| 09:20:27,169 ERROR [STDERR] 10.01.2008 09:20:27 com.sun.facelets.compiler.TagLibraryConfig loadImplicit
| INFO: Added Library from: jar:file:/D:/apps/JBoss-4.2.1-argos/server/default/deploy/Argos3Ear.ear/Argos3Web.war/WEB-INF/lib/richfaces-ui-3.1.2.GA.jar!/META-INF/ajax4jsf.taglib.xml
| 09:20:27,184 ERROR [STDERR] 10.01.2008 09:20:27 com.sun.facelets.compiler.TagLibraryConfig loadImplicit
| INFO: Added Library from: jar:file:/D:/apps/JBoss-4.2.1-argos/server/default/deploy/Argos3Ear.ear/Argos3Web.war/WEB-INF/lib/jsf-facelets_patch.jar!/META-INF/jstl-core.taglib.xml
|
|
View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=4118523#4118523
Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=4118523
18 years, 6 months
[JBoss Seam] - Injecting/Outjecting Primitive Types
by toni
Hi,
how do I access the value of a check box contained inside a jsf view from a SFSB without creating explicitetly a Java Bean for the boolean value?
This does not seem to work
|
| ---- simple page --------
|
| <f:view>
| <h:form>
|
| <h:outputText value="List All"/>
| <h:selectBooleanCheckbox value="#{showallentries}"/>
|
| <h:commandButton type="submit" value="Save" action="#{StatefullTestBean.save}"/>
|
| </h:form>
| </f:view>
|
| ----- simple sfsb ---------
|
|
| Name("linkSectionAction")
| @Stateful
|
| public class StatefullTestBean implements StatefullTtestBeanInterface
| {
|
| @In(create=true)
| @Out
| boolean showallentries;
|
| public String save()
| {
| // IWould like to access the boolean value, but I can't inject/outject it.
| }
| }
|
View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=4118521#4118521
Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=4118521
18 years, 6 months
[Beginners Corner] - hsqldb-ds not in memory persistence
by Mussie
hello forum,
I'm trying to build a database aplication with jboss and could not make my
data persistent. I allready changed the persistence from create-drop to update in the seam booking example.
So here is my question:
is it correct that I have to change the hsqldb into server mode to make the
data persistent?
I tried to do so by changing the hsqldb-ds.xml in my deploy directory. But when I start my hsql database manager it is still in in-memory type only the URL changed to jdbc:hsqldb:hsql://127.0.0.1:1701.
Does anyone know why my database engine doesn't convert to server based persistence?
This is how my hsqldb-ds looks like.
<?xml version="1.0" encoding="UTF-8"?>
|
| <!-- The Hypersonic embedded database JCA connection factory config -->
|
| <!-- $Id: hsqldb-ds.xml 63175 2007-05-21 16:26:06Z rrajesh $ -->
|
| <datasources>
| <local-tx-datasource>
|
| <!-- The jndi name of the DataSource, it is prefixed with java:/ -->
| <!-- Datasources are not available outside the virtual machine -->
| <jndi-name>DefaultDS</jndi-name>
|
| <!-- For server mode db, allowing other processes to use hsqldb over tcp.
| This requires the org.jboss.jdbc.HypersonicDatabase mbean.-->
| <connection-url>jdbc:hsqldb:hsql://${jboss.bind.address}:1701</connection-url>
|
| <!-- For totally in-memory db, not saved when jboss stops.
| The org.jboss.jdbc.HypersonicDatabase mbean is required for proper db shutdown
| <connection-url>jdbc:hsqldb:.</connection-url>
| -->
| <!-- For in-process persistent db, saved when jboss stops.
| The org.jboss.jdbc.HypersonicDatabase mbean is required for proper db shutdown
|
| <connection-url>jdbc:hsqldb:${jboss.server.data.dir}${/}hypersonic${/}localDB</connection-url>
| -->
| <!-- The driver class -->
| <driver-class>org.hsqldb.jdbcDriver</driver-class>
|
| <!-- The login and password -->
| <user-name>sa</user-name>
| <password></password>
|
| <!--example of how to specify class that determines if exception means connection should be destroyed
| -->
| <!--exception-sorter-class-name>org.jboss.resource.adapter.jdbc.vendor.DummyExceptionSorter</exception-sorter-class-name-->
|
| <!-- this will be run before a managed connection is removed from the pool for use by a client-->
| <!--<check-valid-connection-sql>select * from something</check-valid-connection-sql> -->
|
| <!-- The minimum connections in a pool/sub-pool. Pools are lazily constructed on first use -->
| <min-pool-size>5</min-pool-size>
|
| <!-- The maximum connections in a pool/sub-pool -->
| <max-pool-size>20</max-pool-size>
|
| <!-- The time before an unused connection is destroyed -->
| <!-- NOTE: This is the check period. It will be destroyed somewhere between 1x and 2x this timeout af
| ter last use -->
| <!-- TEMPORARY FIX! - Disable idle connection removal, HSQLDB has a problem with not reaping threads
| on closed connections -->
| <idle-timeout-minutes>0</idle-timeout-minutes>
|
| <!-- sql to call when connection is created
| <new-connection-sql>some arbitrary sql</new-connection-sql>
| -->
|
| <!-- sql to call on an existing pooled connection when it is obtained from pool
| <check-valid-connection-sql>some arbitrary sql</check-valid-connection-sql>
| -->
|
| <!-- example of how to specify a class that determines a connection is valid before it is handed out
| from the pool
| <valid-connection-checker-class-name>org.jboss.resource.adapter.jdbc.vendor.DummyValidConnectionChecker</valid-connection-checker-class-name>
| -->
|
| <!-- Whether to check all statements are closed when the connection is returned to the pool,
| this is a debugging feature that should be turned off in production -->
| <track-statements/>
|
| <!-- Use the getConnection(user, pw) for logins
| <application-managed-security/>
| -->
|
| <!-- Use the security domain defined in conf/login-config.xml -->
| <security-domain>HsqlDbRealm</security-domain>
|
| <!-- Use the security domain defined in conf/login-config.xml or the
| getConnection(user, pw) for logins. The security domain takes precedence.
| <security-domain-and-application>HsqlDbRealm</security-domain-and-application>
| -->
|
| <!-- HSQL DB benefits from prepared statement caching -->
| <prepared-statement-cache-size>32</prepared-statement-cache-size>
|
| <!-- corresponding type-mapping in the standardjbosscmp-jdbc.xml -->
| <metadata>
| <type-mapping>Hypersonic SQL</type-mapping>
| </metadata>
|
| <!-- When using in-process (standalone) mode
| <depends>jboss:service=Hypersonic,database=localDB</depends>-->
| <!-- Uncomment when using hsqldb in server mode-->
| <depends>jboss:service=Hypersonic</depends>
|
| </local-tx-datasource>
|
| <!-- Uncomment if you want hsqldb accessed over tcp (server mode)-->
| <mbean code="org.jboss.jdbc.HypersonicDatabase"
| name="jboss:service=Hypersonic">
| <attribute name="Port">1701</attribute>
| <attribute name="BindAddress">${jboss.bind.address}</attribute>
| <attribute name="Silent">true</attribute>
| <attribute name="Database">default</attribute>
| <attribute name="Trace">false</attribute>
| <attribute name="No_system_exit">true</attribute>
| </mbean>
|
|
| <!-- For hsqldb accessed from jboss only, in-process (standalone) mode
| <mbean code="org.jboss.jdbc.HypersonicDatabase"
| name="jboss:service=Hypersonic,database=localDB">
| <attribute name="Database">localDB</attribute>
| <attribute name="InProcessMode">true</attribute>
| </mbean>
| -->
| </datasources>
|
Anyway if someone knows what is wrong with my hsqldb-ds I'd appreciate it or
is there a tutorial or example with Jboss Java5 and HSQL persistence (not in memory).
Because this is all I need an example of an application where I can store user acounts
in a hsqldb not only as long as the server runs. I want to find those acounts in the db
even if I restart my server (PC)!
Can anyone help me out?
thanks and best regards,
Mussie
View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=4118516#4118516
Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=4118516
18 years, 6 months
[JBoss Seam] - Re: Data disappeared when clicking on Conversation outjectio
by gus888
"jacob.orshalick" wrote : Without some code (the view, the navigation, etc), I don't think anyone is going to be able to help here...
Thank you, Jacob. Following are my code snippets:pages.xml
| <page view-id="*">
| <navigation>
| <rule if-outcome="emailList">
| <redirect view-id="/emails.xhtml"/>
| </rule>
| <rule if-outcome="phoneList">
| <redirect view-id="/phones.xhtml"/>
| </rule>
| ....
|
| sidebar.xhtml
| <div>
| <ice:commandLink value="Contact Emails"
| action="#{contactServicer.retrieveEmails}"/>
| </div>
|
| <div>
| <ice:commandLink value="Contact Phones"
| action="#{contactServicer.retrievePhones}"/>
| </div>
| ...
|
| emails.xhtml
| <ice:panelSeries style="clear: both;"
| value="#{emailList}"
| var="email" rendered="#{!empty emailList}">
| <div class="row">
| <ice:outputText value="#{email.emailAddress}"/>
| </div>
| ....
|
| phones.xhtml
| <ice:panelSeries style="clear: both;"
| value="#{phoneList}"
| var="phone" rendered="#{!empty phoneList}">
| <div class="row">
| <ice:outputText value="#{phone.phoneNumber}"/>
| </div>
| ....
|
| @Name("contactServicer")
| @Stateless
| @Scope(ScopeType.STATELESS)
| public class ContactServicerBean implements ContactServicer {
|
|
| @Out(required=false, scope=ScopeType.CONVERSATION) //EVENT and PAGE don't work
| private List<Email> emailList;
|
| @Out(required=false, scope=ScopeType.CONVERSATION) //EVENT and PAGE don't work
| private List<Phone> phoneList;
|
|
| public String retrieveEmails() {
| emailList = em.createNamedQuery("...").getResultList();
| return "emailList"
| }
|
| public String retrievePhones() {
| phoneList = em.createNamedQuery("...").getResultList();
| return "phoneList";
| }
|
| ....
| }
|
"jacob.orshalick" wrote : If you outject to the conversation, you must begin a long-running conversation to have the data available on the next request (the next click of a commandLink). Otherwise, the temporary conversation will be destroyed and your data is gone on the next request.I don't know which pattern is good for enterprise project based on my codes above. Seam wiki pagination sample is using Stateless bean + Event outjection, but I couldn't make this work.
View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=4118509#4118509
Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=4118509
18 years, 6 months
[JBoss Seam] - Custom interceptors do not work with super classes
by Kragoth
When creating my own interceptor I was hoping to have super class that all my classes could extend that would give them my interceptor.
However, the initInterceptors method in the SEAM Component.java does not scan superclasses for annotations.
So I have the following code.
My Annotation
| package gekko.web.services;
|
| import static java.lang.annotation.ElementType.TYPE;
| import static java.lang.annotation.RetentionPolicy.RUNTIME;
|
| import java.lang.annotation.Retention;
| import java.lang.annotation.Target;
|
| import org.jboss.seam.annotations.intercept.Interceptors;
|
| @Target(TYPE)
| @Retention(RUNTIME)
| @Interceptors(GekkoSpringInjector.class)
| public @interface SpringAutowirable {}
|
My Super class
| package gekko.web.actionbean;
|
| import gekko.web.services.SpringAutowirable;
|
| @SpringAutowirable
| public class AbstractSeamComponent {
|
| }
|
And finally my sub-class
| package gekko.web.actionbean.enquiry;
|
| *imports stripped*
|
| @Name("catSubcatEnquiry")
| @Scope(PAGE)
| public class CatSubcatEnquiry extends AbstractSeamComponent {
|
| .....
|
| }
|
If I use the extends Superclass the Interceptor never fires.
If I change this and make an interface like
| package gekko.web.actionbean.enquiry;
|
| import gekko.web.services.SpringAutowirable;
|
| @SpringAutowirable
| public interface TestInterface {
|
| }
|
and use
| @Name("catSubcatEnquiry")
| @Scope(PAGE)
| public class CatSubcatEnquiry implements TestInterface {
| ...
| }
|
That works fine.
If you have a look at the Spring AnnotationUtils.java you will find that in there findAnnotation method it does look in super classes.
As seen here.
| public static <A extends Annotation> A findAnnotation(Method method, final Class<A> annotationType) {
|
| if (!annotationType.isAnnotation()) {
| throw new IllegalArgumentException(annotationType + " is not an annotation");
| }
| A annotation = getAnnotation(method, annotationType);
| Class<?> cl = method.getDeclaringClass();
| while (annotation == null) {
| cl = cl.getSuperclass();
| if (cl == null || cl.equals(Object.class)) {
| break;
| }
| try {
| method = cl.getDeclaredMethod(method.getName(), method.getParameterTypes());
| annotation = getAnnotation(method, annotationType);
| }
| catch (final NoSuchMethodException ex) {
| // We're done...
| }
| }
| return annotation;
| }
|
Is there a possiblity of making Seam behave the same way?
View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=4118502#4118502
Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=4118502
18 years, 6 months