[JBoss Web Services] New message: "@SchemaValidation"
by Ben Stokes
User development,
A new message was posted in the thread "@SchemaValidation":
http://community.jboss.org/message/521917#521917
Author : Ben Stokes
Profile : http://community.jboss.org/people/jay_bee
Message:
--------------------------------------------------------------
Hi all,
Has anyone had any experience using the @SchemaValidation tag?
I'm generating web services using annotations, but when using the schema validation annotation with no arguments it's unable to find the wsdl. Putting the address of the wsdl in explicitly into the annotations' arguments then throws up problems with namespaces. I assumed that as I'm using default arguments for the web service then the default arguments for schema validation would be enough, but apparently not.
Does anyone have any general advice or know where I can find some good documentation detailing how to use the @SchemaValidation?
Cheers
--------------------------------------------------------------
To reply to this message visit the message page: http://community.jboss.org/message/521917#521917
16 years, 3 months
[jBPM] New message: "Re: JBPM 4.3 and JPA/Hibernate integration question"
by Santanu Saraswati
User development,
A new message was posted in the thread "JBPM 4.3 and JPA/Hibernate integration question":
http://community.jboss.org/message/521916#521916
Author : Santanu Saraswati
Profile : http://community.jboss.org/people/saraswati.santanu
Message:
--------------------------------------------------------------
Why do you need to do this? Even wih 4.2 or any other 4.x.
Since you are using Spring, to configure hibernate session factory you have to create LocalSessionFactoryBean (or AnnotationSessionFactory which is a child class of LocalSessionFactoryBean, unless you have your own SessionFactory bean implementation). Now if you create a bean for SpringHelper then that should be good enough. A typical SpringHelper bean may look like this:
*
*
* <bean id="jbpmConfiguration" class="org.jbpm.pvm.internal.processengine.SpringHelper">
<property name="jbpmCfg">
<value>jbpm/jbpm.cfg.xml</value>
</property>
</bean>*
jBPM config location will change as per you settings.
SpringHelper is ApplicationContextAware. So application context will be injected there. Then it finds any bean of type LocalSessionFactoryBean from the application context. I believe searching bean of type AbstractSessionFactoryBean would have been better, but LocalSessionFactoryBean is just good enough. So you do not need to call any special method to inject SessionFactory into jBPM.
--------------------------------------------------------------
To reply to this message visit the message page: http://community.jboss.org/message/521916#521916
16 years, 3 months
[JBoss Cache POJO Edition] New message: "Using ExpirationAlgorithm with PojoCache"
by Wendy Schmitz
User development,
A new message was posted in the thread "Using ExpirationAlgorithm with PojoCache":
http://community.jboss.org/message/521901#521901
Author : Wendy Schmitz
Profile : http://community.jboss.org/people/citress
Message:
--------------------------------------------------------------
I am trying to configure an eviction policy using the ExpriationAlgorithm for my PojoCache, and I would like to specify a time-to-live value for each pojo I insert into the cache. The only documentation I found says to do this:
Cache cache = DefaultCacheFactory.createCache();
Fqn fqn1 = Fqn.fromString("/node/1");
Long future = new Long(System.currentTimeMillis() + 2000);
// sets the expiry time for a node
cache.getRoot().addChild(fqn1).put(ExpirationConfiguration.EXPIRATION_KEY, future);
However, since I am using a PojoCache, I have to retrieve the underlying generic cache (through getCache()) in order to object the generic Cache in order to call .getRoot().addChild(...).put(....). The documentation for getCache() says only to use this for non-POJO cache operations.
Can I use ExpirationAlogrithm wtih PojoCache, and if so, how do I configure the time-to-live for each pojo I'm inserting into the cache?
Thanks!
--------------------------------------------------------------
To reply to this message visit the message page: http://community.jboss.org/message/521901#521901
16 years, 3 months
[JBoss Web Services] New message: "WS-Addressing serialization interop error"
by Guzman LlambiÂas
User development,
A new message was posted in the thread "WS-Addressing serialization interop error":
http://community.jboss.org/message/521899#521899
Author : Guzman LlambiÂas
Profile : http://community.jboss.org/people/gllambi
Message:
--------------------------------------------------------------
Hi!! I'm doing some interoperability tests with .NET 3.5 using WS-AtomicTransaction and have some problems with a serialization interpretation of WS-Addressing's Endpoint Reference. In particular, with it's metadata tag.
Here is a SOAP message built by JBossTransactions to register a participant in a transaction. It uses JBossWS to build the soap mesage. In particular, to serialize the endpointReference (RegistrationService). As you can see, it has a metadata tag that's empty. Well, .NET's implementation of WS-AT doesn't understand the message if it has a metadata tag empty!! It can understand it if it doesn't appear or if it has some content.
<env:Envelope xmlns:env='http://schemas.xmlsoap.org/soap/envelope/'>
<env:Header>
<wscoor:CoordinationContext
env:mustUnderstand='1' xmlns:wscoor='http://docs.oasis-open.org/ws-tx/wscoor/2006/06'>
<wscoor:CoordinationContext xmlns:ns3='http://www.w3.org/2005/08/addressing'>
<wscoor:Identifier>urn:-3f570b7e:d61:4ad386e0:73</wscoor:Identifier>
<wscoor:CoordinationType>http://docs.oasis-open.org/ws-tx/wsat/2006/06
</wscoor:CoordinationType>
<wscoor:RegistrationService>
<ns3:Address>http://vmxp.localdomain:8080/ws-c11/RegistrationService</ns3:Address>
<ns3:ReferenceParameters>
<wsarj:InstanceIdentifier
xmlns:wsarj='http://schemas.arjuna.com/ws/2005/10/wsarj'>-3f570b7e:d61:4ad386e0:73</wsarj:InstanceIdentifier>
</ns3:ReferenceParameters>
<ns3:Metadata />
</wscoor:RegistrationService>
</wscoor:CoordinationContext>
</wscoor:CoordinationContext>
</env:Header>
<env:Body>
<ns1:depositar xmlns:ns1="http://services.lins.fing.edu.uy/">
<idCuenta>1</idCuenta>
<monto>5000.0</monto>
</ns1:depositar>
</env:Body>
Ok! This is not a JBossWS interoperability problem. Is a .NET's problem, as the WS-Addressing XML Schema says this scenario may happen. But, as I can't change .NET's implementation and I got to have this working, I want to change JBossWS implementation to remove the metadata tag if it has no content. It still be a correct WS-Addressing message. So, the question where you can help me is: which class (and method) of JBossWS I have to change in order to remove the metadata tag?
It's very important that somebody could tell me this, in order to achieve interoperability with .NET 3.5 using WS-AtomicTransaction. I would appreciate it a lot!!!
Thanks in advance
Guzman
PD: Here's the link to JBossTransactions forum where I discuss the problem with Adinn http://community.jboss.org/thread/145652. It would be great to find a tidy and quick solution as this one.
--------------------------------------------------------------
To reply to this message visit the message page: http://community.jboss.org/message/521899#521899
16 years, 3 months