June 2008 - jboss-dev-forums - Jboss List Archives

[Nukes Development] - JET FUEL $100.00 PER BARREL

by HRH2

I AM A FULL SERVICE FUEL DEALER/EXPORTER IN THE UNITED STATES. I CARRY JET A; JET A1; AVGAS; 100LL; HELICOPTER FUEL; AVIATION FUEL. I SELL FUEL FROM 24 REFINERIES COAST TO COAST THAT ARE AFFILIATES. I APPRECIATE THE OPPORTUNITY TO BID ON YOUR FUEL REQUIREMENTS. PLEASE INCLUDE THE EXACT DESTINATION AND QUANTITY IN YOUR REQUEST ON COMPANY LETTERHEAD. PLEASE ALLOW A 14 DAY LEAD WAY ON FUEL DELIVERY. SO, IF YOU REQUIRE FUEL, I LOOK FORWARD TO EXCEEDING YOUR EXPECTATIONS IN MY FUEL PRODUCTS. TYPICAL FULL SALES OFFER I, Harrison Rains Hanover, as the SELLER, with full authority and legal responsibility, under penalty of perjury, hereby confirm that I am ready willing and able to sell the commodity: JET A1 under the following terms and conditions below. PRODUCT: JET A1 ORIGIN: USA SPECIFICATIONS: SPECIFICATION DEPENDS UPON DELIVERY OPTION. QUANTITY: ONE MILLION BARRELS (1,000,000 BARRELS) AND GREATER. CONTRACT TERM: SPOT DELIVERY: BUYER'S CHOICE SUBJECT TO SELLER APPROVAL. PRICE: $100.00USD PER BARREL PAYMENT: CASHIER CHEQUE AT CLOSING OR TT IN ADVANCE OF CLOSING. WARRANTY: PRODUCER WARRANTS QUALITY. SGS INSPECTION AVAILABLE AT BUYER'S COST AFTER CLOSING AND BEFORE DELIVERY. PROCEDURES 1. BUYER issues LETTER defining quantity required and desired price. The letter will also disclose Q88 information if buyer is taking delivery via ship. Recent safety inspection, less than 90 days old, must accompany Q88. If delivery is to be made via pipeline, the letter will disclose the exact physical address of the tank storage facility; a contact person; telephone number; tank numbers; and a recent ANSI safety inspection report less than 90 days. 2. SELLER issues sales contract based upon information provided by BUYER in the LETTER. 3. The BUYER will establish its own separate account at FRONTIER BANK, MAIN BRANCH, in Everett, Washington and deposit the full amount of the purchase. 4. The SELLER and BUYER shall meet in a TTM at the FRONTIER BANK. At the TTM the SELLER and BUYER shall sign the SALES CONTRACT. 5. After the SALES CONTRACT is signed the BUYER shall draw a cashiers cheque from its account at FRONTIER BANK paid to the order of SELLER. 6. SELLER and BUYER exchange POP and cashier cheque. POP is the contract between the SELLER and the major oil company refining and supplying the JET A1 for this transaction. The POP will be redacted as to the supply price. 7. Deliveries begin as per the terms of the contract YOU MAY CONTACT ME AT osec.sugar(a)gmail.com. View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=4159346#4159346 Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=4159346

16 years, 1 month

1
0
0 / 0

[Design of JBoss ESB] - Re: A problem about soapAction and wsdl in JBossESB

by Kevin.Conner＠jboss.com

That is the correct email address but I have not seen anything come through. Can you get onto the #jbossesb IRC channel on freenode? View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=4159333#4159333 Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=4159333

16 years, 1 month

1
0
0 / 0

[Design of JBoss jBPM] - jbpm-api first draft

by thomas.diesler＠jboss.com

Folks, The first draft of the API is available here http://jbws.dyndns.org/jbpm-site/jbpm-api/apidocs/index.html The associated test case is here http://fisheye.jboss.com/browse/JbpmSvn/tempranillo/jpdl/branches/tdiesle... I implemented a mapping to the current jBPM3 code base for this basic test. On purpose, the API leaves out everything that is not covered by this usecase. The issue that deals with API design is http://jira.jboss.org/jira/browse/JBPM-1250 Please provide feedback. View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=4159332#4159332 Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=4159332

16 years, 1 month

1
0
0 / 0

[Design of JBoss ESB] - Re: How to password protect the ESB console application (jbo

by Kevin.Conner＠jboss.com

jBPM should already have had a policy configured but, due to a bug in the installation script, this doesn't get applied. This was fixed in http://jira.jboss.com/jira/browse/JBESB-1802. Unfortunately we do not include a protected version of the jbossesb console at present, this is something you will have to setup yourself. The platform versions of these consoles are protected but you can only get those through a support contract. View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=4159331#4159331 Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=4159331

16 years, 1 month

1
0
0 / 0

[Design of JBoss ESB] - Re: Regarding JBoss ESB

by Kevin.Conner＠jboss.com

So what was the problem? View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=4159327#4159327 Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=4159327

16 years, 1 month

1
0
0 / 0

[Design of JBoss jBPM] - Re: jPDL 4 early feedback

by tom.baeyens＠jboss.com

Notice that there are some TODO's in the namespace overview page (at the bottom). Ideas on those todo's are also welcome. I might highlight those TODO's later here in the forum as separate posts. View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=4159308#4159308 Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=4159308

16 years, 1 month

1
0
0 / 0

[Design of JBoss jBPM] - jPDL 4 early feedback

by tom.baeyens＠jboss.com

I have outlined the initial scope and schema for jPDL 4. http://docs.jboss.com/jbpm/jpdl4/doc/xsd/ Early feedback is welcome. View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=4159307#4159307 Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=4159307

16 years, 1 month

1
0
0 / 0

[Design of JBoss Web Services] - Re: JBMETA-44, ws annotation processing for references

by alessio.soldano＠jboss.com

The AS testsuite doesn't cover this specific test afaik while the JBossWS ones do, didn't look at the TCK instead. Thank you then, I'll wait for 1.0.0.Beta24. View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=4159301#4159301 Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=4159301

16 years, 1 month

1
0
0 / 0

[Design of JBoss Web Services] - Re: JBMETA-44, ws annotation processing for references

by emuckenhuber

"alessio.soldano(a)jboss.com" wrote : | The above change was done because of the "<service-interface> cannot be null" error at the beginning of this thread that actually proved to be caused by the annotatedElement not being set, wan't it? | Yes i think that was the orignal intention. Although this should not cause any regressions in the tck or AS testsuite? I'm going to revert it - so it will be in the next metadata release. Thanks View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=4159298#4159298 Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=4159298

16 years, 1 month

1
0
0 / 0

[Design of JBoss Web Services] - Re: JBMETA-44, ws annotation processing for references

by alessio.soldano＠jboss.com

I'm running some test cases on JBossWS side to validate the JBMETA-44 and I've just come to this: "alex.loubyansky(a)jboss.com" wrote : Another question related to JBMETA-44 and JBCTS-797. It's not clear to me how the @WebServiceRef should be mapped to ServiceReferenceMetaData. | | What (if anything) in @WebServiceRef should specify the service-interface? | | The current processing of @WebServiceRef is | if(annotation.type() != Object.class) | | ref.setServiceRefType(annotation.type().getName()); | | else | | ref.setServiceRefType(getType(element)); | | if(annotation.value() != Object.class) | | ref.setServiceInterface(annotation.value().getName()); | | | | Is this correct? The example Scott posted above is from JBCTS-797 which currently fails because "service-interface is null". | Yes, as Thomas said, this should be the right implementation. I've just seen that commit 74508 changed the implementation to: | if(annotation.type() != Object.class) | ref.setServiceRefType(annotation.type().getName()); | else | ref.setServiceRefType(getType(element)); | if(annotation.value() != Object.class) | ref.setServiceInterface(annotation.value().getName()); | else | ref.setServiceInterface(ref.getServiceRefType()); | In my opinion this is not right since you might end up having the SEI class name in the serviceInterface attribute in cases where a reference whose type is a SEI is defined. The above change was done because of the "<service-interface> cannot be null" error at the beginning of this thread that actually proved to be caused by the annotatedElement not being set, wan't it? Thanks View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=4159286#4159286 Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=4159286

16 years, 1 month

1
0
0 / 0

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

2009

2008

2007

2006

jboss-dev-forums June 2008