You are viewing a plain text version of this content. The canonical link for it is here.
Posted to java-dev@axis.apache.org by jayachandra <ja...@gmail.com> on 2005/09/09 10:38:25 UTC
[Axis2] Doesn't addressing classes come bundled with axis2-0.91.jar?
Hi!
The single jar of all classes that is created inside the target/lib folder,
namely axis2-0.91.jar seems to not include in it the addressing classes viz.
org.apache.axis2.handlers.addressing.AddressingInHandler
Is it by design, just the way axis2-commons is provided seperated?
Sorry, if this has been made clear earlier.
Thank you
Jaya
--
-- Jaya
Re: [Axis2] Doesn't addressing classes come bundled with axis2-0.91.jar?
Posted by Deepal Jayasinghe <de...@opensource.lk>.
Hi Jaya;
As I know it is not require to have *.AddressingHnadler in jar file , addressing module is inside the axis2-0.91.jar file (/module/addressing.mar) , and the class file your talking about is a class of addressing module therefore it is no need to have that in jar file as classfile.
Thanks,
Deepal
................................................................
~Future is Open~
----- Original Message -----
From: jayachandra
To: axis-dev@ws.apache.org
Sent: Friday, September 09, 2005 2:38 PM
Subject: [Axis2] Doesn't addressing classes come bundled with axis2-0.91.jar?
Hi!
The single jar of all classes that is created inside the target/lib folder, namely axis2-0.91.jar seems to not include in it the addressing classes viz. org.apache.axis2.handlers.addressing.AddressingInHandler
Is it by design, just the way axis2-commons is provided seperated?
Sorry, if this has been made clear earlier.
Thank you
Jaya
--
-- Jaya
Re: [Axis2] Doesn't addressing classes come bundled with
axis2-0.91.jar?
Posted by Glen Daniels <gl...@thoughtcraft.com>.
Hi Chinthaka:
> BTW, we have couple of new modules. Can we come in to conclusion on what
> to be included and what to be excluded from the axis2 jar file, please ?
>
> Currently following are in he jar - core, tool, xml, wsdl, saaj, common,
> addressing
Once it's done, I'd like databinding to be in there. I think it should
be possible to build a non-databinding version if you want one, but part
of the goal of the the simple databinding system is to allow
"code-first" deployment, which MUST be simple (no messing around with
copying jars). I'd like to make sure people can take Axis2 out of the
box and quickly deploy existing objects/classes as Web Services.
--Glen
Re: [Axis2] Doesn't addressing classes come bundled with axis2-0.91.jar?
Posted by robert burrell donkin <ro...@gmail.com>.
On 9/10/05, Glen Daniels <gl...@thoughtcraft.com> wrote:
<snip>
> > it might also be worth considering using uberjar and jarjar to create
> > an absolutely standard release jar contain all dependencies.
> > (axis2-standard.jar, say.)
>
> If I understand your meaning correctly, I'd think "complete" would be
> better than "standard" for that, but we can work out all the naming
> issues as we move forward. For now we should decide if indeed we want
> something like jar styles, and get the framework implemented in the
> maven project files.
+1
- robert
Re: [Axis2] Doesn't addressing classes come bundled with
axis2-0.91.jar?
Posted by Glen Daniels <gl...@thoughtcraft.com>.
Hi Robert!
> (without wanting to ignite naming wars) modes sounds like a very cool
> idea but it may be confusing for users if they are all called
> axis2.jar.
+1
> for example, it might be worth considering whether building with
> 'axis.jarstyle=compact' should create 'axis2-compact.jar'.
Also +1. I think we should decide on the standard set of stuff that is
the default build, and make that "axis2.jar", then make the other styles
named appropriately "axis2-compact.jar", "axis2-jaxws.jar", etc
> it might also be worth considering using uberjar and jarjar to create
> an absolutely standard release jar contain all dependencies.
> (axis2-standard.jar, say.)
If I understand your meaning correctly, I'd think "complete" would be
better than "standard" for that, but we can work out all the naming
issues as we move forward. For now we should decide if indeed we want
something like jar styles, and get the framework implemented in the
maven project files.
--Glen
Re: [Axis2] Doesn't addressing classes come bundled with axis2-0.91.jar?
Posted by robert burrell donkin <ro...@gmail.com>.
On 9/9/05, Dennis Sosnoski <dm...@sosnoski.com> wrote:
> Is the axis2.jar intended to be minimal, for client use and such? If so,
> it seems like wsdl should be left out, too.
(without wanting to ignite naming wars) modes sounds like a very cool
idea but it may be confusing for users if they are all called
axis2.jar.
for example, it might be worth considering whether building with
'axis.jarstyle=compact' should create 'axis2-compact.jar'.
it might also be worth considering using uberjar and jarjar to create
an absolutely standard release jar contain all dependencies.
(axis2-standard.jar, say.)
- robert
Re: [Axis2] Doesn't addressing classes come bundled with axis2-0.91.jar?
Posted by Dennis Sosnoski <dm...@sosnoski.com>.
Is the axis2.jar intended to be minimal, for client use and such? If so,
it seems like wsdl should be left out, too.
- Dennis
Sanjiva Weerawarana wrote:
>IMO: axis2.jar should only contain core, xml, wsdl, common and
>addressing.
>
>(The tool jar doesn't play into the runtime right now, right?)
>
>Sanjiva.
>
>On Fri, 2005-09-09 at 15:00 +0600, Eran Chinthaka wrote:
>
>
>>Just fixed it. Take an update and build the jar.
>>
>>BTW, we have couple of new modules. Can we come in to conclusion on what
>>to be included and what to be excluded from the axis2 jar file, please ?
>>
>>Currently following are in he jar - core, tool, xml, wsdl, saaj, common,
>>addressing
>>
>>
>>
>>Regards,
>>Chinthaka
>>
>>jayachandra wrote:
>>
>>
>>
>>>Hi!
>>>The single jar of all classes that is created inside the target/lib
>>>folder, namely axis2-0.91.jar seems to not include in it the
>>>addressing classes viz.
>>>org.apache.axis2.handlers.addressing.AddressingInHandler
>>>Is it by design, just the way axis2-commons is provided seperated?
>>>Sorry, if this has been made clear earlier.
>>>
>>>Thank you
>>>Jaya
>>>--
>>>-- Jaya
>>>
>>>
>>
>>
>
>
>
Re: [Axis2] Doesn't addressing classes come bundled with
axis2-0.91.jar?
Posted by Sanjiva Weerawarana <sa...@opensource.lk>.
IMO: axis2.jar should only contain core, xml, wsdl, common and
addressing.
(The tool jar doesn't play into the runtime right now, right?)
Sanjiva.
On Fri, 2005-09-09 at 15:00 +0600, Eran Chinthaka wrote:
> Just fixed it. Take an update and build the jar.
>
> BTW, we have couple of new modules. Can we come in to conclusion on what
> to be included and what to be excluded from the axis2 jar file, please ?
>
> Currently following are in he jar - core, tool, xml, wsdl, saaj, common,
> addressing
>
>
>
> Regards,
> Chinthaka
>
> jayachandra wrote:
>
> > Hi!
> > The single jar of all classes that is created inside the target/lib
> > folder, namely axis2-0.91.jar seems to not include in it the
> > addressing classes viz.
> > org.apache.axis2.handlers.addressing.AddressingInHandler
> > Is it by design, just the way axis2-commons is provided seperated?
> > Sorry, if this has been made clear earlier.
> >
> > Thank you
> > Jaya
> > --
> > -- Jaya
>
>
Re: [Axis2] Doesn't addressing classes come bundled with axis2-0.91.jar?
Posted by Eran Chinthaka <ch...@opensource.lk>.
Just fixed it. Take an update and build the jar.
BTW, we have couple of new modules. Can we come in to conclusion on what
to be included and what to be excluded from the axis2 jar file, please ?
Currently following are in he jar - core, tool, xml, wsdl, saaj, common,
addressing
Regards,
Chinthaka
jayachandra wrote:
> Hi!
> The single jar of all classes that is created inside the target/lib
> folder, namely axis2-0.91.jar seems to not include in it the
> addressing classes viz.
> org.apache.axis2.handlers.addressing.AddressingInHandler
> Is it by design, just the way axis2-commons is provided seperated?
> Sorry, if this has been made clear earlier.
>
> Thank you
> Jaya
> --
> -- Jaya