text:
London, August 30, 2014 – Independent organizations in Egypt face a looming crackdown, 44 international and national human rights groups from across the global said today in a joint statement.
The Egyptian Social Solidarity Ministry placed an advertisement in leading state newspaper Al-Ahram on July 18, 2014, giving all Egyptian and international non-governmental organizations until September 2 to register under Law 84/2002, a restrictive measure passed during the Mubarak rule. This law empowers the government to shut down any group virtually at will, freeze its assets, confiscate its property, reject nominees to its governing board, block its funding, or deny requests to affiliate with international organizations. The law also does not indicate that NGOs have the right to appeal the decision.
"The al-Sisi government's demand for all organizations to register under the discredited 2002 law is nothing but an order for them to surrender their independence," said Sarah Leah Whitson, Middle East and North Africa director at Human Rights Watch. "There's no way that an organization can register under Law 84 and still be considered 'independent' from the government."
The law provides for criminal penalties up to one year in prison for unauthorized activities by independent groups. Under the government of Hosni Mubarak, the authorities routinely harassed activists and arbitrarily shut down independent groups.
"Egyptian authorities are using the law to orchestrate a witch hunt against NGOs and put them under their thumb. The government must withdraw the requirement for compulsory registration of NGOs under the current law, which is contrary to international human rights standards," said Hassiba Hadj Sahraoui, Deputy Director of the Middle East and North Africa Program at Amnesty International.
Egyptian organizations have been seeking to abolish Law 84/2002 since it was enacted, and the various governments since then have proposed several new draft laws concerning independent groups, but none have become law. Some organizations have opted to register as law firms or nonprofit companies instead of as associations under this law.
"We cannot see any justification for resurrecting Mubarak era legislation imposing re-registration process that could effectively close down or criminalize human rights organizations critical of the government," said Gerald Staberock, secretary-general of the World Organization Against Torture (OMCT). "What is needed to overcome the present crisis is respect for human rights, not closing NGOs down."
Egyptian non-governmental organizations have repeatedly said they do not object to—indeed, they encourage— a new associations law that will provide for independent oversight and transparency in funding and operations. They have submitted numerous proposals, including an alternative draft law that they say complies with international standards and best practices.
They negotiated with the Social Solidarity Ministry for more than six months to draft a new law, upon invitation from the former Minister of Social Solidarity, Ahmed al-Borai. Al-Borai submitted a consensus draft to the Cabinet in February for introduction to the new parliament, once elected. But the government has ignored this draft and all prior proposals.
Instead, it has disclosed a new draft associations law that permits authorities to shut down any of the over 40,000 Egyptian independent groups, pending a court order, or refuse to license new groups on vague grounds of harming "national unity." The draft law would create a Coordinating Committee made up of government officials, including representatives of the Ministry of Interior and the General Intelligence Services, who would have control over anything to do with the registration, activities and funding of foreign NGOs in Egypt, as well as over any foreign funding received by Egyptian NGOs. The law also imposes harsher penalties than the current law of 84/2002, including prison sentences of up to three years and fines not less than USD $14,000 for activities that includes operating without a license, raising funds without permission or operating in association with an international group without permission from the government committee.
"There needs to be an overhaul of the whole legal framework to allow civil society to operate independently from the government, which is the purpose of civil society," said David Tolbert, president of the International Center for Transitional Justice. "Enforcing the existing Mubarak era law or enacting an even more repressive draft law will shut down what remains of independent public civil society in Egypt."
Pending the passage of this new more restrictive law, the government has declared that it will enforce the existing repressive law, and demanded that even groups now lawfully registered as law firms or nonprofit companies register as associations under the 84/2002 law. Independent Egyptian human rights organizations that have documented human rights abuse under the Mubarak, the Supreme Council of the Armed Forces, Morsy, and al-Sisi governments, have told international partners that they will be shut down entirely rather than register under the prohibitive 84/2002 law.
"The existing law and the draft bill rob independent NGOs of all meaning and deny Egypt creative energies by effectively shutting down the few remaining legitimate channels for public action," said Karim Lahidji, president of the International Federation for Human Rights (FIDH). "Even during Mubarak's three decades of stagnation and stifled public space, the government never went as far as this crackdown threatens to go."
The 2002 law and the provisions of the new draft bill are entirely at odds with the international pledges Egypt made and the recommendations it accepted in its first Universal Periodic Review (UPR) at the UN Human Rights Council in 2010. The government at that time had pledged to revise the 2002 law to minimize governmental intervention and give organizations greater autonomy.
It accepted recommendations to guarantee freedom of association and to put in place simple, rapid, non-discriminatory procedures for establishing organizations, and to end administrative arbitrary discretion in establishing and controlling groups, and instead to bring Egypt's associations law into compliance with international human rights standards. Egypt's next UPR is to be in October.
Over the last 12 years, a number of treaty bodies have criticized the restrictions on NGOs in Egypt under the current legislation.
"We today face the very real prospect that in a matter of days authorities will effectively shut down what remains of independent civil society in Egypt, long one of the most vibrant in the Arab region," said Michel Tubiana, president of the Euro-Mediterranean Human Rights Network. "This should not only ring alarm bells in Egypt, but among all those concerned about the future of civil society and human rights throughout the world."
• Adil Soz- International Foundation for Protection of Freedom of Speech • Albanian Media Institute • Aliansi Jurnalis Independen (AJI)- Indonesia • Amnesty International • Asian Legal Resource Centre • Association of Independent Electronic Media • Article 19 • Bytes for All, Pakistan • Canadian Journalist for Free Expression (CJFE) • Centre for Independent Journalism- Malaysia • Centre for Media Freedom & Responsibility • Centro de Estudios Legales y Sociales (CELS) • CIVICUS • Commonwealth Human Rights Initiative • Conectas • East and Horn of Africa Human Rights Defenders Project • Electronic Frontier Foundation • Euro-Mediterranean Human Rights Network • Freedom Forum • Globe International Center • Human Rights Watch • I'lam Media Center • Independent Journalism Center • Initiative for Freedom of Expression • Iniyan • Institut Studi Arus Infromasi (ISAI) • International Centre for Transitional Justice (ICTJ) • International Federation for Human Rights (FIDH) • International Federation of Journalists, Asia Pacific • International Press Institute • Journaliste en Danger (JED-DRC) • Le Réseau des Défenseurs des Droits Humains en Afrique Centrale (REDHAC) • Norwegian People's Aid (NPA) • Media, Entertainment & Arts Alliance (MEAA) • Pakistan Press Foundation • Pan-African Human Rights Defenders Network • PEN American Center • PEN Canada • PEN International • Sexual Minorities Uganda (SMUG) • The Center for Media Studies and Peacebuilding (CEMESP-Liberia) • The International Service for Human Rights • World Association of Community Radio Broadcasters (AMARC) • World Organization Against Torture (OMCT)
Photo: Egypt Students March, February 21, 2012 (Jonathan Rashad)


text:
Visiting address:
Industrigatan 14
521 73 Kinnarp
Postal address:
Kinnarps AB
521 88 Kinnarp
Phone: 0515 - 38 000
Fax: 0515 - 33 701
Guess what?
An entire section of our website is dedicated to professionals working with our products. We call it Design Tools. Providing a list of our entire product portfolio, it also contains direct downloadable links to useful resources. The product list can be filtered according to specific wants and needs. Nifty. Go to Design Tools

subset: commoncrawl


text:
Diamond Tech
- Diamond Tech
Powder Vibe Unit With Original Tip
The Powder Vibe is a quick and mess-free way to precisely dispense frits or enamels onto any surface for enameling, fusing and lampworking projects. To use, hold the Powder Vibe like you would hold a pen or pencil, with the barrel resting between your thumb and index finger. Use your index finger to apply pressure to either the right or left side of the pressure switch located on the body to activate and release frit/enamels from the Powder Vibe unit. PLEASE NOTE: Bearfoot Tools by Studio ...


text: Finished in Cherry Bordeaux on select hardwoods and veneers. The elegant swan neck pediment of this fine clock features rare bookmatched olive ash burl, a turned finial, and a carved shell overlay. Olive ash burl corner overlays frame the crystal-cut oval glass on the lower door, providing a striking view of the pendulum and weights. The polished brass-finished dial offers elaborate corner spandrels, a center disk, a silver chapter ring with applied brass Arabic numerals, and an astrological moon phase dial. The polished brass-finished pendulum includes a center disk that complements the dial and coordinates with the banded, polished-brass weight shells. Elaborately carved, reeded columns with turned top and bottom caps and carved oval appliques enhance the front view of the clock. The multitiered base features a decorative cutout. Removable beveled glass top side panels allow easy access to the movement. The side lower glass is also beveled. A high-precision, German-made, Kieninger® cable-driven, triple-chime movement plays choice of Westminster, St. Michael, or Whittington 1/4, 1/2, and 3/4 chimes accordingly with full chime and strike on the hour. Automatic nighttime chime shut-off option. Adjustable levelers under each corner provide stability on uneven and carpeted floors. Free brass Heirloom nameplate will be engraved with your name and special date. Free Heirloom Record Document with brass-finished capsule is included.The case is illuminated by an interior light. Locking door for added security. 2 year warranty on parts and workmanship.Designed and Assembled in the USA. Height 86.25" (219 cm) Width 23" (58 cm) Depth 13.5" (34 cm)


text: 100% cotton pre-shrunk jersey knit. Seamless twin needle 7/8" collar. Taped neck and shoulders. Twin needle sleeve and hem bottoms. Quarter turned to eliminate centre crease. Sedex approved supplier. Washing Instructions Machine wash warm. Inside out, with like colours. Only non-chlorine bleach. Tumble dry medium. Do not iron if decorated. Do not dry clean


text:
Among the practices that most helped me when I was a CIO was dividing my time according to what I called the "third-third-third" model. As best I could, I tried to limit one third of my work time to minding the store and looking after day-to-day operations. I devoted another third to fostering strong relationships with peers and customers. The final third—and in my view the most critical—I set aside for learning.
It takes discipline to keep to this schedule; immediate tasks can easily overwhelm a CIO's day. And like other experienced executives in positions of power, CIOs can start believing they already know all they need to know about how to do their jobs. Yet I believe it's terribly important to set aside time to learn more about leadership, management, technology and your industry. As the saying goes, "When you are through learning, you are through." Nothing is more dangerous than believing you have all the answers; it's one of the surest ways to guarantee personal failure.
But where do you go learn? For me, professional IT associations—in particular, the Society for Information Management—have been central for learning and whatever success I've enjoyed. (In the interest of full disclosure, I have been active in SIM for most of its 36 years, serving as president in 1983, and I am still active in its leadership development programs.) But would I still feel the same way if I were beginning my career now? CIOs have so many alternatives. Each year, IT vendors, event management firms, business schools, research and consulting firms, publishing companies, and other for-profit and nonprofit enterprises, as well as online communities, organize hundreds of conferences and Web seminars covering every conceivable topic on an IT executive's agenda. The result is an overwhelming plethora of useful information, and networking opportunities, for CIOs.
Given all this competition for CIOs' time, what should be the purpose of nonprofit professional membership associations? Does an organization like SIM, and others such as the Association of Information Technology Professionals, the Black Data Processing Associates and the Financial Executives Institute, still have anything special to offer, particularly when it comes to education? Indeed they do. I believe such organizations not only remain relevant and important, but offer something that cannot be done by any other kind of organization: They can serve as a professional home where CIOs and other IT executives can let down their guard, and therefore learn things they cannot learn anywhere else.
Conferences, workshops and research firms can help CIOs learn a specific skill, or drill down into a particular topic. But the kind of learning CIOs need most of all goes well beyond what one-shot events can provide. When their rough-and-tumble professional world turns especially bumpy, and the need to learn is most immediate and pressing, CIOs require a place to turn for advice from people who care about them and can help them. Because they provide repeated, regular get-togethers with peers, professional associations offer CIOs and IT executives a chance to form close, trusting relationships. There is no hidden sales agenda, as there inevitably is with meetings sponsored by vendors or research firms, and there's no need to hold back, as with industry associations where competitors gather. In such a setting, it's not an oxymoron to say CIOs can talk openly and confidentially about what they are going through. They can learn from peers who have no axes—either professional or personal—to grind and who have experienced what they're going through and know where the potholes are.
Equally important, professional associations provide the opportunity to make personal discoveries and to become inspired. One of the things I've come to know is that learning to be a leader is by no means the same thing as learning to manage. Learning to manage is well served by conventional lectures and training, because you are learning about something outside yourself. But learning to lead requires learning about what's inside you. Leadership development is not training, but a journey of personal discovery of one's values, natural gifts and personal weaknesses—that's why it's called development. It is a matter of learning how to hone those gifts, compensate for those weaknesses and figure out which mix of techniques best fit the situations you are likely to come across in your job.
Learning to lead isn't something that can be absorbed by sitting in a lecture hall and listening to leadership experts. Rather, the best place to learn what it takes to be an effective leader is in the kind of intimate and trusting setting that a membership association can provide. The openness that kind of environment engenders creates the greatest opportunity for CIOs to not only learn, but to find inspiration.
Non-profit associations also provide the best venue for addressing public issues affecting all CIOs. In the past, CIOs have been concerned with such issues as software licensing laws and Y2K. For the foreseeable future, CIOs also will be wrestling with the legalities of security and privacy issues: How do we keep cyberspace safe and secure? What is the proper balance between national security and the privacy of employee and customer data? What limits should be placed on the use of customer data? By marshalling a critical mass of credible IT executives from many industries, non-profit IT associations can be an effective way for CIOs to influence lawmakers and regulators and to heighten public awareness.
While most large companies are involved in lobbying to some degree, CIOs cannot rely on their own companies to take a public stand on these issues. I believe membership associations need to do more advocacy work in the future. Congress and the executive branch will consider new laws and regulations, not of all of them helpful, to bring order to what is still a young, even immature industry. CIOs must continue to speak with a single voice if they are to help that process along. SIM's suggestions in 2002 to President Bush's Critical Infrastructure Protection Board, advising the creation of an independent organization that would set security standards for private corporations, is a good start, even though this suggestion was not included in the board's final report.
Lifelong learning, personal discovery, public advocacy—these needs may not be new, but they aren't ever going to go away. Indeed, they have only intensified as the CIO's role has grown more complex. I believe that only an independent association of IT executives can completely meet all three needs. That's why IT associations benefit the companies that pay their dues just as much as they benefit the IT executives who join and participate in them.
In a practical sense, these organizations should lower the risk that CIOs will fail in their difficult jobs. CIOs who are effective, knowledgeable leaders will simply perform better. They'll also last longer in their jobs, saving their employers the problems that arise when the CIO role becomes a revolving door. Companies may be tempted, when reducing expenses, to cut back support for such organizations, just as CIOs may be tempted to skip a meeting when they're busy. Don't. Professional associations are one of the most important investments of time or money companies and members can make.
Darwin A. John has held CIO-level positions at the Federal Bureau of Investigation, the Church of Jesus Christ of Latter-day Saints, and the Scott Paper Co. He is currently an advisor to the director of the FBI and to Blackwell Consulting Services in Chicago.
Illustraion by: John Kascht


text:
Find Oncologist in Kashmir Highway Islamabad. Discover the best Oncologist in Kashmir Highway Islamabad list with their details like Contact Number, Timings, Fees, and further information. Our esteemed Gynecologist stands at the forefront of delivering compassionate and comprehensive healthcare services. Embrace the transformative experience of Oncologist in Kashmir Highway Islamabad and embark on a journey towards better health and well-being. Experience the best health care of Oncologist in Kashmir Highway Islamabad, so schedule your appointment with a Gynecologist today.
Oncologist in Islamabad - Oncology is the specialized field that deals with cancer or tumors. The domain of oncology includes three major categories: medical oncology, surgery oncology, and radiation oncology. Oncologists are the specialist who diagnose and treat cancer patients. A medical oncologist treat cancer with chemotherapy, surgical oncologist removes the tumor and other affected areas in an operation, and radiation oncologist treats cancer with radiation therapy. The field of Oncology is thriving in Pakistan with some of the popular names. Find the complete list of Oncologist in Islamabad here on this page including male and female both. Area wise listing is also available to find your specialist doctors easily located near to you. You will also find here the list of best Oncologist in Islamabad with complete details including phone no, hospital sitting address, clinic address, email, website, patient reviews and doctor ratings of Oncologist in Islamabad.
To find a reputable Oncologist in Islamabad visit this page.
To book an online consultation with a Oncologist in Islamabad, you can Visit our Doctors Pages.
Is there any private clinic for you, if yes please give me location and contact no to get appointment.
He is the best cancer specialist in Islamabad.
Patient name zahir shah khan daignose Basal cell carcinoma stage1 is there electron therapy 4Mev in nori haopital
ڈاکٹر صاحبہ۔ کیا آپ پرائیویٹ طور پر بھی مریض چیک کر لیں گی پلیز؟؟؟ آپ کی فیس کیا ہو گی
The nice oncologist in the Islamabad city that give the great treatment and the many peoples go there for taking the officious treatment from him
Disclaimer: All material on this website is provided for your information only and may not be construed as medical advice or instruction. No action or inaction should be taken based solely on the contents of this information; instead, readers should consult appropriate health professionals on any matter relating to their health and well-being. The data information and opinions expressed here are believed to be accurate, which is gathered from different sources but might have some errors. Hamariweb.com is not responsible for errors or omissions. Doctors and Hospital officials are not necessarily required to respond or go through this page.


text:
Building a SOAP Webservices Proxy Module using Spring Webservices
Some time ago I wanted to see how easy it is to write a web services proxy (wsproxy) using Spring Web Services. So, I thought I would share the result on Github. Feel free to use it (Apache v2 license) or let it serve as basis for your own development. The remainder of the article will explain the idea, how I used Spring web services to build it and a short guide on how to use the current implementation.
A wsproxy in this context is a central soap aware access layer which relays messages between systems. This relaying works in two directions; for services hosted internally (inbound mode) but also for services hosted externally were we are the client (outbound mode). One can compare this with a traditional http forward/reverse proxy but instead of operating on application transport it goes one level higher in the stack and deals with application messages; in this case soap.
In outbound mode our internal services will (normally) use the wsproxy as a http forward proxy. It will then deal with delivering the received message to the actual target. For inbound mode the module will act as a reverse proxy accepting incoming messages from external clients and relay them to our internal services.
Before we continue, a few words about forward/reverse proxies:
A forward proxy is something the client explicitly configures in addition to specifying a target URL. The http stack of the client will send the message to the configured proxy and sent the host/port of the actual desired target host via http headers (Host header). The proxy then deals with forwarding the request to the desired target host/port and return the response to the client. Thus the proxy composes the host and port for the target URL out of the http Host header. For the path it will use the path from the request as received from the client. A reverse proxy behaves (from the point of the client) as the actual target server. The client is not aware of any proxies and does neither have to configure anything special. What the client uses as target URL is the URL of the reverse proxy. The reverse proxy will be able to intercept the message from the client and forward it to the actual target within the network. The reverse proxy will required extra configuration as for example the URL (host, port and possibly path) of the target service, as host/port cannot be deduced from the request or http headers.
When using this module, one can still implement an actual http reverse proxy on boundaries for TLS offloading or other transport purposes. For external inbound traffic (messages coming from external clients destined for internal service) the wsproxy module will simply be the second reverse proxy in line for incoming requests. For internal outbound traffic (messages from internal clients destined for external endpoints) the URL of the http reverse proxy will be configured as the target URL for that specific service on the wsproxy module.
One of the features of having such a soap aware wsproxy is centralizing concerns. The goal is that soap traffic passing through can be intercepted. This way we can implement things such as: audit logging, monitoring, access control, message security, … doing so we create a centralized place to deal with these requirements instead of having to re-implement them per application.
I chose Spring web services because there is no complicated infrastructure or design to understand. It it also very extensible and offers re-use at the right level for our requirements.
However, at this time I should also point out that there are existing solutions out there which can do this as well and more. They often go under the name of xml security gateways and come as software package or fully equipped appliances. As always you should outweigh the benefits of these existing solutions over writing something yourself. Fact is that they don't come for free (to say the least) and you still need someone with the right skills for configuring and maintaining them. As we will see, our requirements are easy to fulfill with a bit of code (and the help of Spring Web Services) giving us all the control we need.
For the requirements I had an easy to extend design in mind with following out of the box requirements:
- Outbound mode needs to be configuration free for standard usages. This means that when needing to access a new external services our proxy should relay messages without requiring extra configuration
- Messages passing the gateway need to be logged. Without extra configuration the entire message should be logged by default. Optionally, we need to be able to configure more fine grained which parts needs to be logged for specific services
- For (mostly external) outbound communication we should be able to configure a forward proxy or override the target with a pre-configured host (an existing reverse proxy or the actual endpoint)
- The module must be able to forward messages over secure transport in case there is no external reverse proxy present for offloading outbound secure transport. For inbound secure transport we will let this be handled by the container where the module is running on; so this is out of scope for the module
- Be able to apply and handle message integrity/confidentiality
The component design looks like this:
There are 3 main components. The endpoint (catch-all endpoint in the drawing), which will act as the receiver for the message being sent to the wsproxy. The forwarder, which will relay the message to the target. Finally, the interceptor chains are the hooks where we are able to intercept the messages being sent/received and do something with them.
These 3 components are offered by Spring Web Services; the endpoint is a org.springframework.ws.server.endpoint.annotation.Endpoint implementing org.springframework.ws.server.endpoint.MessageEndpoint to be able to receive the raw payload. The forwarder uses org.springframework.ws.client.core.WebServiceTemplate and the interceptor chains are org.springframework.ws.client.support.interceptor.ClientInterceptor and/or org.springframework.ws.server.EndpointInterceptor depending on which sides they need to function (more on that later). For message security we will use WSS4J, but this is just an implementation of an interceptor, thus not a new component.
It is important to realize that there are two interceptor chains. From the point of the wsproxy, we'll call the first one the "inbound chain". This is the one operating between the client and the wsproxy. The "outbound chain" is the one operating between the wsproxy and target endpoint. So, if we have an internal client accessing an external endpoint via our wsproxy, the inbound chain will be invoked when the message is received by the wsproxy. The outbound chain will be invoked from the moment the wsproxy relays the message to the target endpoint. Spring has two interfaces to distinguish on which "side" the interceptor operates (an interceptor can also implement both interfaces, making it able to function on both sides). The org.springframework.ws.server.EndpointInterceptor operates on the endpoint side, for the wsproxy this is inbound. The org.springframework.ws.client.support.interceptor.ClientInterceptor operates on the client side, so for the wsproxy this is outbound. Btw; we're using inbound and outbound rather then the original Spring naming (client/endpoint) to avoid confusion. As you've noticed by now, the wsproxy is also an endpoint and a client. However, when we refer to "client" we mean the actual service client and the "endpoint" is the actual target service.
The module itself will run on a standard JEE servlet container as your typical Spring application. For all inbound traffic the http (or https) connector from the container is used. For all outbound traffic the WebServiceTemplate is used configured with commons httpclient under the hood, which we'll be able to use for both http and https if required. Service identification is done the "doclit" style. This means we take the first element of the body including it's namespace. This is represented as a QName. This identification is important as we'll have configuration on a per service basis, such as the forward proxy, forwarding protocol, endpoint URL mapping, specific loggers etc.
Ok enough of this. let's take this baby for a spin! Import the project in your IDE of choice, make sure you import it as a Maven project as Maven will have to filter the file active_environment.properties (this is done automatically via the default profile). Then we will:
- Setup a normal standalone soap based endpoint
- Deploy wsproxy
- Use a web services client to access the endpoint via the proxy module
For bootstrapping a simple endpoint there is a class SimpleEndpoint foreseen in the tests sources which uses the JDK internal JAX-WS and http server to bootstrap a webservice endpoint:
public class SimpleEndpoint { public static void main(String args[]) { Endpoint.publish("http://localhost:9999/simple", new SimpleWebServiceEndpoint()); } @WebService public static class SimpleWebServiceEndpoint { public Date getCurrentDate(String randomParameter) { return new Date(); } } }
Just run this as a new Java application, it will remain running until the process is killed. Boot the wsproxy by deploying the project to your server of choice (I'll be using Tomcat7), there is no extra configuration required. As for the client we'll be using soap-ui (you can also use cURL if you like). In soap-ui we first have to create the project. We do this based on the WSDL exposed by our test service (accessible under http://localhost:9999/simple?WSDL). Next, we'll have to configure our wsproxy module as the http forward proxy in soap-ui:
The soap-ui projects are also availale in the project if you want. Don't forget to enable the proxy settings as explained above, they are not saved as part of the project.
Important: don't forget to disable the proxy settings again if you are starting with a new project. soap-ui will use the proxy settings for standard http traffic and not only for soap/http. For example; when creating a new project based on a WSDL URL, soap-ui will use the http proxy settings as well to retrieve the WSDL. Since the wsproxy module is not a pure http proxy (but a soap proxy instead) it will not allow non-soap traffic through.
The last thing we need to configure is the target URL in soap-ui. The wsproxy module is by default (on tomcat at least) deployed under the context root named after the filename. In our case this means the module is reachable under: http://localhost:8080/ws-proxy/
There are two options:
- Deploy the module under the root of the application server (/) instead. In that case nothing needs to be changed to the target URL. The target URL will remain the same URL as you would be using without the proxy module
- Use a context root of choice, but in that case you'll have to prefix the context root to the target URL
In our case we are in the second scenario, this means that we'll have to change the proposed target URL from "http://localhost:9999/simple" to "http://localhost:9999/ws-proxy/simple".
What happens is that soap-ui sends the request to the host/port specified in the proxy settings (it will thus not sent the request to localhost:9999 but to localhost:8080 instead). The path however is retained; the request is actually sent to localhost:8080 with path "ws-proxy/simple". With the module deployed under "ws-proxy" you can now see why this path prefix has to be there. If the path would start with "simple" we would get a 404. The remainder of the path is not important for the infrastructure, as the Spring dispatcher servlet (configuration can be found in WsProxyWebApplicationInitializer) is bound to "/*". So every subsequent path is treated by the servlet in every case.
To be able to forward the message to the actual target, the module will calculate the target URL:
- First check if there is a pre-configured target URL for the given endpoint based upon the service identification (payload root element + namespace). This is configured in EndpointTargetUrlMapping as we will see later.
- If nothing found, check if there is a http Host header present, use host:port as the target server. For the path, use the path as present in the request, but subtract the context root under which this module is deployed (if any)
The latter means that in our case the module is deployed under "ws-proxy" and the request path is "ws-proxy/simple", which will result in a target URL of "http://localhost:999/simple" When executing the request, we'll get this answer:
In the wsproxy log file we can see the intercepted request and response being logged:
51948 [http-bio-8080-exec-5] DEBUG be.error.wsproxy.interceptors.internalchain.LoggingInterceptor - SID:{http://wsproxy.error.be/}getCurrentDate INBOUND SIDE Request:<?xml version="1.0" encoding="UTF-8" standalone="no"?> <soapenv:Envelope xmlns:soapenv="http://schemas.xmlsoap.org/soap/envelope/" xmlns:wsp="http://wsproxy.error.be/"> <soapenv:Header/> <soapenv:Body> <wsp:getCurrentDate> <!--Optional:--> <arg0>?</arg0> </wsp:getCurrentDate> </soapenv:Body> </soapenv:Envelope> 51949 [http-bio-8080-exec-5] DEBUG be.error.wsproxy.core.ForwardingClient - Using information from Host header as hostname/port 51949 [http-bio-8080-exec-5] DEBUG be.error.wsproxy.core.ForwardingClient - Got webservice forwarding request, sending to:http://localhost:9999/simple 51981 [http-bio-8080-exec-5] DEBUG be.error.wsproxy.core.ForwardingClient - Using interceptors:[class be.error.wsproxy.interceptors.externalchain.HttpRequestHeaderTransfererInterceptor] 51981 [http-bio-8080-exec-5] DEBUG be.error.wsproxy.core.ForwardingClient$3 - Opening [org.springframework.ws.transport.http.HttpComponentsConnection@1dd5e19a] to [http://localhost:9999/simple] 51991 [http-bio-8080-exec-5] DEBUG be.error.wsproxy.core.ForwardingClient - Forwarding (http://localhost:9999/simple) done. 51994 [http-bio-8080-exec-5] DEBUG be.error.wsproxy.interceptors.internalchain.LoggingInterceptor - SID:{http://wsproxy.error.be/}getCurrentDate INBOUND SIDE Response:<?xml version="1.0" encoding="UTF-8" standalone="no"?> <S:Envelope xmlns:S="http://schemas.xmlsoap.org/soap/envelope/"> <S:Body> <ns2:getCurrentDateResponse xmlns:ns2="http://wsproxy.error.be/"> <return>2013-10-28T15:55:29.717+01:00</return> </ns2:getCurrentDateResponse> </S:Body> </S:Envelope>
In the default setup default logging happens on the inbound side. The inbound interceptors are configure here:
@Configuration public class InboundInterceptors { @Autowired private PayloadRootAnnotationMethodEndpointMapping catchAllEndpointMapping; @Autowired private MessageDispatcher messageDispatcher; @Configuration public static class FirstInlineInterceptors { @Bean public DelegatingSmartSoapEndpointInterceptor loggingInterceptor() { return new DelegatingSmartSoapEndpointInterceptor(new LoggingInterceptor()); } } @Configuration public static class ServiceSpecificInterceptors { } @Configuration public static class LastInLineInterceptors { } }
If you want to configure this logging interceptor also on the outbound side, you can add them in OutboundInterceptors. LoggingInterceptor both implements EndpointInterceptor and ClientInterceptor. To continue with our requirements, there is also an interceptor which is able to log fragments based on XPath expression. The LoggingXPathInterceptor is service specific and hence we'll be adding this one to the ServiceSpecificInterceptors. The difference is that service specific interceptors use PayloadRootSmartSoapEndpointInterceptor which we need to give namespace and payload root element to identify the service. The configured interceptor will only be invoked for that service. The first in line and last in line use
DelegatingSmartSoapEndpointInterceptor which will be invoked for any request.
@Configuration public static class ServiceSpepcificInterceptors { @Bean public PayloadRootSmartSoapEndpointInterceptor getCurrentDateLoggingInterecptor() { LoggingXPathInterceptor loggingXPathInterceptor = new LoggingXPathInterceptor(); loggingXPathInterceptor.addRequestXPaths(new WebServiceMessageXPathExpressionMetaData( "//*[local-name()='arg0']", "requestParameter")); loggingXPathInterceptor.addResponseXPaths(new WebServiceMessageXPathExpressionMetaData( "//*[local-name()='return']", "responseParameter")); return new PayloadRootSmartSoapEndpointInterceptor(loggingXPathInterceptor, "http://wsproxy.error.be/", "getCurrentDate"); } }
When we execute the request again in soap-ui, we can see that the request argument and response value are extracted logged to our log file:
DEBUG be.error.wsproxy.interceptors.internalchain.LoggingXPathInterceptor - SID:{http://wsproxy.error.be/}getCurrentDate XPATHID:requestParameter VALUE:? DEBUG be.error.wsproxy.interceptors.internalchain.LoggingXPathInterceptor - SID:{http://wsproxy.error.be/}getCurrentDate XPATHID:responseParameter VALUE:2013-10-28T16:50:29.537+01:00
The WebServiceMessageXPathExpressionMetaData operates by default on the soap body (payload) and treats the given XPaths as mandatory (but non blocking). To see other options check the javadoc on WebServiceMessageXPathExpressionMetaData.
The properties that can be configured are located in the package be.error.wsproxy.configuration.properties. Following classes exist:
The default Spring profile "local", enabled via Maven the default Maven filter, will resolve them from the properties file in
wsproxy_local_demo.properties. The configuration is always stored as a simple string allowing for easy externalization in for example a JNDI environment. The three first properties determine how messages will be forwarded, to start with EndpointProtocolMapping:
In the above scenario the target URL was automatically deduced from the Host parameters as our internal client was using the module as a forward proxy. Since the host parameters do not contain any notion about protocols, the wsproxy assumed http as the forwarding protocol by default. If don't have a reverse proxy which takes care of offloading TLS, you can ask the proxy module to forward over https instead. You can do this by setting the protocol mapping to https for a specific service:
EndpointTargetUrlMapping allows to define the target URL directly. This is required in the scenario where an external client will be accessing our internal service. In that case the target URL can no longer be deduced; external clients will not use our module as forward proxy but the message will simply end up on our module as it would be the actual service. The module then needs to know to where it should forward the message to:
This can also be used to override the target URL all together. The forwarder will first look if there is an explicit URL defined for the given service, if so that one will be given precedence.
The ForwardProxy can be configured when the wsproxy module on its turn needs to communicate via a http forward proxy in order to reach the target. This is also configurable on a per service basis.
Remember that the forward proxy does not change anything on how the target URL is calculated. Instead of directly accessing the target URL, the message will be forward to the configurered proxy if the setting is used:
The keystores point to the keystore configuration containing store location, store password, key alias and key password. They are used when we want to apply message security which we'll cover next.
keystores.location=${project.root.dir}/config/test-keystores keystore=${keystores.location}/keystore.jks keystore.password=changeme key.alias=mykey key.password=changeme truststore=${keystores.location}/truststore.jks truststore.password=changeme
To satisfy the last requirement (integrity/confidentiality) we'll be using WSS4J via the Spring Wss4jSecurityInterceptor. This interceptor needs to be configured on the outbound side in our example were we have an internal client accessing an external service. The steps we will perform:
- Setup a secured standalone soap based endpoint
- Configure the wsproxy with message security for the given service
- Deploy wsproxy
- Use a web services client to access the endpoint via the proxy module
For the secured endpoint SimpleSecuredEndpoint is foreseen using JAXWS and WSIT. The WSIT configuration can be found in META-INF/wsit-be.error.wsproxy.SimpleSecuredEndpoint$SimpleWebServiceEndpoint.xml enabling message integrity on our endpoint.
public class SimpleSecuredEndpoint { public static void main(String args[]) throws IOException { // Set WSIT_HOME manually, we're only using this for testing purposes. This way we can have a dynamic path based // on the project location in filesystem to resolve the keystores via the WSIT configuratin in META-INF System.setProperty("WSIT_HOME", new ClassPathResource("").getFile().getParent() + "/../config/test-keystores/"); Endpoint.publish("http://localhost:9999/simple", new SimpleWebServiceEndpoint()); } @WebService(serviceName = "SimpleEndpoint") @Addressing(enabled = false, required = false) public static class SimpleWebServiceEndpoint { public Date getCurrentDateSecured(String randomParameter) { return new Date(); } } }
Important: the JAXWS implementation shipped with the JDK does not contain WSIT. It is just the JAXWS RI. In order for this to work you'll have to download the latest Metro release yourself which bundles everything together. See Metro home page. When you've downloaded Metro, run SimpleSecuredEndpoint passing along the endorsed system property:-Djava.endorsed.dirs=/path_to_metro/lib. This will ensure the entire JAXWS implementation is used from the external libraries. When everything is running fine you'll be seeing a line:
INFO: WSP5018: Loaded WSIT configuration from file: file:/home/koen/....
The configuration of the WSS4J interceptor enabling message integrity in OutboundInterceptors:
@Bean public Map<QName, List<ClientInterceptor>> customClientInterceptors() throws Exception { Map<QName, List<ClientInterceptor>> mapping = new HashMap<>(); List<ClientInterceptor> list = new ArrayList<>(); list.add(getCurrentDateServiceSecurityInterceptor()); list.add(new LoggingInterceptor()); mapping.put(new QName("http://wsproxy.error.be/", "getCurrentDateSecured"), list); return mapping; } private Wss4jSecurityInterceptor getCurrentDateServiceSecurityInterceptor() throws Exception { Wss4jSecurityInterceptor interceptor = new Wss4jSecurityInterceptor(); // Outgoing interceptor.setSecurementActions("Signature Timestamp"); interceptor .setSecurementSignatureParts("{}{http://schemas.xmlsoap.org/soap/envelope/}Body;{}{http://docs.oasis-open.org/wss/2004/01/oasis-200401-wss-wssecurity-utility-1.0.xsd}Timestamp"); interceptor.setSecurementSignatureKeyIdentifier("IssuerSerial"); Pair<String, String> key = keystore.getKeyAliasPasswords().get(0); interceptor.setSecurementUsername(key.getLeft()); interceptor.setSecurementPassword(key.getRight()); interceptor.setSecurementSignatureAlgorithm("http://www.w3.org/2000/09/xmldsig#rsa-sha1"); interceptor.setSecurementSignatureDigestAlgorithm("http://www.w3.org/2000/09/xmldsig#sha1"); interceptor.setSecurementTimeToLive(700); interceptor.setValidationTimeToLive(700); interceptor.setSecurementSignatureCrypto(keystoreCrypto); // Incomming interceptor.setValidationActions("Timestamp Signature"); interceptor.setValidationSignatureCrypto(truststoreCrypto); return interceptor; }
On line 6 and 7 we add the custom interceptor to the list of interceptors used by the ForwardingClient. We've also added the LoggingInterceptor on the outbound so we can see the secured messages going out and coming in. To test the message security configuration deploy the wsproxy and use soap-ui to fire the request. The soap-ui setup is no different then setup for the non-secured endpoint.
Important:There seems to be an issue with C14N. When the request is sent as normal, WSIT will complain that the calculated digest does not match with the one in the message. I'm going to investigate this further, but this appears to be a problem of WSIT and not WSS4J, since the same problem also happens when soap-ui is configured as a secured client and directly communicates with the endpoint rather then using the wsproxy module. To get around this and see the test working, remove the line feed between the soap Body start element and the payload root start element. Also remove the line feed between the soap Body end element and the payload root end element:
<soapenv:Envelope xmlns:soapenv="http://schemas.xmlsoap.org/soap/envelope/" xmlns:wsp="http://wsproxy.error.be/"> <soapenv:Header/> <soapenv:Body><wsp:getCurrentDateSecured> <!--Optional:--> <arg0>?</arg0> </wsp:getCurrentDateSecured></soapenv:Body> </soapenv:Envelope>
The soap-ui projects are also availale in the project if you want. Don't forget to enable the proxy settings as explained before, they are not saved as part of the project.
The result:
<S:Envelope xmlns:S="http://schemas.xmlsoap.org/soap/envelope/" xmlns:ds="http://www.w3.org/2000/09/xmldsig#" xmlns:exc14n="http://www.w3.org/2001/10/xml-exc-c14n#" xmlns:wsse="http://docs.oasis-open.org/wss/2004/01/oasis-200401-wss-wssecurity-secext-1.0.xsd" xmlns:wsu="http://docs.oasis-open.org/wss/2004/01/oasis-200401-wss-wssecurity-utility-1.0.xsd" xmlns:xs="http://www.w3.org/2001/XMLSchema"> <S:Header/> <S:Body wsu:Id="_5002"> <ns2:getCurrentDateSecuredResponse xmlns:ns2="http://wsproxy.error.be/"> <return>2013-10-29T14:26:25.789+01:00</return> </ns2:getCurrentDateSecuredResponse> </S:Body> </S:Envelope>
Nothing spectacular as the wsproxy added message security when forwarding the request and removed it when returning the response. If we look at the wsproxy log files, we'll first see the request entering on the inboud side:
34 [http-bio-8080-exec-3] DEBUG be.error.wsproxy.interceptors.logging.LoggingInterceptor - SID:{http://wsproxy.error.be/}getCurrentDate INBOUND SIDE Request:<?xml version="1.0" encoding="UTF-8" standalone="no"?> <soapenv:Envelope xmlns:soapenv="http://schemas.xmlsoap.org/soap/envelope/" xmlns:wsp="http://wsproxy.error.be/"> <soapenv:Header/> <soapenv:Body> <wsp:getCurrentDateSecured> <!--Optional:--> <arg0>?</arg0> </wsp:getCurrentDateSecured> </soapenv:Body> </soapenv:Envelope>
The request is secured and forward to the endpoint:
394 [http-bio-8080-exec-3] DEBUG be.error.wsproxy.interceptors.logging.LoggingInterceptor - SID:{http://wsproxy.error.be/}getCurrentDate OUTBOUND SIDE Request:<?xml version="1.0" encoding="UTF-8" standalone="no"?> <soapenv:Envelope xmlns:soapenv="http://schemas.xmlsoap.org/soap/envelope/" xmlns:wsp="http://wsproxy.error.be/"> <soapenv:Header> <wsse:Security xmlns:wsse="http://docs.oasis-open.org/wss/2004/01/oasis-200401-wss-wssecurity-secext-1.0.xsd" xmlns:wsu="http://docs.oasis-open.org/wss/2004/01/oasis-200401-wss-wssecurity-utility-1.0.xsd" soapenv:mustUnderstand="1"> <wsu:Timestamp wsu:Id="TS-518848887F924441AB13830540361321"> <wsu:Created>2013-10-29T13:40:36.130Z</wsu:Created> <wsu:Expires>2013-10-29T13:45:36.130Z</wsu:Expires> </wsu:Timestamp> <ds:Signature xmlns:ds="http://www.w3.org/2000/09/xmldsig#" Id="SIG-518848887F924441AB13830540361916"> <ds:SignedInfo> ...
The secured response is received from the endpoint;
524 [http-bio-8080-exec-3] DEBUG be.error.wsproxy.interceptors.logging.LoggingInterceptor - SID:{http://wsproxy.error.be/}getCurrentDate OUTBOUND SIDE Response:<?xml version="1.0" encoding="UTF-8" standalone="no"?> <S:Envelope xmlns:S="http://schemas.xmlsoap.org/soap/envelope/" xmlns:ds="http://www.w3.org/2000/09/xmldsig#" xmlns:exc14n="http://www.w3.org/2001/10/xml-exc-c14n#" xmlns:wsse="http://docs.oasis-open.org/wss/2004/01/oasis-200401-wss-wssecurity-secext-1.0.xsd" xmlns:wsu="http://docs.oasis-open.org/wss/2004/01/oasis-200401-wss-wssecurity-utility-1.0.xsd" xmlns:xs="http://www.w3.org/2001/XMLSchema"> <S:Header> <wsse:Security S:mustUnderstand="1"> <wsu:Timestamp xmlns:ns15="http://www.w3.org/2003/05/soap-envelope" xmlns:ns16="http://docs.oasis-open.org/ws-sx/ws-secureconversation/200512" wsu:Id="_3"> <wsu:Created>2013-10-29T13:40:36Z</wsu:Created> <wsu:Expires>2013-10-29T13:45:36Z</wsu:Expires> </wsu:Timestamp> <ds:Signature xmlns:ns15="http://www.w3.org/2003/05/soap-envelope" xmlns:ns16="http://docs.oasis-open.org/ws-sx/ws-secureconversation/200512" Id="_1"> <ds:SignedInfo> ...
Security information is processed and validated. If ok, the security information is stripped and the response returned (to our client, soap-ui in this case):
567 [http-bio-8080-exec-3] DEBUG be.error.wsproxy.interceptors.logging.LoggingInterceptor - SID:{http://wsproxy.error.be/}getCurrentDate INBOUND SIDE Response:<?xml version="1.0" encoding="UTF-8" standalone="no"?> <S:Envelope xmlns:S="http://schemas.xmlsoap.org/soap/envelope/" xmlns:ds="http://www.w3.org/2000/09/xmldsig#" xmlns:exc14n="http://www.w3.org/2001/10/xml-exc-c14n#" xmlns:wsse="http://docs.oasis-open.org/wss/2004/01/oasis-200401-wss-wssecurity-secext-1.0.xsd" xmlns:wsu="http://docs.oasis-open.org/wss/2004/01/oasis-200401-wss-wssecurity-utility-1.0.xsd" xmlns:xs="http://www.w3.org/2001/XMLSchema"> <S:Header/> <S:Body wsu:Id="_5002"> <ns2:getCurrentDateSecuredResponse xmlns:ns2="http://wsproxy.error.be/"> <return>2013-10-29T14:40:36.357+01:00</return> </ns2:getCurrentDateSecuredResponse> </S:Body> </S:Envelope>
Until now all tests have been done simulating an internal client accessing an external service. In case you want to use the module to do the inverse; serving external clients accessing internally hosted services, it is more of the same. For each internally hosted service to which the module will forward you would have to register a target URL using the endpoint.target.url.mapping configuration parameter. Interceptors continue working the same way, but remember that for example for message security you probably want the Wss4jSecurityInterceptor to be configured on the inbound side, as in this scenario the inbound side is the external facing side. There is no issue in configuring the Wss4jSecurityInterceptor on both inbound and outbound side for different service; all configuration is based on a per service basis.
For example: service x (identified by namespace and payload root element) is an internal hosted service. Service y is an external service which internal clients want to access. For securing our internal service x we would be adding Wss4jSecurityInterceptor as service specific inbound interceptor in the InboundInterceptors configuration. This interceptor will thus only be active on the wsproxy endpoint (only serving the inbound side, in this example the external facing side) and only for service x. For securing the calls to service y, we would register Wss4jSecurityInterceptor in OutboundInterceptors, adding message security for messages being sent to the external service y by the wsproxy module.
Ok, that's about it! Feel free to drop me a message if this was somehow useful or if you have ideas for improvement!


text:
IO::Dir - supply object methods for directory handles
use IO::Dir;
my $d = IO::Dir->new(".");
if (defined $d) {
while (defined($_ = $d->read)) { something($_); }
while (defined($_ = $d->read)) { something_else($_); }
undef $d;
tie my %dir, 'IO::Dir', ".";
foreach (keys %dir) {
print $_, " " , $dir{$_}->size,"\n";
The IO::Dir
package provides two interfaces to perl's directory reading routines.
The first interface is an object approach. IO::Dir
provides an object constructor and methods, which are just wrappers around perl's built in directory reading routines.
is the constructor for IO::Dir
objects. It accepts one optional argument which, if given, new
will pass to open
The following methods are wrappers for the directory related functions built into perl (the trailing 'dir' has been removed from the names). See perlfunc for details of these functions.
also provides an interface to reading directories via a tied hash. The tied hash extends the interface beyond just the directory reading routines by the use of lstat
, from the File::stat
package, unlink
, rmdir
and utime
The keys of the hash will be the names of the entries in the directory. Reading a value from the hash will be the result of calling File::stat::lstat
. Deleting an element from the hash will delete the corresponding file or subdirectory, provided that DIR_UNLINK
is included in the OPTIONS
Assigning to an entry in the hash will cause the time stamps of the file to be modified. If the file does not exist then it will be created. Assigning a single integer to a hash element will cause both the access and modification times to be changed to that value. Alternatively a reference to an array of two values can be passed. The first array element will be used to set the access time and the second element will be used to set the modification time.
Graham Barr. Currently maintained by the Perl Porters. Please report all bugs at https://github.com/Perl/perl5/issues.
Copyright (c) 1997-2003 Graham Barr <firstname.lastname@example.com>. All rights reserved. This program is free software; you can redistribute it and/or modify it under the same terms as Perl itself.


text:
Welcome to the August Carnival of Natural Parenting: Creating With Kids
This post was written for inclusion in the monthly Carnival of Natural Parenting hosted by Hobo Mama and Code Name: Mama. This month our participants have shared how they make messes and masterpieces with children. Please read to the end to find a list of links to the other carnival participants.
How to build a butterfly house in 11 easy steps
One day Mikko was charming the socks off a Home Depot worker, who gifted him with a child-size apron, workshop pin, and butterfly house kit. She asked me if he were five years old — he was, I believe, two at the time — but then said he could have the kit anyway.
So we put it away, but not till he was five. Earlier this year, I got all ambitious and decided: We were making a butterfly house, dang it!
This is a good summery project for you and your little ones. Just be sure to follow all the steps precisely.
Step 1: Read the instructions.
Step 2: Sand the wood.
Step 3: Insert an unrelated hex screwdriver into the nail hole and crank it.
Step 4: Use hammer to pound in nails.
Step 5: Put philips-head screwdriver in nail hole and spin.
Step 6: Use needle-nose pliers on nails to do … something.
Step 7: Continue using screwdriver while someone else applies wood glue.
Step 8: Insert rope through the slits.
Step 9: Perform some sort of woodworking magic involving a wrench and rope and hex driver.
Step 10: Voila! It's done! Time to decorate.
Step 11: Wait for warm weather, and then insert sliced bananas. (Do not reverse the order.)
With heartfelt appreciation to Sam for picking out the photos and helping with captions.
Now, presuming you actually do want to make a butterfly house and don't have a conveniently gifted kit, here are the basics, yo:
- Get some thin wood. Plywood or scraps should do nicely.
- The sides are shaped like a rectangle with a right-angle triangle on top. The back is a tall rectangle, the front a shorter rectangle. They all fit together like the picture, see? The bottom is a square that fits flush with the other pieces. The roof is a rectangle that overlaps the opening a little on all sides.
- Cut long, thin slits in the front piece. This is how butterflies get in. I'm hope they remember to fold their wings before they leave or they'll think they're stuck. Butterflies are probably pretty dumb.
- Sand the wood. (Mikko got one step right.)
- Use wood glue and then short nails to attach the side pieces to the back.
- Do the same to attach the front piece.
- Do the same to attach the bottom.
- For the roof, hammer one nail into the back center. It should then swivel so you can open and close the top.
- Put in some twigs and leaves or moss, along with a few pieces of ripe (or overripe) fruit. Hang it up, and wait for butterfly visitors!
(Not actually from our butterfly house.)
Visit Hobo Mama and Code Name: Mama to find out how you can participate in the next Carnival of Natural Parenting!
Please take time to read the submissions by the other carnival participants:
- Family Draw Time Art Show — Kate Wicker shares art (and inspiration!) from her family's cherished tradition of family draw time.
- The Rules of Creativity: Learning to Create with the "Non-Creative" — Zoe at Give an Earthly shares how she learned to accept her "non-creative" child and claims that anyone, child or adult, can be creative given the right handling and environment.
- Creating With Kids: 4 Ways That Work For Us — See how Kristin at Intrepid Murmurings nurtures creativity with her kids through craft projects, outdoor creative play, celebrating the creative process, and setting up "little spaces of beauty."
- Creating memories, not things — Mrs. Green from Little Green Blog reflects on life with a ten year old and how 'creating together' has evolved from 'things' to memories.
- The Gift of Creation — It may be hot, but Kellie at Our Mindful Life is already thinking about winter.
- Hidden Talents — Sylvia at MaMammalia describes how providing the opportunity for creativity sometimes means learning to look for hidden talents in unusual places.
- Creating Joy — CatholicMommy at Working to be Worthy shares how she and her one year-old son create joy for their community.
- How to do Crafts with Kids — Gaby from Tmuffin guest posts at Natural Parents Network and describes how to keep things simple when doing crafts with kids for magical (easy-to-clean, and tantrum-free) results.
- Sugar & Spice & Baking on the Kitchen Floor — Carrie at Love Notes Mama enjoys making a mess in the kitchen with her daughter.
- Young Scientist Makes Purple Potion — Hannah at Wild Parenting loves being a lab assistant for the young scientist in her life.
- Making a butterfly house — Lauren at Hobo Mama demonstrates the proper way to build a wooden butterfly house with a preschooler.
- Nurturing Creativity — Amyables at Toddler In Tow shares the enjoyment she feels in nurturing the creativity of her children.
- Home School Music - Sparking A New Generation Of Musicians — Based on her musical background, Chante at My Natural Motherhood Journey talks about how she creates with and teaches music to her children.
- Creating (im)perfectly Together — Mudpiemama shares some of the highlights of a summer spent building everything from ships to hoops but most of a lesson on letting go of perfection.
- Family Soccer Kick Around — When her children wanted to play soccer, Mandy at Living Peacefully with Children helped organize something that would work for her family.
- Creating Memories Together on Skype — Deb Chitwood at Living Montessori Now tells how you can create memories online with adult children or anyone who lives in another city or country.
- We'll always have Halloween: Creating costumes for kids — Jessica Claire at Crunchy-Chewy Mama is not the craftiest mom on the block, but she does make a mean homemade Halloween costume.
- Let's Make Juice! — Wendylori at High Needs Attachment shares about the benefits of juicing with kids, as well as a quick recipe.
- Everything's Better When It's Homemade — Amanda at Let's Take the Metro praises the art of homemade goods.
- Creating the Opportunity for Art — Jenn at Monkey Butt Junction shares how her family has created an environment conducive to art.
- 10 Easy and Functional Crafts Preschoolers Can Do with Minimal Assistance — Dionna at Code Name: Mama offers ten easy crafts preschoolers can do while sitting near parents — but they don't need a lot of parental help. Added bonus: all of these ten ideas double as something functional (gifts, decor, educational).
- Creating with Kids: Singing Together — Ana at Pandamoly details the important role music takes in her household and provides a quick (and easy!) tutorial for creating fun songs to sing together!
- Create This — jessica at instead of institutions considers different aspects of creativity including those without an end product.
- Make Your Own Pocket Bib — A tutorial from Amy at Anktangle on how to make two simple and quick bibs to keep your little one clean at the table.
- Creating Together in the Kitchen — Despite not feeling "crafty," Momma Jorje finds a way to create and connect with her toddler.
- An Artist-Mama's Perspective — In this post, Shannon at The Artful Mama discusses the differences between her choice of artistic outlet and her son's, and how they embrace those differences together.
- Heart of the Home — Jona at Life, Intertwined shares some highlights of cooking with kids.
- Getting creative with kids — Isil at Smiling like Sunshine shares how much she enjoys watching her daughter getting creative.
- Creating with Children - The Nature/Seasonal Table — Jennifer at Hybrid Rasta Mama celebrates the rhythm of the natural world with her toddler through the creation of a seasonal nature table.
- How Involving My Kid Saves My Sanity — The Happy Hippie Homemaker explains how involving her toddler in projects allows her to get more done, while providing valuable opportunities to teach and to bond (added bonus: amazing oatmeal raisin cookie recipe!).
- In the Kitchen with Kids — Cooking with Real and Pretend Food — Terri from Child of the Nature Isle engages her kids in the kitchen with culinary creations of both real and pretend food.


text:
Select a shipping country for a quote:::
At gifts.ie, your satisfaction is guaranteed. We have been shipping gifts for over 15 years in Ireland. Click on the below for independent feedback from some of our customers.
A beautiful gift for any new baby boy that will look fantastic in his new nursury! The print contains Baby's date of birth, full name, time of birth, weight and place of birth.
The personalised vibrant print is then presented in a wooden frame (Black or White) with a clear perspex cover.
Print Size: A3 (297 x 420 mm), Frame Size: 335mm x 447mm x 15mm.


text:
The S&L Catalog
For more than 40 years, Pivot Interiors – which specializes in office furniture services – has been creating environments that inspire innovation, foster collaboration and increase productivity. Its workspace designs feature leading-edge products that make use of unique textures and a wide variety of materials specifically designed for busy offices. At its new showroom in Santa Clara Pivot utilizes advanced technologies to convey the company's brand and values, showcase these memorable projects, help clients plan their office spaces, train Pivot employees, and engage visitors and showcase the company's capabilities and projects.
Working with partners, Gensler and Collaboration Solutions, Pivot selected four Planar Systems display products for the new showroom. These products are the Clarity® Matrix™ LCD Video Wall System, Planar® Mosaic™ Architectural Video Wall, Planar® UltraRes™ Series 4K LCD displays, and Planar® PS Series HD LCD displays.
"Planar was the obvious choice because all these displays are designed to integrate well with any environment. They give Pivot's showroom a really unique experiential feel whether you're viewing them in the main reception area, in any of the conference or training rooms or in other areas," says Jeremy Short, CEO of Collaboration Solutions.
Planar products at work throughout
In what Pivot calls the plaza area of the showroom – which is the central focus of the showroom space – a four wide by two high (4x2) video wall has been installed. It is comprised of eight 46-inch Clarity Matrix LCD displays (LXHD46), creating a video wall nearly 100 square feet in size. The video wall is used to welcome clients and visitors, and also as a platform for client meetings and for Pivot's after-hours entertainment and events. During business-day usage, the video wall hosts Pivot presentations to clients, including live video conferences with other Pivot offices. After business hours, the video wall supports all-hands presentations for employees, videos and other entertainment; and similar content for outside visitors and organizations which rent the space for their own meetings and events.
Behind the reception area is Pivot's main conference room, where more in-depth and private client and company meetings take place. Here, the primary Planar technology consists of two 84-inch Planar UltraRes Touch displays set flush into a prominent wall, but separated from each other by about 10 inches to accommodate a video conferencing camera. Displayed content includes live a calendar of scheduled meetings, PC-resident presentations and a wide variety of information Pivot and clients share about projects, including floorplans, renderings, products and materials for projects. The interactive touch capability is used to initiate a meeting, kick-off a video conference or enable presenters to call up details, products or other information pertinent to a client's project.
Two other important areas include the Pivot training room and a library. The training room is a large space designed to accommodate company meetings and training sessions using two 98-inch Planar UltraRes Touch displays for "white boarding" presentations with employees, showing training videos and conducting video conferencing meetings with employees at other locations. The library is a less formal area where employees can use a 55-inch interactive Planar PS Series HD LCD display (PS5561T) to share client presentations or access websites to review new products, materials and textures that may be considered for clients' office projects.
Finally, in one other area, a Planar Mosaic Architectural Video Wall has been installed to continue the aesthetic style that has been set throughout the showroom. The Planar Mosaic video wall consists of six 22-inch square tiles (Planar® Salvador™ AD22) abutting two 55-inch rectangular tiles (Planar® Vincent™ AD55).
"The technology of Planar's displays is important because they work so well," says Ken Baugh, CEO of Pivot. "But equally important is their aesthetic; they look great to us, the architects we work with and our clients. Also you can design the displays to work the way your space works; as such, Planar has given us great flexibility."
Features, capabilities leading to Planar selection
Planar display technology was selected both for aesthetic and performance reasons. Aesthetics are important given that the showroom is brand new and Pivot wanted displays that are sleek, clean and bright, and look like they were specifically designed to integrate with the space — an important requirement since many visitors include client designers and architects. All of the Planar displays accommodate this requirement by virtue of their ultra-slim profiles, small bezels, and small tiled bezel widths. In the case of Planar Mosaic, tiles can be mounted in virtually any arrangement to achieve any desired visual or architectural effect.
"All of the Planar technology delivers an excellent cost of ownership and ease of maintenance; plus, Planar paid lots of attention to the details. They are absolutely a great partner for us," says Pivot's Ken Baugh.


text:
Robichaud, Schroepfer & Correia, P.A.
Car Collision Attorney in Duluth
Ask a Question,
Describe Your Situation,
Request a Consultation
Call (612) 333-3343 or fill out the short form below. We will usually respond within 1 business day but often do so the same day. Don't hesitate, your questions are welcome.
Why Choose Us
Our team of attorneys have the knowledge and experience to ensure that your rights are protected and you get the compensation you deserve. And with decades of experience, we pride ourselves on the personal service and individual attention we provide to each of our clients. We're here every step of the way.
How Does It Work
- Following a car accident, the most important step you can take is to contact an experienced Car Collision Attorney in Duluth.
- After reviewing the details and devising an effective strategy, we will take immediate action on your case.
- We will handle all communications with the insurance companies, evaluate any police reports, talk to witnesses, etc.
- Throughout each step of this intricate legal process, we will operate with your best interest in mind.
Schedule a Consultation Today
"Don't waste time with anyone else. If you seek justice for your legal issue, call RSC Law!"
Reviews - Robichaud, Schroepfer & Correia, P.A., Duluth
Following a car accident, the legal forms will quickly pile up, along with never-ending medical bills. In addition to your physical and emotional pain, you may also suffer lost wages. The reality of the matter is that you cannot tackle this immense challenge alone. It is imperative that you contact our experienced Car Collision Attorney in Duluth. Call us today to take advantage of your free consultation.
How To Get Started
- The first and most important step is to call us today and schedule your free consultation.
- During the initial consultation, one of our experienced attorneys will review the details of your case.
- We will discuss all of your legal options, and devise an effective strategy.
- We will fight relentlessly on your behalf, so that you can focus on your recovery.
News & Resources
RSC Law Announces the Hiring of an Experienced Immigration Attorney
MINNEAPOLIS, Minnesota—RSC Law proudly announces the hiring of Associate Attorney Evangeline Dhawan-Maloney. Evangeline brings a…
RSC Law Announces Super Lawyers Selections for Two Attorneys
MINNEAPOLIS, Minnesota—RSC Law proudly announces that attorneys Paul Schroepfer and Robert Correia have been selected…
Personal Injury Attorney Robert A. Correia Named Attorney of the Year
MINNEAPOLIS, Minnesota—Robert A. Correia, Shareholder and Lead Attorney of Robichaud, Schroepfer & Correia, P.A., has…


text:
Psalm text (Ps 19:8, 9, 10, 11)
Lord, You have the words of everlasting lifeorYour words, O Lord, are spirit and life.
The law of the Lord is perfect,refreshing the soul;the decree of the Lord is trustworthy,giving wisdom to the simple.
The precepts of the Lord are right,rejoicing the heart;the command of the Lord is clear,enlightening the eye.
The fear of the Lord is pure,enduring forever.the ordinances of the Lord are true,all of them just.
They are more precious than gold,than a heap of purest gold;sweeter also than syrupor honey from the comb.
By Joel Stein
By Aaron Thompson
The English translation of the Psalm Response(s) and Gospel verse(s) from Lectionary for Mass © 1969, 1981, 1997, International Committee on English in the Liturgy, Inc. All rights reserved.


text:
"For all those who came in late..." - Lee Falk
This thread is to announce the various Demonstrations and other non-convention Activities I will be hosting unlike the previous threads this one doesn't have a date attached and I'll use it till I get back to a regular schedule.
Not only is this thread for announcing anything I am running but if you need to get in touch with ne here is a great place, on top of that if anyone else wants to run an (Anima Tactics) event in Australia and would like to post their day here, feel free.
Location of Demonstrations:
Mind Games, Melbourne,. 244 Swanston Street in the heart of the CBD, Victoria, Australia.
For specific information post questions here or email: [email protected]
- Raith