Re: [EMAIL PROTECTED]: Project cocoon-block-jms (in module cocoon) failed

[sebb]

On Tue, 9 Nov 2004 17:08:36 +, sebb <[EMAIL PROTECTED]> wrote:
> On Tue, 09 Nov 2004 10:33:26 -0500, Stefano Mazzocchi
> 
> 
> <[EMAIL PROTECTED]> wrote:
> > Stefan Bodewig wrote:
> >
> >
> > > On Mon, 08 Nov 2004, Stefano Mazzocchi <[EMAIL PROTECTED]> wrote:
> > >
> > >
> > >>Geoff Howard wrote:
> > >
> > >
> > >>>I find it hard to believe the jms spec has changed, though I
> > >>>suppose this is possible.
> > >
> > >
> > > Which version does geronimo-* implement?  Maybe it is a change between
> > > 1.0.2 (the version of JMS we had before Niclas changed it to the
> > > geronimo version) and 1.1 - which seems to be the current version.
> > >
> > > Any reason we use Geronimo snapshots instead of the "official" Sun
> > > jars, BTW?
> >
> > no really. We shipt it with geronimo's and that compiles so I thought
> > that was going to be better, but nope.
> >
> > If we identified there is a API change between 1.0.2 and 1.1, I'd rather
> > have cocoon update to the latest JMS API rather than having to different
> > packages in gump since it seems that cocoon is the only one having that
> > problem anyway.
> 
> Not quite - JMeter is also failing to find JMS, but as it's optional,
> no error is generated.
> 
> See:
> 
> http://brutus.apache.org/gump/public/jakarta-jmeter/jakarta-jmeter/gump_work/build_jakarta-jmeter_jakarta-jmeter.html
> 
> ...
> 
> /usr/local/gump/packages/jms1.0.2/lib/jms.jar ...
> 
> ...
> 
> jms-message:
>  [echo] Classes for JMS support not found in classpath
> 
> I don't understand why the JMS jar is not being found - hopefully the
> latest JMS might solve this...
> 

Duh! This is a JMeter build.xml issue.
Gump builds use a different target in the build file, and set the
properties directly, rather than checking for a class name ...

> >
> > --
> > Stefano.
> >
> >
> >
>

-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]

Re: [EMAIL PROTECTED]: Project cocoon-block-jms (in module cocoon) failed

[sebb]

On Tue, 09 Nov 2004 10:33:26 -0500, Stefano Mazzocchi
<[EMAIL PROTECTED]> wrote:
> Stefan Bodewig wrote:
> 
> 
> > On Mon, 08 Nov 2004, Stefano Mazzocchi <[EMAIL PROTECTED]> wrote:
> >
> >
> >>Geoff Howard wrote:
> >
> >
> >>>I find it hard to believe the jms spec has changed, though I
> >>>suppose this is possible.
> >
> >
> > Which version does geronimo-* implement?  Maybe it is a change between
> > 1.0.2 (the version of JMS we had before Niclas changed it to the
> > geronimo version) and 1.1 - which seems to be the current version.
> >
> > Any reason we use Geronimo snapshots instead of the "official" Sun
> > jars, BTW?
> 
> no really. We shipt it with geronimo's and that compiles so I thought
> that was going to be better, but nope.
> 
> If we identified there is a API change between 1.0.2 and 1.1, I'd rather
> have cocoon update to the latest JMS API rather than having to different
> packages in gump since it seems that cocoon is the only one having that
> problem anyway.

Not quite - JMeter is also failing to find JMS, but as it's optional,
no error is generated.

See:

http://brutus.apache.org/gump/public/jakarta-jmeter/jakarta-jmeter/gump_work/build_jakarta-jmeter_jakarta-jmeter.html

...

/usr/local/gump/packages/jms1.0.2/lib/jms.jar ...

...

jms-message:
 [echo] Classes for JMS support not found in classpath


I don't understand why the JMS jar is not being found - hopefully the
latest JMS might solve this...

> 
> --
> Stefano.
> 
> 
>

-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]

Re: [EMAIL PROTECTED]: Project cocoon-block-jms (in module cocoon) failed

[Stefano Mazzocchi]

Stefan Bodewig wrote:
On Tue, 09 Nov 2004, Stefano Mazzocchi <[EMAIL PROTECTED]> wrote:

If we identified there is a API change between 1.0.2 and 1.1, I'd
rather have cocoon update to the latest JMS API rather than having
to different packages in gump since it seems that cocoon is the only
one having that problem anyway.

Looks like Cocoon was using JMS 1.1, but we only provided 1.0.2:

  [javac] 
/home/gump/workspaces2/public/workspace/cocoon/src/blocks/jms/java/org/apache/cocoon/components/jms/JMSConnectionManagerImpl.java:217:
 cannot resolve symbol
  [javac] symbol  : method createConnection (java.lang.String,java.lang.String)
  [javac] location: interface javax.jms.ConnectionFactory
  [javac] return factory.createConnection(cc.getUserName(), 
cc.getPassword());
  [javac]   ^

Is here

  [javac] 
/home/gump/workspaces2/public/workspace/cocoon/src/blocks/jms/java/org/apache/cocoon/components/jms/JMSConnectionManagerImpl.java:231:
 cannot resolve symbol
  [javac] symbol  : method createConnection ()
  [javac] location: interface javax.jms.ConnectionFactory
  [javac] return factory.createConnection();
  [javac]   ^

Is here

The J2EE 1.3 version

looks like a marker interface.
JMS 1.1 is on the way to my disk (and to brutus after that).
awesome! thanks :-)
--
Stefano.


smime.p7s
Description: S/MIME Cryptographic Signature

Re: [EMAIL PROTECTED]: Project cocoon-block-jms (in module cocoon) failed

[Stefan Bodewig]

On Tue, 09 Nov 2004, Stefano Mazzocchi <[EMAIL PROTECTED]> wrote:

> If we identified there is a API change between 1.0.2 and 1.1, I'd
> rather have cocoon update to the latest JMS API rather than having
> to different packages in gump since it seems that cocoon is the only
> one having that problem anyway.

Looks like Cocoon was using JMS 1.1, but we only provided 1.0.2:

>[javac] 
> /home/gump/workspaces2/public/workspace/cocoon/src/blocks/jms/java/org/apache/cocoon/components/jms/JMSConnectionManagerImpl.java:217:
>  cannot resolve symbol
>[javac] symbol  : method createConnection 
> (java.lang.String,java.lang.String)
>[javac] location: interface javax.jms.ConnectionFactory
>[javac] return 
> factory.createConnection(cc.getUserName(), cc.getPassword());
>[javac]   ^

Is here



>[javac] 
> /home/gump/workspaces2/public/workspace/cocoon/src/blocks/jms/java/org/apache/cocoon/components/jms/JMSConnectionManagerImpl.java:231:
>  cannot resolve symbol
>[javac] symbol  : method createConnection ()
>[javac] location: interface javax.jms.ConnectionFactory
>[javac] return factory.createConnection();
>[javac]   ^

Is here



The J2EE 1.3 version

looks like a marker interface.

JMS 1.1 is on the way to my disk (and to brutus after that).

Stefan

-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]

Re: [EMAIL PROTECTED]: Project cocoon-block-jms (in module cocoon) failed

[Stefano Mazzocchi]

Stefan Bodewig wrote:
On Mon, 08 Nov 2004, Stefano Mazzocchi <[EMAIL PROTECTED]> wrote:

Geoff Howard wrote:

I find it hard to believe the jms spec has changed, though I
suppose this is possible.

Which version does geronimo-* implement?  Maybe it is a change between
1.0.2 (the version of JMS we had before Niclas changed it to the
geronimo version) and 1.1 - which seems to be the current version.
Any reason we use Geronimo snapshots instead of the "official" Sun
jars, BTW?
no really. We shipt it with geronimo's and that compiles so I thought 
that was going to be better, but nope.

If we identified there is a API change between 1.0.2 and 1.1, I'd rather 
have cocoon update to the latest JMS API rather than having to different 
packages in gump since it seems that cocoon is the only one having that 
problem anyway.

--
Stefano.


smime.p7s
Description: S/MIME Cryptographic Signature

Re: [EMAIL PROTECTED]: Project cocoon-block-jms (in module cocoon) failed

[Stefan Bodewig]

On Mon, 08 Nov 2004, Stefano Mazzocchi <[EMAIL PROTECTED]> wrote:

> Geoff Howard wrote:

>> I find it hard to believe the jms spec has changed, though I
>> suppose this is possible.

Which version does geronimo-* implement?  Maybe it is a change between
1.0.2 (the version of JMS we had before Niclas changed it to the
geronimo version) and 1.1 - which seems to be the current version.

Any reason we use Geronimo snapshots instead of the "official" Sun
jars, BTW?

Stefan

-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]

Re: [EMAIL PROTECTED]: Project cocoon-block-jms (in module cocoon) failed

[Stefano Mazzocchi]

I was going to work on this today but I got sidetracked.
Geoff Howard wrote:
Can someone give some help figuring out what is wrong with gump for
the JMS block?  The build snippet below appears to show a failure due
to classpath (unresolved symbol) but the geronimo jms spec jar is in
the classpath (also below) and the block actually does build using the
build script.
gump.xml has a dependency declared: 
project="geronimo-spec-jms"/> but I can't see where that project is
declared in our gump descriptor.  
it's not declared in our own gump descriptor, but it's a gump-wide thing 
(checkout the gump CVS module if you want to know more)

I find it hard to believe the jms
spec has changed, though I suppose this is possible.  The gump site
appears to say that the geronimo-spec-jms project is a pseudo project,
just a binary jar included, making this change even less likely.
Any tips for tracking this down?
I really have no clue either.
Any gumpmeister with a clue?
--
Stefano.


smime.p7s
Description: S/MIME Cryptographic Signature