hi Brian,
I've invented my a new system porperty session.serialization.jboss=true (default) / false :) . Also, taking into account Clebert advice to use factories. I'll create org.jboss.web.tomcat.tc6.session.SessionSerializationFactory class similar to the factory in JBC but it doesn't override the default implementation to change class loader context since we already deal with it inside http session replication code. The class reads the system property mentioned above and sets the boolean value UseJBossSerialization and static methods to create ObjectOuputStream, ObjectInputStream, MarshalledValue, MarshalledObject. Those methods will be used in conjunction with UseJBossSerialization falg to serialize the objects in JBossCacheService before inserting into the cache and deserialize after returing a retrieved value.
View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=3968131#3968131
Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=3968131
Query capability and (Service) Object classification would be good candidates for initial inclusion or rather as part of the registry core use cases.
Are there any code skeletons that can be put inside svn or maybe wait till mark gets back? Btw, I am assuming that the registry is going to be a standalone server as well as embedded within the soa stack. Clients may want to run the registry as a standalone service. I'll have to look over the previous discussions to check, this may be irrelevant.
View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=3968130#3968130
Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=3968130
Hi
I have been trying to figure out a fundamental inconsistency with JBossWS. When I deploy a SessionBean as a web service with JBoss-4.0.4 + JBossWS 1.0.2 + EJB3; JBossWS deploys the service and generates a WSDL description of the service.
In the generated WSDL the output messages are defined with a name INTERFACE-NAME_METHOD-NAMEResponse.
However, when the service is invoked the message returned from the service is METHOD-NAMEResponse.
Surely the the message names should be the same? How can we program with web services if JBossWS returns messages that don't conform to the WSDL description of those messages?
Regards
Doug
View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=3968125#3968125
Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=3968125
"arvinder" wrote : What i think I was leaning to was, will we use the registry to hold objects other than Services, such as XSDs and XSLTs that are application resources that need to be accessed centrally? Thereby implying can a Service also be classed as an Application Resource ?
Sure, that'd be technically possible - everything would just be a "RegistryObject" (including Service, Classification, Concept objects etc) ala JAXR. Whether we need the query capability at this level from the getgo???
View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=3968123#3968123
Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=3968123
| <Connector port="8443" address="${jboss.bind.address}"
| maxThreads="100" strategy="ms" maxHttpHeaderSize="9192"
| emptySessionPath="true"
| scheme="https" secure="true" clientAuth="false"
| keystoreFile="<keystore.pfx>"
| keystorePass="<some_password>"
| keystoreType="pkcs12"
| algorithm="IbmX509"
| sslProtocol = "SSL_TLS" />
|
This is the connector setting that has worked on IBM JDK5. Check the keystore type (that indicated pkcs12)
View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=3968120#3968120
Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=3968120