RE: another compilation error

"Tim Anderson" <[email protected]> Tue, 3 May 2005 23:45:51 +1000
Newsgroups	gmane.comp.java.openjms.user
Message-ID	<000e01c54fe6$6c36cbd0$387ffddc@xerces>
Hmm - not clear to me why castor would be generating
bad sources for you.

Try running the following:

> cd modules/jms
> maven clean
> maven java:compile

Send me the output of the compile off list,
along with a zip of the target/castor/src tree

> -----Original Message-----
> From: openjms-user-admin-5NWGOfrQmneRv+LV9MX5uipxlwaOVQ5f@public.gmane.org 
> [mailto:openjms-user-admin-5NWGOfrQmneRv+LV9MX5uipxlwaOVQ5f@public.gmane.org] On Behalf 
> Of Laszlo Schaffer personal
> Sent: Tuesday, 3 May 2005 5:02 PM
> To: [email protected]
> Subject: RE: [openjms-user] another compilation error
> 
> 
> 
> I tried with cleanup also but the result is the same
> For example
> 
> D:\OtherJava\opensource_dev\openjms\modules\jms\src\main\java\
> org\exolab\jms
> \authentication\UserManager.java:226: incompatible types
> found   : java.lang.Object
> required: org.exolab.jms.config.SecurityConfiguration
>             
> ConfigurationManager.getConfig().getSecurityConfiguration();
> 
> See the attached out and err files
> 
> (Note:However I could compile the project after these errors had been
> corrected)
> 
> Regards
> saf
> 
> -----Original Message-----
> From: openjms-user-admin-5NWGOfrQmneRv+LV9MX5uipxlwaOVQ5f@public.gmane.org
> [mailto:openjms-user-admin-5NWGOfrQmneRv+LV9MX5uipxlwaOVQ5f@public.gmane.org] On Behalf 
> Of Tim Anderson
> Sent: 2005. május 3. 5:54
> To: [email protected]
> Subject: RE: [openjms-user] another compilation error
> 
> Did you do a clean build?
> > maven o:clean
> > maven -Dmaven.test.skip -Dmaven.castor.fork o:build
> 
> > -----Original Message-----
> > From: openjms-user-admin-5NWGOfrQmneRv+LV9MX5uipxlwaOVQ5f@public.gmane.org
> > [mailto:openjms-user-admin-5NWGOfrQmneRv+LV9MX5uipxlwaOVQ5f@public.gmane.org] On Behalf 
> > Of Laszlo Schaffer personal
> > Sent: Tuesday, 3 May 2005 3:23 AM
> > To: [email protected]
> > Subject: [openjms-user] another compilation error
> > 
> > 
> > Hello,
> > 
> > Another things, I have checked out the latest jms version with maven
> > 
> >  
> > 
> > maven scm:checkout-project -Dmaven.scm.method=cvs
> > -Dmaven.scm.cvs.module=openjms 
> > -Dmaven.scm.cvs.root=:pserver:[email protected]:/c
> > vsroot/openjms
> > -Dmaven.scm.checkout.dir=.
> > 
> >  
> > 
> > then I started to compile the full project
> > 
> >  
> > 
> > maven -Dmaven.test.skip -Dmaven.castor.fork o:build
> > 
> >  
> > 
> > There were many errors (>20!)  like this
> > 
> > D:\OtherJava\openjms-dev\openjms\modules\jms\src\main\java\org
> > \exolab\jms\au
> > thentication\UserManager.java:226: incompatible types
> > 
> > found   : java.lang.Object
> > 
> > required: org.exolab.jms.config.SecurityConfiguration
> > 
> >             
> > ConfigurationManager.getConfig().getSecurityConfiguration();
> > 
> >                                                             
>          ^
> > 
> > D:\OtherJava\openjms-dev\openjms\modules\jms\src\main\java\org
> > \exolab\jms\au
> > thentication\UserManager.java:298: cannot resolve symbol
> > 
> > symbol  : method getUser ()
> > 
> > location: class java.lang.Object
> > 
> >             org.exolab.jms.config.User[] users =
> > config.getUsers().getUser();
> > 
> >  
> > 
> > Finally I have to recheck and repair some class (now it is
> > working) but the question is could anybody compile the jms 
> > code without any modification?
> > 
> > Thanks
> > 
> > saf
> > 
> >  
> > 
> > -----Original Message-----
> > From: openjms-user-admin-5NWGOfrQmneRv+LV9MX5uipxlwaOVQ5f@public.gmane.org
> > [mailto:openjms-user-admin-5NWGOfrQmneRv+LV9MX5uipxlwaOVQ5f@public.gmane.org] On Behalf
> > Of Tim Anderson
> > Sent: 2005. április 30. 15:37
> > To: [email protected]
> > Subject: RE: [openjms-user] httptunneling/callback
> > 
> >  
> > 
> > You also need to specify the tunnel in the JNDI provider URL:
> > 
> >  
> > 
> > String url = "https://safhome:8443/openjms-tunnel/tunnel";
> > 
> > props.put(Context.PROVIDER_URL, url);
> > 
> >  
> > 
> > -----Original Message-----
> > From: openjms-user-admin-5NWGOfrQmneRv+LV9MX5uipxlwaOVQ5f@public.gmane.org
> > [mailto:openjms-user-admin-5NWGOfrQmneRv+LV9MX5uipxlwaOVQ5f@public.gmane.org] On Behalf
> > Of Tim Anderson
> > Sent: Saturday, 30 April 2005 11:25 PM
> > To: [email protected]
> > Subject: RE: [openjms-user] httptunneling/callback
> > 
> > How have you deployed the tunnel?
> > 
> >  
> > 
> > Given your configuration, the WAR needs to be copied to:
> > 
> >   <TOMCAT_HOME>/webapps/openjms-tunnel.war
> > 
> >  
> > 
> >  
> > 
> >  -----Original Message-----
> > From: openjms-user-admin-5NWGOfrQmneRv+LV9MX5uipxlwaOVQ5f@public.gmane.org
> > [mailto:openjms-user-admin-5NWGOfrQmneRv+LV9MX5uipxlwaOVQ5f@public.gmane.org] On Behalf
> > Of Laszlo Schaffer personal
> > Sent: Friday, 29 April 2005 5:43 PM
> > To: [email protected]
> > Subject: RE: [openjms-user] httptunneling/callback
> > 
> > Hello!
> > 
> >  
> > 
> > I have tried the https/tunneling feature.
> > 
> > The Tomcat5 and JMS Server have been configured as you have
> > suggested. 
> > 
> > They are working fine (with jms admin I can connect to the server)
> > 
> > But from my test app I could not connect to the server
> > 
> > Here is the code
> > 
> >  
> > 
> > props.put(Context.INITIAL_CONTEXT_FACTORY,
> > "org.exolab.jms.jndi.InitialContextFactory");
> > 
> > //URL=https://safhome:8443
> > 
> > props.put(Context.PROVIDER_URL, url);
> > 
> >  
> > 
> > context = new InitialContext(props); // drop exception
> > 
> >  
> > 
> > factory = (QueueConnectionFactory)
> > context.lookup("QueueConnectionFactory");
> > 
> >  
> > 
> > connection = factory.createQueueConnection();
> > 
> > connection.start();
> > 
> > 
> > 
> >  
> > 
> > EXCEPTION
> > 
> > 2005-04-29 09:24:56,921 ERROR TestViewController - connect:
> > 
> > javax.naming.CommunicationException: Failed to get registry
> > service for URL: https://safhome:8443 [Root exception is 
> > java.rmi.ConnectIOException: Failed to create connection; 
> > nested exception is: 
> > 
> >             org.exolab.jms.net.connector.ConnectException:
> > Failed to connect to URI=https://safhome:8443/]
> > 
> >             at
> > org.exolab.jms.jndi.InitialContextFactory.getInitialContext(In
> > itialContextFa
> > ctory.java:109)
> > 
> >             at 
> > javax.naming.spi.NamingManager.getInitialContext(NamingManager
> > .java:667)
> > 
> >             at
> > 
> javax.naming.InitialContext.getDefaultInitCtx(InitialContext.java:247)
> > 
> >             at
> > javax.naming.InitialContext.init(InitialContext.java:223)
> > 
> >  
> > 
> > And here is my jmsconfig
> > 
> >  
> > 
> > <HttpsConfiguration webServerHost="safhome"
> > 
> >             webServerPort="8443"
> > 
> >             port="3030"
> > 
> >             servlet="/openjms-tunnel/tunnel"  />
> > 
> >  
> > 
> >  
> > 
> >    <Connectors>
> > 
> >       <Connector scheme="https">
> > 
> >          <ConnectionFactories>
> > 
> >              <TopicConnectionFactory 
> name="TopicConnectionFactory" />
> > 
> >              <QueueConnectionFactory 
> name="QueueConnectionFactory" />
> > 
> >         </ConnectionFactories>
> > 
> >      </Connector>
> > 
> >    </Connectors>
> > 
> >  
> > 
> > Any suggestion?
> > 
> >  
> > 
> > Thanks
> > 
> > Laszlo Schaffer
> > 
> >  
> > 
> > -----Original Message-----
> > From: openjms-user-admin-5NWGOfrQmneRv+LV9MX5uipxlwaOVQ5f@public.gmane.org
> > [mailto:openjms-user-admin-5NWGOfrQmneRv+LV9MX5uipxlwaOVQ5f@public.gmane.org] On Behalf
> > Of Daniel Otero
> > Sent: 2005. április 8. 0:04
> > To: [email protected]
> > Subject: Re: [openjms-user] httptunneling/callback
> > 
> >  
> > 
> > Hi saf, what you need to do (if you are using the 0.7.7-dev
> > version) is (if you can wait a few days things will be 
> > simplified a bit):
> > 
> > On the server side:
> > 
> > 1) place the .war in the webapps/ directory.
> > 
> > 2) define the https connector and it's configuration like 
> this (in the
> > openjms.xml):
> > 
> > <Connectors>
> > <Connector scheme="https">
> > <ConnectionFactories>
> > <TopicConnectionFactory name="TopicConnectionFactory" />
> > <QueueConnectionFactory name="QueueConnectionFactory" /> 
> > </ConnectionFactories> </Connector> </Connectors>
> > 
> > <HttpsConfiguration webServerHost="your.webserver.com"
> > webServerPort="9999"
> > port="3030"
> > servlet="/openjms-tunnel/tunnel"
> > />
> > 
> > Note: in the next few days the TopicConnectionFactory and
> > QueueConnectionFactory will be replaced by a single entry 
> > like so - and the examples should be modified accordingly:
> > 
> > <ConnectionFactory name="ConnectionFactory" />
> > 
> > On the cliet side...
> > 
> > 1) You need to set up your keystore and run your java client
> > with the usual parameters (-Djavax.net.ssl.trustStore="$TSTORE"
> > -Djavax.net.ssl.keyStore="$KSTORE" 
> -Djavax.net.ssl.keyStoreType="jks"
> > -Djavax.net.ssl.keyStorePassword="$KPASS" )
> > 
> > I believe the plan is to make these part of the
> > jndi.properties file (i.e. look in examples/basic and see 2) 
> > below). But that won't happen for a few days...
> > 
> > 2) The good news is that if you need to use a proxy-server to
> > get through the corporate firewall the properties to do this 
> > can already be specified in the jndi.properties file like so 
> > (much like the ssl ones will probably end
> > up):
> > 
> > org.exolab.jms.net.https.proxyHost=local.proxy.com
> > org.exolab.jms.net.https.proxyPort=3128
> > 
> > if user authentication is required you can also use the following:
> > 
> > org.exolab.jms.net.https.proxyUser=user
> > org.exolab.jms.net.https.proxyPassword=password
> > 
> > On Apr 7, 2005, at 11:07 AM, Laszlo Schaffer personal wrote:
> > 
> > Hello!
> > 
> >  
> > 
> > It is possible to use MessageListeneronMessage() behind a
> > client firewall?
> > 
> > I have read something about this TunnelServlet but I do not
> > know how can I use this?
> > 
> > What I need a configuration where a client there is behind a
> > firewall (the jms server server also) and the connection is 
> > being made using https
> > 
> > Recently have download and compiled the 0.7.7-dev version but
> > how can I use this Tunneling feature?
> > 
> >  
> > 
> > Thanks
> > 
> > saf
> > 
> > -----Original Message-----
> > From: openjms-user-admin-5NWGOfrQmneRv+LV9MX5uipxlwaOVQ5f@public.gmane.org
> > [mailto:openjms-user-admin-5NWGOfrQmneRv+LV9MX5uipxlwaOVQ5f@public.gmane.org] On Behalf
> > Of Marco Lettere
> > Sent: 2005. április 12. 13:03
> > To: Marco Lettere
> > Cc: [email protected]
> > Subject: [openjms-user] Re: Strange error in compilation of 
> 0.7.7-dev
> > 
> > I found the problem by myself. Googling for some terms I've
> > found that 
> > the problem resides in the relation between jdk 1.4 and ant. 
> > The solution was to include a "-Dmaven.castor.fork=true" 
> > switch on the 
> > maven command line.
> > Hope this could help out anyone having similar problems.
> > M.
> > 
> > Marco Lettere wrote:
> > 
> > > Hello to everyone,
> > > I'm trying to build the openjms-0.7.7-dev version. I made
> > it to build
> > > everything until the maven "tools" goal.
> > > Here I get the following problem:
> > >
> > --------------------------------------------------------------
> > --------------
> > ------------------------------------------------------
> > >
> > > BUILD FAILED
> > > File......
> > >
> > /home/synapsis/m.lettere/.maven/cache/maven-multiproject-plugi
> > n-1.3.1/plugin
> > .jelly
> > >
> > > Element... maven:reactor
> > > Line...... 217
> > > Column.... 9
> > > Unable to obtain goal [multiproject:install-callback] --
> > >
> > /home/synapsis/m.lettere/.maven/cache/maven-castor-plugin-1.2/
> > plugin.jelly:9
> > 2:38:
> > > <ant:java> java.lang.NoClassDefFoundError: 
> > > sun/reflect/ConstructorAccessorImpl
> > > Total time: 16 seconds
> > > Finished at: Tue Apr 12 09:39:27 CEST 2005
> > >
> > --------------------------------------------------------------
> > --------------
> > --------------------------------------------------------
> > >
> > >
> > > I read that this could be related to ant and jdk versions
> > but I really
> > > can't figure out where the problem resides. Can any of you
> > tell me any
> > > solution?
> > > Thank you,
> > > M.
> > >
> > 
> > 
> > 
> > -------------------------------------------------------
> > SF email is sponsored by - The IT Product Guide
> > Read honest & candid reviews on hundreds of IT Products from
> > real users.
> > Discover which products truly live up to the hype. Start 
> reading now.
> > http://ads.osdn.com/?ad_id=6595&alloc_id=14396&op=click
> > _______________________________________________
> > openjms-user mailing list
> > [email protected]
> > https://lists.sourceforge.net/lists/listinfo/openjms-user
> > 
> > 
> > 
> > -------------------------------------------------------
> > This SF.Net email is sponsored by: NEC IT Guy Games.
> > Get your fingers limbered up and give it your best shot. 4
> > great events, 4
> > opportunities to win big! Highest score wins.NEC IT Guy 
> Games. Play to
> > win an NEC 61 plasma display. Visit http://www.necitguy.com/?r 
> > _______________________________________________
> > openjms-user mailing list
> > [email protected]
> > https://lists.sourceforge.net/lists/listinfo/openjms-user
> > 
> 
> 
> 
> -------------------------------------------------------
> This SF.Net email is sponsored by: NEC IT Guy Games.
> Get your fingers limbered up and give it your best shot. 4 
> great events, 4
> opportunities to win big! Highest score wins.NEC IT Guy Games. Play to
> win an NEC 61 plasma display. Visit http://www.necitguy.com/?r 
> _______________________________________________
> openjms-user mailing list
> [email protected]
> https://lists.sourceforge.net/lists/listinfo/openjms-user
> 



-------------------------------------------------------
This SF.Net email is sponsored by: NEC IT Guy Games.
Get your fingers limbered up and give it your best shot. 4 great events, 4
opportunities to win big! Highest score wins.NEC IT Guy Games. Play to
win an NEC 61 plasma display. Visit http://www.necitguy.com/?r