[jira] Created: (SM-961) Cannot retrieve WSDL from http su

2007-05-31 Thread Michael Mattox (JIRA)
Cannot retrieve WSDL from http su
-

 Key: SM-961
 URL: https://issues.apache.org/activemq/browse/SM-961
 Project: ServiceMix
  Issue Type: Bug
  Components: servicemix-http
Affects Versions: 3.1.1
 Environment: JDK 1.5, Windows XP, xfire
Reporter: Michael Mattox
 Attachments: BookService.wsdl

I set up an http consumer & provider to pass through to an external webservice 
created with xfire & running under tomcat.  WSDL is attached, and here is my 
xbean.xml:

http://servicemix.apache.org/http/1.0";
   xmlns:test="http://xfire.codehaus.org";>

http://127.0.0.1:8080/test-business-service/services/BookService";
   />

http://0.0.0.0:8192/BookService/";
   defaultMep="http://www.w3.org/2004/08/wsdl/in-out"; 
   soapVersion="1.1"
   soap="true"
   />
   


When I request the WSDL with the URL http://ics030126:8192/BookService/?wsdl I 
get:

HTTP ERROR: 404
Unable to find requested resource
RequestURI=/BookService/main.wsdl
Powered by Jetty://

Interesting is that it rewrites the URL to be /BookService/main.wsdl.  That's 
not what I asked for.  In the logs I see:

10:42:00,453 | DEBUG | btpool0-1  | HttpComponent| 
e.servicemix.soap.SoapEndpoint  276 | Retrieving proxied endpoint definition
10:42:00,469 | DEBUG | btpool0-1  | HttpComponent| 
icemix.common.DefaultComponent   79 | Querying service description for 
ServiceEndpoint[service={http://xfire.codehaus.org}BookService,endpoint=bookServiceProviderEndpoint]
10:42:00,469 | DEBUG | btpool0-1  | HttpComponent| 
icemix.common.DefaultComponent   87 | No description found for 
{http://xfire.codehaus.org}BookService:bookServiceProviderEndpoint
10:42:00,578 | DEBUG | btpool0-0 - Acceptor0 SelectChannelConnector @ 
0.0.0.0:8192 | JettyContextManager  | ntextManager$ThreadPoolWrapper  441 | 
Dispatching job: [EMAIL PROTECTED],io=1,w=true,b=0|0]

This looks like it's just able to find the service for my endpoint.

I've tried lots of variations in the xbean.xml based on the suggestions of the 
mailing list:

http://www.mail-archive.com/[EMAIL PROTECTED]/msg09064.html

but I still cannot get the WSDL.  Two other people have confirmed the same 
problem, so I assume it's a bug.  I can provide more information if required.



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



[jira] Resolved: (SM-959) ssl truststore is not set for unmanaged

2007-05-31 Thread Thomas Termin (JIRA)

 [ 
https://issues.apache.org/activemq/browse/SM-959?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Thomas Termin resolved SM-959.
--

Resolution: Fixed

Fixed.

Author: tterm
Date: Thu May 31 05:46:32 2007
New Revision: 543125

URL: http://svn.apache.org/viewvc?view=rev&rev=543125
Log:
SM-959 ssl truststore is not set for unmanaged

Modified:

incubator/servicemix/trunk/deployables/bindingcomponents/servicemix-http/src/main/java/org/apache/servicemix/http/jetty/JettyContextManager.java

> ssl truststore is not set for unmanaged
> ---
>
> Key: SM-959
> URL: https://issues.apache.org/activemq/browse/SM-959
> Project: ServiceMix
>  Issue Type: Bug
>  Components: servicemix-http
>Affects Versions: 3.1
>Reporter: Thomas Termin
>Assignee: Thomas Termin
> Fix For: 3.2
>
>
> The truststore is not set for an unmanaged ssl connection as reported by 
> David Potter.

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



Re: servicemix-bean, ServiceUnitAnalyzer

2007-05-31 Thread Guillaume Nodet

Sorry, the week has been quite busy (I have just had my fifth child) ...

On 5/31/07, Eduardo Burgos <[EMAIL PROTECTED]> wrote:


any news?


On 5/24/07, Guillaume Nodet <[EMAIL PROTECTED]> wrote:
>
> On 5/23/07, Eduardo Burgos <[EMAIL PROTECTED]> wrote:
> >
> > JIRA for the custom serviceUnitAnalyzer in jbi-maven-plugin:
> >
> > https://issues.apache.org/activemq/browse/SM-956
> >
> > JIRA for the BeanServiceUnitAnalyzer for the servicemix-bean
component:
> >
> > https://issues.apache.org/activemq/browse/SM-957
>
>
> Thanks !  I'll take a look at these asap.
>
> Regarding the BeanServiceUnitAnalyzer, I only implemented it for
endpoints
> > of type  (I just thought this would be the most common
> > case).
> > I generated the consumes by looking at the fields with @ExchangeTarget
> > using
> > reflection.
>
>
> Yeah, I guess this is the most common use cases.
>
> Please take a look.
> >
> >
> > Eduardo Burgos
> >
> >
> > On 5/23/07, Guillaume Nodet <[EMAIL PROTECTED]> wrote:
> > >
> > > On 5/23/07, Eduardo Burgos <[EMAIL PROTECTED]> wrote:
> > > >
> > > > No, I'm not thinking about removing the other way, it's just to
have
> > > this
> > > > as
> > > > an option.
> > > > About the custom service analyzer, for example, lets say we have a
> > > > component
> > > > that is not supported by this team and we have no possibility to
> > access
> > > > it's
> > > > source code and I still need to build a service unit for it,
> currently
> > > > there
> > > > is no possibility for the jbi-maven-plugin to guess an analyzer
for
> > it,
> > > so
> > > > I
> > > > thought that if we had the option to define the analyzer class at
> > > service
> > > > unit level it should do.
> > >
> > >
> > > Yeah, I was thinking about that too.
> > >
> > > Another example is what I need right now, I'm looking to develop a
> > > > servicemix-bean SU and I couldn't find a ServiceUnitAnalyzer for
> that
> > > > component. I couldn't have solved my problem in a standard way if
I
> > > don't
> > > > have access to this mailing list :)
> > >
> > >
> > > Agreed
> > >
> > > I have it set in my servicemix source and its ready for a diff and
> JIRA.
> > > > Working on the BeanSUAnalyzer as we speak :)
> > >
> > >
> > > Cool, thx !
> > >
> > > Eduardo Burgos
> > > >
> > > > On 5/23/07, Guillaume Nodet <[EMAIL PROTECTED]> wrote:
> > > > >
> > > > > Sure, sounds good !
> > > > > What kind of custom service analyser are thinking about ?
> > > > > Or is that for non servicemix components ?
> > > > >
> > > > > But I don't think we should remove the other way, which work
> > > > > well for servicemix components.
> > > > >
> > > > > Btw, such discussions about enhancing ServiceMix should really
> > > > > take place on the dev list, so please answer to the dev list
> > > > > if possible.
> > > > >
> > > > > On 5/23/07, Eduardo Burgos <[EMAIL PROTECTED]> wrote:
> > > > > >
> > > > > > There is something else I would like to suggest.
> > > > > >
> > > > > > Let's say I have a service-unit artifact and my target
component
> > > does
> > > > > not
> > > > > > have a serviceUnitAnalyzer, I've seen the logic on the
> > > > jbi-maven-plugin
> > > > > > and
> > > > > > how it uses the serviceUnitAnalyzer and I noticed that it
either
> > > uses
> > > > > that
> > > > > > jbi-services.xml file or looks up the target component for a
> > > > > > serviceUnitAnalyzer class name.
> > > > > > What if we also have a
> > > > > > 
> > > > > > declared in that service-unit artifact (not the component)
where
> I
> > > can
> > > > > > specify my desired serviceUnitAnalyzer for that SU. Example:
> > > > > >
> > > > > >  > > > > > myproject
> > > > > > jbi-service-unit
> > > > > > 
> > > > > >   
> > > > > >  
> > > > > > org.apache.servicemix.tooling

> > > > > > jbi-maven-plugin
> > > > > > ${servicemix-version}
> > > > > > 
> > > > > > 
> > org.test.jbi.bean.BeanServiceUnitAnalyzer
> > > > > > 
> > > > > > 
> > > > > >  
> > > > > >   
> > > > > > 
> > > > > >
> > > > > > Notice that the  is in the SU's
> > > > configuration
> > > > > > and
> > > > > > not the component, this way the desired serviceUnitAnalyzer is
> not
> > > > tied
> > > > > to
> > > > > > the component but to the plugin's configuration (And also
> keeping
> > > the
> > > > > > current approach).
> > > > > >
> > > > > >
> > > > > > Then in the
> > > > > >
> > > > > >
> > > > >
> > > >
> > >
> >
>
org.apache.servicemix.maven.plugin.jbi.GenerateServiceUnitDescriptorMojoclass
> > > > > > add a String field called 'serviceUnitAnalyzerClass' and
insert
> > this
> > > > > > where it finds the serviceUnitAnalyzer class:
> > > > > >
> > > > > > if (useServiceUnitAnalyzer.booleanValue()) {
> > > > > > +if (serviceUnitAnalyzerClass!= null)
> > > > > > +return serviceUnitAnalyzerClass;
> > > > > > MavenProject project =
> > > getComponentProject();
> > > > > >
> >

Re: Getting started guide

2007-05-31 Thread Bummer

Awesome !!!  Great !!!

JCA related(Using jencks, XA(2pc), restoring, Connecting DB/MQ other than
ActiveMQ, ) stuff would be really great.
Since those issues are the things that we are currently using right now.

Alos I was looking for samples regarding EPR (dynamic endpoint resolution).

Thanks a lot. I really appreciated.


Gert Vanthienen wrote:
> 
> L.S.,
> 
> 
> After having followed the user mailing list for a while, it seems that 
> it's quite a steep learning curve to get started with ServiceMix. 
> I would like to add a tutorial or getting started guide to the website, 
> just guiding a new user through the existing documentation and trying to 
> explain some key concepts on the way.  Something like...
> # starting the container and connect to it using JMX
> # installing some components and deploying e.g. the wsdl-first example 
> [to explain e.g. components, service assembly, service unit]
> # building a simple SA, e.g. re-using the 'File binding' page [to 
> explain about the maven archetypes]
> # building e.g. the protocol bridge example to explain about message 
> exchange patterns, routing, ...
> 
> Would this be a worthwhile addition or are there other areas in the 
> documentation that need work more urgently?  Are there any other topics 
> to include in this guided tour?
> 
> 
> Regards,
> 
> Gert
> 
> 

-- 
View this message in context: 
http://www.nabble.com/Getting-started-guide-tf3836548s12049.html#a10906830
Sent from the ServiceMix - Dev mailing list archive at Nabble.com.