[JBossWS] - Re: implementing wsse:UserNameToken
by rayymlai
Further to the last email thread:
1. A colleague of mine shows me the source code UsernameToken.java from JBossWS 1.0.3 GA. it looks like UsernameToken(Element) method does read the "Username" and "Password" from the SOAP message.
e.g.
public UsernameToken(Element element) throws WSSecurityException {
this.doc = element.getOwnerDocument();
String id = element.getAttributeNS(Constants.WSU_NS, Constants.ID);
...
Element child = Util.getFirstChildElement(element);
if (child == null || ! Constants.WSSE_NS.equals(child.getNamespaceURI()) || ! "Username".equals(child.getLocalName()))
throw new WSSecurityException("Username child expected in UsernameToken element");
this.username = XMLUtils.getFullTextChildrenFromElement(child);
child = Util.getNextSiblingElement(child);
...
}
I've tried the following permutation of changes, but I still can't make the WSS 1.0 username token profile work in JBossWS.
1. in both jboss-wsse-server.xml and jboss-wsse-client.xml, specify , e.g.
2. in the jboss-wsse*.xml, specify and (derived from the source code UsernameToken.java):
manager
manager
3. Specify username and password in the SOAP stub
(as per advice from the previous email threads)
- refer to previous reply
4. Control test - Don't specify anything in the jboss-wsse*.xml. Don't add any user or password in the SOAP stub. This is a control test, to ensure whether or has made any difference.
- no difference when running the wss samples.
Any advice?
Thanks.
View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=3982175#3982175
Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=3982175
17 years, 6 months
[JBoss Seam] - Re: Use of @Out with JSTL/ui:include
by ekusnitz
Ugh, this is getting really strange. As suggested, I changed my code to the following (note use of 'preNewObject' instead of 'newObject')
<h:panelGroup rendered="#{!preNewObject}">
<ui:include src="/pages/admin/Node/NodeDetails.xhtml" />
</h:panelGroup>
<h:panelGroup rendered="#{preNewObject}">
<ui:include src="/pages/admin/Node/ChooseNodeType.xhtml" />
</h:panelGroup>
It starts to work. It starts with the NodeDetails page because preNewObject is set to false. When the user chooses to create a new object, it's set to true, and the ChooseNodeType page loads correctly. Now, here's the weird thing. The OK button on that page -- whose action is 'newObject' -- stops working! The action is never called. I have a feeling there's a bug here somewhere. How best to proceed?
View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=3982169#3982169
Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=3982169
17 years, 6 months
[Messaging, JMS & JBossMQ] - Own dead letter queue
by andreyT
I want to write erroneous messages in own dead letter queue (sns/DLQ).
For this purpose I use the following code:
ejb-jar.xml:
| <ejb-jar>
| <description>HearerMDB</description>
| <display-name>HearerMDB</display-name>
| <enterprise-beans>
| <message-driven>
| <ejb-name>HearerMDB</ejb-name>
| <ejb-class>com.hearer.Hearer</ejb-class>
| <message-destination-type>javax.jms.Queue</message-destination-type>
| <activation-config>
| <activation-config-property>
| <activation-config-property-name>MaxPoolSize</activation-config-property-name>
| <activation-config-property-value>6</activation-config-property-value>
| </activation-config-property>
| <activation-config-property>
| <activation-config-property-name>providerAdapterJNDI</activation-config-property-name>
| <activation-config-property-value>java:/SnsJMSProvider</activation-config-property-value>
| </activation-config-property>
| </activation-config>
| </message-driven>
| </enterprise-beans>
| </ejb-jar>
|
jboss.xml
| <jboss>
| <enterprise-beans>
| <message-driven>
| <ejb-name>HearerMDB</ejb-name>
| <destination-jndi-name>queue/interlayC</destination-jndi-name>
| <configuration-name>Standard2 Message Driven Bean</configuration-name>
| <invoker-bindings>
| <invoker>
| <invoker-proxy-binding-name>sintel-message-driven-bean</invoker-proxy-binding-name>
| </invoker>
| </invoker-bindings>
| </message-driven>
| </enterprise-beans>
|
| <invoker-proxy-bindings>
| <invoker-proxy-binding>
| <name>sintel-message-driven-bean</name>
| <invoker-mbean>sintel</invoker-mbean>
| <proxy-factory>org.jboss.ejb.plugins.jms.JMSContainerInvoker</proxy-factory>
| <proxy-factory-config>
| <JMSProviderAdapterJNDI>java:/SnsJMSProvider</JMSProviderAdapterJNDI>
| <ServerSessionPoolFactoryJNDI>StdJMSPool</ServerSessionPoolFactoryJNDI>
| <CreateJBossMQDestination>false</CreateJBossMQDestination>
| <MinimumSize>1</MinimumSize>
| <MaximumSize>15</MaximumSize>
| <KeepAliveMillis>30000</KeepAliveMillis>
| <MaxMessages>1</MaxMessages>
| <MDBConfig>
| <ReconnectIntervalSec>10</ReconnectIntervalSec>
| <DLQConfig>
| <DestinationQueue>queue/sns/DLQ</DestinationQueue>
| <MaxTimesRedelivered>10</MaxTimesRedelivered>
| <TimeToLive>0</TimeToLive>
| </DLQConfig>
| </MDBConfig>
| </proxy-factory-config>
| </invoker-proxy-binding>
| </invoker-proxy-bindings>
|
| <container-configurations>
| <container-configuration>
| <container-name>Standard2 Message Driven Bean</container-name>
| <call-logging>true</call-logging>
| <invoker-proxy-binding-name>sintel-message-driven-bean</invoker-proxy-binding-name>
| <container-interceptors>
| <interceptor>org.jboss.ejb.plugins.ProxyFactoryFinderInterceptor</interceptor>
| <interceptor>org.jboss.ejb.plugins.LogInterceptor</interceptor>
| <interceptor>org.jboss.ejb.plugins.RunAsSecurityInterceptor</interceptor>
| <!-- CMT -->
| <interceptor transaction="Container">org.jboss.ejb.plugins.TxInterceptorCMT</interceptor>
| <interceptor transaction="Container">org.jboss.ejb.plugins.CallValidationInterceptor</interceptor>
| <interceptor transaction="Container">org.jboss.ejb.plugins.MessageDrivenInstanceInterceptor</interceptor>
| <!-- BMT -->
| <interceptor transaction="Bean">org.jboss.ejb.plugins.MessageDrivenInstanceInterceptor</interceptor>
| <interceptor transaction="Bean">org.jboss.ejb.plugins.MessageDrivenTxInterceptorBMT</interceptor>
| <interceptor transaction="Bean">org.jboss.ejb.plugins.CallValidationInterceptor</interceptor>
| <interceptor>org.jboss.resource.connectionmanager.CachedConnectionInterceptor</interceptor>
| </container-interceptors>
| <instance-pool>org.jboss.ejb.plugins.MessageDrivenInstancePool</instance-pool>
| <instance-cache></instance-cache>
| <persistence-manager></persistence-manager>
| <container-pool-conf>
| <MaximumSize>100</MaximumSize>
| </container-pool-conf>
| </container-configuration>
| </container-configurations>
| </jboss>
|
But messages are still kept in standard queue (queue/DLQ).
What is made incorrectly?
View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=3982168#3982168
Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=3982168
17 years, 6 months
[JBoss Seam] - Re: Step-by-Step Seam Getting Started Guide
by diablo341
I'm getting an error working through the guide. I installed AS 4.0.5.GA and jbpm starters kit 3.1.2. I get the following error when deploying the sample project:
| 11:17:55,517 INFO [EARDeployer] Init J2EE application: file:/C:/jboss_installs/jboss-4.0.5.GA/server/default/deploy/sample.ear
| 11:17:55,687 ERROR [MainDeployer] Could not initialise deployment: file:/C:/jboss_installs/jboss-4.0.5.GA/server/default/deploy/sample.ear
| org.jboss.deployment.DeploymentException: Failed to find module file: jbpm-3.1.1.jar
| at org.jboss.deployment.EARDeployer.init(EARDeployer.java:257)
| at org.jboss.deployment.MainDeployer.init(MainDeployer.java:872)
| at org.jboss.deployment.MainDeployer.deploy(MainDeployer.java:809)
Will jbpm-3.1.2.jar not work? If so, where do I find jbpm-3.1.1.jar?
John
View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=3982167#3982167
Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=3982167
17 years, 6 months