ebxmlms-develop — Development discussions

[ebxmlms-develop] Non-compliance found, and other changes requested

[Gait B. <gai...@ti...>]

Hi,

while doing some internal testing in preparation for the =
interoperability tests in Europe (within CEN), I found some issues with =
the MSH.
First issue is with the Service element, which, according to section =
3.1.4.1 of the ebMS 2 spec must be a URI unless a type attribute is =
present. AFAICT, the MSH does not check this.

Second is with multiple Errors: The API does not allow for adding =
multiple errors to an ebXML message. The only function to add an Error =
is the addErrorList function, which will add an ErrorList element with =
one Error. I suggest that the ebxmlMessage class is augmented with an =
addError function, which creates the ErrorList when needed. Alternative =
is to allow for the creation of an empty ErrorList, and open up the =
addError in the ErrorList class.

The third issue is related to DuplicateElimination.
I set up two Monitors talking to each other. One Monitor repeatedly =
sends a message with a fixed message id and time stamp, and duplicate =
elimination (DE) turned on. However, all messages are received by the =
other Monitor. After adding some additional logging to =
MessageServer.hasReceived, I found that the record for the corresponding =
message is never retrieved from the database. I also noticed that =
hasReceived queries against a set of application context parameters and =
the message id, which I believe to be wrong, at least for DE. For DE, =
checking should be done on the parameters passed in from the message, =
since we want to check for duplication of the message itself.
Did I miss something in the configuration that might break proper DE =
handling? Could it be that it does not work because I'm looping back on =
the same MSH, and the sending Monitor actually updates the DB in between =
calls?

thnx,
~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
Gait Boxman
Manager Advanced Technology & Standards
TIE Product Development BV
Amsterdam, The Netherlands
Tel: +31 20 658 9091  Fax: +31 20 658 9945
E-mail: gai...@ti...  WWW: www.TIEglobal.com
~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~

[ebxmlms-develop] MSH over SSL

[Wing K. C. <wk...@it...>]

SSBnb3QgYSBwcm9ibGVtIHdoZW4gSSB0cnkgdG8gc2V0IHVwIHR3byBNU0hzIHRvIHRhbGsgd2l0
aCBlYWNoIG90aGVyIG92ZXINClNTTC4NCg0KVGhlIG1lc3NhZ2UgZmxvdyBJIHdhbnQgdG8gdHJ5
IGlzOiBMb29wYmFja19saW51eCAtPiBNU0hfbGludXggLT4gU1NMIC0+DQpNU0hfcGMgLT4gTG9v
cGJhY2tfcGMNCg0KSSBkZXBsb3llZCBNU0ggdjA5MTQgdG8gYSBQQyBhbmQgYSBMaW51eCwgcnVu
bmluZyBvbiBUb21jYXQgNC4wLjQgd2hpY2ggYXJlDQpTU0wtZW5hYmxlZC4gSSBhbHNvIHBhdGNo
ZWQgeGFsYW4uamFyIHRvIHRoZSBlbmRvcnNlZCBkaXJlY3RvcnkuDQoNCkkgYWxzbyBpbXBvcnRl
ZCB0aGUgc2VydmVyIGNlcnQgaW50byB0aGUgamF2YSBrZXlzdG9yZXMgb2YgdGhlIG9wcG9zaXRl
DQptYWNoaW5lcywgZWcsDQpJbiBMaW51eCwga2V5dG9vbCChVmV4cG9ydCChVmZpbGUgWFhYIKFW
YWxpYXMgdG9tY2F0DQpJbiBQQywga2V5dG9vbCChVmltcG9ydCChVmZpbGUgWFhYIKFWYWxpYXMg
WVlZIKFWa2V5c3RvcmUNCiVKQVZBX0hPTUUvanJlL2xpYi9zZWN1cml0eS9jYWNlcnRzDQoNClR5
cGluZyBodHRwczovL3BjX2lwOjg0NDMvbXNoIGFuZCBodHRwczovL2xpbnV4X2hvc3RuYW1lOjg0
NDMvbXNoIGluDQpicm93c2VyIGdpdmVzIG5vcm1hbCByZXNwb25zZS4NCg0KUnVubmluZyBMb29w
YmFjayB0byBzZW5kIHRvIG9uZXNlbGYgc3VjY2VlZGVkIHRvby4gVGhhdCBpcywgdGhlcmUgd2Fz
IG5vDQpwcm9ibGVtIGZvciBMb29wYmFja19saW51eCB0byBzZW5kIG1lc3NhZ2UgdG8gaXRzZWxm
IHZpYQ0KaHR0cHM6Ly9saW51eF9ob3N0bmFtZTo4NDQzL21zaCBhbmQgZm9yIExvb3BiYWNrX3Bj
IHRvIHNlbmQgbWVzc2FnZSB0bw0KaXRzZWxmIHZpYSBodHRwczovL3BjX2lwOjg0NDMvbXNoDQoN
ClRoZSBwcm9ibGVtIGhhcHBlbmVkIHdoZW4gSSByYW4gTG9vcGJhY2tfbGludXggd2l0aCB0b01T
SFVybCA9DQpodHRwczovL3BjX2lwOjg0NDMvbXNoLCBhIFByaXZpbGVnZWRBY3Rpb25FeGNlcHRp
b24gd2FzIHRocm93biBhbmQgaXQNCmZhaWxlZCB0byBzZW5kIHRoZSBtZXNzYWdlLiBCZWxvd3Mg
YXJlIGV4dHJhY3RzIGZyb20gdGhlIExpbnV4IE1TSCBsb2cuIFRoZQ0Kc2FtZSBlcnJvciBoYXBw
ZW5lZCB3aGVuIEkgcmFuIExvb3BiYWNrX3BjIHdpdGggdG9NU0hVcmwgPQ0KaHR0cHM6Ly9saW51
eF9ob3N0bmFtZTo4NDQzL21zaC4NCg0KMjAwMi0xMi0xOSAxNzowMzo0NCwwMDAgREVCVUcgW0h0
dHBQcm9jZXNzb3JbODA4MF1bM11dOiBSZWNlaXZlZCByZXF1ZXN0DQpmb3Igc2VuZGluZyBtZXNz
YWdlDQoyMDAyLTEyLTE5IDE3OjAzOjQ2LDkxMCBERUJVRyBbSHR0cFByb2Nlc3Nvcls4MDgwXVsz
XV06IEZpbmFsIHNlcXVlbmNlDQpudW1iZXIgaW4gc3RvcmU6IC05OTk5DQoyMDAyLTEyLTE5IDE3
OjAzOjQ2LDkxMCBERUJVRyBbSHR0cFByb2Nlc3Nvcls4MDgwXVszXV06IEVudGVyaW5nDQpNZXNz
YWdlU2VydmVyLnN0b3JlDQoyMDAyLTEyLTE5IDE3OjAzOjQ2LDk2MCBERUJVRyBbSHR0cFByb2Nl
c3Nvcls4MDgwXVszXV06DQpnZXRSZXBvc2l0b3J5RmlsZU5hbWUgcmV0dXJuOiBSMDAwMFxlWVFO
b3pnRU5nSURtT0psUXIyV0RRPT0NCjIwMDItMTItMTkgMTc6MDM6NDcsMDIwIERFQlVHIFtIdHRw
UHJvY2Vzc29yWzgwODBdWzNdXTogSW5zZXJ0IGludG8NCm1lc3NhZ2VzdG9yZSBkYXRhYmFzZQ0K
MjAwMi0xMi0xOSAxNzowMzo0NywwMjAgREVCVUcgW1RocmVhZC0zXTogU2VuZC4uLiB0cnkgIzEN
CjIwMDItMTItMTkgMTc6MDM6NDcsMDIwIERFQlVHIFtUaHJlYWQtM106IEVudGVyaW5nIE1lc3Nh
Z2VTZXJ2ZXIucmV0cnkNCjIwMDItMTItMTkgMTc6MDM6NDcsMDcwIERFQlVHIFtUaHJlYWQtM106
IEN1cnJlbnQ6IDAgc3BlY2lmaWVkOiAxDQoyMDAyLTEyLTE5IDE3OjAzOjQ3LDA3MCBERUJVRyBb
VGhyZWFkLTNdOiBVcGRhdGUgc3RhdGUgdG8gYmVjb21lIDENCjIwMDItMTItMTkgMTc6MDM6NDgs
MjgwIERFQlVHIFtUaHJlYWQtM106DQpoay5oa3UuY2VjaWQucGhvZW5peC5tZXNzYWdlLmhhbmRs
ZXIuSHR0cFNlbmRlciBjYW5ub3Qgc2VuZCBtZXNzYWdlDQpzdWNjZXNzZnVsbHkgZm9yIDEgdGlt
ZXM6DQpoay5oa3UuY2VjaWQucGhvZW5peC5tZXNzYWdlLnRyYW5zcG9ydC5UcmFuc3BvcnRFeGNl
cHRpb246DQpqYXZhLnNlY3VyaXR5LlByaXZpbGVnZWRBY3Rpb25FeGNlcHRpb246IGphdmF4Lnht
bC5zb2FwLlNPQVBFeGNlcHRpb246DQpNZXNzYWdlIHNlbmQgZmFpbGVkDQoNCkRvZXMgYW55Ym9k
eSBrbm93IHdoYXQgaGFwcGVucz8gVGhhbmtzIGZvciBhbnkgYWR2aWNlLg0KDQpSZWdhcmRzLA0K
V0sNCg==

[ebxmlms-develop] Re: [ebxmlms-general] SourceCode Missing

[Jason v. Z. <ja...@ze...>]

On Thu, 2002-12-12 at 01:17, Patrick Yee wrote:
> Dear Ciju,
>  
> I am sorry that the classes you mentioned are those proprietary
> libraries provided by our center. So no source code is available in
> the public. However, we can give you more information about the
> classes if you have special need on the library. So, would you please
> tell us about your case and so that we can provide appropriate
> assistance?

Proprietary libraries used in an open source project? Will the sources
ever be released? Hermes is an open source project, yes?

> Thanks a lot.
>  
> Regards, -Patrick
> --
> Patrick Yee
> System Architect
> Center for E-Commerce Infrastructure Development (CECID)
> Dept. of Computer Science and Information Systems
> The University of Hong Kong
> Tel: (852) 22415674
> Fax: (852) 25474611
>  
>         ----- Original Message ----- 
>         From: Ciju Kurian
>         To: ebx...@li...
>         Cc: ebx...@li...
>         Sent: Thursday, December 12, 2002 1:27 PM
>         Subject: [ebxmlms-general] SourceCode Missing
>         
>         
>          
>         
>          
>         
>         Hi All,
>         
>          
>         
>         In the below mentioned import statements, I am not able to
>         locate the source code nor the documentation for
>         AuthenticationManager, Logger and Property classes in the
>         extracted hermes_ebms2_all_in_one_0920.zip file.
>         
>          
>         
>         Could any body tell me where to find the source code, or is
>         there any link to get these source codes.
>         
>          
>         
>         import hk.hku.cecid.phoenix.common.util.AuthenticationManager;
>         
>         import hk.hku.cecid.phoenix.common.util.Logger;
>         
>         import hk.hku.cecid.phoenix.common.util.Property;
>         
>          
>         
>         Thanks in advance,
>         
>          
>         
>         Regards,
>         
>         Ciju
-- 
jvz.

Jason van Zyl
ja...@ze...
http://tambora.zenplex.org

In short, man creates for himself a new religion of a rational
and technical order to justify his work and to be justified in it.
  
  -- Jacques Ellul, The Technological Society

[ebxmlms-develop] Re: [ebxmlms-general] SourceCode Missing

[Patrick Y. <kc...@ce...>]

Dear Ciju,

I am sorry that the classes you mentioned are those proprietary =
libraries provided by our center. So no source code is available in the =
public. However, we can give you more information about the classes if =
you have special need on the library. So, would you please tell us about =
your case and so that we can provide appropriate assistance?

Thanks a lot.

Regards, -Patrick
--
Patrick Yee
System Architect
Center for E-Commerce Infrastructure Development (CECID)
Dept. of Computer Science and Information Systems
The University of Hong Kong
Tel: (852) 22415674
Fax: (852) 25474611

  ----- Original Message -----=20
  From: Ciju Kurian=20
  To: ebx...@li...=20
  Cc: ebx...@li...=20
  Sent: Thursday, December 12, 2002 1:27 PM
  Subject: [ebxmlms-general] SourceCode Missing


  =20

  =20

  Hi All,

  =20

  In the below mentioned import statements, I am not able to locate the =
source code nor the documentation for 'AuthenticationManager', 'Logger' =
and 'Property' classes in the extracted hermes_ebms2_all_in_one_0920.zip =
file.

  =20

  Could any body tell me where to find the source code, or is there any =
link to get these source codes.

  =20

  import hk.hku.cecid.phoenix.common.util.AuthenticationManager;

  import hk.hku.cecid.phoenix.common.util.Logger;

  import hk.hku.cecid.phoenix.common.util.Property;

  =20

  Thanks in advance,

  =20

  Regards,

  Ciju

[ebxmlms-develop] SourceCode Missing

[Ciju K. <cij...@ua...>]

 
 
Hi All,
 
In the below mentioned import statements, I am not able to locate the
source code nor the documentation for 'AuthenticationManager', 'Logger'
and 'Property' classes in the extracted hermes_ebms2_all_in_one_0920.zip
file.
 
Could any body tell me where to find the source code, or is there any
link to get these source codes.
 
import hk.hku.cecid.phoenix.common.util.AuthenticationManager;
import hk.hku.cecid.phoenix.common.util.Logger;
import hk.hku.cecid.phoenix.common.util.Property;
 
Thanks in advance,
 
Regards,
Ciju

[ebxmlms-develop] test

[Jason v. Z. <ja...@ze...>]

-- 
jvz.

Jason van Zyl
ja...@ze...
http://tambora.zenplex.org

In short, man creates for himself a new religion of a rational
and technical order to justify his work and to be justified in it.
  
  -- Jacques Ellul, The Technological Society

Re: [ebxmlms-develop] URL and File base document receipt

[Frankie L. <fr...@mi...>]

Dear Anthony,

It's great to drill in the source code =3D). The code that I am =
referring to is the current version in CVS source tree (pre-0.9.2.0).

The subtlety of message delivery lies on the fact that the message =
listener that an application register with the Request object is never =
called directly by MSH. For the message polling approach, the message =
listener of the client application is called by the Request object if it =
receives any new message from MSH. If the application is using trusted =
repository, although the message listener seems to be unchanged as =
stated in the following block, the MSH actually has no implementation of =
the client message listener, and it results in a ClassNotFoundException =
error. Therefore, in the trusted repository approach, the only correct =
way is to use the =
hk.hku.cecid.phoenix.message.handler.MessageListenerImpl.

if (this is a file protocol && client url returning a path that is _not_ =
in
trusted repository) {
    ... =20
}
else {
>>>>    - use this clientURL to do registration directly
}

Hope this helps.

--
Frankie Lam
Assistant Technology Officer
Center for E-Commerce Infrastructure Development (CECID)
Dept. of Computer Science and Information Systems
The University of Hong Kong
Tel: (852) 22415737
Fax: (852) 25474611
  ----- Original Message -----=20
  From: ant...@re...=20
  To: 'Frankie Lam'=20
  Cc: ebx...@li...=20
  Sent: Friday, October 25, 2002 7:22 AM
  Subject: RE: [ebxmlms-develop] URL and File base document receipt


  Sorry to keep drilling at this but...

  What version of the code are you looking at? From the downloaded 914 =
version
  the deliverToApplication() in MessageServiceHandler
  has only the following code

      private synchronized void deliverToApplication(ApplicationContext
          appContext, EbxmlMessage ebxmlMessage)
          throws MessageServiceHandlerConnectionException {
          final MessageServiceHandlerConnection mshConnection =3D
              (MessageServiceHandlerConnection) mshConnectionTable.
              get(appContext);

          if (mshConnection =3D=3D null) {
              final String errorMessage =3D "Unknown application =
context: "
                  + appContext.toString() ;
              throw new =
MessageServiceHandlerConnectionException(errorMessage);
          }
          final MessageListener messageListener =3D mshConnection.
              getMessageServiceHandlerConfig().getMessageListener();
          messageListener.onMessage(ebxmlMessage);
      }

  it doesn't have any isDelivered checks as you described below.
  which basically means that the only thing that deliverToApplication =
does is call the onMessage of the message listener, I can't see the code =
that you have provided anywhere? Is there a new version since 914, 913 =
has the same code that I described above.

    -----Original Message-----
    From: ebx...@li... =
[mailto:ebx...@li...]On Behalf Of Frankie =
Lam
    Sent: Thursday, October 24, 2002 7:48 PM
    To: ant...@re...
    Cc: ebx...@li...
    Subject: Re: [ebxmlms-develop] URL and File base document receipt


    Hi Anthony,

    The skeleton of the code in register() is like this:

    if (this is a file protocol && client url returning a path that is =
_not_ in
    trusted repository) {
        - get message listener repository from the properties file
        if (appcontext supplied has not been registered) {
            - use our directory to store messages
        }
        else {
            - use directory name of previously registered connection =
object
        }
        - use our default MessageListenerImpl with the directory name =
returned
    above
        - register using this MessageListenerImpl and application =
contexts
    supplied by user
    }
    else {
        // this is either a URL that is using file protocol and =
returning a
    trusted repository,
        // or http URL etc.
        - use this clientURL to do registration directly
    }

    Then in method deliverToApplication():

            final boolean isDelivered =3D ((clientUrl !=3D null && =
clientUrl.
                getProtocol().equals(MessageListener.PROTOCOL_FILE) &&
                trustedListenerRepository.contains(clientUrl.getPath()) =
=3D=3D
    false) ?
                false : true);
            if (stored) {
                ...
            }
            else if (!isDelivered) {
                =
messageServer.setDeliveryStatus(ebxmlMessage.getMessageId(),
    false);
            }

    That means

        isDelivered =3D (there is a client URL, based on the file =
protocol, and it
    is in trustedRepository).

    So we can divide it into three cases:
    1)  File URL + using trustedRepository
    2)  File URL + not using trustedRepository
    3)  URL based on other protocols

    For case (1), isDelivered =3D true. Thus the message is marked as =
"delivered"
    in the database and cannot be polled by the application through =
Request
    object. This means that the client actually needs to monitor =
consistently
    the trusted repository for any new messages.

    For case (2), isDelivered =3D false. The client can poll the MSH for =
new
    messages through the request object.

    For case (3), the application should not poll for new messages =
through the
    request object, since the messages are delivered directly to the =
specified
    URL.

    Note that the onMessage() method of the client application is called =
by
    Request object only, so onMessage() would not be invoked for case =
(1) and
    (3).

    --
    Frankie Lam
    Assistant Technology Officer
    Center for E-Commerce Infrastructure Development (CECID)
    Dept. of Computer Science and Information Systems
    The University of Hong Kong
    Tel: (852) 22415737
    Fax: (852) 25474611

    ----- Original Message -----
    From: <ant...@re...>
    To: <ebx...@li...>
    Sent: Thursday, October 24, 2002 4:36 PM
    Subject: RE: [ebxmlms-develop] URL and File base document receipt


    > Hi all,
    >
    > Just an update that may interest some,
    > I was still having trouble with this issue (of getting LoopBack to =
write
    to
    > the dir I wanted) and so jumped into the code a little - but I =
think I
    > resolved it - either that or I have messed things up terribly.
    >
    > If getClientUrl() is set to return a file dir url in LoopBack.java
    > (rather than returning null) the submitted file should get written =
to the
    > directory supplied (according to the doco) but I still wasn't =
getting the
    > file written to the dir I wanted it to (even after setting the =
trusted
    > repository property).
    >
    > The code in MessageServiceHandler.register( )
    > states...
    >         if =
(clientUrl.getProtocol().equals(MessageListener.PROTOCOL_FILE)
    &&
    >             =
trustedListenerRepository.contains(clientUrl.getPath()) =3D=3D
    > false)
    > {
    > blah blah blah
    > set up MessageListenerImpl with the clientUrl you have set
    > }
    >
    > Shouldn't the comparison be checking on 'true'
    >         if =
(clientUrl.getProtocol().equals(MessageListener.PROTOCOL_FILE)
    &&
    >             =
trustedListenerRepository.contains(clientUrl.getPath()) =3D=3D
    true)
    >
    > When I changed this to be =3D=3D true
    > I was able to get the file written to the directory that I =
specified.
    >
    > If this wasn't the case, the MessageListener would always call
    > LoopBack.onMessage() rather than calling the
    > MessageListenerImpl.onMessage() - which is the one that will write =
to the
    > file directory.
    > If you don't do this then you have to have the file writing code =
in your
    own
    > onMessage() method, which defeats the purpose of having the =
getClientUrl()
    >
    > If I am totally out of whack here let me know, just an =
observation.....
    >
    >
    > Ants
    >
    > PS. If what I have said is true - then there should be code in the
    > register() method to do the same thing for HTTP protocol as well =
as file
    > protocol as you can't submit to a HTTP port.
    >
    >
    >
    > -----Original Message-----
    > From: ebx...@li...
    > [mailto:ebx...@li...]On Behalf Of =
Gait
    > Boxman
    > Sent: Tuesday, October 22, 2002 6:29 PM
    > To: ant...@re...
    > Cc: ebx...@li...
    > Subject: Re: [ebxmlms-develop] URL and File base document receipt
    >
    >
    > Hi Anthony,
    >
    > the folder you specify needs to be listed as a trusted repository, =
which
    is
    > defined in the msh.properties.xml file at
    > MSH/MessageListener/TrustedRepository.
    > For starters, you could change the location to
    > file://C:/tmp/ebxmlms/trustedRepository1 to see if it's working =
ok. Be
    sure
    > to create the folder.
    >
    > Gait.
    > ----- Original Message -----
    > From: <ant...@re...>
    > To: <ebx...@li...>
    > Sent: Tuesday, October 22, 2002 8:16 AM
    > Subject: [ebxmlms-develop] URL and File base document receipt
    >
    >
    > > I'm having a bit of trouble understanding how the URL and file =
based doc
    > > receipt works.
    > >
    > > The documentation states that for MSH to post the received =
document to a
    > URL
    > > or file system, instead of using the onMessage function
    > > to provide a URL in the getClientUrl function.
    > >
    > > Using the LoopBack Class as an example, if I return a Url such =
as
    > > "file://C:/tmp" in the getClientUrl function, should the message =
that
    the
    > > loopback class has sent to itself be written to the directory =
that I
    > > specified. I have tried this and it seems that this is not the =
case. It
    > > still calls the onMessage function and there are no files =
written to the
    > > directory I specified.
    > >
    > > Any info is appreciated,
    > >
    > > Thanks
    > >
    > > Anthony Ellis
    > >
    > >
    > >
    > > -------------------------------------------------------
    > > This sf.net emial is sponsored by: Influence the future of
    > > Java(TM) technology. Join the Java Community Process(SM) =
(JCP(SM))
    > > program now. http://ad.doubleclick.net/clk;4699841;7576301;v?
    > > http://www.sun.com/javavote
    > > _______________________________________________
    > > ebxmlms-develop mailing list
    > > ebx...@li...
    > > https://lists.sourceforge.net/lists/listinfo/ebxmlms-develop
    >
    >
    >
    > -------------------------------------------------------
    > This sf.net emial is sponsored by: Influence the future of
    > Java(TM) technology. Join the Java Community Process(SM) (JCP(SM))
    > program now. http://ad.doubleclick.net/clk;4699841;7576301;v?
    > http://www.sun.com/javavote
    > _______________________________________________
    > ebxmlms-develop mailing list
    > ebx...@li...
    > https://lists.sourceforge.net/lists/listinfo/ebxmlms-develop
    >
    >
    >
    > -------------------------------------------------------
    > This sf.net email is sponsored by: Influence the future
    > of Java(TM) technology. Join the Java Community
    > Process(SM) (JCP(SM)) program now.
    >
    =
http://ad.doubleclick.net/clk;4729346;7592162;s?http://www.sun.com/javavo=
te
    > _______________________________________________
    > ebxmlms-develop mailing list
    > ebx...@li...
    > https://lists.sourceforge.net/lists/listinfo/ebxmlms-develop
    >

RE: [ebxmlms-develop] URL and File base document receipt

[<ant...@re...>]

Sorry to keep drilling at this but...

What version of the code are you looking at? From the downloaded 914 version
the deliverToApplication() in MessageServiceHandler
has only the following code

    private synchronized void deliverToApplication(ApplicationContext
        appContext, EbxmlMessage ebxmlMessage)
        throws MessageServiceHandlerConnectionException {
        final MessageServiceHandlerConnection mshConnection =
            (MessageServiceHandlerConnection) mshConnectionTable.
            get(appContext);

        if (mshConnection == null) {
            final String errorMessage = "Unknown application context: "
                + appContext.toString() ;
            throw new
MessageServiceHandlerConnectionException(errorMessage);
        }
        final MessageListener messageListener = mshConnection.
            getMessageServiceHandlerConfig().getMessageListener();
        messageListener.onMessage(ebxmlMessage);
    }

it doesn't have any isDelivered checks as you described below.
which basically means that the only thing that deliverToApplication does is
call the onMessage of the message listener, I can't see the code that you
have provided anywhere? Is there a new version since 914, 913 has the same
code that I described above.

  -----Original Message-----
  From: ebx...@li...
[mailto:ebx...@li...]On Behalf Of Frankie Lam
  Sent: Thursday, October 24, 2002 7:48 PM
  To: ant...@re...
  Cc: ebx...@li...
  Subject: Re: [ebxmlms-develop] URL and File base document receipt


  Hi Anthony,

  The skeleton of the code in register() is like this:

  if (this is a file protocol && client url returning a path that is _not_
in
  trusted repository) {
      - get message listener repository from the properties file
      if (appcontext supplied has not been registered) {
          - use our directory to store messages
      }
      else {
          - use directory name of previously registered connection object
      }
      - use our default MessageListenerImpl with the directory name returned
  above
      - register using this MessageListenerImpl and application contexts
  supplied by user
  }
  else {
      // this is either a URL that is using file protocol and returning a
  trusted repository,
      // or http URL etc.
      - use this clientURL to do registration directly
  }

  Then in method deliverToApplication():

          final boolean isDelivered = ((clientUrl != null && clientUrl.
              getProtocol().equals(MessageListener.PROTOCOL_FILE) &&
              trustedListenerRepository.contains(clientUrl.getPath()) ==
  false) ?
              false : true);
          if (stored) {
              ...
          }
          else if (!isDelivered) {
              messageServer.setDeliveryStatus(ebxmlMessage.getMessageId(),
  false);
          }

  That means

      isDelivered = (there is a client URL, based on the file protocol, and
it
  is in trustedRepository).

  So we can divide it into three cases:
  1)  File URL + using trustedRepository
  2)  File URL + not using trustedRepository
  3)  URL based on other protocols

  For case (1), isDelivered = true. Thus the message is marked as
"delivered"
  in the database and cannot be polled by the application through Request
  object. This means that the client actually needs to monitor consistently
  the trusted repository for any new messages.

  For case (2), isDelivered = false. The client can poll the MSH for new
  messages through the request object.

  For case (3), the application should not poll for new messages through the
  request object, since the messages are delivered directly to the specified
  URL.

  Note that the onMessage() method of the client application is called by
  Request object only, so onMessage() would not be invoked for case (1) and
  (3).

  --
  Frankie Lam
  Assistant Technology Officer
  Center for E-Commerce Infrastructure Development (CECID)
  Dept. of Computer Science and Information Systems
  The University of Hong Kong
  Tel: (852) 22415737
  Fax: (852) 25474611

  ----- Original Message -----
  From: <ant...@re...>
  To: <ebx...@li...>
  Sent: Thursday, October 24, 2002 4:36 PM
  Subject: RE: [ebxmlms-develop] URL and File base document receipt


  > Hi all,
  >
  > Just an update that may interest some,
  > I was still having trouble with this issue (of getting LoopBack to write
  to
  > the dir I wanted) and so jumped into the code a little - but I think I
  > resolved it - either that or I have messed things up terribly.
  >
  > If getClientUrl() is set to return a file dir url in LoopBack.java
  > (rather than returning null) the submitted file should get written to
the
  > directory supplied (according to the doco) but I still wasn't getting
the
  > file written to the dir I wanted it to (even after setting the trusted
  > repository property).
  >
  > The code in MessageServiceHandler.register( )
  > states...
  >         if
(clientUrl.getProtocol().equals(MessageListener.PROTOCOL_FILE)
  &&
  >             trustedListenerRepository.contains(clientUrl.getPath()) ==
  > false)
  > {
  > blah blah blah
  > set up MessageListenerImpl with the clientUrl you have set
  > }
  >
  > Shouldn't the comparison be checking on 'true'
  >         if
(clientUrl.getProtocol().equals(MessageListener.PROTOCOL_FILE)
  &&
  >             trustedListenerRepository.contains(clientUrl.getPath()) ==
  true)
  >
  > When I changed this to be == true
  > I was able to get the file written to the directory that I specified.
  >
  > If this wasn't the case, the MessageListener would always call
  > LoopBack.onMessage() rather than calling the
  > MessageListenerImpl.onMessage() - which is the one that will write to
the
  > file directory.
  > If you don't do this then you have to have the file writing code in your
  own
  > onMessage() method, which defeats the purpose of having the
getClientUrl()
  >
  > If I am totally out of whack here let me know, just an observation.....
  >
  >
  > Ants
  >
  > PS. If what I have said is true - then there should be code in the
  > register() method to do the same thing for HTTP protocol as well as file
  > protocol as you can't submit to a HTTP port.
  >
  >
  >
  > -----Original Message-----
  > From: ebx...@li...
  > [mailto:ebx...@li...]On Behalf Of Gait
  > Boxman
  > Sent: Tuesday, October 22, 2002 6:29 PM
  > To: ant...@re...
  > Cc: ebx...@li...
  > Subject: Re: [ebxmlms-develop] URL and File base document receipt
  >
  >
  > Hi Anthony,
  >
  > the folder you specify needs to be listed as a trusted repository, which
  is
  > defined in the msh.properties.xml file at
  > MSH/MessageListener/TrustedRepository.
  > For starters, you could change the location to
  > file://C:/tmp/ebxmlms/trustedRepository1 to see if it's working ok. Be
  sure
  > to create the folder.
  >
  > Gait.
  > ----- Original Message -----
  > From: <ant...@re...>
  > To: <ebx...@li...>
  > Sent: Tuesday, October 22, 2002 8:16 AM
  > Subject: [ebxmlms-develop] URL and File base document receipt
  >
  >
  > > I'm having a bit of trouble understanding how the URL and file based
doc
  > > receipt works.
  > >
  > > The documentation states that for MSH to post the received document to
a
  > URL
  > > or file system, instead of using the onMessage function
  > > to provide a URL in the getClientUrl function.
  > >
  > > Using the LoopBack Class as an example, if I return a Url such as
  > > "file://C:/tmp" in the getClientUrl function, should the message that
  the
  > > loopback class has sent to itself be written to the directory that I
  > > specified. I have tried this and it seems that this is not the case.
It
  > > still calls the onMessage function and there are no files written to
the
  > > directory I specified.
  > >
  > > Any info is appreciated,
  > >
  > > Thanks
  > >
  > > Anthony Ellis
  > >
  > >
  > >
  > > -------------------------------------------------------
  > > This sf.net emial is sponsored by: Influence the future of
  > > Java(TM) technology. Join the Java Community Process(SM) (JCP(SM))
  > > program now. http://ad.doubleclick.net/clk;4699841;7576301;v?
  > > http://www.sun.com/javavote
  > > _______________________________________________
  > > ebxmlms-develop mailing list
  > > ebx...@li...
  > > https://lists.sourceforge.net/lists/listinfo/ebxmlms-develop
  >
  >
  >
  > -------------------------------------------------------
  > This sf.net emial is sponsored by: Influence the future of
  > Java(TM) technology. Join the Java Community Process(SM) (JCP(SM))
  > program now. http://ad.doubleclick.net/clk;4699841;7576301;v?
  > http://www.sun.com/javavote
  > _______________________________________________
  > ebxmlms-develop mailing list
  > ebx...@li...
  > https://lists.sourceforge.net/lists/listinfo/ebxmlms-develop
  >
  >
  >
  > -------------------------------------------------------
  > This sf.net email is sponsored by: Influence the future
  > of Java(TM) technology. Join the Java Community
  > Process(SM) (JCP(SM)) program now.
  >

http://ad.doubleclick.net/clk;4729346;7592162;s?http://www.sun.com/javavote
  > _______________________________________________
  > ebxmlms-develop mailing list
  > ebx...@li...
  > https://lists.sourceforge.net/lists/listinfo/ebxmlms-develop
  >

Re: [ebxmlms-develop] URL and File base document receipt

[Frankie L. <fr...@mi...>]

Hi Anthony,

The skeleton of the code in register() is like this:

if (this is a file protocol && client url returning a path that is _not_ =
in
trusted repository) {
    - get message listener repository from the properties file
    if (appcontext supplied has not been registered) {
        - use our directory to store messages
    }
    else {
        - use directory name of previously registered connection object
    }
    - use our default MessageListenerImpl with the directory name =
returned
above
    - register using this MessageListenerImpl and application contexts
supplied by user
}
else {
    // this is either a URL that is using file protocol and returning a
trusted repository,
    // or http URL etc.
    - use this clientURL to do registration directly
}

Then in method deliverToApplication():

        final boolean isDelivered =3D ((clientUrl !=3D null && =
clientUrl.
            getProtocol().equals(MessageListener.PROTOCOL_FILE) &&
            trustedListenerRepository.contains(clientUrl.getPath()) =
=3D=3D
false) ?
            false : true);
        if (stored) {
            ...
        }
        else if (!isDelivered) {
            messageServer.setDeliveryStatus(ebxmlMessage.getMessageId(),
false);
        }

That means

    isDelivered =3D (there is a client URL, based on the file protocol, =
and it
is in trustedRepository).

So we can divide it into three cases:
1)  File URL + using trustedRepository
2)  File URL + not using trustedRepository
3)  URL based on other protocols

For case (1), isDelivered =3D true. Thus the message is marked as =
"delivered"
in the database and cannot be polled by the application through Request
object. This means that the client actually needs to monitor =
consistently
the trusted repository for any new messages.

For case (2), isDelivered =3D false. The client can poll the MSH for new
messages through the request object.

For case (3), the application should not poll for new messages through =
the
request object, since the messages are delivered directly to the =
specified
URL.

Note that the onMessage() method of the client application is called by
Request object only, so onMessage() would not be invoked for case (1) =
and
(3).

--
Frankie Lam
Assistant Technology Officer
Center for E-Commerce Infrastructure Development (CECID)
Dept. of Computer Science and Information Systems
The University of Hong Kong
Tel: (852) 22415737
Fax: (852) 25474611

----- Original Message -----
From: <ant...@re...>
To: <ebx...@li...>
Sent: Thursday, October 24, 2002 4:36 PM
Subject: RE: [ebxmlms-develop] URL and File base document receipt


> Hi all,
>
> Just an update that may interest some,
> I was still having trouble with this issue (of getting LoopBack to =
write
to
> the dir I wanted) and so jumped into the code a little - but I think I
> resolved it - either that or I have messed things up terribly.
>
> If getClientUrl() is set to return a file dir url in LoopBack.java
> (rather than returning null) the submitted file should get written to =
the
> directory supplied (according to the doco) but I still wasn't getting =
the
> file written to the dir I wanted it to (even after setting the trusted
> repository property).
>
> The code in MessageServiceHandler.register( )
> states...
>         if =
(clientUrl.getProtocol().equals(MessageListener.PROTOCOL_FILE)
&&
>             trustedListenerRepository.contains(clientUrl.getPath()) =
=3D=3D
> false)
> {
> blah blah blah
> set up MessageListenerImpl with the clientUrl you have set
> }
>
> Shouldn't the comparison be checking on 'true'
>         if =
(clientUrl.getProtocol().equals(MessageListener.PROTOCOL_FILE)
&&
>             trustedListenerRepository.contains(clientUrl.getPath()) =
=3D=3D
true)
>
> When I changed this to be =3D=3D true
> I was able to get the file written to the directory that I specified.
>
> If this wasn't the case, the MessageListener would always call
> LoopBack.onMessage() rather than calling the
> MessageListenerImpl.onMessage() - which is the one that will write to =
the
> file directory.
> If you don't do this then you have to have the file writing code in =
your
own
> onMessage() method, which defeats the purpose of having the =
getClientUrl()
>
> If I am totally out of whack here let me know, just an =
observation.....
>
>
> Ants
>
> PS. If what I have said is true - then there should be code in the
> register() method to do the same thing for HTTP protocol as well as =
file
> protocol as you can't submit to a HTTP port.
>
>
>
> -----Original Message-----
> From: ebx...@li...
> [mailto:ebx...@li...]On Behalf Of Gait
> Boxman
> Sent: Tuesday, October 22, 2002 6:29 PM
> To: ant...@re...
> Cc: ebx...@li...
> Subject: Re: [ebxmlms-develop] URL and File base document receipt
>
>
> Hi Anthony,
>
> the folder you specify needs to be listed as a trusted repository, =
which
is
> defined in the msh.properties.xml file at
> MSH/MessageListener/TrustedRepository.
> For starters, you could change the location to
> file://C:/tmp/ebxmlms/trustedRepository1 to see if it's working ok. Be
sure
> to create the folder.
>
> Gait.
> ----- Original Message -----
> From: <ant...@re...>
> To: <ebx...@li...>
> Sent: Tuesday, October 22, 2002 8:16 AM
> Subject: [ebxmlms-develop] URL and File base document receipt
>
>
> > I'm having a bit of trouble understanding how the URL and file based =
doc
> > receipt works.
> >
> > The documentation states that for MSH to post the received document =
to a
> URL
> > or file system, instead of using the onMessage function
> > to provide a URL in the getClientUrl function.
> >
> > Using the LoopBack Class as an example, if I return a Url such as
> > "file://C:/tmp" in the getClientUrl function, should the message =
that
the
> > loopback class has sent to itself be written to the directory that I
> > specified. I have tried this and it seems that this is not the case. =
It
> > still calls the onMessage function and there are no files written to =
the
> > directory I specified.
> >
> > Any info is appreciated,
> >
> > Thanks
> >
> > Anthony Ellis
> >
> >
> >
> > -------------------------------------------------------
> > This sf.net emial is sponsored by: Influence the future of
> > Java(TM) technology. Join the Java Community Process(SM) (JCP(SM))
> > program now. http://ad.doubleclick.net/clk;4699841;7576301;v?
> > http://www.sun.com/javavote
> > _______________________________________________
> > ebxmlms-develop mailing list
> > ebx...@li...
> > https://lists.sourceforge.net/lists/listinfo/ebxmlms-develop
>
>
>
> -------------------------------------------------------
> This sf.net emial is sponsored by: Influence the future of
> Java(TM) technology. Join the Java Community Process(SM) (JCP(SM))
> program now. http://ad.doubleclick.net/clk;4699841;7576301;v?
> http://www.sun.com/javavote
> _______________________________________________
> ebxmlms-develop mailing list
> ebx...@li...
> https://lists.sourceforge.net/lists/listinfo/ebxmlms-develop
>
>
>
> -------------------------------------------------------
> This sf.net email is sponsored by: Influence the future
> of Java(TM) technology. Join the Java Community
> Process(SM) (JCP(SM)) program now.
>
http://ad.doubleclick.net/clk;4729346;7592162;s?http://www.sun.com/javavo=
te
> _______________________________________________
> ebxmlms-develop mailing list
> ebx...@li...
> https://lists.sourceforge.net/lists/listinfo/ebxmlms-develop
>

Re: [ebxmlms-develop] URL and File base document receipt

[Frankie L. <fr...@mi...>]

Hi Anthony,

The skeleton of the code in register() is like this:

if (this is a file protocol && client url returning a path that is _not_ in
trusted repository) {
    - get message listener repository from the properties file
    if (appcontext supplied has not been registered) {
        - use our directory to store messages
    }
    else {
        - use directory name of previously registered connection object
    }
    - use our default MessageListenerImpl with the directory name returned
above
    - register using this MessageListenerImpl and application contexts
supplied by user
}
else {
    // this is either a URL that is using file protocol and returning a
trusted repository,
    // or http URL etc.
    - use this clientURL to do registration directly
}

Then in method deliverToApplication():

        final boolean isDelivered = ((clientUrl != null && clientUrl.
            getProtocol().equals(MessageListener.PROTOCOL_FILE) &&
            trustedListenerRepository.contains(clientUrl.getPath()) ==
false) ?
            false : true);
        if (stored) {
            ...
        }
        else if (!isDelivered) {
            messageServer.setDeliveryStatus(ebxmlMessage.getMessageId(),
false);
        }

That means

    isDelivered = (there is a client URL, based on the file protocol, and it
is in trustedRepository).

So we can divide it into three cases:
1)  File URL + using trustedRepository
2)  File URL + not using trustedRepository
3)  URL based on other protocols

For case (1), isDelivered = true. Thus the message is marked as "delivered"
in the database and cannot be polled by the application through Request
object. This means that the client actually needs to monitor consistently
the trusted repository for any new messages.

For case (2), isDelivered = false. The client can poll the MSH for new
messages through the request object.

For case (3), the application should not poll for new messages through the
request object, since the messages are delivered directly to the specified
URL.

Note that the onMessage() method of the client application is called by
Request object only, so onMessage() would not be invoked for case (1) and
(3).

--
Frankie Lam
Assistant Technology Officer
Center for E-Commerce Infrastructure Development (CECID)
Dept. of Computer Science and Information Systems
The University of Hong Kong
Tel: (852) 22415737
Fax: (852) 25474611

----- Original Message -----
From: <ant...@re...>
To: <ebx...@li...>
Sent: Thursday, October 24, 2002 4:36 PM
Subject: RE: [ebxmlms-develop] URL and File base document receipt


> Hi all,
>
> Just an update that may interest some,
> I was still having trouble with this issue (of getting LoopBack to write
to
> the dir I wanted) and so jumped into the code a little - but I think I
> resolved it - either that or I have messed things up terribly.
>
> If getClientUrl() is set to return a file dir url in LoopBack.java
> (rather than returning null) the submitted file should get written to the
> directory supplied (according to the doco) but I still wasn't getting the
> file written to the dir I wanted it to (even after setting the trusted
> repository property).
>
> The code in MessageServiceHandler.register( )
> states...
>         if (clientUrl.getProtocol().equals(MessageListener.PROTOCOL_FILE)
&&
>             trustedListenerRepository.contains(clientUrl.getPath()) ==
> false)
> {
> blah blah blah
> set up MessageListenerImpl with the clientUrl you have set
> }
>
> Shouldn't the comparison be checking on 'true'
>         if (clientUrl.getProtocol().equals(MessageListener.PROTOCOL_FILE)
&&
>             trustedListenerRepository.contains(clientUrl.getPath()) ==
true)
>
> When I changed this to be == true
> I was able to get the file written to the directory that I specified.
>
> If this wasn't the case, the MessageListener would always call
> LoopBack.onMessage() rather than calling the
> MessageListenerImpl.onMessage() - which is the one that will write to the
> file directory.
> If you don't do this then you have to have the file writing code in your
own
> onMessage() method, which defeats the purpose of having the getClientUrl()
>
> If I am totally out of whack here let me know, just an observation.....
>
>
> Ants
>
> PS. If what I have said is true - then there should be code in the
> register() method to do the same thing for HTTP protocol as well as file
> protocol as you can't submit to a HTTP port.
>
>
>
> -----Original Message-----
> From: ebx...@li...
> [mailto:ebx...@li...]On Behalf Of Gait
> Boxman
> Sent: Tuesday, October 22, 2002 6:29 PM
> To: ant...@re...
> Cc: ebx...@li...
> Subject: Re: [ebxmlms-develop] URL and File base document receipt
>
>
> Hi Anthony,
>
> the folder you specify needs to be listed as a trusted repository, which
is
> defined in the msh.properties.xml file at
> MSH/MessageListener/TrustedRepository.
> For starters, you could change the location to
> file://C:/tmp/ebxmlms/trustedRepository1 to see if it's working ok. Be
sure
> to create the folder.
>
> Gait.
> ----- Original Message -----
> From: <ant...@re...>
> To: <ebx...@li...>
> Sent: Tuesday, October 22, 2002 8:16 AM
> Subject: [ebxmlms-develop] URL and File base document receipt
>
>
> > I'm having a bit of trouble understanding how the URL and file based doc
> > receipt works.
> >
> > The documentation states that for MSH to post the received document to a
> URL
> > or file system, instead of using the onMessage function
> > to provide a URL in the getClientUrl function.
> >
> > Using the LoopBack Class as an example, if I return a Url such as
> > "file://C:/tmp" in the getClientUrl function, should the message that
the
> > loopback class has sent to itself be written to the directory that I
> > specified. I have tried this and it seems that this is not the case. It
> > still calls the onMessage function and there are no files written to the
> > directory I specified.
> >
> > Any info is appreciated,
> >
> > Thanks
> >
> > Anthony Ellis
> >
> >
> >
> > -------------------------------------------------------
> > This sf.net emial is sponsored by: Influence the future of
> > Java(TM) technology. Join the Java Community Process(SM) (JCP(SM))
> > program now. http://ad.doubleclick.net/clk;4699841;7576301;v?
> > http://www.sun.com/javavote
> > _______________________________________________
> > ebxmlms-develop mailing list
> > ebx...@li...
> > https://lists.sourceforge.net/lists/listinfo/ebxmlms-develop
>
>
>
> -------------------------------------------------------
> This sf.net emial is sponsored by: Influence the future of
> Java(TM) technology. Join the Java Community Process(SM) (JCP(SM))
> program now. http://ad.doubleclick.net/clk;4699841;7576301;v?
> http://www.sun.com/javavote
> _______________________________________________
> ebxmlms-develop mailing list
> ebx...@li...
> https://lists.sourceforge.net/lists/listinfo/ebxmlms-develop
>
>
>
> -------------------------------------------------------
> This sf.net email is sponsored by: Influence the future
> of Java(TM) technology. Join the Java Community
> Process(SM) (JCP(SM)) program now.
>
http://ad.doubleclick.net/clk;4729346;7592162;s?http://www.sun.com/javavote
> _______________________________________________
> ebxmlms-develop mailing list
> ebx...@li...
> https://lists.sourceforge.net/lists/listinfo/ebxmlms-develop
>

RE: [ebxmlms-develop] URL and File base document receipt

[<ant...@re...>]

Hi all,

Just an update that may interest some,
I was still having trouble with this issue (of getting LoopBack to write to
the dir I wanted) and so jumped into the code a little - but I think I
resolved it - either that or I have messed things up terribly.

If getClientUrl() is set to return a file dir url in LoopBack.java
(rather than returning null) the submitted file should get written to the
directory supplied (according to the doco) but I still wasn't getting the
file written to the dir I wanted it to (even after setting the trusted
repository property).

The code in MessageServiceHandler.register( )
states...
        if (clientUrl.getProtocol().equals(MessageListener.PROTOCOL_FILE) &&
            trustedListenerRepository.contains(clientUrl.getPath()) ==
false)
		{
			blah blah blah
			set up MessageListenerImpl with the clientUrl you have set
		}

Shouldn't the comparison be checking on 'true'
        if (clientUrl.getProtocol().equals(MessageListener.PROTOCOL_FILE) &&
            trustedListenerRepository.contains(clientUrl.getPath()) == true)

When I changed this to be == true
I was able to get the file written to the directory that I specified.

If this wasn't the case, the MessageListener would always call
LoopBack.onMessage() rather than calling the
MessageListenerImpl.onMessage() - which is the one that will write to the
file directory.
If you don't do this then you have to have the file writing code in your own
onMessage() method, which defeats the purpose of having the getClientUrl()

If I am totally out of whack here let me know, just an observation.....


Ants

PS. If what I have said is true - then there should be code in the
register() method to do the same thing for HTTP protocol as well as file
protocol as you can't submit to a HTTP port.



-----Original Message-----
From: ebx...@li...
[mailto:ebx...@li...]On Behalf Of Gait
Boxman
Sent: Tuesday, October 22, 2002 6:29 PM
To: ant...@re...
Cc: ebx...@li...
Subject: Re: [ebxmlms-develop] URL and File base document receipt


Hi Anthony,

the folder you specify needs to be listed as a trusted repository, which is
defined in the msh.properties.xml file at
MSH/MessageListener/TrustedRepository.
For starters, you could change the location to
file://C:/tmp/ebxmlms/trustedRepository1 to see if it's working ok. Be sure
to create the folder.

Gait.
----- Original Message -----
From: <ant...@re...>
To: <ebx...@li...>
Sent: Tuesday, October 22, 2002 8:16 AM
Subject: [ebxmlms-develop] URL and File base document receipt


> I'm having a bit of trouble understanding how the URL and file based doc
> receipt works.
>
> The documentation states that for MSH to post the received document to a
URL
> or file system, instead of using the onMessage function
> to provide a URL in the getClientUrl function.
>
> Using the LoopBack Class as an example, if I return a Url such as
> "file://C:/tmp" in the getClientUrl function, should the message that the
> loopback class has sent to itself be written to the directory that I
> specified. I have tried this and it seems that this is not the case. It
> still calls the onMessage function and there are no files written to the
> directory I specified.
>
> Any info is appreciated,
>
> Thanks
>
> Anthony Ellis
>
>
>
> -------------------------------------------------------
> This sf.net emial is sponsored by: Influence the future of
> Java(TM) technology. Join the Java Community Process(SM) (JCP(SM))
> program now. http://ad.doubleclick.net/clk;4699841;7576301;v?
> http://www.sun.com/javavote
> _______________________________________________
> ebxmlms-develop mailing list
> ebx...@li...
> https://lists.sourceforge.net/lists/listinfo/ebxmlms-develop



-------------------------------------------------------
This sf.net emial is sponsored by: Influence the future of
Java(TM) technology. Join the Java Community Process(SM) (JCP(SM))
program now. http://ad.doubleclick.net/clk;4699841;7576301;v?
http://www.sun.com/javavote
_______________________________________________
ebxmlms-develop mailing list
ebx...@li...
https://lists.sourceforge.net/lists/listinfo/ebxmlms-develop

Re: [ebxmlms-develop] URL and File base document receipt

[Gait B. <gai...@ti...>]

Hi Anthony,

the folder you specify needs to be listed as a trusted repository, which is
defined in the msh.properties.xml file at
MSH/MessageListener/TrustedRepository.
For starters, you could change the location to
file://C:/tmp/ebxmlms/trustedRepository1 to see if it's working ok. Be sure
to create the folder.

Gait.
----- Original Message -----
From: <ant...@re...>
To: <ebx...@li...>
Sent: Tuesday, October 22, 2002 8:16 AM
Subject: [ebxmlms-develop] URL and File base document receipt


> I'm having a bit of trouble understanding how the URL and file based doc
> receipt works.
>
> The documentation states that for MSH to post the received document to a
URL
> or file system, instead of using the onMessage function
> to provide a URL in the getClientUrl function.
>
> Using the LoopBack Class as an example, if I return a Url such as
> "file://C:/tmp" in the getClientUrl function, should the message that the
> loopback class has sent to itself be written to the directory that I
> specified. I have tried this and it seems that this is not the case. It
> still calls the onMessage function and there are no files written to the
> directory I specified.
>
> Any info is appreciated,
>
> Thanks
>
> Anthony Ellis
>
>
>
> -------------------------------------------------------
> This sf.net emial is sponsored by: Influence the future of
> Java(TM) technology. Join the Java Community Process(SM) (JCP(SM))
> program now. http://ad.doubleclick.net/clk;4699841;7576301;v?
> http://www.sun.com/javavote
> _______________________________________________
> ebxmlms-develop mailing list
> ebx...@li...
> https://lists.sourceforge.net/lists/listinfo/ebxmlms-develop

Re: [ebxmlms-develop] URL and File base document receipt

[Frankie L. <fr...@mi...>]

If you want the message to be written to the path specified in the URL, the
path must also be specified exactly in the
/Property/MSH/MessageListener/TrustedRepository, which is actually a list of
paths delimited by semicolon. For example, if the URL returned by
getClientUrl() is "file://C:/tmp", then "C:/tmp" should be specified in
/Property/MSH/MessageListener/TrustedRepository.

The reason for this design is to prevent any malicious programs from
requesting the MSH to write messages to arbitrary locations, which can be a
security threat if the MSH runs in a privileged user account.

Best regards,
  Frankie

----- Original Message -----
From: <ant...@re...>
To: <ebx...@li...>
Sent: Tuesday, October 22, 2002 2:16 PM
Subject: [ebxmlms-develop] URL and File base document receipt


> I'm having a bit of trouble understanding how the URL and file based doc
> receipt works.
>
> The documentation states that for MSH to post the received document to a
URL
> or file system, instead of using the onMessage function
> to provide a URL in the getClientUrl function.
>
> Using the LoopBack Class as an example, if I return a Url such as
> "file://C:/tmp" in the getClientUrl function, should the message that the
> loopback class has sent to itself be written to the directory that I
> specified. I have tried this and it seems that this is not the case. It
> still calls the onMessage function and there are no files written to the
> directory I specified.
>
> Any info is appreciated,
>
> Thanks
>
> Anthony Ellis
>
>
>
> -------------------------------------------------------
> This sf.net emial is sponsored by: Influence the future of
> Java(TM) technology. Join the Java Community Process(SM) (JCP(SM))
> program now. http://ad.doubleclick.net/clk;4699841;7576301;v?
> http://www.sun.com/javavote
> _______________________________________________
> ebxmlms-develop mailing list
> ebx...@li...
> https://lists.sourceforge.net/lists/listinfo/ebxmlms-develop
>

[ebxmlms-develop] URL and File base document receipt

[<ant...@re...>]

I'm having a bit of trouble understanding how the URL and file based doc
receipt works.

The documentation states that for MSH to post the received document to a URL
or file system, instead of using the onMessage function
to provide a URL in the getClientUrl function.

Using the LoopBack Class as an example, if I return a Url such as
"file://C:/tmp" in the getClientUrl function, should the message that the
loopback class has sent to itself be written to the directory that I
specified. I have tried this and it seems that this is not the case. It
still calls the onMessage function and there are no files written to the
directory I specified.

Any info is appreciated,

Thanks

Anthony Ellis