[JBoss Web Services] New message: "Re: WS-Security: keystores and truststores"
by Aleksander Adamowski
User development,
A new message was posted in the thread "WS-Security: keystores and truststores":
http://community.jboss.org/message/521661#521661
Author : Aleksander Adamowski
Profile : http://community.jboss.org/people/the_olo
Message:
--------------------------------------------------------------
Hi!
Does anyone know of a method for JBoss-WS that would make it search for truststore and keystore files on the classpath, not on a fixed path?
I can do this currently with Spring-WS, e.g. in spring-ws-servlet.xml I can specify the following:
This way we don't have to put the same keystores and truststores in all the WARs that compose the full enterprise application EAR.
We couldn't find any similar functionality for JBoss-WS. Here are the example paths in the wsse configuration file:
<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>META-INF/bob-sign.jks</key-store-file>
<key-store-password>password</key-store-password>
<key-store-type>jks</key-store-type>
<trust-store-file>META-INF/wsse10.truststore</trust-store-file>
<trust-store-password>password</trust-store-password>
The paths are either:
1. filesystem-absolute, which makes configuration, deployment and general management of server environments a nightmare: keystores have to be placed in exactly the same locations on all servers in all dev, test and production environments regardless of OS - this completely eliminates the possibility of using an OS with incompatible filesystems layout, like MS Windows, in the development chain,
2. or relative to the root of the WAR archive, which requires placing keystore copies in all WARs and complicates production deployment: all cryptographic keys must be replaced by key staff, which isn't qualified to mess with the EARs and WARs inside them.
--------------------------------------------------------------
To reply to this message visit the message page: http://community.jboss.org/message/521661#521661
16 years, 3 months
[jBPM] New message: "jBPM 4.3 - Problem with SpringHelper ("cannot find SpringTransaction in current environment")"
by Olivier Test
User development,
A new message was posted in the thread "jBPM 4.3 - Problem with SpringHelper ("cannot find SpringTransaction in current environment")":
http://community.jboss.org/message/521659#521659
Author : Olivier Test
Profile : http://community.jboss.org/people/OlivierL
Message:
--------------------------------------------------------------
I'm having trouble creating the processEngine bean from SpringHelper :
{code:xml}<bean id="springHelper" class="org.jbpm.pvm.internal.processengine.SpringHelper">
<property name="jbpmCfg" value="jbpm.cfg.xml"/>
</bean>
<bean id="processEngine" factory-bean="springHelper" factory-method="createProcessEngine" />{code}
This results in the following exception when spring builds the application context :
{quote}org.springframework.beans.factory.BeanCreationException: Error creating bean with name 'processEngine' defined in class path resource [ordermanager-core-applicationContext.xml]: Instantiation of bean failed; nested exception is org.springframework.beans.factory.BeanDefinitionStoreException: Factory method [protected org.jbpm.api.ProcessEngine org.jbpm.pvm.internal.processengine.SpringHelper.createProcessEngine()] threw exception; nested exception is org.jbpm.api.JbpmException: no org.jbpm.pvm.internal.tx.SpringTransaction in current environment
at org.springframework.beans.factory.support.ConstructorResolver.instantiateUsingFactoryMethod(ConstructorResolver.java:444)
at org.springframework.beans.factory.support.AbstractAutowireCapableBeanFactory.instantiateUsingFactoryMethod(AbstractAutowireCapableBeanFactory.java:903)
at org.springframework.beans.factory.support.AbstractAutowireCapableBeanFactory.createBeanInstance(AbstractAutowireCapableBeanFactory.java:817)
at org.springframework.beans.factory.support.AbstractAutowireCapableBeanFactory.doCreateBean(AbstractAutowireCapableBeanFactory.java:440)
at org.springframework.beans.factory.support.AbstractAutowireCapableBeanFactory$1.run(AbstractAutowireCapableBeanFactory.java:409)
at java.security.AccessController.doPrivileged(Native Method)
at org.springframework.beans.factory.support.AbstractAutowireCapableBeanFactory.createBean(AbstractAutowireCapableBeanFactory.java:380)
at org.springframework.beans.factory.support.AbstractBeanFactory$1.getObject(AbstractBeanFactory.java:264)
at org.springframework.beans.factory.support.DefaultSingletonBeanRegistry.getSingleton(DefaultSingletonBeanRegistry.java:222)
at org.springframework.beans.factory.support.AbstractBeanFactory.doGetBean(AbstractBeanFactory.java:261)
at org.springframework.beans.factory.support.AbstractBeanFactory.getBean(AbstractBeanFactory.java:185)
at org.springframework.beans.factory.support.AbstractBeanFactory.getBean(AbstractBeanFactory.java:164)
at org.springframework.beans.factory.support.DefaultListableBeanFactory.preInstantiateSingletons(DefaultListableBeanFactory.java:429)
at org.springframework.context.support.AbstractApplicationContext.finishBeanFactoryInitialization(AbstractApplicationContext.java:728)
at org.springframework.context.support.AbstractApplicationContext.refresh(AbstractApplicationContext.java:380)
at org.springframework.web.context.ContextLoader.createWebApplicationContext(ContextLoader.java:255)
at org.springframework.web.context.ContextLoader.initWebApplicationContext(ContextLoader.java:199)
at org.springframework.web.context.ContextLoaderListener.contextInitialized(ContextLoaderListener.java:45)
at org.apache.catalina.core.StandardContext.listenerStart(StandardContext.java:3843)
at org.apache.catalina.core.StandardContext.start(StandardContext.java:4350)
at org.apache.catalina.core.ContainerBase.start(ContainerBase.java:1045)
at org.apache.catalina.core.StandardHost.start(StandardHost.java:719)
at org.apache.catalina.core.ContainerBase.start(ContainerBase.java:1045)
at org.apache.catalina.core.StandardEngine.start(StandardEngine.java:443)
at org.apache.catalina.core.StandardService.start(StandardService.java:516)
at org.apache.catalina.core.StandardServer.start(StandardServer.java:710)
at org.apache.catalina.startup.Catalina.start(Catalina.java:578)
at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:39)
at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25)
at java.lang.reflect.Method.invoke(Method.java:597)
at org.apache.catalina.startup.Bootstrap.start(Bootstrap.java:288)
at org.apache.catalina.startup.Bootstrap.main(Bootstrap.java:413)
Caused by: org.springframework.beans.factory.BeanDefinitionStoreException: Factory method [protected org.jbpm.api.ProcessEngine org.jbpm.pvm.internal.processengine.SpringHelper.createProcessEngine()] threw exception; nested exception is org.jbpm.api.JbpmException: no org.jbpm.pvm.internal.tx.SpringTransaction in current environment
at org.springframework.beans.factory.support.SimpleInstantiationStrategy.instantiate(SimpleInstantiationStrategy.java:127)
at org.springframework.beans.factory.support.ConstructorResolver.instantiateUsingFactoryMethod(ConstructorResolver.java:435)
... 32 more
Caused by: org.jbpm.api.JbpmException: no org.jbpm.pvm.internal.tx.SpringTransaction in current environment
at org.jbpm.pvm.internal.env.EnvironmentImpl.getFromCurrent(EnvironmentImpl.java:204)
at org.jbpm.pvm.internal.env.EnvironmentImpl.getFromCurrent(EnvironmentImpl.java:190)
at org.jbpm.pvm.internal.tx.SpringCommandCallback.doInTransaction(SpringCommandCallback.java:47)
at org.springframework.transaction.support.TransactionTemplate.execute(TransactionTemplate.java:128)
at org.jbpm.pvm.internal.tx.SpringTransactionInterceptor.execute(SpringTransactionInterceptor.java:55)
at org.jbpm.pvm.internal.svc.EnvironmentInterceptor.executeInNewEnvironment(EnvironmentInterceptor.java:53)
at org.jbpm.pvm.internal.svc.EnvironmentInterceptor.execute(EnvironmentInterceptor.java:40)
at org.jbpm.pvm.internal.svc.RetryInterceptor.execute(RetryInterceptor.java:55)
at org.jbpm.pvm.internal.processengine.ProcessEngineImpl.checkDb(ProcessEngineImpl.java:152)
at org.jbpm.pvm.internal.processengine.SpringProcessEngine.create(SpringProcessEngine.java:70)
at org.jbpm.pvm.internal.cfg.ConfigurationImpl.buildProcessEngine(ConfigurationImpl.java:92)
at org.jbpm.pvm.internal.processengine.SpringHelper.createProcessEngine(SpringHelper.java:47)
at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:39)
at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25)
at java.lang.reflect.Method.invoke(Method.java:597)
at org.springframework.beans.factory.support.SimpleInstantiationStrategy.instantiate(SimpleInstantiationStrategy.java:115)
... 33 more{quote}
My jbpm.cfg.xml :
{code:xml}<?xml version="1.0" encoding="UTF-8"?>
<jbpm-configuration>
<import resource="jbpm.jpdl.cfg.xml" />
<import resource="jbpm.identity.cfg.xml" />
<!-- <import resource="jbpm.jobexecutor.cfg.xml" />-->
<process-engine-context>
<repository-service />
<repository-cache />
<execution-service />
<history-service />
<management-service />
<identity-service />
<task-service />
<!-- Here we needed to change the transaction interceptor -->
<command-service name="txRequiredCommandService">
<retry-interceptor />
<environment-interceptor />
<spring-transaction-interceptor useCurrent="false"/>
</command-service>
<id-generator />
<types resource="jbpm.variable.types.xml" />
<address-resolver />
<business-calendar />
</process-engine-context>
<transaction-context>
<repository-session />
<db-session />
<message-session />
<timer-session />
<history-session />
<mail-session>
<mail-server>
<session-properties resource="jbpm.mail.properties" />
</mail-server>
</mail-session>
<!--
Need to set explicitly that we don't want jbpm to create sessions
-->
<hibernate-session current="true" factory="jbpmSessionFactory"/>
</transaction-context>
</jbpm-configuration>{code}
I'have done some research and found this jira : https://jira.jboss.org/jira/browse/JBPM-2710. So I'm aware of spring integration problems in version 4.3. However my problem seems different, and I suspect a configuration problem even if I can't figure out what is wrong (my jbpm.cfg.xml worked well with jBPM 4.2 and 4.1).
Any help would be appreciated.
--------------------------------------------------------------
To reply to this message visit the message page: http://community.jboss.org/message/521659#521659
16 years, 3 months
[JNDI and Naming] New message: "Re: Name lookup fails, reason unknown"
by Timothy Mowlem
User development,
A new message was posted in the thread "Name lookup fails, reason unknown":
http://community.jboss.org/message/521658#521658
Author : Timothy Mowlem
Profile : http://community.jboss.org/people/jvm
Message:
--------------------------------------------------------------
Hello Peter,
Thank you for your response. If I was starting a fresh app I would certainly use a newer version. But the app I am modifying is currently deployed on JBoss v4.0.4 so I am using the same version (well actually installed 4.0.5 but the app is running on 4.0.4) to try and keep as close as possible to that. I will probably suggest upgrading it when I roll out a new version but for now I am trying to get the app running on my dev machine.
I did go through the process and I can only see queues and factories in the global JNDI namespace which I guess just confirms the fact that the bean has not been bound to its name.
So back to my question as to why?
Any help appreciated.
Thank you.
--------------------------------------------------------------
To reply to this message visit the message page: http://community.jboss.org/message/521658#521658
16 years, 3 months
[JBoss Messaging] New message: "Rescheduling message delivery"
by Sergey Gus
User development,
A new message was posted in the thread "Rescheduling message delivery":
http://community.jboss.org/message/521656#521656
Author : Sergey Gus
Profile : http://community.jboss.org/people/sergus
Message:
--------------------------------------------------------------
Hello all.
Need some help in managing delivery of messages to queue.
We have an application that sends messages to queue. For each message sent there is "JMS_JBOSS_SCHEDULED_DELIVERY" property set to indicate when the message should be delivered for processing. Here is code snippet:
...
message.setLongProperty("JMS_JBOSS_SCHEDULED_DELIVERY", System.currentTimeMillis() + 3 * 60 * 60 * 1000);
producer.send(message);
...
Most of the time the delivery of the message is scheduled for 3 hours after it is sent.
However, after the message has been sent, sometimes there is a need
1) To change delivery of the message to earlier or later time
2) To cancel message delivery i.e undo send operation
I've not found how this can be done neither from JMX console nor programatically.
Is there any way to accomplish these requirements?
Thank you on advance.
--------------------------------------------------------------
To reply to this message visit the message page: http://community.jboss.org/message/521656#521656
16 years, 3 months
[PKI concepts] Why Jboss need (signed cert and) root-cert in PEM format?
by Sven Aluoor
Hi folks
We have here a Jboss app and web server. We signed the SSL-certificate
that end-user don't have ugly error messages. I don't understand why
we need to import the Root-Cert in PEM format?
$ keytool -import -trustcacerts -file rootcert.pem -keystore
myserver.keystore -alias root
The Root-Cert is in web browser, why there is a must to import in keystore?
Did I misunderstood PKI basics?
cheers Sven
16 years, 3 months
