Re: [Axis2] 1.4 branch broken?

[keith chapman]

Hi Dennis,

You should go into the tools folder and build the axis2-aar-maven-plugin and
the axais-mar-maven-plugin first. Then build axis2 from the root level.

Thanks,
Keith.

On Fri, Mar 6, 2009 at 12:57 PM, Dennis Sosnoski  wrote:

> Ok, so that's not the cause of the problem. I guess the real issue is just
> that there's no longer a 1.4-SNAPSHOT repository available. So anyone have
> any ideas on how I can get the code to build?
>
>  - Dennis
>
>
> keith chapman wrote:
>
>> Dennis,
>>
>> Isn't that the correct behaviour? The tag should be versioned 1.4.1 while
>> the branch stays on 1.4-SNAPSHOT.
>>
>> Thanks,
>> Keith,
>>
>> On Fri, Mar 6, 2009 at 12:33 PM, Dennis Sosnoski > d...@sosnoski.com>> wrote:
>>
>>I did a fresh checkout of the Java 1.4 branch from svn in order to
>>retrofit some code. When I try running "mvn install", I get:
>>
>>Downloading:
>>
>> http://people.apache.org/repo/m2-snapshot-repository/org/apache/axis2/axis2-mar-maven-plugin/1.4-SNAPSHOT/axis2-mar-maven-plugin-1.4-SNAPSHOT.jar
>>Downloading:
>>
>> http://ws.zones.apache.org/repository2/org/apache/axis2/axis2-mar-maven-plugin/1.4-SNAPSHOT/axis2-mar-maven-plugin-1.4-SNAPSHOT.jar
>>  [INFO]
>>
>>  
>>[ERROR] BUILD ERROR
>>   [INFO]
>>
>>  
>>[INFO] Plugin could not be found - check that the goal name is
>>correct: Unable to download the artifact from any repository
>>
>>Anyone have an idea of what's wrong? Is it just that the change
>>from 1.4-SNAPSHOT to 1.4.1 was never checked in?
>>
>>Thanks,
>>
>> - Dennis
>>
>>--Dennis M. Sosnoski
>>SOA and Web Services in Java
>>Training and Consulting
>>http://www.sosnoski.com - http://www.sosnoski.co.nz
>>Seattle, WA +1-425-939-0576 - Wellington, NZ +64-4-298-6117
>>
>>
>>
>>
>> --
>> Keith Chapman
>> Senior Software Engineer
>> WSO2 Inc.
>> Oxygenating the Web Service Platform.
>> http://wso2.org/
>>
>> blog: http://www.keith-chapman.org
>>
>


-- 
Keith Chapman
Senior Software Engineer
WSO2 Inc.
Oxygenating the Web Service Platform.
http://wso2.org/

blog: http://www.keith-chapman.org

Re: [Axis2] 1.4 branch broken?

[Dennis Sosnoski]

Thanks, Keith - that got me as far as the codgen build. I then had to 
manually change the adb pom.xml to use version 1.4-SNAPSHOT, since the 
svn version of the pom is using 1.4.1. Now it dies during xmlbeans 
tests, but I got as far as I needed.


 - Dennis


keith chapman wrote:

Hi Dennis,

You should go into the tools folder and build the 
axis2-aar-maven-plugin and the axais-mar-maven-plugin first. Then 
build axis2 from the root level.


Thanks,
Keith.

On Fri, Mar 6, 2009 at 12:57 PM, Dennis Sosnoski > wrote:


Ok, so that's not the cause of the problem. I guess the real issue
is just that there's no longer a 1.4-SNAPSHOT repository
available. So anyone have any ideas on how I can get the code to
build?

 - Dennis


keith chapman wrote:

Dennis,

Isn't that the correct behaviour? The tag should be versioned
1.4.1 while the branch stays on 1.4-SNAPSHOT.

Thanks,
Keith,

On Fri, Mar 6, 2009 at 12:33 PM, Dennis Sosnoski
mailto:d...@sosnoski.com>
>> wrote:

   I did a fresh checkout of the Java 1.4 branch from svn in
order to
   retrofit some code. When I try running "mvn install", I get:

   Downloading:
 
 http://people.apache.org/repo/m2-snapshot-repository/org/apache/axis2/axis2-mar-maven-plugin/1.4-SNAPSHOT/axis2-mar-maven-plugin-1.4-SNAPSHOT.jar

   Downloading:
 
 http://ws.zones.apache.org/repository2/org/apache/axis2/axis2-mar-maven-plugin/1.4-SNAPSHOT/axis2-mar-maven-plugin-1.4-SNAPSHOT.jar

 [INFO]
 
 
   [ERROR] BUILD ERROR
  [INFO]
 
 

   [INFO] Plugin could not be found - check that the goal name is
   correct: Unable to download the artifact from any repository

   Anyone have an idea of what's wrong? Is it just that the change
   from 1.4-SNAPSHOT to 1.4.1 was never checked in?

   Thanks,

- Dennis

   --Dennis M. Sosnoski
   SOA and Web Services in Java
   Training and Consulting
   http://www.sosnoski.com - http://www.sosnoski.co.nz
   Seattle, WA +1-425-939-0576 - Wellington, NZ +64-4-298-6117




-- 
Keith Chapman

Senior Software Engineer
WSO2 Inc.
Oxygenating the Web Service Platform.
http://wso2.org/

blog: http://www.keith-chapman.org




--
Keith Chapman
Senior Software Engineer
WSO2 Inc.
Oxygenating the Web Service Platform.
http://wso2.org/

blog: http://www.keith-chapman.org

Re: [jira] Resolved: (AXIS2-3987) Axis2 Addressing treats MessageID as a required element

[Brian De Pradine]

That's the tricky bit. It is not us making it mandatory, it is the spec 
stating that it is mandatory. The following is taken from  [1].

In either of the above cases, if the related message lacks a [message id] 
property, the processor MUST fault.

[1] http://www.w3.org/TR/2006/REC-ws-addr-core-20060509/#formreplymsg 

Cheers

Brian DePradine
Web Services Development
IBM Hursley
External  +44 (0) 1962 816319 Internal 246319

If you can't find the time to do it right the first time, where will you 
find the time to do it again?


robert lazarski  wrote on 27/02/2009 13:55:04:

> [image removed] 
> 
> Re: [jira] Resolved: (AXIS2-3987) Axis2 Addressing treats MessageID 
> as a required element
> 
> robert lazarski 
> 
> to:
> 
> axis-dev
> 
> 27/02/2009 13:55
> 
> Please respond to axis-dev
> 
> On Fri, Feb 27, 2009 at 10:43 AM, Brian DePradine (JIRA)
>  wrote:
> >
> > [ https://issues.apache.org/jira/browse/AXIS2-3987?
> page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
> >
> > Brian DePradine resolved AXIS2-3987.
> > 
> >
> >Resolution: Won't Fix
> >
> > As the message id may be required in some situations, according to
> the WS-Addressing spec, no change will be made.
> >
> 
> But if its optional, why do we make it mandatory? That seems to me to
> be an obvious contradiction, isn't it? It would be a violation of the
> spec if it couldn't be made optional, right?
> 
> Rainy day here ... not that I have dog in this hunt.
> 
> - R
> 
> >> Axis2 Addressing treats MessageID as a required element
> >> ---
> >>
> >> Key: AXIS2-3987
> >> URL: https://issues.apache.org/jira/browse/AXIS2-3987
> >> Project: Axis 2.0 (Axis2)
> >>  Issue Type: Bug
> >>  Components: Addressing
> >> Environment: Ubuntu, jdk 1.5
> >>Reporter: Isuru Eranga Suriarachchi
> >>
> >> According to both WS-Addressing final and submission 
> specifications, the Message Id is an optional element in the header.
> But when I engaged Axis2 addressing to a simple client and set only 
> the Action, it adds a message Id as well. I tried the following 
> option as well. But it didn't work.
> >> options.setProperty(INCLUDE_OPTIONAL_HEADERS, Boolean.FALSE);
> >> So I can't create a message without the optional element 
> "MessageID" using Axis2..
> >
> > --
> > This message is automatically generated by JIRA.
> > -
> > You can reply to this email to add a comment to the issue online.
> >
> >






Unless stated otherwise above:
IBM United Kingdom Limited - Registered in England and Wales with number 
741598. 
Registered office: PO Box 41, North Harbour, Portsmouth, Hampshire PO6 3AU

[jira] Commented: (AXIS2-3987) Axis2 Addressing treats MessageID as a required element

[Brian DePradine (JIRA)]

[ 
https://issues.apache.org/jira/browse/AXIS2-3987?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12679554#action_12679554
 ] 

Brian DePradine commented on AXIS2-3987:


For future reference, here is the section of the ws-addressing spec that states 
when the message id is required:

http://www.w3.org/TR/2006/REC-ws-addr-core-20060509/#formreplymsg

> Axis2 Addressing treats MessageID as a required element
> ---
>
> Key: AXIS2-3987
> URL: https://issues.apache.org/jira/browse/AXIS2-3987
> Project: Axis 2.0 (Axis2)
>  Issue Type: Bug
>  Components: Addressing
> Environment: Ubuntu, jdk 1.5
>Reporter: Isuru Eranga Suriarachchi
>
> According to both WS-Addressing final and submission specifications, the 
> Message Id is an optional element in the header. But when I engaged Axis2 
> addressing to a simple client and set only the Action, it adds a message Id 
> as well. I tried the following option as well. But it didn't work.
> options.setProperty(INCLUDE_OPTIONAL_HEADERS, Boolean.FALSE);
> So I can't create a message without the optional element "MessageID" using 
> Axis2.. 

-- 
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.

[jira] Commented: (AXIS2-4069) un-wrapped parameters option leads to invalid Java code

[Kirill Safonov (JIRA)]

[ 
https://issues.apache.org/jira/browse/AXIS2-4069?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12679620#action_12679620
 ] 

Kirill Safonov commented on AXIS2-4069:
---

Any plans on this to be fixed? It prevents us from moving from Axis2 1.3 that 
has some critical drawbacks

> un-wrapped parameters option leads to invalid Java code
> ---
>
> Key: AXIS2-4069
> URL: https://issues.apache.org/jira/browse/AXIS2-4069
> Project: Axis 2.0 (Axis2)
>  Issue Type: Bug
>  Components: codegen
>Affects Versions: 1.4.1
>Reporter: Marius Scurtescu
>Priority: Critical
>
> Generating Java client for the Salesforce partner WSDL, using the maven 
> plugin. Same issue with command line code generator.
> If "un-wrap parameters" is enabled then invalid Java code is generated. An 
> extra comma is put at the beginning of the parameter list of some methods.
> Since the Salesforce partner WSDL is not publicly available, you have to 
> login to your Salesforce account and download it from there, not sure if I am 
> allowed to attach it here.

-- 
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.