wsdl4j update breaks BPEL
by Jason T. Greene
Hi Alejandro,
We have to update to the latest wsdl4j to resolve CTS issues, is it
possible to update BPEL to be compatible?
Thanks,
-Jason
java.lang.AbstractMethodError:
org.jbpm.bpel.xml.ArchiveWsdlLocator.close()V
at
com.ibm.wsdl.xml.WSDLReaderImpl.readWSDL(WSDLReaderImpl.java:2339)
at
org.jbpm.bpel.xml.BpelReader.readWsdlDocument(BpelReader.java:412)
at
org.jbpm.bpel.par.DefDescriptorArchiveParser.readDocuments(DefDescriptorArchiveParser.java:102)
at
org.jbpm.bpel.par.DefDescriptorArchiveParser.readFromArchive(DefDescriptorArchiveParser.java:59)
at
org.jbpm.jpdl.par.ProcessArchive.parseProcessDefinition(ProcessArchive.java:81)
at
org.jbpm.bpel.ant.ServiceGeneratorTask.execute(ServiceGeneratorTask.java:45)
at
org.apache.tools.ant.UnknownElement.execute(UnknownElement.java:275)
at org.apache.tools.ant.Task.perform(Task.java:364)
at org.apache.tools.ant.Target.execute(Target.java:341)
at org.apache.tools.ant.Target.performTasks(Target.java:369)
at
org.apache.tools.ant.Project.executeSortedTargets(Project.java:1216)
at org.apache.tools.ant.Project.executeTarget(Project.java:1185)
at
org.apache.tools.ant.helper.DefaultExecutor.executeTargets(DefaultExecutor.java:40)
at
org.apache.tools.ant.Project.executeTargets(Project.java:1068)
at org.apache.tools.ant.Main.runBuild(Main.java:668)
at org.apache.tools.ant.Main.startAnt(Main.java:187)
at org.apache.tools.ant.launch.Launcher.run(Launcher.java:246)
at org.apache.tools.ant.launch.Launcher.main(Launcher.java:67)
--
xxxxxxxxxxxxxxxxxxxxxxxxxxxx
Jason T. Greene
Senior Software Engineer
JBoss, a division of Red Hat
xxxxxxxxxxxxxxxxxxxxxxxxxxxx
19 years
[Design of JBoss Web Services] - WS-Policy brainstorming
by palin
Hi all,
working on test cases to extract requirements for ws-policy and ws-policy attachment implementations, we (Stefano and me) started thinking how the policy framework could be, thus we would like to do a little brainstorm here to share our thoughts on the issue.
1) First of all, we do need ws-po and ws-poa since we need ws-rm; for this reason the main goal would be to do the minimal work to get a working policy framework that can be used to test the future ws-rm implementation. Thus we will start supporting normal policy form (http://www.w3.org/Submission/WS-Policy/#Normal_Form_Policy_Expression) only as agreed with Thomas;
compact form (http://www.w3.org/Submission/WS-Policy/#Compact_Policy_Expression) will be added later.
For the same reason we think all UDDI related stuff (http://www.w3.org/Submission/WS-PolicyAttachment/#AttachingPoliciesUsingUDDI) could also be added in the future.
2) We nevertheless think that in order to be able to obtain future good interoperability, even now we should at least think about how this upcoming ws-po/ws-poa implementation will interact with ws-rm policy and other implementations of specs depending on policy.
3) We immagine that all the spec implementations based on ws-policy would be only required to provide mechanisms for their own assertions, ws-po/ws-poa implementation instead would provide all we need for alternatives, scope and effective policy selection, policy intersection and so on. This is what is defined in Policy Model and Policy Expression chapters of ws-policy spec:
http://www.w3.org/Submission/WS-Policy/#Policy_Model
http://www.w3.org/Submission/WS-Policy/#Policy_Expression
and in chapter 3 and 4 of ws-policy attachment:
http://www.w3.org/Submission/WS-PolicyAttachment/#PolicyAttachment
http://www.w3.org/Submission/WS-PolicyAttachment/#AttachingPolicyUsingWSD...
4) We would ofcourse need metadata for ws-policy and these will contain specific metadata of eventual assertions belonging to ws-rm, etc. We think we should be able to go to and from metadata parsing/writing wsdl, with the wstool or may be via annotations that could be defined for assertions.
5) Thomas wrote an initial policy implementation some times ago: this is to be used as a starting point for core ws-policy metadata, since it already contains a policy model implementation. This should be further developed to add scope/effective policy mechanisms.
6) Speaking about how these metadata creation could be plugged into the existing source, we think that we could evaluate something similar to what has been done for other extension implementations like eventing and addressing (MetaDataBuilder creating ExtensibleMetaData objects and so on).
Any comments and/or ideas?
Thanks
Alessio Soldano
http://www.javalinux.it
http://www.javalinuxlabs.org
View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=4031571#4031571
Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=4031571
19 years
j2eetck-mods broken?
by Alejandro Guizar
Recently I updated j2eetck-mods and javaee5-cts to the most recent
versions in CVS head. I installed TCK 5_0b, rebuilt everything and ran
the suite. I found out every test was failing because the VM was exiting
with code 1. I removed TCK 5_0b and tried again with 5_0_tempb-b06. Same
problem. I am running everything in Windows.
Apparently the harness executes a badly formatted command, shown below.
Note the java command appears after the class name and other options.
com.sun.ts.lib.harness.ExecTSTestCmd CLASSPATH=[list of ';' separated
paths] DISPLAY=:0.0 HOME=C:\Documents and Settings\aguizar
windir=C:\WINDOWS SYSTEMROOT=C:\WINDOWS
PATH=\dev\jbossas\trunk\build\output\jboss-5.0.0.Beta2\nativelib
C:\dev\jdk1.5.0_10\jre/bin/java -DTS_HOME=C:\dev\tck5\javaeetck
Are you hitting this problem as well? Where can I read about changes to
j2eetck-mods?
Thanks,
Alejandro
19 years
/jbossws/trunk broken use -r2628
by Thomas Diesler
Hi Jas,
your latest commit seems to have bits missing
cheers
-thomas
--
xxxxxxxxxxxxxxxxxxxxxxxxxxxx
Thomas Diesler
Web Service Lead
JBoss, a division of Red Hat
xxxxxxxxxxxxxxxxxxxxxxxxxxxx
19 years
