[jBPM] - Re: Problem while viewing the tasks in jbpm console
by S V S G Krishna Murthy K
S V S G Krishna Murthy K [https://community.jboss.org/people/murthy516] created the discussion
"Re: Problem while viewing the tasks in jbpm console"
To view the discussion, visit: https://community.jboss.org/message/713899#713899
--------------------------------------------------------------
Hi Chris/Tihomir,
Really Thank you so much for your valuable suggestions.I able to found jbpm.console.properties in jbpm5.2(couldnt able to find in 5.1),and modified to my Ip.Its worked.:-).And one more problem I'm facing since many days in this Tasks context.
The personal tasks are being successfully appeared after starting a process for a certain user(like krisv).When I make ant stop.demo,and again I make ant start.demo,the personal tasks are being gets removed.(As per my knowledge,I think the task ids are getting removed from database).How should I stop it.It means even if I'd done ant stop.demo,and ant start.demo the personal tasks must not get removed for that particular user.It should remain as before.What are the files i need to modify to achieve this?.Please suggest me in this context.
Thanks
--------------------------------------------------------------
Reply to this message by going to Community
[https://community.jboss.org/message/713899#713899]
Start a new discussion in jBPM at Community
[https://community.jboss.org/choose-container!input.jspa?contentType=1&con...]
12 years, 11 months
[jBPM] - Possible problems with orm.xml
by Nick Stevenson
Nick Stevenson [https://community.jboss.org/people/walterwhite] created the discussion
"Possible problems with orm.xml"
To view the discussion, visit: https://community.jboss.org/message/714336#714336
--------------------------------------------------------------
I'm trying to deploy jbpm 5.2 on jboss 7.0.2 and keep running into the following problem :
Caused by: org.hibernate.MappingException: *Could not determine type for: java.util.Set, at table: ProcessInstanceInfo, for columns: [org.hibernate.mapping.Column(eventTypes)]*
at org.hibernate.mapping.SimpleValue.getType(SimpleValue.java:303) [hibernate-core-4.0.0.CR2.jar:4.0.0.CR2]
at org.hibernate.mapping.SimpleValue.isValid(SimpleValue.java:287) [hibernate-core-4.0.0.CR2.jar:4.0.0.CR2]
at org.hibernate.mapping.Property.isValid(Property.java:215) [hibernate-core-4.0.0.CR2.jar:4.0.0.CR2]
at org.hibernate.mapping.PersistentClass.validate(PersistentClass.java:466) [hibernate-core-4.0.0.CR2.jar:4.0.0.CR2]
at org.hibernate.mapping.RootClass.validate(RootClass.java:267) [hibernate-core-4.0.0.CR2.jar:4.0.0.CR2]
at org.hibernate.cfg.Configuration.validate(Configuration.java:1285) [hibernate-core-4.0.0.CR2.jar:4.0.0.CR2]
at org.hibernate.cfg.Configuration.buildSessionFactory(Configuration.java:1714) [hibernate-core-4.0.0.CR2.jar:4.0.0.CR2]
at org.hibernate.ejb.EntityManagerFactoryImpl.<init>(EntityManagerFactoryImpl.java:76) [hibernate-entitymanager-4.0.0.CR2.jar:4.0.0.CR2]
at org.hibernate.ejb.Ejb3Configuration.buildEntityManagerFactory(Ejb3Configuration.java:899) [hibernate-entitymanager-4.0.0.CR2.jar:4.0.0.CR2]
... 80 more
When I configured my personal persistence.xml and orm.xml, I referenced https://community.jboss.org/message/643956#643956 https://community.jboss.org/message/643956, which is really a similiar problem. This fixed by initial startup (as I changed my old ProcessInstancesWaitingForEvent query to the suggested one at the bottom of the conversation). Now, however, when Spring is deploying, I'm seeing the same issue :
Caused by: javax.persistence.PersistenceException: *[PersistenceUnit: org.jbpm.persistence.jpa-jboss] Unable to build EntityManagerFactory*
at org.hibernate.ejb.Ejb3Configuration.buildEntityManagerFactory(Ejb3Configuration.java:908) [hibernate-entitymanager-4.0.0.CR2.jar:4.0.0.CR2]
at org.hibernate.ejb.Ejb3Configuration.buildEntityManagerFactory(Ejb3Configuration.java:884) [hibernate-entitymanager-4.0.0.CR2.jar:4.0.0.CR2]
at org.hibernate.ejb.HibernatePersistence.createContainerEntityManagerFactory(HibernatePersistence.java:73) [hibernate-entitymanager-4.0.0.CR2.jar:4.0.0.CR2]
at org.springframework.orm.jpa.LocalContainerEntityManagerFactoryBean.createNativeEntityManagerFactory(LocalContainerEntityManagerFactoryBean.java:225) [org.springframework.orm-3.0.6.RELEASE.jar:]
at org.springframework.orm.jpa.AbstractEntityManagerFactoryBean.afterPropertiesSet(AbstractEntityManagerFactoryBean.java:310) [org.springframework.orm-3.0.6.RELEASE.jar:]
at org.springframework.beans.factory.support.AbstractAutowireCapableBeanFactory.invokeInitMethods(AbstractAutowireCapableBeanFactory.java:1477) [org.springframework.beans-3.0.6.RELEASE.jar:]
at org.springframework.beans.factory.support.AbstractAutowireCapableBeanFactory.initializeBean(AbstractAutowireCapableBeanFactory.java:1417) [org.springframework.beans-3.0.6.RELEASE.jar:]
... 74 more
Caused by: org.hibernate.MappingException: *Could not determine type for: java.util.Set, at table: ProcessInstanceInfo, for columns: [org.hibernate.mapping.Column(eventTypes)]*
at org.hibernate.mapping.SimpleValue.getType(SimpleValue.java:303) [hibernate-core-4.0.0.CR2.jar:4.0.0.CR2]
at org.hibernate.mapping.SimpleValue.isValid(SimpleValue.java:287) [hibernate-core-4.0.0.CR2.jar:4.0.0.CR2]
at org.hibernate.mapping.Property.isValid(Property.java:215) [hibernate-core-4.0.0.CR2.jar:4.0.0.CR2]
at org.hibernate.mapping.PersistentClass.validate(PersistentClass.java:466) [hibernate-core-4.0.0.CR2.jar:4.0.0.CR2]
at org.hibernate.mapping.RootClass.validate(RootClass.java:267) [hibernate-core-4.0.0.CR2.jar:4.0.0.CR2]
at org.hibernate.cfg.Configuration.validate(Configuration.java:1285) [hibernate-core-4.0.0.CR2.jar:4.0.0.CR2]
at org.hibernate.cfg.Configuration.buildSessionFactory(Configuration.java:1714) [hibernate-core-4.0.0.CR2.jar:4.0.0.CR2]
at org.hibernate.ejb.EntityManagerFactoryImpl.<init>(EntityManagerFactoryImpl.java:76) [hibernate-entitymanager-4.0.0.CR2.jar:4.0.0.CR2]
at org.hibernate.ejb.Ejb3Configuration.buildEntityManagerFactory(Ejb3Configuration.java:899) [hibernate-entitymanager-4.0.0.CR2.jar:4.0.0.CR2]
... 80 more
I made sure ALL references to any orm.xml had this new query. When I searched against the jbpm 5.2 jars, I found that *jbpm-persistence-jpa-5.2.0.Final.jar* had its own orm.xml and JBPMorm.xml that was using the "old" query (and version=1.0). I manually changed these to use the "new" query and redeployed, but with no luck. Is this a Hibernate 4 issue? A JPA mismatch issue? Am I possible configuring Spring incorrectly?
ANY information would be helpful.
(Using a mysql DB with MySQL connector jar, by the way)
--------------------------------------------------------------
Reply to this message by going to Community
[https://community.jboss.org/message/714336#714336]
Start a new discussion in jBPM at Community
[https://community.jboss.org/choose-container!input.jspa?contentType=1&con...]
12 years, 11 months
Re: [jboss-user] [EJB3] - How to configure EJB3 MDBs for IBM Websphere MQ
by onzyone
onzyone [https://community.jboss.org/people/onzyone] commented on the document
"How to configure EJB3 MDBs for IBM Websphere MQ"
To view all comments on this document, visit: https://community.jboss.org/docs/DOC-12944#comment-8897
--------------------------------------------------
Hello, I have tried to implament both the orignal post and then the updates that Yogananth put in, this into my project, but I keep geting the following error
Please can you help point me in the right direction
Thanks,
2012-02-03 14:17:39,765 ERROR [org.jboss.kernel.plugins.dependency.AbstractKernelController] (HDScanner) Error installing to Parse: name=vfszip:/opt/jboss/jboss-5.1.0.GA/server/default/deploy/sample-ear-1.0-SNAPSHOT.ear/ state=Not Installed mode=Manual requiredState=Parse
org.jboss.deployers.spi.DeploymentException: Error creating managed object for vfszip:/opt/jboss/jboss-5.1.0.GA/server/default/deploy/sample-ear-1.0-SNAPSHOT.ear/sample-ejb-1.0-SNAPSHOT.jar/
at org.jboss.deployers.spi.DeploymentException.rethrowAsDeploymentException(DeploymentException.java:49)
at org.jboss.deployers.spi.deployer.helpers.AbstractParsingDeployerWithOutput.createMetaData(AbstractParsingDeployerWithOutput.java:362)
at org.jboss.deployers.spi.deployer.helpers.AbstractParsingDeployerWithOutput.createMetaData(AbstractParsingDeployerWithOutput.java:322)
at org.jboss.deployers.spi.deployer.helpers.AbstractParsingDeployerWithOutput.createMetaData(AbstractParsingDeployerWithOutput.java:294)
at org.jboss.deployment.JBossEjbParsingDeployer.createMetaData(JBossEjbParsingDeployer.java:95)
at org.jboss.deployers.spi.deployer.helpers.AbstractParsingDeployerWithOutput.deploy(AbstractParsingDeployerWithOutput.java:234)
at org.jboss.deployers.plugins.deployers.DeployerWrapper.deploy(DeployerWrapper.java:171)
at org.jboss.deployers.plugins.deployers.DeployersImpl.doDeploy(DeployersImpl.java:1439)
at org.jboss.deployers.plugins.deployers.DeployersImpl.doInstallParentFirst(DeployersImpl.java:1157)
at org.jboss.deployers.plugins.deployers.DeployersImpl.doInstallParentFirst(DeployersImpl.java:1210)
at org.jboss.deployers.plugins.deployers.DeployersImpl.install(DeployersImpl.java:1098)
at org.jboss.dependency.plugins.AbstractControllerContext.install(AbstractControllerContext.java:348)
at org.jboss.dependency.plugins.AbstractController.install(AbstractController.java:1631)
at org.jboss.dependency.plugins.AbstractController.incrementState(AbstractController.java:934)
at org.jboss.dependency.plugins.AbstractController.resolveContexts(AbstractController.java:1082)
at org.jboss.dependency.plugins.AbstractController.resolveContexts(AbstractController.java:984)
at org.jboss.dependency.plugins.AbstractController.change(AbstractController.java:822)
at org.jboss.dependency.plugins.AbstractController.change(AbstractController.java:553)
at org.jboss.deployers.plugins.deployers.DeployersImpl.process(DeployersImpl.java:781)
at org.jboss.deployers.plugins.main.MainDeployerImpl.process(MainDeployerImpl.java:702)
at org.jboss.system.server.profileservice.repository.MainDeployerAdapter.process(MainDeployerAdapter.java:117)
at org.jboss.system.server.profileservice.hotdeploy.HDScanner.scan(HDScanner.java:362)
at org.jboss.system.server.profileservice.hotdeploy.HDScanner.run(HDScanner.java:255)
at java.util.concurrent.Executors$RunnableAdapter.call(Executors.java:471)
at java.util.concurrent.FutureTask$Sync.innerRunAndReset(FutureTask.java:351)
at java.util.concurrent.FutureTask.runAndReset(FutureTask.java:178)
at java.util.concurrent.ScheduledThreadPoolExecutor$ScheduledFutureTask.access$201(ScheduledThreadPoolExecutor.java:165)
at java.util.concurrent.ScheduledThreadPoolExecutor$ScheduledFutureTask.run(ScheduledThreadPoolExecutor.java:267)
at java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1110)
at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:603)
at java.lang.Thread.run(Thread.java:679)
Caused by: org.jboss.xb.binding.JBossXBException: Failed to parse source: Element { http://java.sun.com/xml/ns/javaee http://java.sun.com/xml/ns/javaee}jboss is not bound as a global element.
at org.jboss.xb.binding.parser.sax.SaxJBossXBParser.parse(SaxJBossXBParser.java:203)
at org.jboss.xb.binding.UnmarshallerImpl.unmarshal(UnmarshallerImpl.java:168)
at org.jboss.xb.util.JBossXBHelper.parse(JBossXBHelper.java:189)
at org.jboss.xb.util.JBossXBHelper.parse(JBossXBHelper.java:166)
at org.jboss.deployers.vfs.spi.deployer.SchemaResolverDeployer.parse(SchemaResolverDeployer.java:137)
at org.jboss.deployers.vfs.spi.deployer.SchemaResolverDeployer.parse(SchemaResolverDeployer.java:121)
at org.jboss.deployers.vfs.spi.deployer.AbstractVFSParsingDeployer.parseAndInit(AbstractVFSParsingDeployer.java:256)
at org.jboss.deployers.vfs.spi.deployer.AbstractVFSParsingDeployer.parse(AbstractVFSParsingDeployer.java:188)
at org.jboss.deployers.spi.deployer.helpers.AbstractParsingDeployerWithOutput.createMetaData(AbstractParsingDeployerWithOutput.java:348)
... 29 more
Caused by: org.jboss.xb.binding.JBossXBRuntimeException: Element { http://java.sun.com/xml/ns/javaee http://java.sun.com/xml/ns/javaee}jboss is not bound as a global element.
at org.jboss.xb.binding.sunday.unmarshalling.SundayContentHandler.startElement(SundayContentHandler.java:660)
at org.jboss.xb.binding.parser.sax.SaxJBossXBParser$DelegatingContentHandler.startElement(SaxJBossXBParser.java:401)
at org.apache.xerces.parsers.AbstractSAXParser.startElement(Unknown Source)
at org.apache.xerces.xinclude.XIncludeHandler.startElement(Unknown Source)
at org.apache.xerces.impl.XMLNSDocumentScannerImpl.scanStartElement(Unknown Source)
at org.apache.xerces.impl.XMLNSDocumentScannerImpl$NSContentDispatcher.scanRootElementHook(Unknown Source)
at org.apache.xerces.impl.XMLDocumentFragmentScannerImpl$FragmentContentDispatcher.dispatch(Unknown Source)
at org.apache.xerces.impl.XMLDocumentFragmentScannerImpl.scanDocument(Unknown Source)
at org.apache.xerces.parsers.XML11Configuration.parse(Unknown Source)
at org.apache.xerces.parsers.XML11Configuration.parse(Unknown Source)
at org.apache.xerces.parsers.XMLParser.parse(Unknown Source)
at org.apache.xerces.parsers.AbstractSAXParser.parse(Unknown Source)
at org.apache.xerces.jaxp.SAXParserImpl$JAXPSAXParser.parse(Unknown Source)
at org.jboss.xb.binding.parser.sax.SaxJBossXBParser.parse(SaxJBossXBParser.java:199)
... 37 more
2012-02-03 14:17:39,766 WARN [org.jboss.system.server.profileservice.hotdeploy.HDScanner] (HDScanner) Failed to process changes
org.jboss.deployers.client.spi.IncompleteDeploymentException: Summary of incomplete deployments (SEE PREVIOUS ERRORS FOR DETAILS):
*** DEPLOYMENTS IN ERROR: Name -> Error
vfszip:/opt/jboss/jboss-5.1.0.GA/server/default/deploy/sample-ear-1.0-SNAPSHOT.ear/ -> org.jboss.deployers.spi.DeploymentException: Error creating managed object for vfszip:/opt/jboss/jboss-5.1.0.GA/server/default/deploy/sample-ear-1.0-SNAPSHOT.ear/sample-ejb-1.0-SNAPSHOT.jar/
DEPLOYMENTS IN ERROR:
Deployment "vfszip:/opt/jboss/jboss-5.1.0.GA/server/default/deploy/sample-ear-1.0-SNAPSHOT.ear/" is in error due to the following reason(s): org.jboss.xb.binding.JBossXBRuntimeException: Element { http://java.sun.com/xml/ns/javaee http://java.sun.com/xml/ns/javaee}jboss is not bound as a global element.
at org.jboss.deployers.plugins.deployers.DeployersImpl.checkComplete(DeployersImpl.java:993)
at org.jboss.deployers.plugins.deployers.DeployersImpl.checkComplete(DeployersImpl.java:939)
at org.jboss.deployers.plugins.main.MainDeployerImpl.checkComplete(MainDeployerImpl.java:873)
at org.jboss.system.server.profileservice.repository.MainDeployerAdapter.checkComplete(MainDeployerAdapter.java:128)
at org.jboss.system.server.profileservice.hotdeploy.HDScanner.scan(HDScanner.java:369)
at org.jboss.system.server.profileservice.hotdeploy.HDScanner.run(HDScanner.java:255)
at java.util.concurrent.Executors$RunnableAdapter.call(Executors.java:471)
at java.util.concurrent.FutureTask$Sync.innerRunAndReset(FutureTask.java:351)
at java.util.concurrent.FutureTask.runAndReset(FutureTask.java:178)
at java.util.concurrent.ScheduledThreadPoolExecutor$ScheduledFutureTask.access$201(ScheduledThreadPoolExecutor.java:165)
at java.util.concurrent.ScheduledThreadPoolExecutor$ScheduledFutureTask.run(ScheduledThreadPoolExecutor.java:267)
at java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1110)
at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:603)
at java.lang.Thread.run(Thread.java:679)
--------------------------------------------------
12 years, 11 months
[JBoss Tools] - m2e(clipse)-wtp 0.15.0 : New & Noteworthy
by Fred Bricon
Fred Bricon [https://community.jboss.org/people/fbricon] modified the blog post:
"m2e(clipse)-wtp 0.15.0 : New & Noteworthy"
To view the blog post, visit: https://community.jboss.org/community/tools/blog/2012/02/03/m2eclipse-wtp...
--------------------------------------------------------------
Maven Integration for Eclipse WTP 0.15.0, a.k.a m2eclipse-wtp, a.k.a m2e-wtp is available.
This release contains mostly bug fixes, but a few improvements managed to slip in. The complete release notes are available https://issues.sonatype.org/secure/ReleaseNote.jspa?projectId=10310&versi... here.
m2e-wtp 0.15.0 is compatible with the JavaEE distributions of Eclipse Helios and Indigo, requires at least m2e 1.0 (works with 1.1) and mavenarchiver plugin >= 0.14.0 (0.15.0 should be automatically installed).
As usual, m2e-wtp can be installed from :
* the Maven Discovery mechanism, for new installations : Window > Preferences > Maven > Discovery > Open catalog
* the http://marketplace.eclipse.org/content/maven-integration-eclipse-wtp Eclipse Marketplace : Help > Eclipse Marketplace
* the update site : *http://download.jboss.org/jbosstools/updates/m2eclipse-wtp/ http://download.jboss.org/jbosstools/updates/m2eclipse-wtp/*
So let's see what are the highlights of this new release :
h3. Packaging inclusion/exclusion support improvements
For war project, previous m2e-wtp versions used to use <packagingIncludes> and <packagingExcludes> attributes from the maven-war-plugin config to enable (or not) the deployment of project dependencies to WTP servers. In 0.15.0, the same level of support has been added to EAR projects using maven-ear-plugin 2.7+. However, the problem with this approach is, other resources (web pages, classes ...) are not properly excluded (using the <*SourceInclude> and <*SourceExclude> attributes).
In order to address this problem, https://community.jboss.org/people/rob.stryker Rob Stryker, committer on WTP and lead of JBoss AS tooling in JBoss Tools, provided an implementation for JBoss AS servers that might be generalized to other WTP server adapters (if they decide to do so). Basically, some new metadata is added to the project's .settings/org.eclipse.wst.common.component like :
<?xml version="1.0" encoding="UTF-8"?>
<project-modules id="moduleCoreId" project-version="1.5.0">
<wb-module deploy-name="webOrEar">
...
<property name="component.inclusion.patterns" value="pattern1,pattern2"/>
<property name="component.exclusion.patterns" value="pattern3,pattern4"/>
</wb-module>
</project-modules>
The patterns are separated with a comma and exclusions take precedence over inclusions : resources matching one of the exclusion patterns are not deployed, even if they match one of the inclusion patterns. That solution is not maven-bound so any other kind of project can benefit from it.
Now all m2e-wtp 0.15.0 does is map the maven patterns to their equivalent component metadata. This gives :
https://community.jboss.org/servlet/JiveServlet/showImage/38-4510-17915/c... https://community.jboss.org/servlet/JiveServlet/downloadImage/38-4510-179...
In the example above, a warning is displayed as both <warSourceIncludes> and <packagingIncludes> are defined. Since both patterns could overlap, it might lead to some weird behavior where WTP would actually deploy more files than a maven CLI build. In order to minimize (we can not totally solve) that potential discrepancy we only keep the packaging patterns in the component files and recommend using <packagingIncludes> only.
Currently, this feature only works in combination with the JBoss AS Tools from JBoss Tools 3.3.0.Beta1 (nightly builds available from http://download.jboss.org/jbosstools/updates/nightly/trunk/ http://download.jboss.org/jbosstools/updates/nightly/trunk/), but we'll try to make other WTP Server adapter vendors support it in the future (as part of WTP core API).
h3. Warnings added when unsupported dependency types are detected
As of today, if a project depends on another workspace project of type ejb-client or test-jar, that specific dependency will not be packaged properly by WTP, as Maven would do in command line. Moreover, you'll experience some class leakage on the compilation and test classpaths in Eclipse (ex: non client classes being visible). The only known workarounds to this issue are to disable workspace resolution, or close the dependent project and rely on the dependencies from the local maven repository.
Ideally, in order to make the deployment part work, we would need to introduce new WTP components, but the current WTP API https://bugs.eclipse.org/bugs/show_bug.cgi?id=330894 doesn't support it, yet. So, until this is fixed, warning markers are added whenever a project depends on such "unsupported" types. That should hopefully give users an idea of the problem and how to circumvent it.
https://community.jboss.org/servlet/JiveServlet/showImage/38-4510-17913/u... https://community.jboss.org/servlet/JiveServlet/downloadImage/38-4510-179...
h3. Better handling of dependencies in war projects
Previous m2e-wtp versions had, in some use cases, some outstanding issues with regard to dependency management of war projects. In particular,
* when 2 dependencies of the same artifact, but having a different classifier were added to a web project, only one would show up on the classpath. This has been properly fixed.
* in some cases, the timestamped version of a SNAPSHOT dependencies from the local repository, would be copied under the target/ folder, causing some jar locking issues in windows. The rationale behind this behavior is, maven-war-plugin packages snapshot dependencies using the timestamp identifier. Since the name of file in the maven classpath library needs to match the one deployed by WTP, a copy was performed. To fix this problem, the default file pattern matching used for dependency deployment has been changed to @{artifactId}@-@{baseVersion}@@{dashClassifier?}@.(a){extension}@. This means that, by default in m2e-wtp, SNAPSHOT dependencies are now deployed using the SNAPSHOT suffix instead of the timestamp. If you need to force the use of timestamped artifacts, then you need to explicitely decalre the following in your pom.xml :
<plugin>
<groupId>org.apache.maven.plugins</groupId>
<artifactId>maven-war-plugin</artifactId>
<version>2.2</version>
<configuration>
<outputFileNameMapping>@{artifactId}@-@{version}@@{dashClassifier?}@.(a){extension}@</outputFileNameMapping>
</configuration>
</plugin>
h3. Removal of conflicting facets on packaging change
If you had a java utility project, that you wanted to upgrade to an EJB project for example, a constraint violation would be raised upon project configuration update (EJB and Utility facets can't be both installed).
This has been fixed by removing all conflicting facets when you change the packaging of a Java EE project, making that conversion completely transparent.
h3. What's next?
m2e 1.1 introduces a new Eclipse to Maven project https://bugs.eclipse.org/bugs/show_bug.cgi?id=359340 conversion API. It means that, in m2e-wtp.next, we will be able to automatically convert existing WTP project configuration to maven's. Dependencies will still need to be set/translated manually but that's a pretty good start IMHO.
h3.
Finally ...
I would like to thank the m2e-wtp community at large for their support and contributions, that's what make this project move forward and make it http://marketplace.eclipse.org/metrics/installs/last30days one of the most popular project on the eclipse marketplace.
Contributions can take the form of :
* patches/pull requests (source is available on https://github.com/sonatype/m2eclipse-wtp/ https://github.com/sonatype/m2eclipse-wtp/), as Laszlo Varadi did to https://issues.sonatype.org/browse/MECLIPSEWTP-201 fix some overlay issue in windows,
* bug reports (at https://issues.sonatype.org/browse/MECLIPSEWTP https://issues.sonatype.org/browse/MECLIPSEWTP)
* help on the documentation in the https://github.com/sonatype/m2eclipse-wtp/wiki wiki.
* answering questions on the https://dev.eclipse.org/mailman/listinfo/m2e-users m2e mailing list
Keep it up.
Fred.
https://twitter.com/#!/fbricon https://twitter.com/#!/fbricon
--------------------------------------------------------------
Comment by going to Community
[https://community.jboss.org/community/tools/blog/2012/02/03/m2eclipse-wtp...]
12 years, 11 months
[JBoss Web Services] - How to modify SOAP body in JBoss 6.1.0. final?
by Martin Jondzic
Martin Jondzic [https://community.jboss.org/people/hordak83] created the discussion
"How to modify SOAP body in JBoss 6.1.0. final?"
To view the discussion, visit: https://community.jboss.org/message/714363#714363
--------------------------------------------------------------
I'm trying to modify SOAP body for an outbound ws client SOAP message, from an application which is deployed on JBoss 6.1.0. Final.
There is a registered HandlerResolver for that purpose, which has the following code:
public boolean handleMessage(SOAPMessageContext messagecontext) {
Boolean outbound = (Boolean) messagecontext.get(MessageContext.MESSAGE_OUTBOUND_PROPERTY);
if (outbound) {
try {
SOAPMessage soapMessage = messagecontext.getMessage();
SOAPBody soapBody = soapMessage.getSOAPBody();
Node firstChild = soapBody.getFirstChild();
String timeStamp = getTimestamp();
String signature = getSignature(firstChild.getLocalName(), timeStamp, secretBytes);
SOAPFactory factory = SOAPFactory.newInstance();
SOAPElement signatureElement = factory.createElement("Signature");
System.out.println(signature);
signatureElement.addTextNode(signature);
SOAPElement timestampElement = factory.createElement("Timestamp");
timestampElement.addTextNode(timeStamp);
firstChild.appendChild(signatureElement);
firstChild.appendChild(timestampElement);
} catch(SOAPException se) {
throw new RuntimeException("SOAPException was thrown.", se);
}
}
return true;
}
However, it throws this exception:
17:59:35,527 WARN [org.apache.cxf.jaxws.handler.HandlerChainInvoker] HANDLER_RAISED_RUNTIME_EXCEPTION: org.w3c.dom.DOMException: WRONG_DOCUMENT_ERR: A node is used in a different document than the one that created it.
at com.sun.org.apache.xerces.internal.dom.ParentNode.internalInsertBefore(Unknown Source) [:1.6.0_27]
at com.sun.org.apache.xerces.internal.dom.ParentNode.insertBefore(Unknown Source) [:1.6.0_27]
at com.sun.org.apache.xerces.internal.dom.NodeImpl.appendChild(Unknown Source) [:1.6.0_27]
for this line:
firstChild.appendChild(signatureElement);
This code worked fine with JBoss 5.1.0.
Any ideas?
Thanks.
--------------------------------------------------------------
Reply to this message by going to Community
[https://community.jboss.org/message/714363#714363]
Start a new discussion in JBoss Web Services at Community
[https://community.jboss.org/choose-container!input.jspa?contentType=1&con...]
12 years, 11 months
