Display Settings:

Format

Send to:

Choose Destination
See comment in PubMed Commons below
Proc Natl Acad Sci U S A. 2003 Jun 24;100(13):8024-9. Epub 2003 Jun 3.

Physical interaction between RRS1-R, a protein conferring resistance to bacterial wilt, and PopP2, a type III effector targeted to the plant nucleus.

Author information

  • 1Max-Planck-Institut für Züchtungsforschung, Abteilung Biochemie, Carl-von-Linne-Weg 10, D-50829 Cologne, Germany. Ldesland@mpiz-koeln.mpg.de

Abstract

RRS1-R confers broad-spectrum resistance to several strains of the causal agent of bacterial wilt, Ralstonia solanacearum. Although genetically defined as recessive, this R gene encodes a protein whose structure combines the TIR-NBS-LRR domains found in several R proteins and a WRKY motif characteristic of some plant transcriptional factors and behaves as a dominant gene in transgenic susceptible plants. Here we show that PopP2, a R. solanacearum type III effector, which belongs to the YopJ/AvrRxv protein family, is the avirulence protein recognized by RRS1-R. Furthermore, an interaction between PopP2 and both RRS1-R and RRS1-S, present in the resistant Nd-1 and susceptible Col-5 Arabidopsis thaliana ecotypes, respectively, was detected by using the yeast split-ubiquitin two-hybrid system. This interaction, which required the full-length R protein, was not observed between the RRS1 proteins and PopP1, another member of the YopJ/AvrRxv family present in strain GMI1000 and that confers avirulence in Petunia. We further demonstrate that both the Avr protein and the RRS1 proteins colocalize in the nucleus and that the nuclear localization of the RRS1 proteins are dependent on the presence of PopP2.

PMID:
12788974
[PubMed - indexed for MEDLINE]
PMCID:
PMC164706
Free PMC Article

Images from this publication.See all images (4)Free text

Fig. 1.
Fig. 2.
Fig. 3.
Fig. 4.
PubMed Commons home

PubMed Commons

0 comments
How to join PubMed Commons

    Supplemental Content

    Full text links

    Icon for HighWire Icon for PubMed Central
    Loading ...
    Write to the Help Desk