You should try to install tortoisesvn (http://tortoisesvn.tigris.org/), checkout the sources. Then, in the context menu in the explorer, you will be able to create a patch. If this is only a new file, you can just attach it to the jira issue. Patches are necessary when files are modified.
Cheers, Guillaume Nodet On 3/30/06, Gerdes, Mike <[EMAIL PROTECTED]> wrote: > > How do I create a patch under windows? I know how to do it with diff under > linux, but since I use a Win2k machine I have no clue. > The SSL support should work now, I will just have to test it. > > -----Ursprüngliche Nachricht----- > Von: Guillaume Nodet [mailto:[EMAIL PROTECTED] > Gesendet: Donnerstag, 30. März 2006 13:23 > An: [email protected] > Betreff: Re: https > > > > If you already have a lightweight component working, you can create a > jira and attach your patch (a simple test case / example would be > cool). > > Thanks, > Guillaume > > On 3/30/06, Gerdes, Mike <[EMAIL PROTECTED]> wrote: > > > > Sounds good, as I said I have done this for the old httpconnector already > > and used there the SslSocketServer already together with new parameters for > > the starting. My only problem with the servicemix-http is how the > > parameters get transported from the xbean xml file to the ServerManager. > > Your post helps much and I will see how far I get. > > > > -----Ursprüngliche Nachricht----- > > Von: Guillaume Nodet [mailto:[EMAIL PROTECTED] > > Gesendet: Donnerstag, 30. März 2006 13:10 > > An: [email protected] > > Betreff: Re: https > > > > > > > > Raising a jira issue is quite easy. > > Just register yourself at http://issues.apache.org/activemq/browse/SM > > Be sure to check somehting like 'remember me' checkbox on first login. > > Then click the 'Create new issue' on the top of the page and fill the > > form... > > > > The ServerManager's only purpose it to manage the http servers. > > The two main methods are createContext and remoteContext. > > createContext is given an url (the locationURI) where the http server > > must be created and is called in ConsumerProcessor.start. > > I guess there will be a need for additional configuration parameters > > on HttpConfiguration for the jetty ssl connector class name > > (currently, there is only one for ssl, > > org.mortbay.jetty.security.SslSocketConnector) and ssl parameters. > > > > Hope this helps, > > Guillaume Nodet > > > > On 3/30/06, Gerdes, Mike <[EMAIL PROTECTED]> wrote: > > > > > > yes I saw the TODO ;), but to be honest I have no clue how to raise a > > > JIRA and also no real idea how to do the patches, be we will see. First I > > > have to try and understand the class. For the old http-component, it was > > > quite easy to add the https support. > > > But I have a question about the servicemix-http component, the properties > > > like the role and the locationURI, how do they get passed to the > > > ServerManager? > > > > > > -----Ursprüngliche Nachricht----- > > > Von: Guillaume Nodet [mailto:[EMAIL PROTECTED] > > > Gesendet: Donnerstag, 30. März 2006 12:02 > > > An: [email protected] > > > Betreff: Re: https > > > > > > > > > > > > Well, https support should be added to the existing servicemix-http > > > component. > > > The org.apache.servicemix.http.ServerManager has a nice TODO to implement. > > > Feel free to raise a JIRA and submit patches (and ask questions if any > > > of course). > > > > > > Cheers, > > > Guillaume Nodet > > > > > > On 3/30/06, Gerdes, Mike <[EMAIL PROTECTED]> wrote: > > > > > > > > hi, > > > > > > > > is anybody working on a servicemix-https component? If not I will try > > > > to rewrite the servicemix-http component myself. > > > > > > > > cya > > > > > > > > mike > > > > > > > > This mail has originated outside your organization, either from an > > > > external partner or the Global Internet. Keep this in mind if you > > > > answer this message. > > > > > > > > > > > > > > > > This mail has originated outside your organization, > > > either from an external partner or the Global Internet. > > > Keep this in mind if you answer this message. > > > > > > This mail has originated outside your organization, either from an > > > external partner or the Global Internet. Keep this in mind if you answer > > > this message. > > > > > > > > > > > This mail has originated outside your organization, > > either from an external partner or the Global Internet. > > Keep this in mind if you answer this message. > > > > This mail has originated outside your organization, either from an external > > partner or the Global Internet. Keep this in mind if you answer this > > message. > > > > > > This mail has originated outside your organization, > either from an external partner or the Global Internet. > Keep this in mind if you answer this message. > > This mail has originated outside your organization, either from an external > partner or the Global Internet. Keep this in mind if you answer this message. >
