[JBoss Web Services] - JBoss Webservice: Endpoint does not contain operation meta data
by Mark Raa
Mark Raa [http://community.jboss.org/people/mark_raa] created the discussion
"JBoss Webservice: Endpoint does not contain operation meta data"
To view the discussion, visit: http://community.jboss.org/message/542499#542499
--------------------------------------------------------------
Hey Guys,
I have deployed a webservice from Eclipse in Java and once it has been successfully deployed, I can browse the WSDL and see the XML in my browser.
However, when I try invoke this service sending it a string parameter, i get the following error:
08:52:09,301 ERROR [SOAPFaultHelperJAXRPC] SOAP request exception
javax.xml.rpc.soap.SOAPFaultException: Endpoint {http://127.0.0.1:8080/Tws/TestW
s}TestWsPort does not contain operation meta data for: {http://dhanago.test.com/
}greet
at org.jboss.ws.core.jaxrpc.SOAPFaultHelperJAXRPC.exceptionToFaultMessag
e(SOAPFaultHelperJAXRPC.java:189)
at org.jboss.ws.core.jaxws.SOAPFaultHelperJAXWS.exceptionToFaultMessage(
SOAPFaultHelperJAXWS.java:183)
at org.jboss.ws.core.jaxws.binding.SOAP11BindingJAXWS.createFaultMessage
FromException(SOAP11BindingJAXWS.java:102)
at org.jboss.ws.core.CommonSOAPBinding.bindFaultMessage(CommonSOAPBindin
g.java:650)
at org.jboss.ws.core.server.ServiceEndpointInvoker.invoke(ServiceEndpoin
tInvoker.java:283)
at org.jboss.wsf.stack.jbws.RequestHandlerImpl.processRequest(RequestHan
dlerImpl.java:468)
at org.jboss.wsf.stack.jbws.RequestHandlerImpl.handleRequest(RequestHand
lerImpl.java:293)
at org.jboss.wsf.stack.jbws.RequestHandlerImpl.doPost(RequestHandlerImpl
.java:203)
at org.jboss.wsf.stack.jbws.RequestHandlerImpl.handleHttpRequest(Request
HandlerImpl.java:129)
at org.jboss.wsf.common.servlet.AbstractEndpointServlet.service(Abstract
EndpointServlet.java:85)
at javax.servlet.http.HttpServlet.service(HttpServlet.java:717)
at org.apache.catalina.core.ApplicationFilterChain.internalDoFilter(Appl
icationFilterChain.java:290)
at org.apache.catalina.core.ApplicationFilterChain.doFilter(ApplicationF
ilterChain.java:206)
at org.jboss.web.tomcat.filters.ReplyHeaderFilter.doFilter(ReplyHeaderFi
lter.java:96)
at org.apache.catalina.core.ApplicationFilterChain.internalDoFilter(Appl
icationFilterChain.java:235)
at org.apache.catalina.core.ApplicationFilterChain.doFilter(ApplicationF
ilterChain.java:206)
at org.apache.catalina.core.StandardWrapperValve.invoke(StandardWrapperV
alve.java:235)
at org.apache.catalina.core.StandardContextValve.invoke(StandardContextV
alve.java:191)
at org.jboss.web.tomcat.security.SecurityAssociationValve.invoke(Securit
yAssociationValve.java:190)
at org.jboss.web.tomcat.security.JaccContextValve.invoke(JaccContextValv
e.java:92)
at org.jboss.web.tomcat.security.SecurityContextEstablishmentValve.proce
ss(SecurityContextEstablishmentValve.java:126)
at org.jboss.web.tomcat.security.SecurityContextEstablishmentValve.invok
e(SecurityContextEstablishmentValve.java:70)
at org.apache.catalina.core.StandardHostValve.invoke(StandardHostValve.j
ava:127)
at org.apache.catalina.valves.ErrorReportValve.invoke(ErrorReportValve.j
ava:102)
at org.jboss.web.tomcat.service.jca.CachedConnectionValve.invoke(CachedC
onnectionValve.java:158)
at org.apache.catalina.core.StandardEngineValve.invoke(StandardEngineVal
ve.java:109)
at org.apache.catalina.connector.CoyoteAdapter.service(CoyoteAdapter.jav
a:330)
at org.apache.coyote.http11.Http11AprProcessor.process(Http11AprProcesso
r.java:905)
at org.apache.coyote.http11.Http11AprProtocol$Http11ConnectionHandler.pr
ocess(Http11AprProtocol.java:592)
at org.apache.tomcat.util.net.AprEndpoint$Worker.run(AprEndpoint.java:20
36)
at java.lang.Thread.run(Thread.java:619)
the code im using to perform the invokation is:
import javax.xml.namespace.QName;
import org.apache.axis.client.Call;
import org.apache.axis.client.Service;
public class webservice
{
public static void main(String[] args)
{
try
{
String endpoint = "http://localhost:8080/Tws/TestWs?wsdl";
Service service = new Service();
Call call = (Call) service.createCall();
call.setTargetEndpointAddress(new java.net.URL(endpoint));
call.setOperationName(new QName("http://schemas.xmlsoap.org", "greet"));
Object ret[] = (Object[]) call.invoke(new Object[] { "Joe" } );
for (int i = 0; i < ret.length; i ++)
{
System.out.println("RESPONSE " + (i + 1) + ": " + ret[i]);
}
}
catch (Exception e)
{
e.printStackTrace();
System.err.println(e.toString());
}
}
}
and the WSDL when opened in my browser looks as follows:
<definitions name='TestWsService' targetNamespace='http://127.0.0.1:8080/Tws/TestWs' xmlns='http://schemas.xmlsoap.org/wsdl/' xmlns:soap='http://schemas.xmlsoap.org/wsdl/soap/' xmlns:tns='http://127.0.0.1:8080/Tws/TestWs' xmlns:xsd='http://www.w3.org/2001/XMLSchema'>
<types>
<xs:schema targetNamespace='http://127.0.0.1:8080/Tws/TestWs' version='1.0' xmlns:tns='http://127.0.0.1:8080/Tws/TestWs' xmlns:xs='http://www.w3.org/2001/XMLSchema'>
<xs:element name='greet' type='tns:greet'/>
<xs:element name='greetResponse' type='tns:greetResponse'/>
<xs:complexType name='greet'>
<xs:sequence>
<xs:element minOccurs='0' name='name' type='xs:string'/>
</xs:sequence>
</xs:complexType>
<xs:complexType name='greetResponse'>
<xs:sequence>
<xs:element minOccurs='0' name='return' type='xs:string'/>
</xs:sequence>
</xs:complexType>
</xs:schema>
</types>
<message name='TestWs_greet'>
<part element='tns:greet' name='greet'></part>
</message>
<message name='TestWs_greetResponse'>
<part element='tns:greetResponse' name='greetResponse'></part>
</message>
<portType name='TestWs'>
<operation name='greet' parameterOrder='greet'>
<input message='tns:TestWs_greet'></input>
<output message='tns:TestWs_greetResponse'></output>
</operation>
</portType>
<binding name='TestWsBinding' type='tns:TestWs'>
<soap:binding style='document' transport='http://schemas.xmlsoap.org/soap/http'/>
<operation name='greet'>
<soap:operation soapAction=' '/>
<input>
<soap:body use='literal'/>
</input>
<output>
<soap:body use='literal'/>
</output>
</operation>
</binding>
<service name='TestWsService'>
<port binding='tns:TestWsBinding' name='TestWsPort'>
<soap:address location='http://127.0.0.1:8080/Tws/TestWs'/>
</port>
</service>
</definitions>
Has anyone experienced an issue like this before? and if so how did you resolve it?
>From my understanding, everything in my WSDL is fine, but for some reason, I cannot invoke it.
Many thanks
Mark
--------------------------------------------------------------
Reply to this message by going to Community
[http://community.jboss.org/message/542499#542499]
Start a new discussion in JBoss Web Services at Community
[http://community.jboss.org/choose-container!input.jspa?contentType=1&cont...]
16 years, 2 months
Re: [jboss-user] [JBoss Tools] - why why why, hibernate ddl exporters won't work?
by Elhanan Maayan
Elhanan Maayan [http://community.jboss.org/people/Elhanan] replied to the discussion
"why why why, hibernate ddl exporters won't work?"
To view the discussion, visit: http://community.jboss.org/message/542482#542482
--------------------------------------------------------------
there are no exceptions, none, i've also stepped through the code, and it seems to running the whole process, only the debug windows still shows the launch.
also if i've specifed a console output, i see no console output, but if i launch eclipse application from plug-in development and specify console output there, i see the output in the console of the eclipse devlopment (meaning the one launched the eclipse application for testing.
my version 3.1.0 GA..
i also so don't see the difference between schema export action and the hibernate launch config.
--------------------------------------------------------------
Reply to this message by going to Community
[http://community.jboss.org/message/542482#542482]
Start a new discussion in JBoss Tools at Community
[http://community.jboss.org/choose-container!input.jspa?contentType=1&cont...]
16 years, 2 months
[JBoss Tools] - JBossToolsRoadmap
by Denis Golovin
Denis Golovin [http://community.jboss.org/people/dgolovin] modified the document:
"JBossToolsRoadmap"
To view the document, visit: http://community.jboss.org/docs/DOC-10800
--------------------------------------------------------------
h2. JBoss Tools Road map
This page outlines the focus areas we will be working on for the next major version of JBoss Tools.
This is a work in progress and if you think something is missing/incorrect then please raise it on our mailing list or forums or simply adjust the page if it is a minor correction.
Detailed road map with concrete issues and bug fixes is to be found in our http://jira.jboss.com/jira/browse/JBIDE?report=com.atlassian.jira.plugin.... jira
For the moment this roadmap is split up in three sections, "General", "Web 2.0" and "SOA" to group the functionality according to their main target audience. Even though they are split up in different sections it does not mean they do not overlap, e.g. JBoss AS, Project Archives and Hibernate will all be relevant for SOA even though they are in Web 2.0 and the same goes for jBPM and Drools which are also relevant for Web 2.0 even though they are in SOA. The division is merely to group these according to the focus of the teams that are primarily working on these. Collaboration will be needed ;)
h3. General
Java SDK: Java 6
Eclipse Target is Eclipse 3.6 (Helios)
IDE runtimes: Windows XP/Vista, Linux 32-bit, Linux 64-bit and Mac OS X 32-bit. (Limted by what VPE can run on)
Targeted runtimes: dependent on each module, but should at least cover the same as Targeted/supported platforms.
Example of runtimes: hibernate, drools, jbpm, hornetq, teid, maven aka. the "independent" parts that the tooling can work without
having a full platform for editing configuration files, junit testing etc.
Targeted Platforms for new features: AS 5 and AS 6, EAP/SOA-P/EPP 5.x.
Additional supported platforms that shouldn't break: AS 3.x, AS 4, EAP/SOA-P/EPP 4.x
Phone Home - do a google analytics ping when Eclipse starts (tracks real usage vs downloads and updatesite).
h4. Configuration
http://community.jboss.org/docs/DOC-11195 JbtUpgradeTo3x should be filled in with the user visible changes in configuration/installation.*[INCOMPLETE]*
Support installation of Platforms vs runtimes from inside Eclipse, aka. point to an existing EAP and it should automatically configure
AS and Seam runtime, point to existing EPP and should be the same as EAP + Portal, point to existing SOA-P same as EAP + Drools, jbpm, etc.
Share the logic with the installer, maybe move it all to the plugins and make a welcome screen/dialog on new workspaces ? (how do we avoid being intrusive ?)
All users project and workspace metadata used in JBoss Tools 3.x should be usable, but not necessarily backwards compatible.
Make all "runtime" plugins use the Configure menu for their enablement and where it is possible be compatible with Facets.
h3. Web 2.0
Web 2.0 is focusing around Seam, Portal and related functionality. Note: This does not mean that the features depend on Seam, having a good experience in context of Seam is though the overall goal.
p.s. if anyone has a better name than Web 2.0 - please speak up ;)
h4. JBoss AS
[From last roadmap] many users have been having problems with deploying HAR, SAR, etc. archives in JBT. We should make that easier. Suggested solutions is to look into having a WTP module type for these and/or provide a way to control which suffix (.har,.sar,.esb vs. default .jar) will be used when deploying.
JBoss 6 should be a first class AS adapter.
Introduce grouping of servers to allow for grouped stop/start/deploy...
Make SCP/SSH option complete, considerations: start/stop server via ssh, invoke jmx to prevent deployment of partial deployments.
https://jira.jboss.org/jira/browse/JBIDE-6119 https://jira.jboss.org/jira/browse/JBIDE-6119 - Runtime detection and installation from Installer should be available from within eclipse
h4. Project Archives
Support "Make Deployable" on folders.
h4. Hibernate
Support Hibernate 3.2,3.3 and 3.5. [3.6 on hold until expected core API changes settles]
[Moved from last roadmap] Multi-Versioned Hibernate - currently we use the bundled Hibernate jars to load the users classes and execute the queries and code generation. Tying us to a very specific version of Hibernate, we should investigate launching as many of these functionalities in an external process.**
Hibernate error reporting should not be done via the main Error log view
Integrate with Dali for Eclipse 3.6
h4. Seam
Umbrella Wizard for Seam Web project *[?]*
Monitor Seam 3 development and see if there are changes needed. Probably espcially with respect to Seamgen.
h3. CDI
Add CDI Validators and Quick Fixes for discovered errors [Needs prioritized list]
h4. Visual Page Editor
Cover any missing JSF 2 features [needs to be identified]
[From old roadmap] Support CDATA
Recreate DnD feature. *[INCOMPLETE]* (Several DnD related issues should be fixed, like drop locations isn't marked during DnD under linux)
http://jira.jboss.org/jira/browse/JBIDE-1304 http://jira.jboss.org/jira/browse/JBIDE-1304 - Docbook XML editor (please, look at comments)
http://jira.jboss.org/jira/browse/JBIDE-1600 http://jira.jboss.org/jira/browse/JBIDE-1600 - Template Designer (we need at least documentation how to develop templates)
https://jira.jboss.org/jira/browse/JBIDE-6131 https://jira.jboss.org/jira/browse/JBIDE-6131 - Page templates in Content assist
Add more templates of projects.*[?]*
Because: I think we should give more points to start to our users.
Ensure you can actually install Plugins even though VPE xulrunner is not supported (i.e. Windows 64 users should be able to use all functionallity such as code completion but not the Visual part by using optional dependencies and loading)
Split Richfaces/VPE features into subcomponents so we get a smaller dependency set for the remaining features.
h4. JSF
Missing JSF 2 features. [need to identify]
https://jira.jboss.org/jira/browse/JBIDE-5219 https://jira.jboss.org/jira/browse/JBIDE-5219 - JSF 2 Kick Start Project
https://jira.jboss.org/jira/browse/JBIDE-5045 https://jira.jboss.org/jira/browse/JBIDE-5045 - Support JSF2 Annotated Managed Beans
https://jira.jboss.org/jira/browse/JBIDE-5135 https://jira.jboss.org/jira/browse/JBIDE-5135 - Support Resources Localization and Versioning in JSF 2
https://jira.jboss.org/jira/browse/JBIDE-5435 https://jira.jboss.org/jira/browse/JBIDE-5435 - JSF Resource identifier validator
h4. Metawidget
http://community.jboss.org/docs/DOC-14240 JbtMetawidgetSupport *[INCOMPLETE]*
h4. Portal
Ensure JBoss Portal and GateIn continues to work.
h3. "SOA"
h4. ESB
Changes to support HornetQ as default MQ runtime in ESB 4.9
h4. WebServices
JAX-WS Web Services: Top Down, Bottom Up
JAX-RS: Bottom up
WS and Rest Testing
Possible tooling changes for CXF WS
h4. Drools
Input needed
h2. Guvnor
input needed
* Based on input from Jervis & Kris V, it looks like just fixes in this area, no new features
h4. jBPM
Ensure jBPM 3 functionallity is stable/complete
h4. Smooks
Direct Source to Target
WSDL/SOAP Source
ESB Service Routing
EDI Templating
h3. BPEL
Rename or reuse BPEL editor ?
WSDL Editor for BPEL ?
h3. Teiid
Integrate Teiid Designer (modeshape?) into JBoss Tools. Look at overlaps.
Integrate/unify deployment with WTP Server view/functionallity ?
h3. Usability
Error messages, logging, defaults.
h3. Public API
Provide public API for JBossTools features [Features list should be defined and prioritized]
Provide public Extension Points [List should be defined and pioritized]
h3. Continuous build/Quality
unittests, pmd, coverage, publishing the results
Separate builds out for modules
Separate unit tests from integration tests
Use Tycho so both Hudson and developers are using the *same* methods
Make mvn drive the build vs Ant (use Maven ant integration where no other option)
Remove unused code and integrate UCDetector in build
h3. Documentation
Context help for JBoss Tools - http://jira.jboss.org/jira/browse/JBDS-264 http://jira.jboss.org/jira/browse/JBDS-264, http://jira.jboss.org/jira/browse/JBIDE-1886 http://jira.jboss.org/jira/browse/JBIDE-1886
--------------------------------------------------------------
Comment by going to Community
[http://community.jboss.org/docs/DOC-10800]
Create a new document in JBoss Tools at Community
[http://community.jboss.org/choose-container!input.jspa?contentType=102&co...]
16 years, 2 months
[jBPM Development] - JBPM-2835 HistroyDetail not saved in database.
by HuiSheng Xu
HuiSheng Xu [http://community.jboss.org/people/rebody] created the discussion
"JBPM-2835 HistroyDetail not saved in database."
To view the discussion, visit: http://community.jboss.org/message/542473#542473
--------------------------------------------------------------
Hi guys,
I create a patch and testcase as Arul said.
https://jira.jboss.org/jira/browse/JBPM-2835 https://jira.jboss.org/jira/browse/JBPM-2835
But the behaviour of HistoryTaskDetail is totally weird. For example, if we use taskService.assignTask() or takeTask(), it won't add any HistoryTaskDetail into database, because AssignTaskCmd didn't notify TaskUpdated event. So the assignee changed details won't be saved. If we want to save the detail information, we have to getTask() first, and modify task information, then invoke taskService.saveTask() to save the task into database and notify TaskUpdated event. But the setAssignee() of TaskImpl must be used in the Environment, otherwise it will throw a None Session in Context Exception. Unfortunately, there is no existing Command for doing this, so we have to create a customized command by ourselves.
So I afraid this part should be rewritten in the future.
--------------------------------------------------------------
Reply to this message by going to Community
[http://community.jboss.org/message/542473#542473]
Start a new discussion in jBPM Development at Community
[http://community.jboss.org/choose-container!input.jspa?contentType=1&cont...]
16 years, 2 months