NPE in wsdl2java
Key: AXIS2-4107
URL: https://issues.apache.org/jira/browse/AXIS2-4107
Project: Axis 2.0 (Axis2)
Issue Type: Bug
Components: codegen
Affects Versions: 1.4.1
Environment: jdk1.5.0_16, Wi
Glen Daniels wrote:
Hi Jarek, Deepal:
Jarek Gawor wrote:
Deepal,
I think you misunderstood. The code assumes there is one deploeyer per
extension. See DeploymentEngine.getDeployerForExtension(). That should
either be:
Deployer getDeployerForExtension(String directory, String extension)
or
L
[
https://issues.apache.org/jira/browse/AXIS2-3651?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12643497#action_12643497
]
Balaji Hari commented on AXIS2-3651:
Where can I get this fix? This has been a blocker
> It is possible that a single POJO (for example) can offer both a
> RESTful interface and a normal SOAP interface. In fact, that can
> happen by having both JAX-RS and JAX-WS annotations on the same pojo.
Well even without having those annotation we can expose a POJO as a SOAP
and REST. I mean RE
This is an issue Keith and I discussed (a while ago) and I don't think I
saw it on the list .. I just remembered it hence the sudden email (no
particular urgency on it; it just came up).
It is possible that a single POJO (for example) can offer both a RESTful
interface and a normal SOAP interf
It is marked as resolved and is in revision 652990it should be in
1.4.1 since it was fixed in 02/May/08. All this information is in the
issue. Next time please examine the issue before posting comment.
Nadir Amra
"Balaji Hari (JIRA)" <[EMAIL PROTECTED]> wrote on 10/29/2008 09:33:44 AM:
Deepal, the REST "deserialization" requires one to know the binding to
know where to pull stuff from (query params, payload etc.). See WSDL 2.0
HTTP binding to understand how that works.
So that has to happen post-dispatch.
Sanjiva.
Deepal jayasinghe wrote:
It is possible that a single POJO
WSDL2Java: minOccurs="0" on primitive types doesn't work properly
-
Key: AXIS2-4108
URL: https://issues.apache.org/jira/browse/AXIS2-4108
Project: Axis 2.0 (Axis2)
Issue Type: B
[
https://issues.apache.org/jira/browse/AXIS2-4108?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Samuel updated AXIS2-4108:
--
Description:
When I'm generating Java classes with wsdl2java (using eclipse WTP plugin) from
this part of xsd
The job of the MessageReceiver is to take a "normalized" message (i.e.
something that looks like SOAP) and "do some valid work" with it - so
this might mean mapping to a Java method and databinding, or calling out
to a piece of hardware, or handing the contents of the body to a cached
instance
> The job of the MessageReceiver is to take a "normalized" message (i.e.
> something that looks like SOAP) and "do some valid work" with it - so
> this might mean mapping to a Java method and databinding, or calling
> out to a piece of hardware, or handing the contents of the body to a
> cached in
Dude, the details of such mapping is dependent on the actual service at
hand. Again, see WSDL 2.0 HTTP binding (which you know). How do you
propose handling that before the service is determined?
Yes, we can do it in a handler that runs post-dispatch. And the difference
between that and the MR
Let me clarify the need for multiple MR's. If we think of codegen, as of now
Axis2 generates the serverside code based on the portType of a WSDL (It does
not take the binding into consideration). Imaging a user has a WSDL such
that the response SOAP message should have a custom SOAP header when the
Keith,
Can it wait till we actually decide to do JAX-RS? Why do we need it
now in other words, is there an effort to enhance WSDL2Java more to
handle these situations?
thanks,
dims
On Wed, Oct 29, 2008 at 10:07 PM, keith chapman <[EMAIL PROTECTED]> wrote:
> Let me clarify the need for multiple M
keith chapman wrote:
> Let me clarify the need for multiple MR's. If we think of codegen, as
> of now Axis2 generates the serverside code based on the portType of a
> WSDL (It does not take the binding into consideration).
Well that is the idea , binding is for the client side not for the
server si
Hi Dims,
I had a look at JAX-RS and thought of starting on it. Thats where this
discussion popped up. I was thinking of sending a mail on this to the dev
list (regarding support for JAX-RS). Currently in order to write a RESTfull
Service in Axis2 you have to deploy your service using WSDL 2.0 [1]
Deepal see my comments inline...
On Thu, Oct 30, 2008 at 7:57 AM, Deepal jayasinghe <[EMAIL PROTECTED]>wrote:
> keith chapman wrote:
> > Let me clarify the need for multiple MR's. If we think of codegen, as
> > of now Axis2 generates the serverside code based on the portType of a
> > WSDL (It doe
I hope I'm still not late to comment on this.
I'm also with Sanjiva on this issue. Axis2 is just not Axis2 project alone.
Axiom and others are integral parts of it. Couple of challenges/questions
from me.
1. Let's take the Glen's proposal on two projects and list down the
developers in each proje
18 matches
Mail list logo
